Hello, All,
I came in this morning to a hung cluster member (AS 4100 running DU 4.0B).
Upon reboot, I found the following error messages in my logs:
DAEMON.LOG (syslog's daemon.debug output)
----------
Dec 7 01:50:42 machineA svrSystem_mib[1983]: svrSystem_mib **ERROR
svrSystem_mib.c line 222: eSNMP error: -4
Dec 7 01:54:49 machineA svrSystem_mib[1983]: svrSystem_mib **ERROR
svrSystem_mib.c line 222: eSNMP error: -4
Dec 7 01:56:03 machineA svrSystem_mib[1983]: svrSystem_mib **ERROR
svrSystem_mib.c line 222: eSNMP error: -4
Dec 7 01:55:57 machineA snmpd[1963]: Sendto failed: 61
Dec 7 01:56:08 machineA snmpd[1963]: Sendto failed: 2
Dec 7 01:56:11 machineA snmpd[1963]: Closing subagent pmgrd, reason: 0
Dec 7 01:56:33 machineA svrSystem_mib[1983]: svrSystem_mib **ERROR
svrSystem_mib.c line 232: Terminating...
Dec 7 01:56:36 machineA snmpd[1963]: Closing subagent advfsd, reason: 0
Dec 7 01:56:48 machineA snmpd[1963]: Closing subagent svrSystem_mib,
reason: 0
Dec 7 01:56:48 machineA snmpd[1963]: Sendto failed: 2
Dec 7 01:56:48 machineA snmpd[1963]: Sendto failed: 2
Dec 7 01:56:48 machineA snmpd[1963]: Closing subagent advfsd, reason: 0
Dec 7 01:56:50 machineA last message repeated 7 times
Dec 7 01:57:26 machineA snmpd[1963]: Closing subagent svrSystem_mib,
reason: 0
Dec 7 01:57:26 machineA snmpd[1963]: Closing subagent advfsd, reason: 0
Dec 7 01:57:26 machineA snmpd[1963]: Sendto failed: 2
Dec 7 01:57:26 machineA snmpd[1963]: Closing subagent advfsd, reason: 0
Dec 7 01:57:27 machineA last message repeated 2 times
Dec 7 01:57:27 machineA snmpd[1963]: Closing subagent svrSystem_mib,
reason: 0
Dec 7 01:57:28 machineA snmpd[1963]: Sendto failed: 61
Dec 7 01:57:28 machineA snmpd[1963]: Sendto failed: 2
Dec 7 01:57:28 machineA snmpd[1963]: Sendto failed: 2
Dec 7 01:57:28 machineA snmpd[1963]: Closing subagent pmgrd, reason: 103
Dec 7 01:57:28 machineA snmpd[1963]: Closing subagent advfsd, reason: 0
Dec 7 01:57:28 machineA snmpd[1963]: Closing subagent advfsd, reason: 103
Dec 7 01:57:28 machineA snmpd[1963]: Closing subagent pmgrd, reason: 103
Dec 7 08:24:48 machineA telnetd[4247]: ttloop: peer died: No such file or
directory
Dec 7 09:08:13 machineA telnetd[4246]: ttloop: peer died: No such file or
directory
Dec 7 09:08:13 machineA telnetd[4213]: ttloop: peer died: No such file or
directory
USER.LOG (syslog's user.debug output)
--------
Dec 7 00:34:59 machineA syslog: Either svrSystem_mib is not running or
envmon.mod module is not loaded. Error cod
e set in packet - General error: 0.
Here are my questions:
0) Any idea what caused these errors?
1) If envmond or any of the mib's are not running, can that cause the
machine to hang or not respond to network requests (it still responded to a
ping, but I couldn't connect)?
2) If a user had processes running that were loading the system, is it
possible that some of these processes died or were killed? If so, how
would I know this? Where might it be logged?
3) (Not related) Where are the cron jobs logged for Digital Unix? I've
seen the cron log but it only has info on when cron started. Must this be
set up to log through syslog, and, if so, how?
Thanks in advance for any help that you can provide.
Changa
Received on Mon Dec 07 1998 - 21:49:57 NZDT