Solution : https://service.sap.com/sap/support/notes/25526 (SAP Service marketplace login required)
Summary :
The issue occurs when the central system log cannot be displayed in environments like Windows NT, where it's unavailable, or AS/400, where it's accessible only from Release 6.40 onwards. For systems where central logging isn't implemented, users can access logs via SM21 or manage through individual server system logs. On UNIX systems, ensure the collector daemon 'rslgcoll' and sender daemon 'rslgsend' are operational as processes, started via the start profile of each instance. Proper configuration of 'rslg/' parameters, as detailed in the documentation, is crucial. Check that the correct port settings are maintained across all instances to avoid conflicts and ensure logs are visible and written correctly.
Key words :
parameters rslg/send_daemon/listen_port rslg/send_daemon/talk_port, rslg/send_daemon/listen_port 1201 rslg/send_daemon/talk_port 1301, rslg/send_daemon/listen_port 1202 rslg/send_daemon/talk_port 1302, /usr/sap/sid/sys/global, system parameter 'rslg/max_diskspace/central', computing center management system, rslg/send_daemon/listen_port, rslg/send_daemon/talk_port, start profile start_<instance>, select system log -> choose ->
Related Notes :
| 1154448 | SAP on HP-UX: Instance number limitations on HP-UX |
| 505545 | DB2/390: stopsap slow with Linux for zSeries applic. server |
| 40003 | rslgsend(002): Address already in use |
| 15291 | SysLog daemons terminate immediately |
| 6515 | rslgcoll(7): bind: Address already in use |
| 2448 | Collector daemon does not start |
| 1725 | SM21: central SysLog cannot be opened |