lpstat HPDPS error

[BradF]

Greetings,

I am getting the following error when I do a lpstat.

lpstat
lpstat: HPDPS error (Cannot determine the local IP address.)
lpstat: HPDPS error (Cannot determine the local IP address.)

I recently changed the IP address of the server via sam and changed the hostname via set_parms hostname.

What do I need to do to make lpstat content?

Thanks!

-Brad

[A. Clay Stephenson]

Hi Brad,

I think you need to stop & restart the pd processes. First, however, I would make sure name resolution is ok. If you are running DNS, you need to update the DNS tables to refelct the new hostname/IP address. If you are running NIS, the NIS hosts map needs to be updated.

Finally,
cd /sbin/init.d

./pd stop
./pd start

I think that will fix you.

Clay

[John Poff]

Hello Brad,

I've run into this problem with HPDPS before. The HPDPS software stores the IP address of the printer inside of the HPDPS configuration, even if you specified a hostname when you created the physical printer. You'll have to use the 'pdset' command to change the 'printer-tcpip-internet-address' attribute for the printer.

Here are the commands to set the IP address for a sample printer named 'it_01' to be 10.1.2.4:

pddisable it01
pdset -c printer -x "printer-tcpip-internet-address=10.1.2.4" it_01
pdenable it01


JP

[BradF]

We are not using hpdps. I bounced pd and I still get the same message.

We are looking at files first for DNS resolution. If I do a nslookup $(hostname) it comes back with the IP address???

-Brad

[John Poff]

Oops. I didn't read the question completely.

If you aren't using HPDPS at all, you should be able to turn it off. Do an /sbin/init.d/pd stop, and then turn it off in /etc/rc.config.d/pd. Set the PD_CLIENT to 0.

JP

[BradF]

I changed the IP addresss on the server via sam and the hostname via set_parms hostname.

I am not running hpdps. Now lpstat comes back with the HPDPS error.

What else to I need to check or change to make lpstat work with out the error message?

[John Poff]

Brad,

Is your hostname and IP address resolving correctly when you do an 'nslookup'?

Have you tried stopping and restarting the lpsched daemon?

Have you tried going into SAM and seeing if you have any printers/spoolers/supervisors created under HPDPS? I know you aren't using it but maybe someone created an object in there once.

JP

[BradF]

I was able to do a nslookup by both hostname and ip address. I stopped and restarted the lp scheduler.

lpstat didn't return this message until the hostname and IP was changed.

There are not any hpdps printers setup in sam.

ALSO, This server used to be part of a ServiceGuard cluster. When it was decommissioned as part of the cluster that is when its IP and hostname was changed.

-Brad

[John Poff]

Brad,

Have you rebooted the system since you changed the IP address?

JP

[BradF]

The system has been rebooted since the hostname and the IP address was changed.

[John Poff]

Brad,

Are you running the lpstat command as root or as a regular user?

JP

[John Poff]

Also,

Does the 'lp' command work?

Did you have anything under /var mounted as another filesystem? Specifically, did you mount /var/spool as a shared filesystem to take spool files with you during a failover? (Don't look at me like that, I've done it before!) :)

JP

[BradF]

JP,

I am running the command as root. /var/spool was not part of the cluster. I am able to print to a printer. There are two jet direct printers setup on the system.

-Brad

#lpstat -t
scheduler is running
no system default destination
device for g001: /dev/null
device for g002: /dev/null
lpstat: HPDPS error (Cannot determine the local IP address.)
g001 accepting requests since May 18 09:51
g002 accepting requests since May 18 09:52
lpstat: HPDPS error (Cannot determine the local IP address.)
printer g001 is idle. enabled since May 18 09:53
fence priority : 0
printer g002 is idle. enabled since May 18 09:52
fence priority : 0
lpstat: HPDPS error (Cannot determine the local IP address.)
lpstat: HPDPS error (Cannot determine the local IP address.)

[John Poff]

Brad,

I know you aren't running HPDPS, but maybe it has gotten corrupt or confused. You can rename the /var/opt/pd/basicdsd.db file and try bouncing pd again.

Try looking in the /var/opt/pd/pdclientd directory. There are some log files in there and they might give us a clue about what it is complaining about.

JP

[BradF]

Shutdown pd, moved off basicsdsd.db and restarted it and had the same message with lpstat.

I looked at the log files and it didn't have any helpful information.

[John Poff]

Brad,

Have you looked in /var/adm/lp/log for any error messages/clues?

Another thing to look at is in the /var/spool/lp/request directory. There is a PDRequest directory in that that takes requests for printing to HPDPS. Do you have that directory? Is it empty? While you are in the request directory, do you have any print queue directories in there that don't show up in lpstat?

JP

[BradF]

The /var/adm/lp/log file just had information about the print job I sent to test the spooler/printer.

In /var/spool/lp/request there is a PDrequest directory but it is empty.

I did not have the lpstat HPDPS message before I changed the hostname/IP.

I will reboot the server again tomorrow.

-Brad

[John Poff]

Brad,

Another thing to check is the /etc/pdclient.conf file. It should have 644 permissions.

JP

[BradF]

I rebooted the server and still have the same issue.

The permissions are set correctly on pdclientd.conf.

New info:

When I go into set_parms hostname I get the following message:
dhcpdb2conf(ERR): main, setdhcpent() failed to access client database

The server is not setup to be a dhcp server. I installed phne_19241 because I saw note on the itrc about dhcp patches.

-Brad

[John Poff]

Brad,

Are you still having the problem with lpstat?

It looks like lpstat tries to report on the status of HPDPS printers also, and the error you are getting is coming from HPDPS. Can you do an nslookup on your two printers g001 and g002, and their IP addresses?

If you aren't running HPDPS, try doing a '/sbin/init.d/pd stop' and then try your lpstat. Maybe if lpstat knows HPDPS isn't running it won't complain?

JP

[BradF]

Yes I am still getting the error message from lpstat. I shutdown hpdps and I still get the error messages.

The printers are jetdirect printers. If I do a nslookup by IP address on them I get a name back from DNS on one and not on the other.

They are configured in jetadmin by IP address.

-Brad

[John Poff]

Brad,

I'd try fixing the DNS entry for the printer that doesn't come up, and then see what you get.

JP

[Jan Verheijen]

We have the same problem even without any changes in ip address.
With all the answers I still cannot solve the problem.

[Michael Knaup]

Hi Brad,

"Cannot determine the local IP address" really seems to point to a name resolution issue and it seems to be the hostname/ip of the host your are sitting on when you do the lpstat or localhost/127.0.0.1.

Do you have an nsswitch.conf configured? If not, do so with "hosts files [NOTFOUND=countinue] dns". And check read permission for other's.

Keep in mind that nslookup could handle nsswitch.conf different from normal resolvers, especially a not existing nsswitch.conf.

Then you should check, if your local ip and 127.0.0.1 are configured in your local /etc/hosts. These ones shouldn't be exclusive in the dns database, but always held locally.

Regarding hpdps: To completely get rid of hpdps, besides checking PD_CLIENT in /etc/rc.config.d/pd, you should also check PD_SPOOLERS and PD_SUPERVISORS to be empty. Otherwise hpdps spoolers or supervisors could be started and confuse the lpstat.

Cheers,

Michael