Very Computer

Sep 29 04:56:19 paradise lockd[126]: create_client: no name for inet address 0x2E
Sep 29 04:56:19 paradise lockd[126]: nlm1_call: RPC: Unknown host
Sep 29 04:56:26 paradise lockd[126]: create_client: no name for inet address 0x2E
Sep 29 04:56:26 paradise lockd[126]: nlm1_call: RPC: Unknown host
Sep 29 04:56:27 paradise lockd[126]: create_client: no name for inet address 0x2E
Sep 29 04:56:27 paradise lockd[126]: nlm1_call: RPC: Unknown host

The system is so bogged down with writing these to the /var/adm/messages file
that I cannot even log into it. I have to crash the machine and reboot which
will fix the problem...for a while. I have tried loading some of the recommended
patches for 2.4 but have not been able to figure this out. If someone can please
shed some light on this it would be greatly appreciated.
Please send me Email with any suggestions.

Ray

--
     _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/

   _/  Systems Administrator         _/   (805) 389-7140 Voice   _/
  _/   Vitesse Semiconductor Corp.  _/    (805) 389-7125 Fax    _/

Quote:>Can anyone help me with a strange problem that has come up
>on a Solaris 2.4 system. Every other night or so it gets
>the following errors:
>Sep 29 04:56:19 paradise lockd[126]: create_client: no name for inet address 0x2E
>Sep 29 04:56:19 paradise lockd[126]: nlm1_call: RPC: Unknown host

--
-Gary Mills-          -Unix Support-           -U of M Computer Services-

] >Can anyone help me with a strange problem that has come up
] >on a Solaris 2.4 system. Every other night or so it gets
] >the following errors:

] >Sep 29 04:56:19 paradise lockd[126]: create_client: no name for inet address 0x2E
] >Sep 29 04:56:19 paradise lockd[126]: nlm1_call: RPC: Unknown host

] The 101977-04 patch seems to eliminate the error messages.  I don't know
] if it actually fixes the underlying problem.  The bug description in the
] README file is a bit confused.

101977-04 only seems to greatly reduce the frequency of these type of
errors.  Under high load, we still get this message.  Waiting for the
new implementation of locking in 2.5 seems to be the way to go :-(

Simon.
--

UNIX Support, CPR Project, Telstra.                     +61 3 9634 3974
-------------------------------------------------------------------------------
I've got a can opener at home.  Sometimes it works, and other times it doesn't.
Sometimes it only goes half-way around, and then does a lap of honor - Jimeoin.

Quote:>Ray:
>I had a similar problem which turned out to be the TCP/IP product I was
>running on my connected PCs. We got around it by setting all the PCs so
>that they wouldn't request locking on files.  Is your setup using any PCs
>as client (Or Macs I guess) if so you may wanna look there.

--
Greg Cannon