Ansicht
Dokumentation
No SYSLOG entries are being written
Tip-No.: 506
( INFO506 )
Fill RESBD Structure from EBP Component Structure
Vendor Master (General Section)
This documentation is copyright by SAP AG.
Short text
No SYSLOG entries are being written
Tip-No.: 506
Symptom
No SYSLOG entries are written, even though errors are clearly occurring.
Cause
Installation error or problem in the SAP kernel.
Solution
What was output after 'stderr'. If English error messages of the
following type appeared:
rslgwr1: Cannot open SysLog-file..... or
/usr/sap/etc52/SLOG: ....
Then the reason is given in the message. Otherwise it's guesswork....
Following are possible reasons:
a) The SAPPARAM paramter 'rslg/local/file' is incorrect
--> correct it.
b) The file is there, but write-protected.
This cannot really happen, although it has been observed in connect-
ion with poor disk organization.
--> chmod 666 ...
c) The directory is missing or is protected
--> (a) or installtions error
d) The program that wanted to write has already opened too many files
(too many open file descriptors).
This would be a problem in the SAP kernel (easily caused) - must be
checked and remedied. Procedure: use following to test with:
SAPPARAM rdisp/TRACE = 0 and examine SYSLOG
SAPPARAM rdisp/TRACE = 2 and examine the 'dev' files.
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up ROGBILLS - Synchronize billing plans
This documentation is copyright by SAP AG.
Length: 1393 Date: 20240425 Time: 090343 sap01-206 ( 16 ms )
