<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: distinct printing issue alog with CUPS in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/distinct-printing-issue-alog-with-cups/m-p/4489775#M38103</link>
    <description>in CUPS's GUI there is an optoon called error policy for each print queue which i made "retry-job" from "stop printer" and keeping under observation.</description>
    <pubDate>Wed, 02 Sep 2009 15:49:10 GMT</pubDate>
    <dc:creator>skt_skt</dc:creator>
    <dc:date>2009-09-02T15:49:10Z</dc:date>
    <item>
      <title>distinct printing issue alog with CUPS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/distinct-printing-issue-alog-with-cups/m-p/4489773#M38101</link>
      <description>&lt;BR /&gt;Red Hat Enterprise Linux Server release 5.2 (Tikanga)&lt;BR /&gt;]# rpm -qa|grep -i cup&lt;BR /&gt;cups-libs-1.2.4-11.18.el5&lt;BR /&gt;cups-1.2.4-11.18.el5&lt;BR /&gt;&lt;BR /&gt;We have some specific situation which CUPS/LINUX is constantly stopping working and the users are not able to print their invoices until somebody clean the the print queue manually.Same printer been shared between Windows and LINUX&lt;BR /&gt;&lt;BR /&gt;here is how we simultae the issue&lt;BR /&gt;&lt;BR /&gt;The printer was OK and an user sent a "large" document (email) to the printer from Windows.After this not able to print from LINUX/CUPS.We requested to the user to delete this print from his windows queue and right after that, we could print document from Windows again ; but not from LINUX again. We have to deleting all queues inside the  specific printer/queue then we will be able to print from cups/LINUX again.&lt;BR /&gt;&lt;BR /&gt;why would a windows job interupt a CUPS queue?&lt;BR /&gt;&lt;BR /&gt;from http:hostnaem:631&lt;BR /&gt;&lt;BR /&gt;i see ""/usr/lib/cups/backend/socket failed"&lt;BR /&gt;&lt;BR /&gt;Description: Printer SpedEBS01_Refi_1 with Upper Tray&lt;BR /&gt;Location: South America - PCALDAS&lt;BR /&gt;Make and Model: HP LaserJet 4000 Foomatic/hpijs&lt;BR /&gt;Printer State: stopped, accepting jobs, published. &lt;BR /&gt;Device URI: socket://200.0.35.73</description>
      <pubDate>Tue, 01 Sep 2009 13:24:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/distinct-printing-issue-alog-with-cups/m-p/4489773#M38101</guid>
      <dc:creator>skt_skt</dc:creator>
      <dc:date>2009-09-01T13:24:24Z</dc:date>
    </item>
    <item>
      <title>Re: distinct printing issue alog with CUPS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/distinct-printing-issue-alog-with-cups/m-p/4489774#M38102</link>
      <description>I just did  did a â  start printerâ   from CUPSâ   GUI and pending jobs got cleared. &lt;BR /&gt;&lt;BR /&gt;Not sure what made the printer "stopped" and why it would report "/usr/lib/cups/backend/socket failed"</description>
      <pubDate>Tue, 01 Sep 2009 17:23:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/distinct-printing-issue-alog-with-cups/m-p/4489774#M38102</guid>
      <dc:creator>skt_skt</dc:creator>
      <dc:date>2009-09-01T17:23:38Z</dc:date>
    </item>
    <item>
      <title>Re: distinct printing issue alog with CUPS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/distinct-printing-issue-alog-with-cups/m-p/4489775#M38103</link>
      <description>in CUPS's GUI there is an optoon called error policy for each print queue which i made "retry-job" from "stop printer" and keeping under observation.</description>
      <pubDate>Wed, 02 Sep 2009 15:49:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/distinct-printing-issue-alog-with-cups/m-p/4489775#M38103</guid>
      <dc:creator>skt_skt</dc:creator>
      <dc:date>2009-09-02T15:49:10Z</dc:date>
    </item>
    <item>
      <title>Re: distinct printing issue alog with CUPS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/distinct-printing-issue-alog-with-cups/m-p/4489776#M38104</link>
      <description>In my experience, HP printers are not reliable if a second job from the network arrives while the printer is in the midst of working on a first job.  I avoid the situation by designating one machine (doesn't matter if it's Windows with the lpd package or Unix; whatever you're more comfortable configuring) to be the print spooling machine.  Only that machine sends jobs directly to the printer, one at a time.  All the other machines send jobs to the spooling printer server.  You of course want to choose a reliable machine as the print spooler.  With this configuration, the HP network print jobs are very reliable.&lt;BR /&gt;</description>
      <pubDate>Thu, 03 Sep 2009 01:27:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/distinct-printing-issue-alog-with-cups/m-p/4489776#M38104</guid>
      <dc:creator>Stephen P. Schaefer</dc:creator>
      <dc:date>2009-09-03T01:27:29Z</dc:date>
    </item>
    <item>
      <title>Re: distinct printing issue alog with CUPS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/distinct-printing-issue-alog-with-cups/m-p/4489777#M38105</link>
      <description>I agree with Stephen: this is a common problem.&lt;BR /&gt;&lt;BR /&gt;However, I seem to remember that once upon a time there was a JetDirect firmware update that was supposed to improve JetDirect's behaviour with multiple simultaneous connections. Is your JetDirect firmware up to date?&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Thu, 03 Sep 2009 10:40:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/distinct-printing-issue-alog-with-cups/m-p/4489777#M38105</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2009-09-03T10:40:10Z</dc:date>
    </item>
  </channel>
</rss>

