Results 1 to 3 of 3

Thread: CUPS - Print jobs that fail to print

  1. #1

    Default CUPS - Print jobs that fail to print

    opensuse 42.2

    We have a server, also running opensuse 42.2, that has CUPS serving a couple of printers. The local host has its printer objects set up to use the CUPS service on the server.

    For one printer I can send documents all day and the docs print.

    The other printer prints one, maybe two docs, then... nothing. The job just sits in the CUPS queue forever. The last bit of info from CUPS is "Connecting to Printer." No further printing to that device until a reboot of the workstation. (Why the workstation? Not the server.) The print job can be canceled. The CUPS access logs, however, seem to tell a different story:
    Code:
    localhost - - [20/Jun/2017:11:30:09 -0700] "POST /printers/hp_p2015d HTTP/1.1" 200 240 Create-Job successful-ok
    localhost - - [20/Jun/2017:11:30:09 -0700] "POST /printers/hp_p2015d HTTP/1.1" 200 22606 Send-Document successful-ok
    localhost - - [20/Jun/2017:12:07:34 -0700] "POST / HTTP/1.1" 200 183 Renew-Subscription successful-ok
    
    192.168.69.115 - - [20/Jun/2017:11:30:12 -0700] "POST /printers/hp_p2015d HTTP/1.1" 200 204 Create-Job successful-ok
    192.168.69.115 - - [20/Jun/2017:11:30:12 -0700] "POST /printers/hp_p2015d HTTP/1.1" 200 30764 Send-Document successful-ok
    It successfully sent the document? Yet the job sits in the queue. Nothing in the error logs.

    Can anyone suggest what may be happening?

  2. #2
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,384
    Blog Entries
    1

    Default Re: CUPS - Print jobs that fail to print

    Quote Originally Posted by jimoe666 View Post
    opensuse 42.2

    We have a server, also running opensuse 42.2, that has CUPS serving a couple of printers. The local host has its printer objects set up to use the CUPS service on the server.

    For one printer I can send documents all day and the docs print.

    The other printer prints one, maybe two docs, then... nothing.
    The actual printer hardware and drivers might be relevant here? Local print queues?
    Code:
    lpstat -t
    The job just sits in the CUPS queue forever. The last bit of info from CUPS is "Connecting to Printer." No further printing to that device until a reboot of the workstation. (Why the workstation? Not the server.) The print job can be canceled. The CUPS access logs, however, seem to tell a different story:
    Code:
    localhost - - [20/Jun/2017:11:30:09 -0700] "POST /printers/hp_p2015d HTTP/1.1" 200 240 Create-Job successful-ok
    localhost - - [20/Jun/2017:11:30:09 -0700] "POST /printers/hp_p2015d HTTP/1.1" 200 22606 Send-Document successful-ok
    localhost - - [20/Jun/2017:12:07:34 -0700] "POST / HTTP/1.1" 200 183 Renew-Subscription successful-ok
    
    192.168.69.115 - - [20/Jun/2017:11:30:12 -0700] "POST /printers/hp_p2015d HTTP/1.1" 200 204 Create-Job successful-ok
    192.168.69.115 - - [20/Jun/2017:11:30:12 -0700] "POST /printers/hp_p2015d HTTP/1.1" 200 30764 Send-Document successful-ok
    It successfully sent the document? Yet the job sits in the queue. Nothing in the error logs.

    Can anyone suggest what may be happening?
    In case you haven't done so already, I suggest increasing CUPS logging verbosity
    Code:
    cupsctl --debug-logging
    then monitor the CUPS error log again when sending print jobs.

  3. #3

    Default Re: CUPS - Print jobs that fail to print

    I have had a lot of problems with the HPIJS driver; it tends to lose communications with certain HP printer models.
    I have solved this problem switching to the HPCUPS driver.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •