[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DIGITAL UNIX (FORMERLY KNOWN AS DEC OSF/1) |
| Notice: | Welcome to the Digital UNIX Conference |
| Moderator: | SMURF::DENHAM |
|
| Created: | Thu Mar 16 1995 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 10068 |
| Total number of notes: | 35879 |
8707.0. "os_mibs errors on OSF V3.2D-1" by IAMOSI::LEUNG () Tue Feb 04 1997 22:28
2 systems with OSF V3.2D-1
DECSafe
snmp running on only one system
That system gets the following errors :
Jan 31 06:30:33 ecesrv00 os_mibs[545]: os_mibs **ERROR
esnmp_poll.c line 372: RESPONSE to REGISTRATION of 'at':
DPI_alreadyRegistered
Jan 31 06:30:33 ecesrv00 os_mibs[545]: os_mibs WARNING
esnmp_poll.c line 201: esnmp_poll: Could not process a
packet
Jan 31 06:30:33 ecesrv00 os_mibs[545]: os_mibs **ERROR
os_mibs.c line 340: eSNMP error: -2
Jan 31 06:31:03 ecesrv00 snmpd[548]: Closing subagent
os_mibs, reason: 103
Thanks
Dennis
Dump of snmpd :
---------------
snmpd SUBTREE registry =
1.3.6.1.2.1.1 up to 1.3.6.1.2.1.2
ACTIVE (pri=1 ), subagent os_mibs registration 'system'
(1.3.6.1.2.1.1)
1.3.6.1.2.1.2 up to 1.3.6.1.2.1.3
ACTIVE (pri=1 ), subagent os_mibs registration
'interfaces' (1.3.6.1.2.1.2)
1.3.6.1.2.1.3 up to 1.3.6.1.2.1.4
ACTIVE (pri=1 ), subagent os_mibs registration 'at' (1.
3.6.1.2.1.3)
1.3.6.1.2.1.4 up to 1.3.6.1.2.1.5
ACTIVE (pri=1 ), subagent os_mibs registration 'ip' (1.
3.6.1.2.1.4)
1.3.6.1.2.1.5 up to 1.3.6.1.2.1.6
ACTIVE (pri=1 ), subagent os_mibs registration 'icmp'
(1.3.6.1.2.1.5)
1.3.6.1.2.1.6 up to 1.3.6.1.2.1.7
ACTIVE (pri=1 ), subagent os_mibs registration 'tcp'
(1.3.6.1.2.1.6)
1.3.6.1.2.1.7 up to 1.3.6.1.2.1.8
ACTIVE (pri=1 ), subagent os_mibs registration 'udp'
(1.3.6.1.2.1.7)
1.3.6.1.2.1.8 up to 1.3.6.1.2.1.9
ACTIVE (pri=1 ), subagent os_mibs registration 'egp'
(1.3.6.1.2.1.8)
1.3.6.1.2.1.10.15 up to 1.3.6.1.2.1.10.16
ACTIVE (pri=1 ), subagent os_mibs registration 'fddi'
(1.3.6.1.2.1.10.15)
1.3.6.1.2.1.11 up to 1.3.6.1.2.1.12
ACTIVE (pri=1 ), subagent os_mibs registration 'snmp'
(1.3.6.1.2.1.11)
1.3.6.1.3.4 up to 1.3.6.1.3.5
ACTIVE (pri=1 ), subagent os_mibs registration 'dot5'
(1.3.6.1.3.4)
2.
root 548 1 0.0 Jan 08 ?? 0:47.37 /usr/sbin/snmpd
root 545 1 0.0 Jan 08 ?? 1:03.48 /usr/sbin/os_mibs
3.
1.3.6.1.2.1.1.1.0 = ecesrv00.dola.wa.gov.au AlphaServer 8200 Model 5/300
Digital UNIX V3.2D-1 (Rev. 41); Fri Jun 14 20:18:53 WST 1996
After stopping and restarting snmp :
snmpd SUBTREE registry =
1.3.6.1.2.1.1 up to 1.3.6.1.2.1.2
ACTIVE (pri=1 ), subagent os_mibs registration 'system'
(1.3.6.1.2.1.1)
1.3.6.1.2.1.2 up to 1.3.6.1.2.1.3
ACTIVE (pri=1 ), subagent os_mibs registration
'interfaces' (1.3.6.1.2.1.2)
1.3.6.1.2.1.3 up to 1.3.6.1.2.1.4
ACTIVE (pri=1 ), subagent os_mibs registration 'at' (1.
3.6.1.2.1.3)
1.3.6.1.2.1.4 up to 1.3.6.1.2.1.5
ACTIVE (pri=1 ), subagent os_mibs registration 'ip' (1.
3.6.1.2.1.4)
1.3.6.1.2.1.5 up to 1.3.6.1.2.1.6
ACTIVE (pri=1 ), subagent os_mibs registration 'icmp'
(1.3.6.1.2.1.5)
1.3.6.1.2.1.6 up to 1.3.6.1.2.1.7
ACTIVE (pri=1 ), subagent os_mibs registration 'tcp'
(1.3.6.1.2.1.6)
1.3.6.1.2.1.7 up to 1.3.6.1.2.1.8
ACTIVE (pri=1 ), subagent os_mibs registration 'udp'
(1.3.6.1.2.1.7)
1.3.6.1.2.1.8 up to 1.3.6.1.2.1.9
ACTIVE (pri=1 ), subagent os_mibs registration 'egp'
(1.3.6.1.2.1.8)
1.3.6.1.2.1.10.15 up to 1.3.6.1.2.1.10.16
ACTIVE (pri=1 ), subagent os_mibs registration 'fddi'
(1.3.6.1.2.1.10.15)
1.3.6.1.2.1.11 up to 1.3.6.1.2.1.12
ACTIVE (pri=1 ), subagent os_mibs registration 'snmp'
(1.3.6.1.2.1.11)
1.3.6.1.3.4 up to 1.3.6.1.3.5
ACTIVE (pri=1 ), subagent os_mibs registration 'dot5'
(1.3.6.1.3.4)
1.3.6.1.2.1.1.1.0 = ecesrv00.dola.wa.gov.au AlphaServer 8200 Model 5/300
Digital UNIX V3.2D-1 (Rev. 41); Fri Jun 14 20:18:53 WST 1996
root 19926 1 0.0 Feb 03 ?? 0:03.86 /usr/sbin/snmpd
root 19834 1 0.0 Feb 03 ?? 0:04.21 /usr/sbin/os_mibs
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 8707.1 | | SMURF::DANIELE | | Thu Feb 06 1997 08:04 | 59 |
| I would add to the following description, you do not need
to start/stop snmpd. And if you have any more information
about what's happening on the system please let me know.
Mike
<<< MOLAR::MKNME_USER3:[NOTES$LIBRARY]SNMP.NOTE;2 >>>
-< SNMP >-
================================================================================
Note 278.1 ERROR os_mibs.c ? 1 of 1
SMURF::DANIELE 47 lines 28-JAN-1997 14:41
--------------------------------------------------------------------------------
Hi,
> 3.2f dunix.
> Customer is running Polycenter Performance MOnitor 1.4 and Polycenter
> DXAdvisor on local node. HP Openview is running on the network.
> About once a month, customer sees the following error in daemon.log
> and on her console:
> Jan 22 16:26:21 ubesfin01 os_mibs[428]: os_mibs **ERROR esnmp_poll.c
> line 372: R
> ESPONSE to REGISTRATION of 'at': DPI_alreadyRegistered
This means that for some reason, os_mibs is trying to reregister
its MIB subtrees after it has already done so.
> Jan 22 16:26:21 ubesfin01 os_mibs[428]: os_mibs WARNING esnmp_poll.c
> line 201: e
> snmp_poll: Could not process a packet
> Jan 22 16:26:21 ubesfin01 os_mibs[428]: os_mibs **ERROR os_mibs.c line
> 340: eSNMP error: -2
This is expected 'unwinding', the -2 indicates a failed registration.
os_mibs now sleeps 30 seconds and reestablishes its protocol state w/snmpd.
Since it has already initiated communications, the first step will be to
'close' its current state.
> Jan 22 16:26:51 ubesfin01 snmpd[436]: Closing subagent os_mibs, reason:
> 103
And here we see the close msg being received and logged by snmpd.
The reason code of 103 is due to a bug in libesnmp.so I just discovered
thanks to this note!
It appears that things continue on their merry way, os_mibs having
reconnected w/ snmpd. Is that correct?
The question is what kicks off the whole thing?
Are they shutting down or somehow signalling os_mibs?
Is this all that's in the log?
Is anything happening on these once a month times?
Thanks,
Mike
|
| 8707.2 | NSR backup? | GIDDAY::LEUNG | | Tue Feb 18 1997 17:29 | 7 |
| RE: .1
Sorry for the late reply.
Customer thinks that an NSR backup was running/completed at the time.
Dennis
|