Re: snmpd dies
On 07.01.24 09:37, Martijn van Duren wrote: On Sat, 2024-01-06 at 16:12 +0100, Nicolas Goy wrote: Unfortunately this isn't enough to give me a hint where the issue might be... Let's keep an eye out and hope that we can gather some more context next time, or that I can find something during normal development. Yeah, I took a glimpse at the logs and I thought it wouldn't help that much, but I still sent them because maybe it might help later. I kept the agent in verbose mode and I will send the logs again if it crash again. Thanks for your time. Have a great day -- Nicolas Goy Engineer & Developer https://www.kuon.ch https://www.goyman.com
Re: snmpd dies
On Sat, 2024-01-06 at 16:12 +0100, Nicolas Goy wrote: > On 06.01.24 00:03, Martijn van Duren wrote: > > On Fri, 2024-01-05 at 13:09 +0100, Nicolas Goy wrote: > > My first assumption is it's a bug in libagentx. However, I don't have > > enough context to reproduce it. Can you reproduce it (somewhat) > > reliably? Can you run snmpd with -vv to log the request(s) that > > trigger it. If that's not sufficient context we might need to compile > > either snmpd and/or libagentx with AX_DEBUG and AX_DEBUG_VERBOSE defined > > and run it in the foreground (this logs all agentx data in hex-form to > > stderr). > > I was unable to reproduce it since it happened, I enabled the -vv flags. > I have only one machine monitoring the router and there is a single job > running every five minutes. I captured the output I got (which did not > trigger the bug). But it *should* be the request that was sent when the > crash occurred. > > Regards > > kuon Unfortunately this isn't enough to give me a hint where the issue might be... Let's keep an eye out and hope that we can gather some more context next time, or that I can find something during normal development.
Re: snmpd dies
On Fri, 2024-01-05 at 13:09 +0100, Nicolas Goy wrote: > Hello, > > I am on OpenBSD 7.4 amd64 and today snmpd died with the following error > message: > > snmpd[44109]: AgentX(1207475061): Protocol > error<27>snmpd_metrics[52600]: [fd:0 sess:3150713266 ctx:]: > unsupported call: agentx-Close-PDU > snmpd[44109]: AgentX(1207475061/3150713266): Closed by snmpd (shutting > down)<26>snmpd[44109]: snmpe: AgentX(1207475061): disappeared unexpected > > > My snmpd.conf > > listen on :::1 snmpv2c > listen on xxx.xxx.xxx.1 snmpv2c > filter-pf-addresses yes > filter-routes yes > > read-only community public > > > Any idea if there is something wrong or if it is just an snmpd bug? > > Regards > My first assumption is it's a bug in libagentx. However, I don't have enough context to reproduce it. Can you reproduce it (somewhat) reliably? Can you run snmpd with -vv to log the request(s) that trigger it. If that's not sufficient context we might need to compile either snmpd and/or libagentx with AX_DEBUG and AX_DEBUG_VERBOSE defined and run it in the foreground (this logs all agentx data in hex-form to stderr). martijn@
snmpd dies
Hello, I am on OpenBSD 7.4 amd64 and today snmpd died with the following error message: snmpd[44109]: AgentX(1207475061): Protocol error<27>snmpd_metrics[52600]: [fd:0 sess:3150713266 ctx:]: unsupported call: agentx-Close-PDU snmpd[44109]: AgentX(1207475061/3150713266): Closed by snmpd (shutting down)<26>snmpd[44109]: snmpe: AgentX(1207475061): disappeared unexpected My snmpd.conf listen on :::1 snmpv2c listen on xxx.xxx.xxx.1 snmpv2c filter-pf-addresses yes filter-routes yes read-only community public Any idea if there is something wrong or if it is just an snmpd bug? Regards -- Nicolas Goy Engineer & Developer https://www.kuon.ch https://www.goyman.com