|
I’m now saving $cmd{expires} in bsmon::decode() into
%BigSister::common::current_status which causes it to be written to bsmon.state
and reread upon restart of bsmon. I changed
Statusmon::TrackLast::get_expires to use this value to determine timeouts. Seems to have done the trick… I have restarted
several times now, and waited a few hours with no more premature purples. -Jeff From: Greetings, I
have a couple cpu intensive tests that I run only once a day. In the
status message, the client sets the timeout to status+2880 which as I
understand it makes the timeout 2 days. It works great so long as I
don’t restart the Big Sister server processes. The problem
I’m encountering is following a restart of the server processes (bsmon
& bbd), a period of time will pass, and then all of these long term tests
will turn purple. They change back the next time the client sends a
status for that test, but since it only runs once a day, it can be purple for
quite a while. I
searched the archives to no avail. Perhaps most people don’t run
tests so infrequently and therefore haven’t encountered this? Any
ideas? The BS
server version is bs-0.99b2 and I’m running it on Solaris. Thanks, -Jeff |
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.