Technical data
12.3.1 Console Notification Does Not Work
If you do not receive any notification messages on the console, or if mail
notification messages are not being sent, determine if the console notification
daemon,
pdconntf, is running by performing the following steps:
1. Determine if the daemon is running:
# ps aux | grep pdconntf
2. If it is not running, try running it from a terminal window:
# /usr/pd/lib/pdconntf
12.3.2 Locating System Error Information
When an error occurs, Advanced Printing Software components report
information by way of:
E-mail from failed server startup
Events, sent as e-mail or console notification
Client messages
System log (syslog)
/var/pd/startup/shutdown CAA log files
• E-mail–The spooler and supervisor executables support an option
that sends e-mail to a designated administrator, when a startup error
occurs. See pdsplr, pdspvr, and pdspvlpr reference pages for more
information.
• Events–When spooler and supervisor processes are properly running,
they can issue events in the form of e-mail messages or console message
notification. The events can report normal activities, such as jobs
completing and printers changing state, or report problems associated
with specific printers, queues, jobs, and servers.
• Client messages–Client programs, such as pdpr, pdls, and pdrm, do not
normally display messages unless a problem occurs while processing the
command. However, the message might not be sufficient to correct the
problem. Additional information can be found in the client machine’s
system logs in /var/adm/syslog.dated/current/lpr.log.To
inspect the log files, you need root access. If you have access to the server
host, you can find information logged in lpr.log on that host.
• syslog–To control the number and severity of messages in
/var/adm/syslog.dated/current/lpr.log set the priority value
associated with lpr in the /etc/syslog.conf file. Hewlett-Packard
Company recommends the setting, lpr.info. See syslog for more
information on how to control the contents of the syslog files.
Troubleshooting 12–5