LDAP-UX Client Services B.04.15 with Microsoft Windows Active Directory Server Administrator's Guide (edition 8)

Table Of Contents
Enabling and Disabling LDAP-UX Logging
When a program or service is behaving incorrectly, enabling logging is one way to examine the
events that occur to determine where the problem is. Enable LDAP-UX Client Services logging
on a particular client as follows:
1. Edit the local startup file /etc/opt/ldapux/ldapux_client.conf and uncomment
the lines starting with #log_facility and #log_level by removing the initial # symbol.
You can set log_level to LOG_INFO to log only unusual events. If LOG_INFO is not
adequate to identify the problem, set log_level to LOG_DEBUG to log trace information.
LOG_DEBUG provides more information, but significantly reduces performance and generates
large log files on active systems.
2. Edit the file /etc/syslog.conf and add a new line at the bottom:
local0.debug <tab> /var/adm/syslog/local0.log
where <tab> is the Tab key on your keyboard.
3. Restart the syslogdaemon with the following command: (Refer to syslogd(1M) for details.)
kill -HUP 'cat /var/run/syslog.pid'
4. Once logging is enabled, run the HP-UX commands or applications that exhibit the problem.
5. Disable logging by commenting out the log_facility and log_level lines in the startup
file /etc/opt/ldapux/ldapux_client.conf. Comment them out by inserting a #
symbol in the first column.
6. Examine the log file at /var/adm/syslog/local0.log to see what actions were performed
and if any are unexpected.
TIP: Enable LDAP logging only long enough to collect the data you need because logging can
significantly reduce performance and generate large log files.
You may want to move the existing log file and start with an empty file:
mv /var/adm/syslog/local0.log /var/adm/syslog/local0.log.save
Restart the syslogdaemon with the following command: (Refer to syslogd(1M)or details.)
kill -HUP 'cat /var/run/syslog.pid'.
Enabling and Disabling PAM Logging
When something is behaving incorrectly, enabling logging is one way to examine the events that
occur to determine where the problem is. Complete the following steps to enable PAM logging
on a particular client. Refer to pam(1), pam.conf(4), and Managing Systems and Workgroups for more
information about PAM.
1. Add the debug option to each line in /etc/pam.conf that contains libpam_krb5.1. For
example:
login account sufficient /usr/lib/security/libpam_krb5.1 debug
login account required /usr/lib/security/libpam_unix.1
su account sufficient /usr/lib/security/libpam_krb5.1 debug
su account required /usr/lib/security/libpam_unix.1
...
2. Edit the file /etc/syslog.confand add a new line at the bottom similar to the following:
*.debug <tab>/var/adm/syslog/debug.log
3. Restart the syslog daemon with the following command. (Refer to syslogd(1M) for details.)
kill -HUP 'cat /var/run/syslog.pid'
146 Administering LDAP-UX Client Services