ok, so I'm not worried about the "Will not Change" errors. How about the Whoops errors? What could cause them?<br><br>Like I said before, I applied a patch you gave me about non-blocking sockets to try to get rid of this. Is there a way to increase the timeout period? This box is under a fairly heavy load at times. Load average stays a constant 3.0 and peaks up to 10-12. And if I do a top, I show a lot of CPU time spent in iowait.<br>
<br>$ nice top<br> 06:58:13 up 102 days, 20:31, 1 user, load average: 3.40, 3.58, 3.60<br>149 processes: 148 sleeping, 1 running, 0 zombie, 0 stopped<br>CPU states: cpu user nice system irq softirq iowait idle<br>
total 0.0% 0.0% 0.4% 0.1% 0.0% 42.4% 56.8%<br> cpu00 0.0% 0.0% 0.0% 0.0% 0.0% 0.0% 100.0%<br> cpu01 0.9% 0.0% 0.9% 0.0% 0.0% 98.0% 0.0%<br>
cpu02 0.0% 0.0% 0.0% 0.0% 0.0% 0.0% 100.0%<br> cpu03 0.0% 0.0% 0.0% 0.0% 0.0% 0.0% 100.0%<br> cpu04 0.0% 0.0% 0.0% 0.0% 0.0% 100.0% 0.0%<br>
cpu05 0.0% 0.0% 0.0% 0.0% 0.0% 44.1% 55.8%<br> cpu06 0.0% 0.0% 0.0% 0.0% 0.0% 36.2% 63.7%<br> cpu07 0.0% 0.0% 0.9% 0.0% 0.0% 62.3% 36.6%<br>
cpu08 0.0% 0.0% 0.9% 0.0% 0.0% 0.0% 99.0%<br> cpu09 0.0% 0.0% 0.0% 0.0% 0.0% 100.0% 0.0%<br> cpu10 0.0% 0.0% 0.9% 0.0% 0.0% 0.0% 99.0%<br>
cpu11 0.0% 0.0% 0.0% 0.0% 0.0% 0.0% 100.0%<br> cpu12 0.0% 0.0% 1.9% 1.9% 0.0% 96.0% 0.0%<br> cpu13 0.0% 0.0% 0.0% 0.0% 0.0% 43.5% 56.4%<br>
cpu14 0.0% 0.0% 0.9% 0.0% 0.0% 35.6% 63.3%<br> cpu15 0.0% 0.0% 100.0% 0.0% 0.0% 0.0% 0.0%<br>Mem: 16411504k av, 15428124k used, 983380k free, 0k shrd, 168924k buff<br>
7224252k actv, 5861544k in_d, 981512k in_c<br>Swap: 2096472k av, 0k used, 2096472k free 14649352k cached<br><br><br>Stew<br><br><br><div class="gmail_quote">On Fri, Mar 28, 2008 at 5:34 AM, Henrik Stoerner <<a href="mailto:henrik@hswn.dk">henrik@hswn.dk</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">On Thu, Mar 27, 2008 at 04:48:00PM -0400, Stewart L wrote:<br>
> Not sure if this is related to my issue about Whoops errors or not, but it<br>
> seems that the history does not always update correctly when a service goes<br>
> down.<br>
><br>
> Seems to be the same problem as here...<br>
><br>
> <a href="http://www.hswn.dk/hobbiton/2008/03/msg00064.html" target="_blank">http://www.hswn.dk/hobbiton/2008/03/msg00064.html</a><br>
><br>
> My history.log shows no issues... Bunch of "Will not update <server.test> -<br>
> color unchanged" messages.<br>
<br>
</div>This is not a problem if the errors appear after restarting Hobbit.<br>
<br>
History updates are normally only logged when the color of a status<br>
changes. However, during a restart color changes might happen while<br>
the history module is not up and running, so the first status that<br>
Hobbit receives after a restart is always sent to the history module.<br>
This message is then logged when the history module detects that the<br>
color hasn't changed, and it drops the update.<br>
<br>
Since updates will usually trickle in from clients during the first<br>
5-10 minutes of Hobbit running, you will see this for a few minutes<br>
after a restart.<br>
<br>
Of course, if this happens without Hobbit having been restarted, it<br>
is more interesting.<br>
<br>
<br>
Regards,<br>
Henrik<br>
<br>
<br>
To unsubscribe from the hobbit list, send an e-mail to<br>
<a href="mailto:hobbit-unsubscribe@hswn.dk">hobbit-unsubscribe@hswn.dk</a><br>
<br>
<br>
</blockquote></div><br><br clear="all"><br>-- <br>Stewart<br><br>The revolution will not be televised.<br>The revolution will be no re-run brothers;<br>The revolution will be live.