What Do I Do If a Message Indicating slogd Is Running Is Displayed but slogd Cannot be Found?
Symptom
The slogd process fails to be started, and the message "Slogd maybe is already running, please check!" is displayed.
Possible Cause
The possible cause is as follows:
The slogd.conf file does not exist in the /var/log/npu/conf/slog directory due to unknown causes. As a result, the slog.conf stored in the directory where the slogd process file is located is used. In this case, the app that is linked with libslog.so communicates with the slogd process using the shared memory (key: 0x474f4c46).
In this case, if the slogd process is stopped abnormally (for example, kill -9), the shared memory cannot be released properly, causing exception in the next slogd startup.
Solution
To rectify the fault, perform the following steps:
- Run the ipcs -m command to check whether the shared memory is occupied.
- Run the ipcrm -M 0x474f4c46 command to delete the shared memory.
- Restart slogd by referring to Log Process Startup.