I have removed most of what has been added recently. I started with the
items that were less default than the standard. This wasn't the fix. I
did remove an external script that is used as well. I will continue to
remove and see if I can find something.
Regards,
Bryan Kennedy
Olivier Beau
<user-c01e948faffb@xymon.invalid
m> To
user-ae9b8668bcde@xymon.invalid
01/21/2009 01:50 cc
PM
Subject
Re: [hobbit] trends graph stop
Please respond to graphing
user-ae9b8668bcde@xymon.invalid
Hi,
Strange.
Have few tried removing all the hosts you added in your monitoring in
the last 2 months ?
(it could be a client sending bad statuses..)
Do you have any NCV or external scripts for rrd ?
(di you tried disabling those ?)
Olivier
On 21/01/2009 18:30, Bryan A Kennedy wrote:Hi. We are running Hobbit v4.2.0 on a Red Hat Ent Linux WS rel 4 server.
We have been running it for about two years without any issues (Great
tool!). A month and a half ago, the trends graphs stopped graphing. I
restart Hobbit/Xymon and the graphs start working for a few hours, then
stop. The issue is with the status channel graphs. The memory used by
this process starts low as expected, then continues to grow until I
restart
it again. A process listing of that process shows
hobbit 24705 0.0 27.1 1099080 1095804 ? S 03:05 0:00
hobbitd_channel --channel=status --log=/home/hobbit/logs/rrd-status.log
hobbitd_rrd --rrddir=/home/hobbit/data/rrd
It is using 27.1% of the memory (4GB total memory) and I just restarted
Hobbit/Xymon 8 hours ago. I have upgraded the kernel on the server, and
tried various debugging options. I have tried removing changes that
happened around the time of the graphing stop, but nothing has shown the
issue.
Looking in the rrd-status.log I do see entries with garbled data
2009-01-21 11:19:11 Bad data in channel, skipping it
2009-01-21 11:19:11 Dropping (more) garbled data
2009-01-21 11:22:35 Bad data in channel, skipping it
2009-01-21 11:22:35 Dropping (more) garbled data
I am at a loss as to what the problem is. I do plan an upgrade to Xymon
v4.2.2, but wanted to see if I could fix this issue first.
Any help would be greatly appreciated. Thank you in advance for your
time.
Regards,
Bryan Kennedy