Hello,

I'm not using this script, but you may run it using:

bash -x? $XYMONCLIENTHOME/ext/mq.sh queuemanagername

replace $XYMONCLIENTHOME with the correct path.

Bash will generate output debug info, so you may see what it is doing.

Also, you may check if the log destination is hardcoded in the script.

Le 27/07/2020 ? 16:39, Neil Simmonds a ?crit?:

Hi all, I'm seeing some really strange behaviour from the MQ.SH script/

We have the standard mq.sh script that comes with Xymon and we have it setup in /xymon/client/etc/clientlaunch.cfg as follows

[mq] ? ? ? ? ENVFILE $XYMONCLIENTHOME/etc/xymonclient.cfg ? ? ? ? CMD $XYMONCLIENTHOME/ext/mq.sh queuemanagername ? ? ? ? LOGFILE $XYMONCLIENTLOGS/xymonmq2client.log ? ? ? ? INTERVAL 1m

The behaviour that we are seeing is that,as expected MQ.SH writes nothing in the way of errors into xymonmq2client.log but what it does write into there is the contents of /xymon/client/tmp/logfetch.hostname.cfg

(i.e. log:/applogs/broker/broker.log:20480 ignore MARK )

I'm at a loss to explain this so am reaching out to the list to see if anyone has come across this

Regards, Neil.

---

Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon