Cannot start snmpd plus "snmp dead but subsys locked" msg

[Lee, John (Sydney)]

Hi fellow net-snmp users,

I have been trying to install net-snmp on Fedora 7 box without success.
Basically, whenever I ran it, I receive "stopping failed" message and
"snmp dead but subsys locked" message.

# uname -r
2.6.21-1.3194.fc7
# yum list net-snmp
Loading "installonlyn" plugin
Installed Packages
net-snmp.i386 1:5.4-14.fc7
installed

# service snmpd restart
Stopping snmpd: [FAILED]
Starting snmpd: [ OK ]
# service snmpd status
snmpd dead but subsys locked
# ps waux | grep snmp
root 417 0.0 0.0 4008 704 pts/0 S+ 17:55 0:00 grep
snmp
root 32714 0.5 0.1 47356 3032 ? Ssl 17:20 0:12
/opt/dell/srvadmin/dataeng/bin/dsm_sa_snmp32d

I am in the process of installing DELL OMSA (Open Manage Server
Administrator) which requires net-snmp to work with it.

The funny thing is I was able to get the same OMSA to work on RHEL 5
without a hitch. I thought RHEL 5 and F7 should be similar but I don't
know why F7 does not work.

Could it be the net-snmp version I am running?

Thanks in advance.
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

[Dave Shield]

Post by Lee, John (Sydney)
# service snmpd restart
Stopping snmpd: [FAILED]
Starting snmpd: [ OK ]
# service snmpd status
snmpd dead but subsys locked

So it looks as if the agent is starting, then falling over.
You need to find out why.

Try looking in the log files, for any output from the snmpd agent.
Alternatively, start the agent manually, using the same options
as in the /etc/init.d/snmpd script, but adding the flags "-f -Le"
That should display any errors on the terminal, where you can
see them.

Dave

[Lee, John (Sydney)]

Thanks Dave for your prompt and generous response.

Post by Dave Shield
Try looking in the log files, for any output from the snmpd agent.

1) /var/log/messages
This does not contain snmp messages.
2) /var/log/snmpd.log
This file is empty.

Post by Dave Shield
Alternatively, start the agent manually, using the same options
as in the /etc/init.d/snmpd script, but adding the flags "-f -Le"
That should display any errors on the terminal, where you can
see them.

I was able to locate /etc/rc.d/init.d/snmpd.
To add the flag "-f -Le", do you mean to run the command like
/etc/rc.d/init.d/snmpd restart -f -Le?
Or do you mean I add the options in /etc/snmp/snmpd.options?
I tried both but they don't seem to put any messages in the log.

Any help would be greatly appreciated!
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

[Dave Shield]

Post by Lee, John (Sydney)

Post by Dave Shield
Alternatively, start the agent manually, using the same options
as in the /etc/init.d/snmpd script, but adding the flags "-f -Le"
That should display any errors on the terminal, where you can
see them.

I was able to locate /etc/rc.d/init.d/snmpd.
To add the flag "-f -Le", do you mean to run the command like
/etc/rc.d/init.d/snmpd restart -f -Le?

No.

Post by Lee, John (Sydney)
Or do you mean I add the options in /etc/snmp/snmpd.options?

Closer.

You should start the SNMP agent *manually* (i.e. not using
the /etc/init.d/snmpd script), using the same options as in
/etc/snmp/snmpd.options, plus "-f -Le"

i.e. something like

snmpd -f -Le `cat /etc/snmp/snmpd.options`


What does this display?

Dave

[Lee, John (Sydney)]

Post by Dave Shield
You should start the SNMP agent *manually* (i.e. not using
the /etc/init.d/snmpd script), using the same options as in
/etc/snmp/snmpd.options, plus "-f -Le"
i.e. something like
snmpd -f -Le `cat /etc/snmp/snmpd.options`

# snmpd -f -Le 'cat /etc/snmp/snmpd.options'
Segmentation fault
# snmpd -f -Le
Segmentation fault

By the way, /etc/snmp/snmpd.options does not exist and there is no
snmpd.options anyway on the machine.

Again, there is nothing in /var/log/messages and /var/log/snmpd.log is
empty.

Any thoughts?
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

[Dave Shield]

Post by Lee, John (Sydney)
# snmpd -f -Le
Segmentation fault

Well, that would explain why the agent doesn't running when you start it!
Is this a binary that you compiled yourself, or a pre-compiled package
that you picked up from somewhere?
If pre-compiled, where did you find it?

Post by Lee, John (Sydney)
By the way, /etc/snmp/snmpd.options does not exist and there is no
snmpd.options anyway on the machine.

Eh?

Post by Lee, John (Sydney)

To add the flag "-f -Le" ....
Or do you mean I add the options in /etc/snmp/snmpd.options?
I tried both.

That's why I suggested adding the options to this file.

Anyway - that's a red herring - if the agent crashes with a
SegFault, then it doesn't matter what options you give it....


Dave

[Lee, John (Sydney)]

The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
On

Behalf Of Dave Shield
Sent: Friday, 28 September 2007 6:41 PM
To: Lee, John (Sydney)
Subject: Re: Cannot start snmpd plus "snmp dead but subsys locked" msg

Post by Lee, John (Sydney)
# snmpd -f -Le
Segmentation fault

Well, that would explain why the agent doesn't running when you start it!
Is this a binary that you compiled yourself, or a pre-compiled package
that you picked up from somewhere?
If pre-compiled, where did you find it?

I just did a yum install net-snmp from Fedora 7.

# yum list net-snmp
Installed Packages
net-snmp.i386 1:5.4-14.fc7
installed

Any thoughts?

[Dave Shield]

Post by Lee, John (Sydney)

Post by Dave Shield
Is this a binary that you compiled yourself, or a pre-compiled package
that you picked up from somewhere?
If pre-compiled, where did you find it?

I just did a yum install net-snmp from Fedora 7.

In which case, I'd suggest that you contact Fedora about this problem.


One thing to try first:
What does
snmpd -f -Le -C
display?
Does that crash or not?

If it does, then talk to the Fedora people.
If it *doesn't* crash (but gives you a message about "no access control"),
then the problem would seem to lie elsewhere.

Dave

[Lee, John (Sydney)]

Post by Dave Shield
What does
snmpd -f -Le -C
display?
Does that crash or not?

# snmpd -f -Le -C
Warning: no access control information configured.
It's unlikely this agent can serve any useful purpose in this state.
Run "snmpconf -g basic_setup" to help you configure the snmpd.conf
file for this agent.
NET-SNMP version 5.4
[smux_accept] accepted fd 9 from 127.0.0.1:47412
refused smux peer: oid SNMPv2-SMI::enterprises.674.10892.1, descr
Systems Management SNMP MIB Plug-in Manager
[smux_accept] accepted fd 9 from 127.0.0.1:47413
refused smux peer: oid SNMPv2-SMI::enterprises.674.10892.1, descr
Systems Management SNMP MIB Plug-in Manager
[smux_accept] accepted fd 9 from 127.0.0.1:47414
refused smux peer: oid SNMPv2-SMI::enterprises.674.10892.1, descr
Systems Management SNMP MIB Plug-in Manager
[smux_accept] accepted fd 9 from 127.0.0.1:47415
refused smux peer: oid SNMPv2-SMI::enterprises.674.10892.1, descr
Systems Management SNMP MIB Plug-in Manager
[smux_accept] accepted fd 9 from 127.0.0.1:47416
refused smux peer: oid SNMPv2-SMI::enterprises.674.10892.1, descr
Systems Management SNMP MIB Plug-in Manager
[smux_accept] accepted fd 9 from 127.0.0.1:47417
refused smux peer: oid SNMPv2-SMI::enterprises.674.10892.1, descr
Systems Management SNMP MIB Plug-in Manager
[smux_accept] accepted fd 9 from 127.0.0.1:47418
...

Any thoughts?
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

[Dave Shield]

Post by Lee, John (Sydney)
# snmpd -f -Le -C
Warning: no access control information configured.
It's unlikely this agent can serve any useful purpose in this state.

OK - so there's nothing wrong with the agent binary itself.
The problem lies somewhere in the config file processing.
The next question is where.

Try running:

snmpd -f -Le -Dread_config

What does that display?

Dave

[Lee, John (Sydney)]

Post by Dave Shield
OK - so there's nothing wrong with the agent binary itself.
The problem lies somewhere in the config file processing.
The next question is where.
snmpd -f -Le -Dread_config
What does that display?

Hi Dave, please see attached.
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

[Dave Shield]

Post by Lee, John (Sydney)

Post by Dave Shield
The problem lies somewhere in the config file processing.
snmpd -f -Le -Dread_config
What does that display?

Hi Dave, please see attached.

------
:
read_config: /etc/snmp/snmpd.conf:459 examining: smuxpeer
.1.3.6.1.4.1.674.10892.1
read_config: /etc/snmp/snmpd.conf:460 examining: trapsink
172.28.18.142 compuware
:
read_config: /etc/snmp/snmpd.conf:459 examining: smuxpeer
.1.3.6.1.4.1.674.10892.1
read_config: Found a parser. Calling it: smuxpeer / .1.3.6.1.4.1.674.10892.1
Segmentation fault

------

So it's falling over when parsing the file /etc/snmp/snmpd.conf.
somewhere between line 459:
smuxpeer .1.3.6.1.4.1.674.10892.1
and line 460:
trapsink 172.28.18.142 compuware

Try commenting out both of these lines, and run the agent ("snmpd -f -Le").
Does it start up OK?
Then try activating one of these two lines, and re-start the agent.
Then try with the other one.

Can you isolate the problem to one of these two snmpd.conf directives?

Dave

[Lee, John (Sydney)]

Post by chloe K
------
So it's falling over when parsing the file /etc/snmp/snmpd.conf.
smuxpeer .1.3.6.1.4.1.674.10892.1
trapsink 172.28.18.142 compuware
Try commenting out both of these lines, and run the agent ("snmpd -f -Le").
Does it start up OK?

Hi Dave, I commented out the 2 lines and below is what I got (I hit
CTRL-C to stop it at the end).
Is this what you meant by OK?

...
[smux_accept] accepted fd 9 from 127.0.0.1:46881
refused smux peer: oid SNMPv2-SMI::enterprises.674.10892.1, descr
Systems Management SNMP MIB Plug-in Manager
[smux_accept] accepted fd 9 from 127.0.0.1:46882
refused smux peer: oid SNMPv2-SMI::enterprises.674.10892.1, descr
Systems Management SNMP MIB Plug-in Manager
Received TERM or STOP signal... shutting down...

Post by chloe K
Then try activating one of these two lines, and re-start the agent.
Then try with the other one.
Can you isolate the problem to one of these two snmpd.conf directives?
Dave

The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

[Dave Shield]

Post by Lee, John (Sydney)
Hi Dave, I commented out the 2 lines and below is what I got (I hit
CTRL-C to stop it at the end).
Is this what you meant by OK?

Yep - that looks fine.

Now try with each of the two lines individually.
One should start up cleanly.
The other should fall over with Segmentation fault

Dave

[Lee, John (Sydney)]

Post by Dave Shield
Now try with each of the two lines individually.
One should start up cleanly.
The other should fall over with Segmentation fault

a)
vi /etc/snmp/snmpd.conf
smuxpeer .1.3.6.1.4.1.674.10892.1
# trapsink 172.28.18.142 compuware

# snmpd -f -Le
Segmentation fault

b)
vi /etc/snmp/snmpd.conf
# smuxpeer .1.3.6.1.4.1.674.10892.1
trapsink 172.28.18.142 compuware

# snmpd -f -Le
[smux_accept] accepted fd 10 from 127.0.0.1:40814
refused smux peer: oid SNMPv2-SMI::enterprises.674.10892.1, descr
Systems Management SNMP MIB Plug-in Manager
[smux_accept] accepted fd 10 from 127.0.0.1:40815
refused smux peer: oid SNMPv2-SMI::enterprises.674.10892.1, descr
Systems Management SNMP MIB Plug-in Manager
Received TERM or STOP signal... shutting down...

So, the culprit is this line:
smuxpeer .1.3.6.1.4.1.674.10892.1

Strange? I got this line from DELL:
http://support.dell.com/support/edocs/software/svradmin/5.2/en/ug/html/s
etup.htm

It works for RHEL5 but in F7, I have this problem.

Any thoughts? Thanks a heap!
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

[Thomas Anders]

Post by Dave Shield
smuxpeer .1.3.6.1.4.1.674.10892.1

Check out patch 1659623 which got applied in SVN Rev. 15942:

http://net-snmp.svn.sourceforge.net/viewvc/net-snmp/branches/V5-4-patches/net-snmp/agent/mibgroup/smux/smux.c?r1=15942&r2=15941&view=patch&pathrev=15942


+Thomas

[Lee, John (Sydney)]

Post by Thomas Anders
http://net-snmp.svn.sourceforge.net/viewvc/net-snmp/branches/V5-4-
patches/net-

snmp/agent/mibgroup/smux/smux.c?r1=15942&r2=15941&view=patch&pathrev=159
42
Sorry Thomas, I am a bit of a newbie in snmpd.
So, do you suggest that "smuxpeer .1.3.6.1.4.1.674.10892.1" does not
work because of the bug that smuxpeer did not specify a password?

As I did not use svn but use "yum install net-snmp" to install it on F7,
do I just "yum remove net-snmp" and then just download the latest
net-snmp from sourceforge and install it again?

Thanks in advance.
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

[Thomas Anders]

Post by Thomas Anders

Post by Thomas Anders
http://net-snmp.svn.sourceforge.net/viewvc/net-snmp/branches/V5-4-
patches/net-

snmp/agent/mibgroup/smux/smux.c?r1=15942&r2=15941&view=patch&pathrev=159
42
Sorry Thomas, I am a bit of a newbie in snmpd.
So, do you suggest that "smuxpeer .1.3.6.1.4.1.674.10892.1" does not
work because of the bug that smuxpeer did not specify a password?
As I did not use svn but use "yum install net-snmp" to install it on F7,
do I just "yum remove net-snmp" and then just download the latest
net-snmp from sourceforge and install it again?

Yep. We only offer binaries for FC6, not FC7, though, so you'd need to
build from source.

If you prefer binary packages instead, you could:

- install a 5.4.x SVN snapshot package for FC7 (see
http://www.net-snmp.org/wiki/index.php/Third-Party_Packages -- let us
know how it works for you)

and/or

- file a bug with Fedora to get them to include the above patch in their
package


+Thomas

[Lee, John (Sydney)]

Post by Thomas Anders
Yep. We only offer binaries for FC6, not FC7, though, so you'd need to
build from source.
- install a 5.4.x SVN snapshot package for FC7 (see
http://www.net-snmp.org/wiki/index.php/Third-Party_Packages -- let us
know how it works for you)
and/or
- file a bug with Fedora to get them to include the above patch in their
package

Thomas, I did "yum remove net-snmp".
I then did the following:
# wget
http://garr.dl.sourceforge.net/sourceforge/net-snmp/net-snmp-5.4.1.tar.g
z
# ./configure
# make
# make test
# make install
# cp /usr/src/net-snmp-5.4.1/EXAMPLE.conf /usr/local/etc/snmp/snmpd.conf

* I made a few changes to make it look like the previous snmpd.conf

# snmpd -f -Le
netsnmp_assert !"registration != duplicate" failed agent_registry.c:535
netsnmp_subtree_load()
netsnmp_assert !"registration != duplicate" failed agent_registry.c:535
netsnmp_subtree_load()
netsnmp_assert !"registration != duplicate" failed agent_registry.c:535
netsnmp_subtree_load()
/usr/local/etc/snmp/snmpd.conf: line 417: Warning: Unknown token:
smuxpeer.
Error opening specified endpoint ""
Server Exiting with code 1

It does not seem to recognize smuxpeer command. Do you know what is
happening?

Also, in this new installation, how can I start snmpd? "service snmpd
start" does not work anymore.
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

[Dave Shield]

# wget http://..../net-snmp-5.4.1.tar.gz
# ./configure
Warning: Unknown token: smuxpeer.

Try
./configure --with-mib-modules=smux

# snmpd -f -Le
netsnmp_assert !"registration != duplicate" failed agent_registry.c:535
netsnmp_subtree_load()

It might be worth applying Official Patch 1805971
(from the project web site), to handle these messages.

Also, in this new installation, how can I start snmpd?
"service snmpd start" does not work anymore.

Check the script that starts the agent.
(Probably something like /etc/init.d/snmpd)
This is probably trying to invoke /usr/sbin/snmpd.
If you've compiled from source using the default settings,
then the agent will be installed as /usr/local/sbin/snmpd.
You may need to tweak the startup script accordingly.

Dave

[Lee, John (Sydney)]

Post by Dave Shield

Post by Lee, John (Sydney)
# snmpd -f -Le
netsnmp_assert !"registration != duplicate" failed

agent_registry.c:535

Post by Dave Shield

Post by Lee, John (Sydney)
netsnmp_subtree_load()

It might be worth applying Official Patch 1805971
(from the project web site), to handle these messages.

Applied patch to agent_registry.c.
Looks good.

Post by Dave Shield

Post by Lee, John (Sydney)
Warning: Unknown token: smuxpeer.

Try
./configure --with-mib-modules=smux

Did the following:
# make clean
# make distclean
# ./configure --with-mib-modules=smux
# make
# make install
# /usr/local/sbin/snmpd -f -Le
Error opening specified endpoint ""
Server Exiting with code 1
# /usr/local/sbin/snmpd -f -Le -Dread_config
...
<output please see attached>
...

Thanks.
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

[Dave Shield]

Post by Lee, John (Sydney)
# /usr/local/sbin/snmpd -f -Le
Error opening specified endpoint ""
Server Exiting with code 1

Hmmm....
What happens if you specify an explicit socket to listen on?
I.e.
/usr/local/sbin/snmpd -f -Le udp:161

Dave

[Lee, John (Sydney)]

Sorry for the late reply Dave - I have been sick for a while.

Post by Dave Shield
Hmmm....
What happens if you specify an explicit socket to listen on?
I.e.
/usr/local/sbin/snmpd -f -Le udp:161

# /usr/local/sbin/snmpd -f -Le udp:161
Error opening specified endpoint "udp:161"
Server Exiting with code 1

Unfortunately same result. Any thoughts?
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

[Dave Shield]

Post by Lee, John (Sydney)

Post by Dave Shield
Hmmm....
What happens if you specify an explicit socket to listen on?
I.e.
/usr/local/sbin/snmpd -f -Le udp:161

# /usr/local/sbin/snmpd -f -Le udp:161
Error opening specified endpoint "udp:161"
Server Exiting with code 1

You've probably got another agent running in the background,
and listening on port 161.
Try shutting that down before starting your agent.

Dave

[Lee, John (Sydney)]

Post by Dave Shield
You've probably got another agent running in the background,
and listening on port 161.
Try shutting that down before starting your agent.

# ps waux | grep snmp
root 1529 0.0 0.0 4008 700 pts/0 S+ 17:18 0:00 grep
snmp
root 2796 0.0 0.1 8864 3396 ? S Oct09 0:02 snmpd
root 32714 0.6 0.1 48380 3076 ? Ssl Sep27 249:32
/opt/dell/srvadmin/dataeng/bin/dsm_sa_snmp32d

# /opt/dell/srvadmin/dataeng/bin/dataeng stop
Stopping Systems Management Data Engine:
Stopping dsm_sa_snmp32d: [ OK ]
Stopping dsm_sa_eventmgr32d: [ OK ]
Stopping dsm_sa_datamgr32d: [ OK ]

# ps waux | grep snmp
root 1568 0.0 0.0 4008 724 pts/0 S+ 17:19 0:00 grep
snmp
root 2796 0.0 0.1 8864 3396 ? S Oct09 0:02 snmpd

# /usr/local/sbin/snmpd -f -Le udp:161
Error opening specified endpoint "udp:161"
Server Exiting with code 1

Sorry, my guess is probably wrong that the DELL snmp32d was also using
udp:161.

Could you please enlighten me on how to locate the other agent?
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

[Thomas Anders]

Post by Lee, John (Sydney)
root 2796 0.0 0.1 8864 3396 ? S Oct09 0:02 snmpd

[...]

Post by Lee, John (Sydney)
Could you please enlighten me on how to locate the other agent?

"lsof -p 2796" output should contain all the information you need.
If you can't locate the start/stop script, "kill 2796" (no, not
"-9") will probably do it as well.


+Thomas

[Lee, John (Sydney)]

Post by Thomas Anders
"lsof -p 2796" output should contain all the information you need.
If you can't locate the start/stop script, "kill 2796" (no, not
"-9") will probably do it as well.

# lsof -p 2796 (please see attached)
# kill 2796
# /usr/local/sbin/snmpd -f -Le udp:161
NET-SNMP version 5.4.1


Received TERM or STOP signal... shutting down...

/usr/local/sbin/snmpd seems to stay on forever without doing anything.

What is happening?
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

[Dave Shield]

Post by Dave Shield
smuxpeer .1.3.6.1.4.1.674.10892.1

Looks like it.

Post by Dave Shield
http://support.dell.com/support/edocs/software/svradmin/5.2/en/ug/html/setup.htm
It works for RHEL5 but in F7, I have this problem.

Do you actually need to use the Server Administrator SNMP facilities?
If not, then the simplest thing is just to leave this particular line out.

Dave

[Dave Shield]

Post by Lee, John (Sydney)
# snmpd -f -Le
Segmentation fault

Well, that would explain why the agent doesn't running when you start it!
Is this a binary that you compiled yourself, or a pre-compiled package
that you picked up from somewhere?
If pre-compiled, where did you find it?

Post by Lee, John (Sydney)
By the way, /etc/snmp/snmpd.options does not exist and there is no
snmpd.options anyway on the machine.

Eh?

Post by Lee, John (Sydney)

To add the flag "-f -Le" ....
Or do you mean I add the options in /etc/snmp/snmpd.options?
I tried both.

That's why I suggested adding the options to this file.

Anyway - that's a red herring - if the agent crashes with a
SegFault, then it doesn't matter what options you give it....


Dave

[chloe K]

Dear Dave

I am sorry to interrupt

I have also same problem to run 5.4.1 in fedora 6 PAE kernel

in my /var/log/snmpd.log. an error is same as John


tail /var/log/snmpd.log
error on subcontainer 'ia_index' insert (-1)
error on subcontainer 'ia_addr' insert (-1)
error on subcontainer 'ia_index' insert (-1)
error on subcontainer 'ia_index' insert (-1)
error on subcontainer 'ia_addr' insert (-1)
error on subcontainer 'ia_index' insert (-1)
error on subcontainer 'ia_addr' insert (-1)
couldn't map value 255 for ipAddressAddrType
not enough space for value
error setting index while loading ipAddressTable cache.


I also run snmpd -f -Le -C and snmpd -f -Le -Dread_config
and also got the "Segmentation fault"

Any idea. Could you help me?

Thank you so much

Post by Lee, John (Sydney)
# snmpd -f -Le -C
Warning: no access control information configured.
It's unlikely this agent can serve any useful purpose in this state.

OK - so there's nothing wrong with the agent binary itself.
The problem lies somewhere in the config file processing.
The next question is where.

Try running:

snmpd -f -Le -Dread_config

What does that display?

Dave

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Net-snmp-users mailing list
Net-snmp-***@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users



---------------------------------
All new Yahoo! Mail
---------------------------------
Get news delivered. Enjoy RSS feeds right on your Mail page.

[Dave Shield]

I also run .... snmpd -f -Le -Dread_config
and also got the "Segmentation fault"

Is that all? No other output?

Dave

[chloe K]

Hi Dave

Thank you in advance. other output are same as snmpd.log
One more info. I didn't install any fedora snmp rpm before and only install snmp from source and also got this problem

Thank you again

snmpd -f -Le -C
netsnmp_assert !"registration != duplicate" failed agent_registry.c:535 netsnmp_subtree_load()
netsnmp_assert !"registration != duplicate" failed agent_registry.c:535 netsnmp_subtree_load()
netsnmp_assert !"registration != duplicate" failed agent_registry.c:535 netsnmp_subtree_load()
error on subcontainer 'ia_addr' insert (-1)
error on subcontainer 'ia_index' insert (-1)
error on subcontainer 'ia_index' insert (-1)
error on subcontainer 'ia_addr' insert (-1)
error on subcontainer 'ia_index' insert (-1)
error on subcontainer 'ia_index' insert (-1)
error on subcontainer 'ia_addr' insert (-1)
error on subcontainer 'ia_index' insert (-1)
error on subcontainer 'ia_addr' insert (-1)
couldn't map value 255 for ipAddressAddrType
not enough space for value
error setting index while loading ipAddressTable cache.
Segmentation fault

snmpd -f -Le -Dread_config
registered debug token read_config, 1
netsnmp_assert !"registration != duplicate" failed agent_registry.c:535 netsnmp_subtree_load()
netsnmp_assert !"registration != duplicate" failed agent_registry.c:535 netsnmp_subtree_load()
netsnmp_assert !"registration != duplicate" failed agent_registry.c:535 netsnmp_subtree_load()
error on subcontainer 'ia_addr' insert (-1)
error on subcontainer 'ia_index' insert (-1)
error on subcontainer 'ia_index' insert (-1)
error on subcontainer 'ia_addr' insert (-1)
error on subcontainer 'ia_index' insert (-1)
error on subcontainer 'ia_index' insert (-1)
error on subcontainer 'ia_addr' insert (-1)
error on subcontainer 'ia_index' insert (-1)
error on subcontainer 'ia_addr' insert (-1)
couldn't map value 255 for ipAddressAddrType
not enough space for value
error setting index while loading ipAddressTable cache.
Segmentation fault

I also run .... snmpd -f -Le -Dread_config
and also got the "Segmentation fault"

Is that all? No other output?

Dave



---------------------------------
All new Yahoo! Mail -
---------------------------------
Get a sneak peak at messages with a handy reading pane.