[Xymon] Alerts Stopped Working with DURATION Keyword
Root, Paul T
Paul.Root at CenturyLink.com
Tue Jan 2 16:10:16 CET 2018
That's very strange.
-----Original Message-----
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Stephen Carville (xymon list)
Sent: Tuesday, January 02, 2018 8:56 AM
To: xymon at xymon.com
Subject: Re: [Xymon] Alerts Stopped Working with DURATION Keyword
On 01/02/2018 06:16 AM, Root, Paul T wrote:
> Lereta Email Checkpoint: External email. Please make sure you trust this source before clicking links or opening attachments.
>
> **********************************************************************
>
> Do a 'ps -ef |grep xymond'
xymon 1219 1214 0 2017 ? 00:02:49 xymond
--pidfile=/var/log/xymon/xymond.pid
--restart=/var/xymon/server/tmp/xymond.chk
--checkpoint-file=/var/xymon/server/tmp/xymond.chk
--checkpoint-interval=600 --log=/var/log/xymon/xymond.log
--admin-senders=127.0.0.1,10.212.2.40 --store-clientlogs=!msgs
xymon 1447 1214 0 2017 ? 00:00:00 xymond_channel
--channel=stachg --log=/var/log/xymon/history.log xymond_history
--pidfile=/var/log/xymon/xymond_history.pid
xymon 1448 1214 0 2017 ? 00:00:00 xymond_channel
--channel=page --log=/var/log/xymon/alert.log xymond_alert
--checkpoint-file=/var/xymon/server/tmp/alert.chk --checkpoint-interval=600
xymon 1449 1214 0 2017 ? 00:00:45 xymond_channel
--channel=client --log=/var/log/xymon/clientdata.log xymond_client
xymon 1450 1214 0 2017 ? 00:00:07 xymond_channel
--channel=status --log=/var/log/xymon/rrd-status.log xymond_rrd
--rrddir=/var/xymon/data/rrd
xymon 1451 1214 0 2017 ? 00:00:02 xymond_channel
--channel=data --log=/var/log/xymon/rrd-data.log xymond_rrd
--rrddir=/var/xymon/data/rrd
xymon 1452 1214 0 2017 ? 00:00:00 xymond_channel
--channel=clichg --log=/var/log/xymon/hostdata.log xymond_hostdata
xymon 1461 1449 0 2017 ? 00:00:28 xymond_client
xymon 1462 1447 0 2017 ? 00:00:00 xymond_history
--pidfile=/var/log/xymon/xymond_history.pid
xymon 1463 1450 0 2017 ? 00:00:35 xymond_rrd
--rrddir=/var/xymon/data/rrd
xymon 1464 1451 0 2017 ? 00:00:10 xymond_rrd
--rrddir=/var/xymon/data/rrd
xymon 1703 1448 0 2017 ? 00:00:00 xymond_alert
--checkpoint-file=/var/xymon/server/tmp/alert.chk --checkpoint-interval=600
xymon 1707 1452 0 2017 ? 00:00:00 xymond_hostdata
> -----Original Message-----
> From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Stephen Carville (xymon list)
> Sent: Sunday, December 31, 2017 1:28 PM
> To: xymon at xymon.com
> Subject: Re: [Xymon] Alerts Stopped Working with DURATION Keyword
>
> On 12/31/2017 08:22 AM, Root, Paul T wrote:
>>
>> What is the owner and group for the file? And with what user/group do you run xymon?
>>
>
> AFAIK, all the processes run as user xymon. Almost all the config files
> are owned by xymon:xymon. A couple that (I think) the webserver has to
> write to are owned by xymon:apache.
>
> $ ls -l
> -rw-rw-r--. 1 xymon xymon 10177 Dec 31 06:55 alerts.cfg
> -rw-rw-r--. 1 xymon xymon 24198 Dec 11 09:11 analysis.cfg
> -rw-r--r--. 1 xymon xymon 2199 Sep 1 16:26 cgioptions.cfg
> -rw-r--r--. 1 xymon xymon 3794 Sep 1 16:26 client-local.cfg
> -rw-r--r--. 1 xymon xymon 11546 Sep 1 16:26 columndoc.csv
> -rw-r--r--. 1 xymon xymon 577 Sep 1 16:26 combo.cfg
> -rw-r--r--. 1 xymon xymon 59 Dec 31 11:11 cookies.session
> -rw-rw-r--. 1 xymon apache 0 Sep 1 16:26 critical.cfg
> -rw-rw-r--. 1 xymon apache 0 Sep 1 16:26 critical.cfg.bak
> -rw-r--r--. 1 xymon xymon 69329 Sep 1 16:26 graphs.cfg
> -rw-r--r--. 1 xymon xymon 3929 Sep 1 16:26 holidays.cfg
> -rw-rw-r--. 1 xymon xymon 483 Nov 14 11:54 hosts.cfg
> drwxrwxr-x. 3 xymon xymon 4096 Dec 30 20:24 hosts.d
> -rw-r--r--. 1 xymon xymon 5684 Sep 8 11:34 protocols.cfg
> -rw-r--r--. 1 xymon xymon 1360 Sep 1 16:26 rrddefinitions.cfg
> -rw-r--r--. 1 xymon xymon 16843 Sep 1 16:26 snmpmibs.cfg
> -rw-r--r--. 1 xymon xymon 10971 Sep 1 16:26 tasks.cfg
> drwxr-xr-x. 2 xymon xymon 6 Sep 1 16:26 tasks.d
> -rw-r--r--. 1 xymon xymon 5482 Sep 1 16:26 xymon-apache.conf
> -rw-r--r--. 1 xymon xymon 3328 Sep 1 16:26 xymonmenu.cfg
> -rw-r--r--. 1 xymon xymon 17547 Sep 20 08:34 xymonserver.cfg
>
> It seemed a little weird to me but I verified that if I remove the
> global read on alerts.cfg, the notifications stop.
>
>> -----Original Message-----
>> From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Stephen Carville (xymon list)
>> Sent: Sunday, December 31, 2017 8:49 AM
>> To: xymon at xymon.com
>> Subject: Re: [Xymon] Alerts Stopped Working with DURATION Keyword
>>
>> On 12/30/2017 09:35 PM, Stephen Carville (xymon list) wrote:
>>>
>>> While trying to add a new alert to alerts.cfg I seem to have killed all
>>> my alerts.
>>
>> Turns out it was -- apparently -- a permissions issue. I changed the
>> perms on alerts.cfg from 0660 to 0664 and the alerts started working
>> correctly again.
>>
>> --
>> _______________________________________________
>> Xymon mailing list
>> Xymon at xymon.com
>> http://lists.xymon.com/mailman/listinfo/xymon
>> This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
>>
>
> _______________________________________________
> Xymon mailing list
> Xymon at xymon.com
> http://lists.xymon.com/mailman/listinfo/xymon
> This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
>
_______________________________________________
Xymon mailing list
Xymon at xymon.com
http://lists.xymon.com/mailman/listinfo/xymon
This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
More information about the Xymon
mailing list