11 Jan
2006
11 Jan
'06
7:52 p.m.
ooookay (and i assume you mean the hobbitd_client service), that does indeed make it Go Away - but, if it ever crashes again for any reason, it will reappear red then go perma-purple again, requiring another manual Drop, yes?
Surely there's a better way to handle this..?
Larry Barber wrote:
The hobbitd_client only issues a status message when it dies. After a restart it will go purple in a half-hour. You just need to do a "drop" of the hobbitd service.
Thanks, Larry Barber
On 1/11/06, *Rob Munsch* <rmunsch at solutionsforprogress.com <mailto:rmunsch at solutionsforprogress.com>> wrote:
So I'm staring at - Program crashed Fatal signal caught! from the purple hobbitd_client status for the server, which is very odd, considering the server (box itself, not just Hobbit binary...) has been completely restarted about an hour ago. There were some horrible, horrible disk problems (many backups and a fsck.reiserfs later... don't ask) due to someone screwing building power whilst i was away and zapping this box with something like 5 restarts in half an hour. ugh. However, having fixed everything else, and up and running from a clean boot, and ONLY running hobbit.sh from the /hobbit/server dir... i'm confused. Hobbitd col shows green. There's only one hobbitd_client running on the box, and it's the one that appeared when the server itself was started. Why does this happen, and how can i stop it? thanks... To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk <mailto:hobbit-unsubscribe at hswn.dk>