Solution : https://service.sap.com/sap/support/notes/2448 (SAP Service marketplace login required)
Summary :
SAP Note discusses the issue where the SysLog collector daemon "rslgcoll" terminates unexpectedly due to a corrupted central SysLog file, potentially caused by a disk space issue during a write operation. The solution involves checking the file’s length as per system release guidelines (152 bytes per record for Release 2.0A on UNIX, 180 bytes per record for Release 4.0A). Two resolution paths are provided: using transaction SM21 to analyze and potentially repair the SysLog via the program 'RSLG0019', or extending the SysLog manually at the UNIX level to balance the file length, or ultimately deleting the corrupt file. Restarting R/3 should resolve the daemon's operation issue.
Key words :
'12345' >> syslog file orecho '12345\c' >> syslog file, syslogthe syslog collector daemon, syslog collector daemon 'rslgcoll', prerequisites central syslog file, rslg/central/file, symptom key word, additional key words, repair program 'rslg0019', central syslog, file results
Related Notes :
| 25526 | Central system log not available |