installing hp8150dn with hppi or addqueue

[Bill Walter]

We have successfully installed an hp8150 laserjet on an HP-UX system via a combination of the hppi WEB page and the menu system accessed via the command line. We have been unable to install this printer, or one identical to it, on an identical HP-UX system. We can ping it and the test print from within the menu system produces the correct test page. When used for the install, the WEB based utility insists this is a local printer, unlike the first system which lists it as "network" and, while the enable process reports success, the printer does not get enabled. Independent of this, addqueue -h -q says it "cannot create queue", yet lpstat -t reports a printer with that is not enabled nor accepting requests, nor is it a default printer but is present. Any suggestions would be much appreciated.

[Javed Khan_1]

Hi,

did you install http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=18922&prodTypeId=18964&prodSeriesId=27349&swLang=8&taskId=135&swEnvOID=7

go to sam select printers/plotters-spooler-printers and plotters-action-add network based printers-Spooler Administration-provide printer
ip address - make changes to queue name - and select proper printer model from list.

This should solve this problem


Javed

[Bill Walter]

Thank you, Javed; however, I believe all this is in place but when we attempt to complete the install, as you have outlined, we get:

!! Cannot shut down the spooler with lpshut !!
Having tried for 5 times. Please shut down the spooler from
the command line, then re-run this configuration.

Then we executed lpshut at the command prompt where it says the scheduler has been shut down. Running sam again results in the same error.

[Javed Khan_1]

Hi,

try by killing lpsched processes manually by kill -9 pid (lpsched)


Javed

[Bill Walter]

Thanks again, Javed. We have killed the lpsched pid and it stayed dead while we used sam to install the printer again. The same lpshut error occurs. At the command line, we found that lpsched was still dead so guess this is not the issue.

[Colmin Gajadar]

If the spooler is stopped, look into /var/spool/lp and if there are files CLD_FIFO and SHEDLOCK, remove them then start the spooler with /usr/sbin/lpsched

[Bill Hassell]

This is likely not a problem with the printer but the spooler system has been corrupted. Start with a validity check using swverify:

swverify PrinterMgmt

Fix any problems, especially permissions, ownership and missing files. You can ignore /usr/share/man permission errors if any. Then remove non-working or incorrectly configured printers with lpadmin -x. Now try the addqueue command.

[Bill Walter]

Bill H has pinpointed the problem(s). The group, mod and own errors can be corrected; however several errors occurred such as:
File "/usr/sbin/lpmove" should have mtime "1171575564" but the actual mtime is "1225394339".

File "/usr/bin/lpr" should have size "614" bytes but the actukal size is "68992" bytes.

Fileset "PrinterMgmt.LP2-SPOOL,1=/,r=B.11.31" had file errors.

[Running swverify/swjob on the identical box, where the printer installed properly, yielded zero errors.]

How did this come about? What can be done to fix errors like these?

[Bill Hassell · Accepted solution]

> several errors occurred such as:
File "/usr/sbin/lpmove" should have mtime "1171575564" but the actual mtime is "1225394339".

This is not quite as big a deal although it's not clear why it changed.

> File "/usr/bin/lpr" should have size "614" bytes but the actukal size is "68992" bytes.

Look at the same file on the other system. It should be a simple script. Just ftp it over to the problem system. Same for the /usr/sbin/lpmove

> Fileset "PrinterMgmt.LP2-SPOOL,1=/,r=B.11.31" had file errors.

This is just summarizing that there were a couple of errors.

> [Running swverify/swjob on the identical box, where the printer installed properly, yielded zero errors.]
>How did this come about? What can be done to fix errors like these?

It's hard to guess what made the changes. Another alternative is to use the HP-UX Install DVD to reinstall the PrinterMgmt package. Then follow that with the latest patches for lp. For 11.31, the latest patches are:

PHCO_37540 or the most recent PHCO_38682 which might be too new at this point. No reboot is necessary and current printer definitions will not be affected, although I would delete and reinstall any problem printers.

[Bill Walter]

Great, Bill, now swverify/swjob report zero errors.
Now I am trying to install the printer(queue) thus:
/opt/hpnpl/bin/addqueue -qhplj8150 -h -inet_lj8150 -LAUTO -ron -ton -Don -boff
(ip hidden for security)

although I can ping the printer, HP-UX reports:
Could not contact . We don't have the GUI, but using smh(sam) from the TUI results in the same contact problem. The same printer is available to the other box.

[Bill Hassell]

Is this printer on another subnet? Ping is only one communication test. Perhaps a router is blocking port 9100? Use hpnpadmin to query the printer:

hpnpadmin -v 12.34.56.78

Check the working printer and the problem printer.

[Bill Walter]

we have run hpnpadmin -v which yielded the following results:

[k3@]/home/root # hpnpadmin -v
*** Receive NO snmp response!
*** (printer down, cable off, or wrong Get community name?)

We asked our network guru to watch as we made another attempt. He could see our telnet connection but saw nothing when we executed the hpnpadmin command. He stated all the ports going out of the server are open.

The community name in snmpd.conf match the entry in snmpd.conf on the server which can access the printer.

[Bill Hassell]

> We asked our network guru to watch as we made another attempt. He could see our telnet connection but saw nothing when we executed the hpnpadmin command. He stated all the ports going out of the server are open.

Apparently not. The snmp message is not helpful -- it just means that hpnpadmin did not connect to the JetDirect card. Try telnet 9100 to see if you can connect to the printer on port 9100. If port 9100 is open, your screen will probably clear and you'll some underscore characters when you press return. Characters are not echoed and you'll have to press CTRL ] to get to a telnet prompt and then quit. If port 9100 is not open, you'll get:

Connecting to 192.168.0.10...

which means the path to that IP address is blocked somewhere. In router terms, the port name may be jetdirect, hpnp, hp-printer or similar. To see normal results, use the working printer's IP address. Another confirmation point is that the working printer is on a different subnet than the failing one -- thus a different router path.

[Bill Walter]

Great suggestion; however, here is what happened:

# telnet 999.999.999.999 9100
Trying...
Connected to 999.999.999.999.
Escape character is '^]'.

telnet> quit
Connection closed.

I performed this test on the other box, where the printer works, with exactly the same results. Looks like port 9100 is open.

[Bill Hassell]

Try standard telnet or a web page pointed to the printer's address. Then check to see that TCP/IP protocol is enabled. There are usually 4 protocols available but each one can be disabled. Telnet will give you a menu, the web page will be a full browser with multiple pages. You can compare both printers with their network settings.

[Bill Walter]

I have examined the printer config, again. It is correctly configured with TCP/IP and port 9100 enabled. Note that both the successful and the unsuccessful servers are pointing at the same printer, so no comparison can be made.

[Bill Hassell]

One last check on the JetDirect card: make sure there are no entries in the access list. This is either empty (any IP address can talk to the card) or has 1 to 10 entries (no IP except those can connect).

When all else fails, use the cold reset in the printer to clear all the JetDirect settings and then reassign the addresses manually with telnet or arp/ping harvesting.