Snmpd[#]: could not encode error response
-
snmpd[56997]: could not encode error response snmpd[25568]: could not encode error responseI have Spiceworks on my network and I think that's causing this error in pfSense's System General Log when it does SNMP queries on it. I did a search on this forum and didn't find anything mentioning "snmpd". Should I install a package on the pfSense box manually?
-
I am getting the error every 4 minutes after an upgrade to 2.2.1. The upgrade seems stuck at.
"Packages are currently being reinstalled in the background.
Do not make changes in the GUI until this is complete."
-
I have the same error but the upgrade isn't stuck with me.
I just get that error every x seconds in the system log.
Did you find a solution for this?
-
Me to! On pf 2.2.4.
Log fills up like this:
Sep 28 21:09:28 snmpd[63972]: could not encode error response Sep 28 21:09:28 snmpd[63972]: could not encode error response Sep 28 21:09:28 snmpd[63972]: could not encode error response Sep 28 21:09:29 snmpd[63972]: could not encode error response Sep 28 21:09:29 snmpd[63972]: could not encode error response Sep 28 21:09:29 snmpd[63972]: could not encode error response Sep 28 21:09:29 snmpd[63972]: could not encode error response Sep 28 21:09:31 snmpd[63972]: could not encode error response Sep 28 21:09:31 snmpd[63972]: could not encode error response Sep 28 21:09:31 snmpd[63972]: could not encode error response Sep 28 21:10:12 snmpd[63972]: could not encode error responseI'm monitoring with Observium.
-
If you search the forum for that error, you'll find a similar thread from a week or two ago – someone tracked it down to a problem in the FreeBSD bsnmpd daemon and how it handles interface IP address queries from the SNMP client (in your case, Spiceworks or whatever NMS you have).
It's a problem in the FreeBSD bsnmpd daemon so it needs to be fixed upstream. We might have one of our devs look at it, if they have some time. See https://redmine.pfsense.org/issues/4298
