From: Shaun.Racine@intier.com
Date: Mon Sep 15 2003 - 06:06:03 EDT
Hi Managers,
Tru64 v5.1A, patch kit 3 (T64V51AB03AS0003-20020827). ES40 / HSG80 LSM &
AdvFS.
One of our sites had a problem with printing after a reboot. The server is
scheduled to reboot at the same time each week, with no previous problems
in this area.
All printing in a queued state.
Tried to restart specific printer queues but no joy.
lpc> restart r5_cp_2
r5_cp_2:
no daemon to abort
r5_cp_2:
lpc: connect: No such file or directory
couldn't start daemon
lpc> quit
No lpd daemon running.
Ended up starting the lpd deamon manually.
root> /usr/sbin/rc3.d/S65lpd start
All printing sprung into life again and remained stable.
No errors in startup logs, typical message (and "NOTICE" when manually
started) from lpr.log;
Sep 14 19:48:34 rimmer lpd[59924]: ERROR -- startdaemon: connect failed to
socket /dev/printer, printer r5_cp_2, error: No suc
h file or directory
Sep 14 19:51:43 rimmer lpd[60121]: NOTICE -- lpd: MASTER DAEMON STARTED
Does anyone know what may have caused this? Or where to look for more
information?
TIA
Shaun
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:35 EDT