BDF hung and had to reboot the server

[Philemon_2]

Hello Experts,

Today morning I did bdf and it hung, so i have to reboot the server. not sure what was the reason for server hung

I checked the following. Could some please help me to identify the problem.

Syslog

Jul 16 10:41:35 cansxdev2 /usr/sbin/nfsd[3745]: poll failed: Interrupted system call. Exiting
Jul 16 10:42:51 cansxdev2 /usr/sbin/envd[2976]: terminated by signal 15
Jul 16 10:42:57 cansxdev2 sshd[1812]: Received signal 15; terminating.
Jul 16 10:43:52 cansxdev2 diagmond[2966]: Exit due to user requested abort
Jul 16 10:44:09 cansxdev2 cimserver[1343]: exited normally
Jul 16 10:44:18 cansxdev2 inetd[1967]: Going down on signal 15
Jul 16 10:44:20 cansxdev2 automount[1945]: exiting
Jul 16 10:44:20 cansxdev2 vasd[1854]: vasd parent process (PID 1854) exiting
Jul 16 10:44:23 cansxdev2 rpcbind: terminate: rpcbind terminating on signal. Restart with "rpcbind -w"
Jul 16 10:44:30 cansxdev2 syslogd: going down on signal 15


/usr/sbin/ netfmt -f /var/adm/nettl.LOG000 > netlog000.out

**********************Auto-Port Aggregation/9000 Networking*****************@#%
Timestamp : Fri Jul 16 EDT 2010 10:58:43.965976
Process ID : 2592 Subsystem : HP_APA
User ID ( UID ) : 0 Log Class : ERROR
Device ID : 900 Path ID : 0
Connection ID : 0 Log Instance : 0
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<2011> HP Auto-Port Aggregation product can't process control
requests while the link aggregation is not enabled.

root@[/root]: lanscan -q
0
4
5
1
2
3
900
901
902
903
904

root@ [/root]: netstat -in
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
lan1 1500 11.224.20.0 11.224.20.50 3454083 0 1405381 0 0
lo0 4136 127.0.0.0 127.0.0.1 5843 0 5843 0 0
root@cansxdev2 [/root]:

[Steven E. Protter]

Shalom,

This most often happens when a remote NFS or Samba mount has gotten stale.

You might try a few diagnostics:
nfsstat

You might if possible to restart the Samba services or NFS services on the box to avoid a reboot.

/sbin/init.d/nfs.client stop
/sbin/init.d/nfs.server stop
/sbin/init.d/nfs.core stop


/sbin/init.d/nfs.core start
/sbin/init.d/nfs.server start
/sbin/init.d/nfs.client start

SEP

[singh sanjeev]

checked for any corrupt entry in /etc/fstab..or any NFs file system non existence on the system.

[Philemon_2]

After restarting the server i again tried BDF and system again hung. i opened another session and tried the following

/sbin/init.d/nfs.client stop
/sbin/init.d/nfs.server stop
/sbin/init.d/nfs.core stop

/sbin/init.d/nfs.core start
/sbin/init.d/nfs.server start
/sbin/init.d/nfs.client start

and also checked /etc/fstab, every thing looks okay but again BDF hungs.

Please help

Thanks,
Philemon

[Patrick Wallek · Accepted solution]

Do you actually have any NFS mounted file systems on this server? Is the NFS server actually accessible? Can you ping it? Are the NFS processes running correctly on the NFS server?

[Steven E. Protter]

Shalom again,

I assumed there was NFS mounts on your system, because the behavior of your system was reported to sound exactly like such a problem.

Don't just do what I post rote.

You need to know you have NFS mounts before you bother with my procedure.

Alternate: Use mstm cstm or xstm. Check your disks. A disk going bad could cause this behavior.

dmesg

grep lbolt /var/adm/syslog/syslog.log

SEP

[Philemon_2]

Thanks for all your suggestions.

I unmounted all volumes and remounted them and i also found that two volumes are full and i cleaned up them, now the issue resolved

Once again thank you so much.

Thanks,
Philemon

[Philemon_2]

Thanks All.