snmpd launched before network is fully up
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
net-snmp (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
If /etc/snmp/
We see the following in /var/log/
Sep 7 15:31:08 dragon9 snmpd[1130]: /etc/snmp/
Sep 7 15:31:08 dragon9 snmpd[1130]: /etc/snmp/
Sep 7 15:31:08 dragon9 snmpd[1130]: /etc/snmp/
Sep 7 15:31:08 dragon9 snmpd[1130]: net-snmp: 3 error(s) in config file(s)
Sep 7 15:31:08 dragon9 snmpd[1130]: NET-SNMP version 5.4.2.1
Sep 7 15:31:11 dragon9 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
Sep 7 15:31:11 dragon9 dhclient: DHCPOFFER of 130.127.48.130 from 130.127.48.1
Sep 7 15:31:11 dragon9 dhclient: DHCPREQUEST of 130.127.48.130 on eth0 to 255.255.255.255 port 67
Sep 7 15:31:11 dragon9 dhclient: DHCPACK of 130.127.48.130 from 130.127.48.1
/etc/init.d/snmpd defines Required-Start to depend on the $network virtual facility, but LSB 3.1 defines $network to be "basic networking support is available. Example: a server program could listen on a socket." which does not imply that things such as DNS name resolution will be available.
Other daemons such as ntpd have the same issue, but they seem to begin to work properly once the system has acquired an IP address via DHCP. snmpd should exhibit this same behavior or it should wait until DNS name resolution is available.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: snmpd 5.4.2.1~
ProcVersionSign
Uname: Linux 2.6.32-28-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Wed Sep 7 18:16:51 2011
InstallationMedia: Ubuntu 10.04.2 LTS "Lucid Lynx" - Release amd64 (20110211.3)
ProcEnviron:
PATH=(custom, no user)
LANG=en_US
SHELL=/bin/bash
SNMPVersion:
NET-SNMP version: 5.4.2.1
Web: http://
Email: <email address hidden>
SourcePackage: net-snmp
mtime.conffile.
mtime.conffile.
Changed in net-snmp (Ubuntu): | |
importance: | Undecided → Medium |
This version has expired long times ago, and so will never get support