JetAdmin Installed but Getting Error

[Jennifer Chiarelli]

I just installed JetAdmin ver D.06.21 on a L2000 running 64bit HP-UX 11.0. The install seemed to go fine. The software says the printer is accessible. A test print works. SAM says the printer is ready. But a simple "cat | lp -d does not print. When I try to use diagnostics within JetAdmin I get the following:

*************************************
* DIAGNOSTICS *
* HP JetAdmin Utility for UNIX *
*************************************

System:
1) Verify installation of software
2) Examine spooler operations

Printer/Network:
3) Test network printer's accessibility
4) Print a test page to printer
5) View HP JetDirect interface's current configuration
6) Check BOOTP and TFTP operations (super-user only)
7) Show HP JetDirect interface's protocol settings
8) Display operational and protocol statistics

?) Help q) Quit

Please enter a selection: 6
Can't perform this task, due to network port has been used by rbootd.
Press the return key to continue ...

It appears that rbootd is the conflict. /etc/services shows:
printer 515/tcp spooler # remote print spooling

Note: I first installed the "Printer Installer" and received the same results. So I removed that and then installed the above JetAdmin. Both programs were down loaded from HP's jetAdmin web site.

This L2000 is my server for both HP 700 series workstations and a flexlm license server for NT workstations. Should I remove rbootd from the startup scripts? Or how can I resolve this conflict?

[Rick Garland]

You can verify that rbootd is the culprit by using lsof to see that the port is actually in use. If so, you may need to modify the port settings in the /etc/services to make sure there are no conflicts. Check the /etc/services and see if two different services are using the same port. If so, you may need to modify.

[Jennifer Chiarelli]

Thanks for the response Rick, but I'm not familiar with lsof. I searched and lsof is not on my system. Do I need to install diagnostics to get it or is this a public domain program?

[Jennifer Chiarelli]

Here are some searches I did in the services file.

rfpux7/etc # cat services|grep boot
bootps 67/udp # Bootstrap Protocol Server
bootpc 68/udp # Bootstrap Protocol Client
instl_boots 1067/udp # installation bootstrap protocol server
instl_bootc 1068/udp # installation bootstrap protocol client
rfpux7/etc # cat services|grep print
printer 515/tcp spooler # remote print spooling
pdclientd 6874/tcp # Palladium print client daemon
pdeventd 6875/tcp # Palladium print event daemon
rfpux7/etc #

I do not see rbootd in the services file. The only print related entries are:

printer 515/tcp spooler # remote print spooling
hpoms-ci-lstn 5403/tcp #SAP spooler support
hpoms-dps-lstn 5404/tcp #SAP spooler support

[John Palmer]

Lanny,

bootp may be a red herring. What does 'lpstat -i -t' tell you about the printer queue?

[Jennifer Chiarelli]

Here is the output from lpstat -i -t

rfpux7/etc # lpstat -i -t
scheduler is running
system default destination: rpfitlj4
device for rpfitlj4: /dev/null
rpfitlj4 accepting requests since Aug 15 18:04
printer rpfitlj4 is idle. enabled since Aug 15 18:04
fence priority : 0

[John Palmer]

So your test print has disappeared from the queue for rpfitlj4. This usually means that all is well, hpnpf (the network interface program) doesn't usually 'black hole' prints.

Check the lp scheduler log (/var/spool/lp/log) for any information regarding the test print.

Also try another test print and monitor with lpstat -i -t. You can also use netstat -a piped into some form of grep to look for a network connection to your printer.

[Anthony deRito]

Lanny, for what its worth, I get the same message "Can't perform this task, due to network port has been used by rbootd." when I run option 6. I am not using rbootd and my scheduler and jetadmin is working fine. I think this message is sending you on the wrong track to solve this problem but I cannot be certain.

Tony

[Antoanetta Naghiu]

Is it a network printer? How do you solve ips, names? What nslookup is saying if run on printer name/IP? Try to edit /etc/hosts with printer's info (name and ip address). Take a look on /etc/nsswitch.

[Jennifer Chiarelli]

Yes it is a network printer connected to a external HP JetDirect Ex Plus. A test print from JetAdmin will print to the printer. A ping of the printer name does work and resolves the name. However, when I use:
cat /etc/hosts | lp -d rfpitlj4
I get: lp: destination "rfpitlj4" non-existent

[Jennifer Chiarelli]

Here is the result of nslookup:

rfpux7/etc # nslookup rfpitlj4
Using /etc/hosts on: rfpux7

looking up FILES
Name: rfpitlj4
Address: 208.43.74.206

[John Palmer]

Lanny,

Your print queue is called 'rpfitlj4' not 'rfpitlj4'. The error message makes all the difference!

[Jennifer Chiarelli]

Very good John! I did not see that before!
Now, when I look in SAM the printer is called "rfpitlj4", yet as you pointed out, the queue is called rpfitlj4. So, the only way I know how to remove this is in SAM. But will SAM remove the bad queue as well?

[John Palmer]

Yes sam will do it or you could just do
lpshut
lpadmin -xrpfitlj4
lpsched

to remove the bad queue.

Then 'jetadmin' to recreate the queue (no need to go through sam).

Regards,
John

[Jennifer Chiarelli]

John,

Ok, the commands worked to delete the queue. Then in JetAdmin I deleted the existing printer. Then when I try to recreate it I get the following:

Completed creating BOOTP/TFTP configuration database for rfpitlj4.

Tftp service is also used to boot up JetDirect. Make
sure /var/adm/inetd.sec allows JetDirect's IP to access
tftp service on this node.

Please wait...
Can't perform this task, due to network port has been used by rbootd.
Press the return key to continue ...

[Jennifer Chiarelli]

And a attempt to print still say's that the printer is non-existant.

[John Palmer]

Just use the 'manage print queue (superuser only)' (or whatever it's called) in jetadmin to create the queue. I don't think that you need to configure bootp.

[Antoanetta Naghiu]

Forget about sam or commands. Play just with jetadmin.
Go to jetadmin main menu, delete the printe and reinstall it.
cd /opt/hpnp/bin
./jetadmin ->1. configuration->4.delete
Back to configuration, go to 3. Add a local spooler, give the printer IP to be sure is not confusion, take care if you like to have the printer queue the same name as the printer you have to modify it (by default is printer_mane_q or something.
Try again, eventually try lp -dqueue_name /etc/hosts (shouldn't make any difference.
Any better?