[Xymon] mq.sh script

[Neil Simmonds]

I've already tried running it with a set -x in the script and get the
following in the log,

+ rm /xymon/client/tmp/mq-server_name.11677
+ TMPFILE=/xymon/client/tmp/mq-server_name.11684
+ touch /xymon/client/tmp/mq-server_name.11684
+ echo 'client server_name.mqcollect mqcollect'
+ '[' 1 '!=' 0 ']'
+ QMGR=PPIM01
+ shift
+ sudo -u mqm mqsc PPIM01 'display qstatus(*) curdepth msgage lgetdate
lgettime'
+ '[' 0 '!=' 0 ']'
+ /xymon/client/bin/xymon ukclamon01 @
log:/opt/IBM/MDMPIM/logs/workflowengine_server_name/db_manager.log:10240
log:`find -L /opt/IBM/MDMPIM/logs/\w*server_name/\w*.log -maxdepth 1  -type
f ! -size 0`:10240
log:/applogs/mdmpim/logs/appsvr_server_name/default.log:10240
log:/opt/IBM/MDMPIM/logs/workflowengine_server_name/customegl.log:20480
log:/opt/IBM/MDMPIM/logs/workflowengine_server_name/default.log:20480
ignore INFO
trigger internal error
file:`find /applogs/mdmpim/dump -name *.txt`
file:`find /applogs/mdmpim/dump -name *.phd``

>From there I can see that it appears to be the line that sends the message
to Xymon that's doing it but U can't see why.

The line in question is underlined and BOLD below (copied the whole script
for context)


TMPFILE="$XYMONTMP/mq-$MACHINE.$$"

touch $TMPFILE

echo "client $MACHINE.mqcollect mqcollect" >$TMPFILE

#
while [ $# != 0 ]
do
    QMGR=$1; shift
    sudo -u mqm mqsc $QMGR 'display qstatus(*) curdepth msgage lgetdate
lgettime' >> $TMPFILE
    ##(echo 'dis ql(*) curdepth'; echo 'dis chs(*)'; echo 'end') | su - mqm
-c "runmqsc $QMGR" >> $TMPFILE
done
#

*$XYMON $XYMSRV "@" < $TMPFILE*
rm $TMPFILE

exit 0




On Mon, Jul 27, 2020 at 5:54 PM Damien Martins via Xymon <xymon at xymon.com>
wrote:

>
>
>
> ---------- Forwarded message ----------
> From: Damien Martins <damien at makelofine.org>
> To: xymon at xymon.com
> Cc:
> Bcc:
> Date: Mon, 27 Jul 2020 18:44:19 +0200
> Subject: Re: [Xymon] mq.sh script
>
> 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 listXymon at xymon.comhttp://lists.xymon.com/mailman/listinfo/xymon
>
>
>
>
> ---------- Forwarded message ----------
> From: Damien Martins via Xymon <xymon at xymon.com>
> To: xymon at xymon.com
> Cc:
> Bcc:
> Date: Mon, 27 Jul 2020 18:44:19 +0200
> Subject: Re: [Xymon] mq.sh script
> _______________________________________________
> Xymon mailing list
> Xymon at xymon.com
> http://lists.xymon.com/mailman/listinfo/xymon
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20200728/0480c275/attachment.htm>