Troubleshooting

The following log files can be used to troubleshoot the ESMC Virtual Appliance. Also, you may be asked by ESET technical support to provide diagnostic logs. These are the log files you can send for analysis:

Log name

Location

Description

ESMC VA configuration

/root/appliance-configuration-log.txt

If your ESMC VA deployment fails, do not restart the appliance and check configuration log file.

ESMC Server

/var/log/eset/RemoteAdministrator/EraServerInstaller.log

/var/log/eset/RogueDetectionSensor/RDSensorInstaller.log

ESMC Server installation log file.

Other ESMC components use a similar path and corresponding file name.

ESMC Server trace log

ESET Management Agent trace log

/var/log/eset/RemoteAdministrator/Server/

/var/log/eset/RemoteAdministrator/Agent/

Check your trace logs:
trace.log

status.html

last-error.html

Other ESMC components use similar path and file names.

Apache HTTP Proxy

/opt/apache/logs/

/var/log/httpd

log file for older versions of ESMC Virtual Appliance

log file for newer versions of ESMC Virtual Appliance

ESMC Server crash dumps

/var/opt/eset/RemoteAdministrator/Server/Dumps/

 

ESMC Server or ESET Management Agent run diagnostic tool

/root/RemoteAdministratorAgentDiagnostic.zip

If you experience issues with your ESMC VA, you can Run diagnostic tool, see ESET Security Management Center Webmin module for details.

If the Server or Agent are crashing and you can not change the logging verbosity via Web Console, you can enable full trace logging by creating the empty file:

For Agent:

touch /var/log/eset/RemoteAdministrator/Agent/traceAll

For Server:

touch /var/log/eset/RemoteAdministrator/Server/traceAll

 

note

Note

We recommend that you use Webmin File manager where you can easily search for files and download logs if necessary.