I had this issue in the past, and it seemed to go away (just lucky?), but again running the latest code ... it seems that snmpd is not starting (properly) on boot? I can't connect to it / get it to respond. If I just manually restart the service, then it's all good. Perhaps an issue with sequencing on boot (i.e. should it not be 50?)?
My snmpd is also at S50 and given that some other servers start at that point there shouldn't be a problem.
Is there anything in the logs after a reboot?
If not you can try to move the starting link to S90 and try again.
Most likely it's some race condition. Keep it as is for now and hopefully it won't repeat after flashing of a newer version.
Otherwise the easiest way I can think of is to add the file in the sysupgrade list of preserved files.
BTW, I just found a second router (completely different HW, brand even) that has this same issue. Thinking that S50 may not be quite the right place for snmpd .
I am running snmpd in a couple of routers without any issue of this kind.
It needs to be analyzed further before reaching a conclusion. Post here the uci export network and cover any sensitive data.
Sure, below. But why look at network? Just trying to understand! snmpd is starting, it's just "dead". Restart and all is OK. BTW, I checked dmesg, nothing there for snmpd
I'd be surprised if they did.
One more thing to try, unless someone else has a better idea, is to debug the S50-snmpd and find at which point it fails. Maybe that would show more on the reason it doesn't start.
User logger to send the debug messages to syslog.
More checking, and I realized I worded this VERY poorly - sorry! The service does start (i.e. it shows as running), it just doesn't reply to queries. After a restart of snmpd ... it's "alive" again => same state (running), but actually replies.
Sure! BTW, it definitely seems like some sort of race condition - had to reboot the router twice ... first time it was fine, second time it failed. Here is the output from the command(s) you noted,