Bookworm SNMP daemon not extending.

Aug 18, 2024 Last reply: 1 year ago 12 Replies

Been trying to set up SNMPD on my raspberry PI and simply cannot get the 'extend' feature working



Everything else checks out as expected..but adding



extend cputemp /usr/local/scripts/thermometer "" extend disktemps /usr/local/scripts/disk-temperatures "" extend hi /usr/bin/echo "Hello world"



to snmpd.conf results in no output in snmpwalk



Is it possible that the extend function is disabled in the latest Raspios Bookworm? If so, how to re-enable? How to check?



Systemd has made finding relevant logging impossible. journalctl reveals nothing of relevance


systemd myth number 20: “systemd makes it impossible to run syslog.”

formatting link

Normally the problem is there is far too much crap in journald logging, so I use rsyslog to filter it all out in to easier to use textual logs.

In another terminal do a journalctl -f to view the live log stream, while you attempt the operation.

---druck

That was back in 2013 when they were claiming the occupation of Czechoslovakia and invasion of Poland weren't anything to be concerned about, they've since taken the low countries and France. Only a small island kingdom of distros are holding out against the forces of evil, while the disunited states of BSD are looking the other way.

We shall fight on the boostrap, we shall fight on the logging, we shall fight in the network and in the resolver, we shall fight in the temp files. We shall never surrender!

---druck

You realize journalctl has its own filtering system to narrow things down? Selection by service name, date range, message priority, just about everything you might care about. Even the fields displayed can be narrowed down.

formatting link

I'm just gonna say it ... WORM earns that name.

Alas, on a PI, still not much other choice. LOTS of things totally screwed up - needlessly. I think Deb hired a bunch of Canonical rejects ... SHAME ! If I wanted the Ubuntu mess I'd have installed that.

Eventually, December maybe, Fedora will finally be tuned for the Pi5 and its weird boot requirements. USE THAT ! If you have a Pi4 or lower, download the OLDER distributions.

On OTHER boxes I've moved to either Manjaro or Fedora-40/XFCE at this point. No more Deb.

HOPING for something like a Devuian fork - an "original Deb" offshoot - even based on BullsEye it'd be a huge improvement. Based on Buster would be even better - still all the old config files and such in the well-documented places/formats.

So SAD - Deb used to be 'the rock', 'the foundation', with no BS. How quickly things can go bad ....... beware .........

Manjaro IS pretty good ... but don't love the 'rolling release' aspect. I have low bandwidth and most any update basically re-installs EVERYTHING. A very sledgehammer solution to the dependencies problem.

PIs are, well, weird. If you read all the text during the installs/updates you will see all kinds of funky patches/workarounds. They're kind of the halfway point between micro-controllers and standard CPU systems and, well, it's WEIRD. They DO have their place however !

But if you DON'T need all those I/O pins, consider a BeeLink or BMax mini-box instead.

Surely there must be a huge crowd of systemd-haters able and willing to contribute resources to the development of Devuan. So why does it lag behind?

Yes, but I don't want to fiddle with all that crap when there is a perfectly working syslog with the configuration files I spent years tuning, and easily grep'able text log files.

journald is a massive step backwards, no matter how many bells and whistles they stick on it.

---druck

I agree the latest Bookworm is not set up the way I want it. I don't want Wayland or Network Manager, and I do want Xorg and rsyslog.

My set up has been migrated from whatever was on the very first 256MB Pi (Stretch?) all the way through to Bullseye on the Pi 4B. With a not quite in place 32 bit to 64 bit Bullseye upgrade, I was then able to in place upgrade to 64 bit Bookworm, and transfer to the Pi 5 - but successfully keeping everything set up identically to how it was previously.

If that option hadn't worked, I'd definitely be looking for alternate distros.

Thing is because I always in place upgraded, I didn't notice when the rot had set in, and was horrified at the changes that had been made when I initially did a clean install of Bookworm for the Pi 5.

---druck

Right there is the true importance of backwards compatibility. I'm sure journald has many wonderful features but babies and bathwater spring to mind.

I shouldn't have mentioned systemd. Journalctl reveals no failures reported by the snmp daemon. It simply silently ignores the 'extend' directive.

Systemd is very Marxist/EUist. There must be one central authority to ensure things are always done the right way. And who decided the right way?

Some appartchik was tasked with it who understood nothing about the real world

systemd myth number 20: “systemd makes it impossible to run syslog.”

formatting link

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required