Martijn van Duren wrote:
>
> Ergo: I *don't* think it's worth creating an errata for this.
>
> OK?
>
> martijn@
Could this be reconsidered? We are experiencing the same issue as we are
uplifting 7.1 to 7.2 fleet and requires a restart of snmpd every 3-5 hours
across hosts.
Thanks,
Jason.
On 2022/11/01 16:03, Ryan Freeman wrote:
> On Tue, Nov 01, 2022 at 11:04:03AM +0100, Martijn van Duren wrote:
> > On Mon, 2022-10-31 at 20:14 -0700, Ryan Freeman wrote:
> > >
> > > I can confirm the snmpd process is no-longer disappearing with this
> > > patch. Almost 24 hours on one VM and 16 ho
On Tue, Nov 01, 2022 at 11:04:03AM +0100, Martijn van Duren wrote:
> On Mon, 2022-10-31 at 20:14 -0700, Ryan Freeman wrote:
> >
> > I can confirm the snmpd process is no-longer disappearing with this
> > patch. Almost 24 hours on one VM and 16 hours on another. Thanks!
> >
> > -Ryan
>
> To be c
On Mon, 2022-10-31 at 20:14 -0700, Ryan Freeman wrote:
>
> I can confirm the snmpd process is no-longer disappearing with this
> patch. Almost 24 hours on one VM and 16 hours on another. Thanks!
>
> -Ryan
To be complete, what happens is the following:
- snmpd sends a getnext request to the back
On Mon, Oct 31, 2022 at 11:05:07AM -0700, Ryan Freeman wrote:
> On Sun, Oct 30, 2022 at 09:21:00AM +0100, Martijn van Duren wrote:
> > On Fri, 2022-10-28 at 13:10 -0700, Ryan Freeman wrote:
> > > On Fri, Oct 28, 2022 at 01:22:57PM +0200, Martijn van Duren wrote:
> > > > I wondered that as well, but
On Sun, Oct 30, 2022 at 09:21:00AM +0100, Martijn van Duren wrote:
> On Fri, 2022-10-28 at 13:10 -0700, Ryan Freeman wrote:
> > On Fri, Oct 28, 2022 at 01:22:57PM +0200, Martijn van Duren wrote:
> > > I wondered that as well, but I tried to simulate the not found and
> > > error code-paths, but I c
On Fri, 2022-10-28 at 13:10 -0700, Ryan Freeman wrote:
> On Fri, Oct 28, 2022 at 01:22:57PM +0200, Martijn van Duren wrote:
> > I wondered that as well, but I tried to simulate the not found and
> > error code-paths, but I couldn't trigger it. So I'm not ruling it
> > out, I just can't reproduce it
On Fri, Oct 28, 2022 at 01:22:57PM +0200, Martijn van Duren wrote:
> I wondered that as well, but I tried to simulate the not found and
> error code-paths, but I couldn't trigger it. So I'm not ruling it
> out, I just can't reproduce it.
>
> Another thing that's weird is that it looks like the ind
I wondered that as well, but I tried to simulate the not found and
error code-paths, but I couldn't trigger it. So I'm not ruling it
out, I just can't reproduce it.
Another thing that's weird is that it looks like the index has been
stripped from sensorStatus, which might be an indication that
wei
I wonder if there are any sensors which disappear and reappear..
On 2022/10/28 10:01, Martijn van Duren wrote:
> Could you run snmpd with `-vv`? That way I also have the specific
> OIDs being requested and returned (both frontend and backend) and
> might make it a little more easy to reproduce.
>
Could you run snmpd with `-vv`? That way I also have the specific
OIDs being requested and returned (both frontend and backend) and
might make it a little more easy to reproduce.
Do note that this adds at least 4 log lines for every request
issues to snmpd, so your logfile might explode a bit.
ma
On Thu, Oct 27, 2022 at 01:46:21PM -0700, Ryan Freeman wrote:
> Hello,
> After upgrading some virtual machines to OpenBSD 7.2, I started noticing
> snmpd dying approx every 6 hours on the upgraded machines.
>
> Oct 27 13:14:33 mirror snmpd[98795]: AgentX(1268939451/2580462718):
> 2506302838
> is
Hello,
After upgrading some virtual machines to OpenBSD 7.2, I started noticing
snmpd dying approx every 6 hours on the upgraded machines.
Oct 27 13:14:33 mirror snmpd[98795]: AgentX(1268939451/2580462718): 2506302838
iso.org.dod.internet.private.enterprises.openBSD.sensorsMIBObjects.sensors.sens
13 matches
Mail list logo
