dev_wait

[rcbatlinux]

I had 4 printers get dev_wait today. All are in different locations on port servers. These are dot matrix printers. Normally dev_wait by my understanding is due to a problem with the device itself. I reset the printers, checked connections, and did a stopsrc -s qdaemon, fuser -k /dev/lp?, killed qdaemon processes left, then startsrc -s qdaemon and still can't get these out of dev_wait. Any ideas?

rcbatlinux

 

[PSD]

rcbat,

Can you cat to the printers?

cat /etc/hosts > /dev/lp0

I assume that they are serial attached printers?

Is there a specific job in the queue if so delete it, it may be in the wrong printing format. In my experience of this problem 9/10 it is a hardware issue on the printer and a reset sorts it out but I have also had incorrect job formats on the queue.

Hope that helps

PSD
IBM Certified Specialist - AIX V4.3 Systems Support
IBM Certified Specialist - AIX V4 HACMP

 

[aixqueen]

My two cents

the stopsrc -cg spooler
startsrc -g spooler
is much better since it starts 3 daemons not just one......
if you are doing LPD/LPR..not sure if it is local or remote?

You may have to clean the ques out since as PSD said there might be a job
out there in a bad format...
--------------------------------
WAITING or DEV_WAIT
Queue could not open and is waiting on a device. The device may be out of paper,
offline, jammed, or have wiring problems.
NEVER add, remove or change any queue when a queue on the same system is in
a DEV_WAIT state without first correcting the problem.
-----------------------------

If all 4 went down at the same time...Is it possible that the port server or whatever you are using lost the connection and could not recover? Or you have a hardware problem with the RAN or port server that is set up?
If you are talking RAN are there errors in the errpt? Are the lights on and AC...?

Clean Ques....

http://techsupport.services.ibm.com...mode=9&documents=390605199014844&database=aix

4 printers same device or RAN is suspicious...........for the device not the printers....
but you still may have to reboot if it is a RAN

 

[rcbatlinux]

I had the customer reboot their system and that seemed to solve problem. When I did a lsdev -C yesterday the printers having the problem stated their device was "defined" and not available. They use a digiport server running realport software. These printers happen to be scattered about on different servers. Strange for sure. But system reboot took care of it. thanks!

rcbatlinux

 

[crowe]

I suspect the digi went offline for whatever reason. (cable unpluged). In the future, I believe cfgmgr will correct the defined state of the digi port server. It is a little less painful than a reboot, and quicker as well.

crowe