topic Re: Server Not Accessable in Operating System - HP-UX

Server Not Accessable

Brent Simon — Wed, 21 Mar 2001 21:04:36 GMT

Hi All,
I have a HP D250 server running HP-UX 11 and the system has 'locked up' twice in two weeks.
What I mean by lock up is that I can't telnet, ftp, to the system, or access databases on the system.

When it locks up, and I try to log into the console, I receive a message saying...
/usr/lib/libnsl.1 Not enough disk space...

This would make me think that the /usr partition would be full, but after rebooting it no disk partition is even close to be being full.

Nothing strange has shown up in the syslog.log either.

Any ideas what could be causing this??

Thanks,

Brent Simon
brent.simon@net-linx.com

Re: Server Not Accessable

Patrick Wallek — Wed, 21 Mar 2001 21:26:16 GMT

Have you checked /var/adm/syslog/syslog.log and /var/adm/syslog/OLDsyslog.log to see if there are any out of disk space error messages there? If there are, it will tell you precisely what is full. It's possible that there is a process running somewhere that is generating a file in one of your file systems and filling it up, but when you reboot the file gets cleaned out.

I would do a bdf on a regular basis and see if any of your LVs grow from day to day. If they do, investigate what is making them grow.

Re: Server Not Accessable

melvyn burnard — Wed, 21 Mar 2001 22:08:37 GMT

Is this the complete message you get??
You may want to look at PHSS_21046 for a known mib2agt memory leak.
Failing that, ensure you have enouggh space configured for a full memory dump and do a TOC when the system has "hung" to create a crash dump and get it analysed by the HP Response Centre

Re: Server Not Accessable

Bill Hassell — Thu, 22 Mar 2001 04:07:22 GMT

The error message is not clear enough to determine the filesystem lacking in space. If any filesystem fills up, that error message will be logged in syslog. It will also be logged on the console but not many people run real terminals anymore. It's a good idea to log all dmesg errors using cron as in:

01,11,21,31,41,51 * * * * /usr/sbin/dmesg - >> /var/adm/dmesg.log

Now all console messages will be logged and also timestamped.

Re: Server Not Accessable

Steven Sim Kok Leong — Thu, 22 Mar 2001 05:26:56 GMT

Hi,

One possibility could be that the number of opened files in your server has been exceeded. When that happens, usually the shared library /usr/lib/libdld.sl is flagged in the error.

Hope this helps. Regards.

Steven Sim Kok Leong
Brainbench MVP for Unix Admin
http://www.brainbench.com

Re: Server Not Accessable

Vincenzo Restuccia — Fri, 23 Mar 2001 11:47:39 GMT

Verify if the memory is full with swapinfo -mt.
You can see the messages in front led.