Menu
▾
▴
Re: [Devmon] [hobbit] RE: Devmon Turning Purple
|
From: Taylor L. <tl...@tr...> - 2008-03-31 13:47:37
|
I had a similar setup, and since applying the patch and removing my cron job I haven't seen devmon go purple, its been up for about 9 days solid, so its working for me. Before that is was going purple at least once every 2 days even with a cronjob to restart it every 4 hours... -----Original Message----- From: dev...@li... [mailto:dev...@li...] On Behalf Of Whilding, Craig Sent: Monday, March 31, 2008 8:37 AM To: dev...@li... Subject: Re: [Devmon] [hobbit] RE: Devmon Turning Purple Apologies for not getting back to you about this sooner, I was off work last week. I have now applied the patched files on our server and removed the cron job that restarted devmon. I will let you know if I have any more problems or if this has fixed it. Thanks, Craig -----Original Message----- From: Buchan Milne [mailto:bg...@st...] Sent: 25 March 2008 09:34 To: dev...@li... Cc: Whilding, Craig Subject: Re: [Devmon] [hobbit] RE: Devmon Turning Purple On Wednesday 05 March 2008 16:41:05 Whilding, Craig wrote: > I've discovered something with this purple problem. If the module that > parses hobbit client data isn't running then devmon seems to remain > fine. > > Basically on one of our servers that runs a proxy sending data to > localhost and our main server one of the modules has died so that no > linux client data gets to the local display. Haven't quite worked out > what will have died yet as I need to run a diff with another box to > check the dead channel but whatever it was it seems to be the service > that devmon disagreed with. > > Any progress on debugging what devmon code causes the problem in the > first place? I can leave this broken for now on mine as the local > display is only a backup if the wan link fails. I managed to reproduce the issue, and I think it is fixed with this commit: http://devmon.svn.sourceforge.net/devmon/?rev=82&view=rev I will test it in production (but I see this issue about once in two weeks in our production environment) this week. I reproduced it by stopping hobbit after devmon had sent at least one status message (i.e. start devmon while hobbit is running), then stopping hobbitit before the next attempt to send a status message. devmon would hang, and log nothing more to the log. With the fix available in the patch from the url above, it will continue logging and running. I have also fixed the "don't poll a device hobbit thinks is down" feature. If there aren't any more serious issues to resolve, I think another release is in order ... maybe 0.3.0 final. Regards, Buchan ------------------------------------------------------------------------ - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketp lace _______________________________________________ Devmon-support mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devmon-support |
