Xymon Mailing List Archive search

ran Trimhistory and it broke something

6 messages in this thread

list Kris Springer · Tue, 23 Mar 2021 10:41:27 -0600 ·
Per the instructions found at https://xymon.sourceforge.io/xymon/help/manpages/man8/trimhistory.8.html I ran the following command to trim my very old log history and ever since then I'm getting the following crash alert.? Also when reviewing history via the webpage I get results but the time stamps are wonky.? I suspect it's because of the program crashing.
Anyone know how to fix?

Trimhistory command I used:
$ ./trimhistory --drop --dropsvcs --droplogs --cutoff=`date +%s --date="1 Jan 2019"` --progress

Alert I'm receiving:
xymond_history purple [549922]
red - Program crashed

Fatal signal caught!

-- 

Kris Springer
list Kris Springer · Tue, 23 Mar 2021 11:41:17 -0600 ·
Upon further searching of mailing list I came across this. https://lists.xymon.com/archive/2019-February/046058.html
I re-ran my command with the 'sudo -u xymon' addition and it worked and xymond_history isn't crashing anymore.

$ cd /home/xymon/server/bin/
$ sudo -u xymon ./trimhistory --drop --dropsvcs --droplogs --cutoff=`date +%s --date="1 Jan 2019"` --progress

Kris Springer
quoted from Kris Springer


Per the instructions found at https://xymon.sourceforge.io/xymon/help/manpages/man8/trimhistory.8.html I ran the following command to trim my very old log history and ever since then I'm getting the following crash alert.? Also when reviewing history via the webpage I get results but the time stamps are wonky.? I suspect it's because of the program crashing.
Anyone know how to fix?

Trimhistory command I used:
$ ./trimhistory --drop --dropsvcs --droplogs --cutoff=`date +%s --date="1 Jan 2019"` --progress

Alert I'm receiving:
xymond_history purple [549922]
red - Program crashed

Fatal signal caught!

-- 

Kris Springer
list Kris Springer · Wed, 31 Mar 2021 11:27:46 -0600 ·
I'm still getting xymond_history crash notifications exactly every 4 hours.? I've looked in /var/log/xymon/ but there's doesn't seem to be any logs that give a clue as to what's happening.

Here's the notification I'm getting exactly every 4 hours.
*xymond_history purple [672384] *
quoted from Kris Springer

*red - Program crashed Fatal signal caught!*


Kris Springer

On 3/23/21 11:41 AM, Kris Springer wrote:
Upon further searching of mailing list I came across this. https://lists.xymon.com/archive/2019-February/046058.html

I re-ran my command with the 'sudo -u xymon' addition and it seemed to work.
quoted from Kris Springer

$ cd /home/xymon/server/bin/
$ sudo -u xymon ./trimhistory --drop --dropsvcs --droplogs --cutoff=`date +%s --date="1 Jan 2019"` --progress

Kris Springer


Per the instructions found at https://xymon.sourceforge.io/xymon/help/manpages/man8/trimhistory.8.html I ran the following command to trim my very old log history and ever since then I'm getting the following crash alert.? Also when reviewing history via the webpage I get results but the time stamps are wonky.? I suspect it's because of the program crashing.
Anyone know how to fix?

Trimhistory command I used:
$ ./trimhistory --drop --dropsvcs --droplogs --cutoff=`date +%s --date="1 Jan 2019"` --progress

Alert I'm receiving:
xymond_history purple [549922]
red - Program crashed

Fatal signal caught!

-- 

Kris Springer

list Jeremy · Wed, 31 Mar 2021 21:28:52 +0000 ·
Hi Kris,

It might be an idea to check for files owned by root under the data directory and change them to xymon.

HTH

Jeremy
quoted from Kris Springer

------ Original Message ------
From: "Kris Springer" <user-c2caa0a7a8d5@xymon.invalid>
To: "Xymon MailingList" <xymon at xymon.com>
Sent: 31/03/2021 18:27:46
Subject: Re: [Xymon] ran Trimhistory and it broke something
I'm still getting xymond_history crash notifications exactly every 4 hours.  I've looked in /var/log/xymon/ but there's doesn't seem to be any logs that give a clue as to what's happening.

Here's the notification I'm getting exactly every 4 hours.
xymond_history purple [672384]
red - Program crashed

Fatal signal caught!

Kris Springer


On 3/23/21 11:41 AM, Kris Springer wrote:
Upon further searching of mailing list I came across this.  https://lists.xymon.com/archive/2019-February/046058.html
I re-ran my command with the 'sudo -u xymon' addition and it seemed to work.

$ cd /home/xymon/server/bin/
$ sudo -u xymon ./trimhistory --drop --dropsvcs --droplogs --cutoff=`date +%s --date="1 Jan 2019"` --progress

Kris Springer


Per the instructions found at https://xymon.sourceforge.io/xymon/help/manpages/man8/trimhistory.8.html I ran the following command to trim my very old log history and ever since then I'm getting the following crash alert.  Also when reviewing history via the webpage I get results but the time stamps are wonky.  I suspect it's because of the program crashing.
Anyone know how to fix?

Trimhistory command I used:
$ ./trimhistory --drop --dropsvcs --droplogs --cutoff=`date +%s --date="1 Jan 2019"` --progress

Alert I'm receiving:
xymond_history purple [549922]
red - Program crashed

Fatal signal caught!

--

Kris Springer

-- 

This email has been checked for viruses by AVG.
https://www.avg.com
list Jeremy Laidman · Thu, 1 Apr 2021 10:26:03 +1100 ·
Perhaps run the xymond_history command manually via strace and see what it
was doing just before it crashed.
quoted from Jeremy

On Thu, 1 Apr 2021, 08:29 Jeremy, <user-6d8e227afca3@xymon.invalid> wrote:
Hi Kris,

It might be an idea to check for files owned by root under the data
directory and change them to xymon.

HTH

Jeremy

------ Original Message ------
From: "Kris Springer" <user-c2caa0a7a8d5@xymon.invalid>
To: "Xymon MailingList" <xymon at xymon.com>
Sent: 31/03/2021 18:27:46
Subject: Re: [Xymon] ran Trimhistory and it broke something

I'm still getting xymond_history crash notifications exactly every 4
hours.  I've looked in /var/log/xymon/ but there's doesn't seem to be any
logs that give a clue as to what's happening.

Here's the notification I'm getting exactly every 4 hours.
*xymond_history purple [672384] *

*red - Program crashed

Fatal signal caught!*


Kris Springer


On 3/23/21 11:41 AM, Kris Springer wrote:

Upon further searching of mailing list I came across this.
https://lists.xymon.com/archive/2019-February/046058.html
I re-ran my command with the 'sudo -u xymon' addition and it seemed to
work.

$ cd /home/xymon/server/bin/
$ sudo -u xymon ./trimhistory --drop --dropsvcs --droplogs --cutoff=`date
+%s --date="1 Jan 2019"` --progress

Kris Springer


Per the instructions found at
https://xymon.sourceforge.io/xymon/help/manpages/man8/trimhistory.8.html
I ran the following command to trim my very old log history and ever since
then I'm getting the following crash alert.  Also when reviewing history
via the webpage I get results but the time stamps are wonky.  I suspect
it's because of the program crashing.
Anyone know how to fix?

Trimhistory command I used:
$ ./trimhistory --drop --dropsvcs --droplogs --cutoff=`date +%s --date="1
Jan 2019"` --progress

Alert I'm receiving:

xymond_history purple [549922]
red - Program crashed

Fatal signal caught!


--

Kris Springer


<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>; Virus-free.
www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>;
<#m_-1312679790177835085_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

list Kris Springer · Mon, 5 Apr 2021 13:26:25 -0600 ·
I ran the following command and it found a few mrtg files that were owned by root user instead of xymon user, but everything else is owned by xymon user.
$ find /home/xymon/data/ -user root

Kris Springer
quoted from Jeremy


On 3/31/21 3:28 PM, Jeremy wrote:
Hi Kris,

It might be an idea to check for files owned by root under the data directory and change them to xymon.

HTH

Jeremy

------ Original Message ------
From: "Kris Springer" <user-c2caa0a7a8d5@xymon.invalid <mailto:user-c2caa0a7a8d5@xymon.invalid>>
To: "Xymon MailingList" <xymon at xymon.com <mailto:xymon at xymon.com>>
Sent: 31/03/2021 18:27:46
Subject: Re: [Xymon] ran Trimhistory and it broke something
I'm still getting xymond_history crash notifications exactly every 4 hours. I've looked in /var/log/xymon/ but there's doesn't seem to be any logs that give a clue as to what's happening.

Here's the notification I'm getting exactly every 4 hours.
*xymond_history purple [672384] *
*red - Program crashed Fatal signal caught!*

Kris Springer

On 3/23/21 11:41 AM, Kris Springer wrote:
Upon further searching of mailing list I came across this. https://lists.xymon.com/archive/2019-February/046058.html
I re-ran my command with the 'sudo -u xymon' addition and it seemed to work.

$ cd /home/xymon/server/bin/
$ sudo -u xymon ./trimhistory --drop --dropsvcs --droplogs --cutoff=`date +%s --date="1 Jan 2019"` --progress

Kris Springer


Per the instructions found at https://xymon.sourceforge.io/xymon/help/manpages/man8/trimhistory.8.html I ran the following command to trim my very old log history and ever since then I'm getting the following crash alert.? Also when reviewing history via the webpage I get results but the time stamps are wonky.? I suspect it's because of the program crashing.
Anyone know how to fix?

Trimhistory command I used:
$ ./trimhistory --drop --dropsvcs --droplogs --cutoff=`date +%s --date="1 Jan 2019"` --progress

Alert I'm receiving:
xymond_history purple [549922]
red - Program crashed

Fatal signal caught!

-- 

Kris Springer

<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>; 	Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>; 

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>