NET-SNMP: Timeout: No Response from 127.0.0.1.

[Alexeys]

Hi 'body,
I have a strange issue:
I've installed
net-snmp 5.3.1 on a RH Linux 2.6.18-8.el5PAE i686 i686 i386 GNU/Linux
net-snmp 5.4.1 on a Ubuntu Hardy 2.6.24-16-generic x86_64 GNU/Linux

once configured a community called root-community and started the service (service snmpd start) both installations act the same:
#snmptranslate .1.3.6.1.2.1.1.3.0
DISMAN-EVENT-MIB::sysUpTimeInstance
#snmpget -v 2c -c root-community 127.0.0.1 SNMPv2-MIB::sysUpTime.0
Timeout: No Response from 127.0.0.1.

in snmpd.log I can see that snmpd receives requests each time:
Connection from UDP: [XXX.XXX.XXX.XXX]:XXXXX

using "ps aux" i can see that snmpd is started with this line:
/usr/sbin/snmpd -Lsd -Lf /var/log/snmp.log -p /var/run/snmpd -a

Stopping that service, when I tryied to start it directly from command line:
#/usr/sbin/snmpd -Lsd -Lf /var/log/snmp.log -p /var/run/snmpd -a

I get response! Every snmpget request is served!

What is happening there?

[Alexeys]

I've just discovered that using the /etc/init.d/snmpd script with start argument (/etc/init.d/snmpd start) just work!

Is the service command the problem? Why?

[Alexeys]

I've just found my answer.
Reading man service the very first description line says:"service runs a System V init script in as predictable environment as possible, removing most environment variables and with current working directory set to /."

So the problem is in the snmpd script which doesn't initialize it's env variables...Nice.

Thank 'body, uh!