Xymon Mailing List Archive search

allevents stops updating after trimhistory

3 messages in this thread

list John Glowacki · Tue, 03 Oct 2006 15:03:17 -0400 · 
Henrik,

On Solaris 9 hobbit 4.1.2 and RedHat 4 hobbit 4.2 I ran trimhistory and
noticed the next day that no events were listed at the bottom of the bb2
page. Working on my 4.2 test system I found hist/allevents stopped
updating after running trimhistory. Restarting hobbit got it working
again. Hobbit should not require any additional restarts after running
trimhistory or it should be mentioned in the man page.

Thanks,
John
list Henrik Størner · Wed, 4 Oct 2006 07:27:50 +0200 ·
▸ quoted from John Glowacki
On Tue, Oct 03, 2006 at 03:03:17PM -0400, John Glowacki wrote:

On Solaris 9 hobbit 4.1.2 and RedHat 4 hobbit 4.2 I ran trimhistory and
noticed the next day that no events were listed at the bottom of the bb2
page. Working on my 4.2 test system I found hist/allevents stopped
updating after running trimhistory. Restarting hobbit got it working
again. Hobbit should not require any additional restarts after running
trimhistory or it should be mentioned in the man page.
I think you're right about this. The hobbitd_history module keeps the
"allevents" file open while it is running, so trimhistory needs to
signal that it should re-open the new (truncated) file. Killing
hobbitd_history (it restarts automatically) fixes this, but that 
shouldn't be needed.


Regards,
Henrik
list Rich Smrcina · Sun, 08 Oct 2006 16:37:55 -0500 · 
This was duplicated on SLES9, I killed hobbitd_history as suggested and new events appeared.
▸ quoted from Henrik Størner

Henrik Stoerner wrote:
On Tue, Oct 03, 2006 at 03:03:17PM -0400, John Glowacki wrote:

On Solaris 9 hobbit 4.1.2 and RedHat 4 hobbit 4.2 I ran trimhistory and
noticed the next day that no events were listed at the bottom of the bb2
page. Working on my 4.2 test system I found hist/allevents stopped
updating after running trimhistory. Restarting hobbit got it working
again. Hobbit should not require any additional restarts after running
trimhistory or it should be mentioned in the man page.
I think you're right about this. The hobbitd_history module keeps the
"allevents" file open while it is running, so trimhistory needs to
signal that it should re-open the new (truncated) file. Killing
hobbitd_history (it restarts automatically) fixes this, but that shouldn't be needed.


Regards,
Henrik


-- 

Rich Smrcina
VM Assist, Inc.
Phone: XXX-XXX-XXXX
Ans Service:  XXX-XXX-XXXX
user-61add9955ef9@xymon.invalid

Catch the WAVV!  http://www.wavv.org
WAVV 2007 - Green Bay, WI - May 18-22, 2007