The SysLog transmission program 'rslgsend' terminates immediately after the system starts. ('rslgsend' is usually renamed se.sap....)
The corresponding 'stderr' file contains:
rslgsend(53) (...): Assertion failed
As the program termination is hard, there will be the following additional message during the next system start:
rslgmcc(71) .rslgsm1_write_pid_file.kill(,0) ... no such process
The file number is missing in the local syslog file.
The SysLog software assumes that one of the first ten records of the local SysLog file contains the file number. If not, a later synchronization will be difficult. For this reason, these incorrect files are not processed by automatic programs.
How can the error occur?
So far, only one way is known: The local SysLog file is deleted but the Shared Memory segment 'SCSA' is not deleted at the same time.
Run report 'RSLG0020'.
This report makes an analysis during the first run. If the report finds something, there are proposals at the end of the list which can be executed by double-clicking.
Additional key words
rslgsmcc(071)
No comments:
Post a Comment