on Jun 15, 2016Article Content
| Article Number | 000020070 |
| Applies To | RSA ACE/Server 5.0.1 (no longer supported as of 8-15-2004) RSA ACE/Server 4.1 Patch 3 (no longer supported as of 2-1-2004) UNIX (AIX, HP-UX, Solaris) Microsoft Windows 2000 |
| Issue | RSA ACE/Server not logging replication error messages to syslog or var/adm/messages file after applying patch 3 RSA ACE/Server 5.0.01 not logging replication error messages to syslog or var/adm/messages file after applying patch 3 |
| Resolution | The replication engine (acesyncd on UNIX) was logging far too much information in the Event Log/Syslog before applying patch 3. After applying patch 3, it logs only the initial connection unless the environment variable SDI_ASD_SYSLOG is defined (Defect number:24658). To get the replication errors logged in system log files, set the environment variable to the log file with a complete path. The below mentioned variable can be set as system variable on the ACE/Server. This variable enables logging replication messages on the Primary server only. On Solaris: SDI_ASD_SYSLOG =/var/adm/messages On AIX and HP-UX: SDI_ASD_SYSLOG =/path for the file/syslog On Windows NT: Start Menu -> Control Panel -> System -> Advanced -> Environment Variables -> System variable Type the name of the variable SDI_ASD_SYSLOG and value as 1. The Primary server must be rebooted before this system variable change takes effect. |
| Legacy Article ID | a14257 |