D390 Server Errors

[Betty Hardin]

We have a D390 server having issues. Not sure what happened to it or what to look for. These are some of the errors displayed when I logon to it. I am able to ping the box from elsewhere on the network but am not able to login; it seems to get stuck in a loop "Init ... /usr/lib/dld.sl: Call to mmap() failed - BSS /usr/lib/libnsl.1" also displays 'fork' errors. I know that it is not a diskspace issue; wondering if this may be corrupted ram? And -if I turn the box off (reboot is not possible without logon) - will it come back up again?

Pid 7150 received a SIGSEGV for stack growth failure.
Possible causes: insufficient memory or swap space,
or stack size exceeded maxssiz.

/usr/lib/dld.sl: No Error
/usr/lib/dld.sl: Not enough space

/usr/lib/dld.sl: Call to mmap() failed - BSS /usr/lib/libnsl.1
/usr/lib/dld.sl: Not enough space
/usr/sbin/sam[220]: 7246 Abort(coredump)

[Leif Halvarsson_2]

Hi,
Do you get any error messages about hardware problem on the front panel display (or the boot console) ?

Is it possible to boot from the installation CD ?

[Kasper Hedensted]

Hi,

Have you tried to see if it is possible to login at the console ?
Is there any additional error messages at the console ?

[KVK]

The issue has been resolved in the latest libc cumulative patch no PHCO_32761 .

http://www5.itrc.hp.com/service/patch/patchDetail.do?BC=patch.breadcrumb.main|patch.breadcrumb.search|&patchid=PHCO_32761&context=hpux:800:11:11

[Adisuria Wangsadinata_1 · Accepted solution]

Hi,

Based on your description, there are 3 issues on the system :

1. the issue could be on insufficient memory or swap space, check the url below for details :

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=641435

2. you need to check the core file that has been generated on your system (since you said the message comes when you're login, the core file on your user's home directory).

run :
# file core
# strings core
# what core

3. for 'fork' issue, check the url below for details :

http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000006334814

For corrupted RAM, usually can check /var/opt/resmon/log/event.log, for any present log with memory issue.

Turn off the system without properly procedure can be harm. But if no choice, make sure there's no user's activity on the system and if possible shutdown all the application that run on the system.

FYI from the issue above, looks like the cause of the problem comes from the resources issue (either kernel or physical ram), so the problem can be appear again if you're not working on the area.

Hope this help you.

Cheers,
AW

[Betty Hardin]

Still having issues with this server; planning to add more ram