<?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: Jet Admin Printer message in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/jet-admin-printer-message/m-p/2832679#M89274</link>
    <description>ALso you do a ps -aef | grep lp and close all the porcess if the lpshut fails .and then restart using lpsched.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Manoj Srivastava</description>
    <pubDate>Thu, 24 Oct 2002 13:44:21 GMT</pubDate>
    <dc:creator>MANOJ SRIVASTAVA</dc:creator>
    <dc:date>2002-10-24T13:44:21Z</dc:date>
    <item>
      <title>Jet Admin Printer message</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/jet-admin-printer-message/m-p/2832676#M89271</link>
      <description>When I try to add a printer using the JetAdmin tool I get the following message&lt;BR /&gt;&lt;BR /&gt; !! Cannot shut down the spooler with lpshut !!&lt;BR /&gt; Having tried for 5 times.  Please shut down the spooler from&lt;BR /&gt; the command line, then re-run this configuration.&lt;BR /&gt;&lt;BR /&gt;What should I do?</description>
      <pubDate>Thu, 24 Oct 2002 13:13:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/jet-admin-printer-message/m-p/2832676#M89271</guid>
      <dc:creator>John M. Fritsch</dc:creator>
      <dc:date>2002-10-24T13:13:42Z</dc:date>
    </item>
    <item>
      <title>Re: Jet Admin Printer message</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/jet-admin-printer-message/m-p/2832677#M89272</link>
      <description>It's telling you to run lpshut from the command line.&lt;BR /&gt;If this fails, you should kill lpsched and then look in /var/spool/lp for FIFO,SCHEDLOCK, and/or CLD_FIFO. If any of these are present remove them.&lt;BR /&gt;&lt;BR /&gt;Should you need to restart the spooler, the command is lpsched. &lt;BR /&gt;</description>
      <pubDate>Thu, 24 Oct 2002 13:17:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/jet-admin-printer-message/m-p/2832677#M89272</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2002-10-24T13:17:06Z</dc:date>
    </item>
    <item>
      <title>Re: Jet Admin Printer message</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/jet-admin-printer-message/m-p/2832678#M89273</link>
      <description>Try running lpshut from the command line or make sure nothing is printing with lpstat command and kill lpsched process and restart spooler.</description>
      <pubDate>Thu, 24 Oct 2002 13:17:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/jet-admin-printer-message/m-p/2832678#M89273</guid>
      <dc:creator>Ken Hubnik_2</dc:creator>
      <dc:date>2002-10-24T13:17:13Z</dc:date>
    </item>
    <item>
      <title>Re: Jet Admin Printer message</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/jet-admin-printer-message/m-p/2832679#M89274</link>
      <description>ALso you do a ps -aef | grep lp and close all the porcess if the lpshut fails .and then restart using lpsched.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Manoj Srivastava</description>
      <pubDate>Thu, 24 Oct 2002 13:44:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/jet-admin-printer-message/m-p/2832679#M89274</guid>
      <dc:creator>MANOJ SRIVASTAVA</dc:creator>
      <dc:date>2002-10-24T13:44:21Z</dc:date>
    </item>
    <item>
      <title>Re: Jet Admin Printer message</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/jet-admin-printer-message/m-p/2832680#M89275</link>
      <description>Are you running JetAdmin as root?</description>
      <pubDate>Thu, 24 Oct 2002 13:44:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/jet-admin-printer-message/m-p/2832680#M89275</guid>
      <dc:creator>Tom Danzig</dc:creator>
      <dc:date>2002-10-24T13:44:39Z</dc:date>
    </item>
    <item>
      <title>Re: Jet Admin Printer message</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/jet-admin-printer-message/m-p/2832681#M89276</link>
      <description>I've had instances where lpshut would not work but I was able to cycle the scheduler with  and /sbin/init.d/lp stop and /sbin/init.d/lp start.&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Thu, 24 Oct 2002 13:46:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/jet-admin-printer-message/m-p/2832681#M89276</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2002-10-24T13:46:12Z</dc:date>
    </item>
    <item>
      <title>Re: Jet Admin Printer message</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/jet-admin-printer-message/m-p/2832682#M89277</link>
      <description>This is no different than running lpshut and it truly does not shutdown lpsched. The reason is simple: one or more of the lpsched processes cannot be terminated, usually due to a network or datacom issue. Use this command to find all the broken lpsched processes:&lt;BR /&gt;&lt;BR /&gt;ps -fulp&lt;BR /&gt;&lt;BR /&gt;Then kill each one with -15, and if that doesn't get them all, use kill -9. Make a note about the printer names that had problems--they caused the issue. Now run jetadmin and you'll be fine.</description>
      <pubDate>Thu, 24 Oct 2002 14:22:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/jet-admin-printer-message/m-p/2832682#M89277</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2002-10-24T14:22:11Z</dc:date>
    </item>
  </channel>
</rss>

