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" <kspringer at innovateteam.com> 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"--progressKris 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"--progressAlert 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