PfSense 2.3 Check_mk working with xinetd

lebernd

Thank you for the guide!

Everything it still works for me under 2.4rc - just remember to grab a new libstatgrab-0.91.txz for Freebsd11.

Best, Bernd

Programie

I've also updated pfSense (in my case the final release of version 2.4) and can confirm it still works. I didn't had to grab a new libstatgrab, it just works for me out of the box (I only had to add the additional include in /etc/inc/filter.inc just like on every update).

steini

Hey guys

I just updated to 2.4 and started getting these errors:

**EDIT / SOLVED

Needed to update libstatgrab
fetch http://pkg.freebsd.org/FreeBSD:11:amd64/latest/All/libstatgrab-0.91.txz && pkg install libstatgrab-0.91.txz

matthewfearnley

After an upgrade to 2.4(.1) I seem to be getting errors now with the Memory Used plugin: UNKNOWN - check failed - please submit a crash report!
(The crash report says: KeyError: 'MemTotal')

Agent output:
Relevant Check_MK output:

<<<mem>>>
SwapTotal: 782336 kB
SwapFree: 782336 kB</mem>
```(No MemTotal line)

My copy of the agent includes a <<<mem>>> section:

Memory Usage

currently we'll need sysutils/muse for this.

if [ -x /usr/local/bin/muse ]
then
echo '<<<mem>>>'

yes, i don't know sed well.

muse -k 2>/dev/null | sed 's/Total/MemTotal/' | sed 's/Free/MemFree/'
swapinfo -k 1K | tail -n 1 | awk '{ print "SwapTotal: "$2" kB\nSwapFree: "$4" kB" }'
fi</mem>


I've installed muse with 'fetch http://pkg.freebsd.org/FreeBSD:11:amd64/latest/All/muse-0.2.txz && pkg install muse-0.2.txz'

But 'muse -k' outputs:

kvm_open: kvm_nlist: No such file or directory
kvm_open: kvm_nlist: No such file or directory
kvm_open: kvm_nlist: No such file or directory
kvm_open: kvm_nlist: No such file or directory
kvm_nlist failed


Possibly the <<<mem>>> code no longer works?  It looks like it used to be in check_mk_agent.freebsd but is not there now.

EDIT: I realised we are using an old, customised version of the agent.  I'm not willing to update wholesale at this point, but this seems to work now, from a less old version of the agent.  It also means we don't have to install muse now.

Memory Usage. First we try statgrab, since

muse does not seem to support >4GB

if [ -x /usr/local/bin/statgrab ] ; then
echo '<<<mem>>>'
statgrab -K mem.total mem.free swap.total swap.free |
awk '{gsub(/swap./,"Swap");}{gsub(/mem./,"Mem");}{gsub(/tot/,"Tot");}{gsub(/free/,"Free");} { print $1": "$3" kB"}'
elif [ -x /usr/local/bin/muse ] ; then
echo '<<<mem>>>'
muse -k 2>/dev/null | sed 's/Total/MemTotal/' | sed 's/Free/MemFree/'
swapinfo -k 1K | tail -n 1 | awk '{ print "SwapTotal: "$2" kB\nSwapFree: "$4" kB" }'
fi</mem></mem>

azekiel

Just update /opt/bin/check_mk_agent with the newest version available from http://git.mathias-kettner.de/git/?p=check_mk.git;a=blob_plain;f=agents/check_mk_agent.freebsd;hb=HEAD and install libstatgrab for the memory display to work (fetch http://pkg.freebsd.org/FreeBSD:11:amd64/latest/All/libstatgrab-0.91.txz && pkg install libstatgrab-0.91.txz)

Overlord

Didn't work for me (pfSense 2.4.2-RELEASE-p1 (amd64)). I did all steps without any problems, but after reloading the filters, nothing happens. Nothing with xinetd or check_mk in the system logs and I can't to "nc localhost 6556" or "telnet localhost 6556".

Programie

@Overlord:

Didn't work for me (pfSense 2.4.2-RELEASE-p1 (amd64)). I did all steps without any problems, but after reloading the filters, nothing happens. Nothing with xinetd or check_mk in the system logs and I can't to "nc localhost 6556" or "telnet localhost 6556".

Does the Check_MK Agent work if called from the terminal?

Try to execute "/opt/bin/check_mk_agent" on your pfSense host.

And what exact error are you getting if you try to reach port 6556? Connection refused? Connection timed out?

A filter reload should show nothing special (i.e. does not contain anything with check_mk). But you should see something like "readjusting service check_mk" in "Status -> System Logs -> System -> General" after reloading the filters.

After a filter reload, the file "/var/etc/xinetd.conf" should contain a line "includedir /opt/etc/xinetd.d". /opt/etc/xinetd.d should be a directory containing your xinetd config file for Check_MK.

Also make sure, xinetd is running: "ps ax | grep xinetd" should return something like "/usr/local/sbin/xinetd -syslog daemon -f /var/etc/xinetd.conf -pidfile /var/run/xinetd.pid"

toddh

Worked perfectly for me on 2.4.2!

Really appreciate the instructions!

Thank you!!!!!!!

karls0

@Programie:

@Overlord:

Didn't work for me (pfSense 2.4.2-RELEASE-p1 (amd64)). I did all steps without any problems, but after reloading the filters, nothing happens. Nothing with xinetd or check_mk in the system logs and I can't to "nc localhost 6556" or "telnet localhost 6556".

Does the Check_MK Agent work if called from the terminal?

Try to execute "/opt/bin/check_mk_agent" on your pfSense host.

And what exact error are you getting if you try to reach port 6556? Connection refused? Connection timed out?

A filter reload should show nothing special (i.e. does not contain anything with check_mk). But you should see something like "readjusting service check_mk" in "Status -> System Logs -> System -> General" after reloading the filters.

After a filter reload, the file "/var/etc/xinetd.conf" should contain a line "includedir /opt/etc/xinetd.d". /opt/etc/xinetd.d should be a directory containing your xinetd config file for Check_MK.

Also make sure, xinetd is running: "ps ax | grep xinetd" should return something like "/usr/local/sbin/xinetd -syslog daemon -f /var/etc/xinetd.conf -pidfile /var/run/xinetd.pid"

HI,
I have also a problem with check_mk and xinetd.

check_mk works from the terminal. I cannot find a xinetd-process on my box. Also, after reloading the filters (with the manually added line to include /opt/etc/xinetd.d) I only find

Feb 24 16:58:45 check_reload_status Reloading filter
in the logs. /var/etc/xinetd.conf is empty

ps doesn't show a xinetd.

How do I start xinetd on pfsense? Shouldn*t it be running by default?

Any help appreciated,
Karl

calebh

For those interested, I've consolidated the instructions into a new thread, and added a line in the update-persistence script to automatically reload the filters after making the change so the check_mk service is started.

https://forum.netgate.com/topic/131967/check_mk-on-pfsense-2-4-w-update-persistence

adamw

Has anybody had success running check_mk 2.0 agent on pfSense 21.02?

Do steps look exactly as described here:

https://forum.netgate.com/topic/131967/check_mk-on-pfsense-2-4-w-update-persistence

?

That post is almost 3 years old.