topic Re: rpc.lockd in Operating System - HP-UX

rpc.lockd

j773303 — Mon, 20 Oct 2003 03:23:30 GMT

The os is 10.20.

Why the rpc.lockd died? My machine is nfs client. I know if the rpc.lockd was died, we can restart by /usr/sbin/rpc.lockd. But I want to knwo why this daemon would be died?

Re: rpc.lockd

Graham Cameron_1 — Mon, 20 Oct 2003 03:29:38 GMT

It's a bit late now to ask.
Anything in syslog ?
If it persists in dying, use -l option to log to a file to see if that gives any clues.
-- Graham

Re: rpc.lockd

RAC_1 — Mon, 20 Oct 2003 03:40:44 GMT

Syslog should give you some information.

Also start it with -l (log option) and post.

Re: rpc.lockd

Dietmar Konermann — Mon, 20 Oct 2003 03:44:15 GMT

There were known issues with rpc.lockd, e.g. dying during memory pressure. Be sure to have the latest patch (PHNE_28886) installed.

Best regards...
Dietmar.

Re: rpc.lockd

Brian Hackley — Tue, 21 Oct 2003 07:10:13 GMT

Hello,

Sometimes but not often, you will find some evidence of logging in syslog, or in /var/adm/rpc.lockd.log If the problem persists, I'd do two things. First, check that the entries in /var/statmon/sm and sm.bak actually point to hosts, and that you
can contact them. Remove any entries that are bogus.

Did you find a core file from rpc.lockd anywhere? THat should tell you what signal it died from, but nothing more since HP ships non-debug binaries.

I concur on the patch recommendation. I would stronly recommend moving to OS 11.11 if possible on your systems!

Hope all this helps,

-> Brian Hackley

Re: rpc.lockd

Elmar P. Kolkman — Tue, 21 Oct 2003 07:55:44 GMT

Also, are you sure it is only the rpc.lockd process ? Because there is an issue with HP-UX 10.20 without proper patching and the Blaster virus killing the RPC portmapper... A patch is available, but perhaps not installed...