RSA ACE/Server not logging replication error messages to syslog or var/adm/messages file after applying patch 3
Originally Published: 2002-12-05
Article Number
Applies To
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 5.0.01 not logging replication error messages to syslog or var/adm/messages file after applying patch 3
Resolution
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.
Related Articles
Error: 'read_config: Could not open config file /opt/ace/data/ sdtacplus.cfg Errno 2: No such file or directory' appears … Number of Views Increase the maximum length of a reserve password hash for the RSA Authentication Agent 7.x for Windows Number of Views Formatting for syslog data sent from RSA Authentication Manager 8.x Number of Views RSA Governance & Lifecycle - App Priority v3 Number of Views Access Fulfillment Express (AFX) does start after applying Patch 11 or higher to RSA Via Lifecycle and Governance 6.9.1 Number of Views
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.9 Release Notes (January 2026) Artifacts to gather in RSA Identity Governance & Lifecycle RSA Governance & Lifecycle 8.0.0 Administrators Guide RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?
