Technical data

12.1.2 Servers Running But Nothing Works
Use the procedure in Section 12.1.1 to determine which components are
running, and which of those respond to the rpcinfo -u or -t commands. If
the protoserver does not respond, perform the following procedure to restart
the print system:
1. Verify that the /var/pd/pts directory is owned by nobody:
# ld -ld /var/pd/pts
2. Kill all pdspvr, pdsplr, and pdspvlpr processes.
# kill -9
3. Send a hangup signal to inetd process:
# kill -HUP ‘cat /var/run/inetd.pid‘
4. Try again to communicate with the protoserver daemon:
# rpcinfo -u host 105004
5. If there is no response or if rpcinfo returns either of the following
messages, “Program not registered” or “Connection refused”, stop and
restart the inetd program:
# kill -9 ‘cat /var/run/inetd.pid‘
# /usr/sbin/inetd
6. Restart the print system spooler (pdsplr) and check whether you can
now communicate with it:
# /usr/pd/lib/pdsplr servername
# pdls -c server servername
If the spooler responds, then restart the other servers similarly.
If you are using CAA in a TruCluster Server environment, use the caa_stop
and caa_start commands to stop and restart Advanced Printing resources.
For example:
# caa_stop -f apx-default
Attempting to stop ’apx-default’ on member borzoi
Stop of ’apx-default’ on member borzoi succeeded.
# caa_start apx-default
Attempting to start ’apx-default’ on member borzoi
Start of ’apx-default’ on member borzoi succeeded.
12.1.3 Supervisor Will Not Shut Down
In some instances, the pdshutdown command is not fully effective in
stopping a supervisor server. In such cases:
1. Wait at least two minutes for the supervisor to exit.
12–2 Troubleshooting