From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Slow SNMP daemon startup
Date: Tue, 15 Dec 2020 16:00:23 -0000 (UTC) [thread overview]
Message-ID: <rramin$k2f$1@ciao.gmane.io> (raw)
In-Reply-To: rram42$17q6$1@ciao.gmane.io
On 2020-12-15, Grant Edwards <grant.b.edwards@gmail.com> wrote:
> After upgrading from an older version of net-snmp (5.7.3 -> 5.8) it
> now takes the snmp daemon anywhere from 5s to a minute to start up. It
> used to start with no noticeable delay.
>
> Has anybody else noticed this?
>
> Does anybody have any guesses on where to start looking for the problem?
>
> There's nothing in the syslog to indicate any problem:
>
> # grep snmp /var/log/messages
> Jan 1 00:00:08 (none) daemon.info snmpd[944]: Created directory: /var/lib/snmp
> Jan 1 00:00:08 (none) daemon.info snmpd[944]: Created directory: /var/lib/snmp/cert_indexes
> Dec 15 15:17:26 (none) daemon.info snmpd[944]: Created directory: /var/lib/snmp/mib_indexes
> Dec 15 15:17:26 (none) daemon.info snmpd[946]: NET-SNMP version 5.8
>
> Though it looks like the ntp daemon has stepped the time while snmpd
> is starting up, so perhaps that's causing a problem...
That's not it. I disable ntp, and it got even worse (over two minutes):
# grep snmp /var/log/messages
Jan 1 00:00:08 (none) daemon.info snmpd[942]: Created directory: /var/lib/snmp
Jan 1 00:00:08 (none) daemon.info snmpd[942]: Created directory: /var/lib/snmp/cert_indexes
Jan 1 00:02:34 (none) daemon.info snmpd[942]: Created directory: /var/lib/snmp/mib_indexes
Jan 1 00:02:34 (none) daemon.info snmpd[944]: NET-SNMP version 5.8
--
Grant
next prev parent reply other threads:[~2020-12-15 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 15:52 [Buildroot] Slow SNMP daemon startup Grant Edwards
2020-12-15 16:00 ` Grant Edwards [this message]
2020-12-15 16:55 ` Grant Edwards
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='rramin$k2f$1@ciao.gmane.io' \
--to=grant.b.edwards@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.