Munin Plugins

[AD6NH]

I'm probably the only one using them but... that's another story.

I have three aprsc servers. All of them are on Ubuntu 20.04. The munin plugins on T2SJC work just fine. I have tried the plugins on both T2HUB2 and SECOND, and they don't work. I get the following error:

$ sudo munin-run aprsc_clientlist
aprsc_munin failed: HTTP request to aprsc failed
Warning: the execution of 'munin-run' via 'systemd-run' returned an error. This may either be caused by a problem with the plugin to be executed or a failure of the 'systemd-run' wrapper. Details of the latter can be found via 'journalctl'

journalctl shows this:

May 27 11:00:07 hub2 sudo[412446]:    ad6nh : TTY=pts/0 ; PWD=/home/ad6nh ; USER=root ; COMMAND=/usr/sbin/munin-run aprsc_clientlist
May 27 11:00:07 hub2 systemd[1]: Started /usr/sbin/munin-run --ignore-systemd-properties aprsc_clientlist.

What do you think?

Phil - AD6NH

[Heikki Hannikainen]

Unfortunately the munin plugin doesn't give a good error message, would be
nice if it said which URL it tried to connect and what was the actual
error.

perldoc aprsc_munin (may need a full path) gives the manual:

NAME
aprsc_munin - Munin plugin which monitors an aprsc server instance

This plugin needs to be able to request
http://localhost:14501/status.json. The URL can be changed in the
configuration to point to another server URL.

This configuration example shows the default settings for the plugin:

[aprsc_munin]
env.url http://127.0.0.1:14501/status.json

LICENSE
BSD


So... Check if you can 'curl -v http://localhost:14501/status.json' - if
not, maybe aprsc status http server is configured to not listen on
localhost (it is bound to another address)?

In that case the munin agent config file needs the above block to point to
a better status.json URL with the correct IP.

- Hessu