Troubleshooting for Unix based systems

Logs location

The logs can be found in the following directories:

/etc/mdss/services_logs
/var/log/mdss

Generating support package

In order to generate a support package you can run the next command:

sudo mdss -u support_package

For more advanced users we offer the following commands:

sudo mdss -u export_logs

This will allow you to save the logs of the containers

sudo mdss -u export_info

This will run some testes and gather info about your system.

sudo mdss -u export_settings

This command will save the relevant setting from your MDSS instance.

The archives will be created in /etc/mdss/

In addition, we offer the option to export your database if you need to use it for migration or debugging purposes.

sudo mdss -u export_db

Installation issues

In order to troubleshoot please run LOG_LEVEL=7 [command] where command is the command that has an issue. For example, if MetaDefender Storage Security cannot be started please run the following command:

sudo LOG_LEVEL=7 mdss -c start

Running behind a proxy

You will need to edit /etc/mdss/customer.env and add the following environment variables to use a proxy server:

HTTP_PROXY="http://proxy_ip:proxy_port" HTTPS_PROXY="https://proxy_ip:proxy_port" no_proxy=mongodb,rabbitmq,redis,mongomigrations,licensingservice,smbservice,discoveryservice,discoveryamazonsdkservice,discoveryazureblobservice,discoveryalibabacloudservice,discoverygooglecloudservice,discoveryboxservice,scanningservice,notificationservice,apigateway,webclient,jobdispatcher,securitychecklistservice,loadbalancerservice,loggingservice,terraformservice,remediationsservice,remediationsservice-amazonsdk,remediationsservice-azureblob,remediationsservice-googlecloud,remediationsservice-alibabacloud,remediationsservice-box

If a proxy is required to access to docker hub in order to pull MDSS images, then this guide should be followed: https://docs.docker.com/network/proxy/

Unable to remove the network

If you encounter some message regarding your network ( similar to network mdss_stack id xxx has active endpoints ) while you tried to remove or update MDSS, please try to restart docker:

systemctl restart docker

"Permission denied" while uninstalling

On some Linux distributions that have SELinux enabled by default you may encounter a "Permission denied" message when uninstalling MDSS. The uninstall still completes successfully and only some docker containers might still be left running if mdss -u clean was not executed before the uninstall. This is due to SELinux policies and can be avoided by disabling SELinux temporarily before uninstalling by running:

sudo setenforce 0

Last updated on

Was this page helpful?