Torkil

I recommend you put subjects in your posts, which will not only increase engagement, but also helps with searching the archives.

On Fri, Mar 18, 2016 at 7:59 AM Torkil Zachariassen < torkil.zachariassen at gmail.com> wrote:

On our xymon (4.3.26) server, which otherwise works just fine, /var/log/xymon/xymonlaunch.log issues the following warning the following every 5 minutes. This again indicates that the culprit is xymonlaunch :

WARNING: Cannot open include file '/var/run/xymonclient-runtime.cfg', line was: include /var/run/xymonclient-runtime.cfg

This seems related to an earlier report @ http://comments.gmane.org/gmane.comp.monitoring.hobbit/26155 stating

<snip>

I suppose there are multiple ways to resolve this, but some advice is needed:

1. include a few line into the server init script (/etc/init.d/xymon) which creates the xymonclients-runtime.cfg file

2. modify or remove the include line in

/usr/lib/xymon/client/etc/xymonclient.cfg on the server

On my installation, I have this in /etc/default/xymon:

cat <<EOF >/var/run/xymonclient-runtime.cfg XYMSERVERS="10.3.3.20 10.3.23.20" XYMSRV="0.0.0.0" EOF

(Note: I have two xymon servers, hence two IP addresses.)

This automatically creates the /var/run/xymonclient-runtime.cfg file each time the Xymon server is started using the init scripts. Not sure if this is the best way, or even a very good way. But it works for me.

The thing is, files in /var/run/ probably shouldn't be expected to exist after a reboot. In practice, I suspect they do for most apps, but a system administrator should be able to wipe this directory out prior to a reboot, and everything should come back like it was before.

We use rpms created from the supplied spec files, and the server has

the xymon package installed only, as the xymon(-server) and xymon-client packages conflicts (you can not install both)

For now we have commented the include line out manually, but please advise on what a proper resolution might look like.

Have you restarted Xymon since doing this? Do the client scripts work as expected?

I suspect that if you remove the include line altogether, you will no longer have XYMSERVERS/XYMSRV defined, and it will break the client side on next restart. (Actually, it might even cause impact on the next execution of xymonclient, typically every 5 minutes.) If this is the case, you would have to replace the include line either with definitions of these variables, or an include for a different file, which you populate with the values you require.

I don't know the "correct" way to do this kind of thing. There's certainly a problem here, where the default install creates errors in the logs. It'd be good to get some input from any of the guys on the list who were involved in creating the spec.

J