When attempting to review the Anti-Malware Daemon (AMD) logs on a Symantec Endpoint Protection (SEP) Linux agent, the file /var/log/sdcsslog/amdlog/sisamd_0.log is missing from the directory. This article explains the scenarios in which this log file may be absent, deleted, or rotated.
SEP 14.3 RU1 and later Linux agents
The creation, rotation, and deletion of sisamd_*.log files are governed by the settings within the Anti-Malware Daemon configuration files.
Configuration File Paths
The parameters controlling log behavior are located in:
Log Rotation Parameters
The following settings in the .ini files define the size thresholds for the logs:
| Parameter | Default Value | Description |
| amdmanagement.log.rotate.size | 10 (MB) | The maximum size a single log file reaches before rotation occurs. |
| amdmanagement.logs.max.size | 100 (MB) | The maximum cumulative size allowed for all sisamd logs in the directory. |
Log Rotation Logic
The SEP Linux agent manages logs through a sequential rotation process:
Service Restart Behavior
Note that whenever the sisamdagent service is restarted, the logging process resets. The agent will immediately begin writing new entries to sisamd_0.log, regardless of the previous state of the log files.