Hello Paride,
thank you for your evaluation of the bug report. I'll try to give you
all the facts to support the process.
In our case the bug is not purely cosmetic. We restrict access for the
read-only community for SNMPv2 in our snmpd.conf to a source host. The host is
defined as a hostname, which is a valid way to specify SOURCE, according the
snmpd.conf manpage:
...
rocommunity COMMUNITY [SOURCE [OID | -V VIEW [CONTEXT]]]
...
A restricted source can either be a specific hostname (or address), or a
subnet
...
When snmpd is unable to resolve hostnames at daemon startup, the daemon
keeps running but our configured source host is unable to do SNMP
requests (which leads to unknowns in our monitoring stack, but that's
just the consequence of the bug...). Only a restart (reload may be
sufficient as well) of the daemon when the network is up fixes the
problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894190
Title:
snmpd starts before the network stack is fully online (network.target
vs network-online.target)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1894190/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
