Printer Issue

printer bhill-proptkt has stopped working

root@bunna: /etc> lpstat -t|grep bhill
        bhill-proptkt
device for bhill-proptkt: /dev/null
system for bhill-proptkt-hp: bunna (as printer bhill-proptkt)
system for bhill-prpjob: bunna (as printer bhill-proptkt)
system for bhill-prpbon: bunna (as printer bhill-proptkt)
bhill-proptkt accepting requests since Tue Apr 18 11:26:09 2006
bhill-proptkt-hp accepting requests since Tue Apr 18 11:26:09 2006
bhill-prpjob accepting requests since Tue Apr 18 11:26:09 2006
bhill-prpbon accepting requests since Tue Apr 18 11:26:09 2006
printer bhill-proptkt waiting for auto-retry. available.
printer bhill-proptkt-hp faulted printing bhill-proptkt-hp-52433. enabled since
Apr 13 11:00 2010. available.
        Warning: bhill-proptkt is down: exec exit fault
printer bhill-prpjob faulted printing bhill-prpjob-52433. enabled since Apr 13
1:00 2010. available.
        Warning: bhill-proptkt is down: exec exit fault
printer bhill-prpbon faulted printing bhill-prpbon-52433. enabled since Apr 13
1:00 2010. available.
        Warning: bhill-proptkt is down: exec exit fault
^Croot@bunna: /etc>

prints are being sent to printer queue ok
have stopped/started lpsched and disable/enable printer queue

any help would be welcome
jgourlayAsked:
Who is Participating?
 
jgourlayAuthor Commented:
Resolved problem by recreating printer queue using jetadmin as couldn't get lpadmin to work
0
 
hdhondtCommented:
I'm not a unix expert, but:

What model printer is this?
How is it connected? If networked, can you still ping it?
Does the printer receive anything when you try to print (as indicated by the printer's front panel display)?
0
 
jgourlayAuthor Commented:
printer is HP4100 networked printer which was working up until last weekend.
printer can be pinged.
all prints being sent can be seen queueing up in /var/spool/lp
test prints can be produced on the printer manually
test prints sent to printer by unix commands also do not print and join queue
I'm trying to get explanation of following messages but no luck so far -
      printer bhill-proptkt waiting for auto-retry. available.
      Warning: bhill-proptkt is down: exec exit fault
0
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

 
wietmanCommented:
Is it possible that the printer IP changed recently?
Can you print to any other printers defined in Unix?

0
 
jgourlayAuthor Commented:
printer ip address is correct
all other printers working ok
0
 
wietmanCommented:
I HATE printer problems!!  When I was a Unix admin, those were the problems I disliked the most.   It looks like you already bounced the LP service, so I won't suggest that.  Is there any kind of LPSCHED log you can look at?
Perhaps under /var/lp/logs or /var/lp/logs/lpNet.
0
 
AmolCommented:
1) paste the o/p of following command
lpstat -o "printername"

2) If its Solaris 10, check the printer service, if its online.

3) check /var/lp/logs if you see any error messages for above printer, paste that.
0
 
jgourlayAuthor Commented:
Sample outputs -

root@bunna: /var/lp/logs>
04/13 15:48:34: printer fault. type: write root, status: 14
msg: (exec exit fault)
04/13 15:49:14: printer fault. type: write root, status: 14
msg: (exec exit fault)
04/13 15:49:24: printer fault. type: write root, status: 14
msg: (exec exit fault)
04/13 15:49:34: printer fault. type: write root, status: 14
msg: (exec exit fault)

root@bunna: /etc> lpstat -o bhill-proptkt|more
bhill-proptkt-52442     servitor           959   Apr 12 08:05
bhill-proptkt-52443     servitor           959   Apr 12 08:05
bhill-proptkt-52445     servitor         10197   Apr 12 08:05
bhill-proptkt-52446     servitor           945   Apr 12 08:05
bhill-proptkt-52447     servitor         10197   Apr 12 08:05
bhill-proptkt-52448     servitor           945   Apr 12 08:06

root@bunna: /etc> lpstat -o bhill-proptkt-hp|more
bhill-proptkt-hp-52442 servitor@bunna      959   Apr 13 15:59
bhill-proptkt-hp-52443 servitor@bunna      959   Apr 13 15:59
bhill-proptkt-hp-52496 servitor@bunna       37   Apr 13 15:59
bhill-proptkt-hp-52508 servitor@bunna      881   Apr 13 15:59
bhill-proptkt-hp-52445 servitor@bunna    10197   Apr 13 15:59

root@bunna: /var/lp/logs> lpstat -p bhill-proptkt
printer bhill-proptkt waiting for auto-retry. available.
        exec exit fault

root@bunna: /etc> lpstat -p bhill-proptkt-hp
printer bhill-proptkt-hp faulted printing bhill-proptkt-hp-52442. enabled since
Apr 13 16:08 2010. available.
        Warning: bhill-proptkt is down: exec exit fault

root@bunna: /etc> lpstat -p bhill-proptkt
printer bhill-proptkt waiting for auto-retry. available.
        exec exit fault
root@bunna: /etc> lpstat -p bhill-proptkt-hp
printer bhill-proptkt-hp faulted printing bhill-proptkt-hp-52442. enabled since
Apr 13 16:14 2010. available.
        Warning: bhill-proptkt is down: exec exit fault
root@bunna: /etc>

root@bunna: /etc> more /etc/printers.conf|grep bhill
bhill-proptkt-hp:\
        :bsdaddr=bunna,bhill-proptkt,Solaris:
bhill-prpjob:\
        :bsdaddr=bunna,bhill-proptkt,Solaris:
bhill-prpbon:\
        :bsdaddr=bunna,bhill-proptkt,Solaris:
bhill-proptkt:\
        :bsdaddr=bunna,bhill-proptkt,Solaris:
root@bunna: /etc>

root@bunna: /etc> more /etc/hosts|grep bhill
172.16.81.12    bhill-proptkt-hp                # Broomhill Job Ticket Printing
172.16.81.12    bhill-proptkt                   # Broomhill Job Ticket Printing
root@bunna: /etc>




0
 
AmolCommented:
ok. do these steps,

1) disable bhill-proptkt
    disable bhill-proptkt-hp

2) clear the printer queue by following command,

cancel -u servitor bhill-proptkt
cancel -u servitor@bunna bhill-proptkt-hp

wait for some time to clear the queue, check nothing should be there in the queue with lpstat -o "printername"

3) enable bhill-proptkt
    enable bhill-proptkt-hp

Now ping the printer and try giving a simple test page. see if it works.
0
 
jgourlayAuthor Commented:
after doing above printer still failing as below

printer bhill-proptkt-hp faulted printing bhill-proptkt-hp-52658. enabled since
Apr 14 09:19 2010. available.
        Warning: bhill-proptkt is down: exec exit fault
printer bhill-prpjob faulted printing bhill-prpjob-52658. enabled since Apr 14 0
9:19 2010. available.
        Warning: bhill-proptkt is down: exec exit fault
printer bhill-prpbon faulted printing bhill-prpbon-52658. enabled since Apr 14 0
9:19 2010. available.
        Warning: bhill-proptkt is down: exec exit fault
0
 
hdhondtCommented:
To make sure it's not the printer itself that is the problem, try doing a cold reset on it, as follows:

Hold down the SELECT (Checkmark) button, and then turn the printer power on. Continue holding down the SELECT (Checkmark) button until all three printer control-panel lights flash once and then remain on. This might take up to 10 seconds.

After the message SELECT LANGUAGE appears on the display, press the UP ARROW button or the DOWN ARROW button until COLD RESET is highlighted.

Press the SELECT (Checkmark) button. The printer performs a cold reset and then continues its power-on sequence.

You will need to set up the IP address details after this,
0
 
AmolCommented:
shut down the printer service, go into the queue in /var/spool/lp and clear out the queued files. It sounds to me like there was a transient error that caused the jobs to spool
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.