|
From: Dan F. <da...@ha...> - 2006-12-01 16:57:54
|
Lionel Bouton wrote: > Michael Zimmermann wrote the following on 30.11.2006 23:49 : > >> after running a while sqlgrey stops working. The logs show, that it >> restarted, but it's >> port is closed after the restart. >> > > It could be the old sqlgrey process still living and bound to the socket > when the new one comes up (the underlying Net::Server::Multiplex library > has already demonstrated this behaviour on my systems). My solution was to : > 1/ add a long enough sleep between the TERM signal (sqlgrey -k or > killall sqlgrey for example) and the restart. > My other policy daemon actually did this from time to time, though i dont recall sqlgrey doing it. My solution was first the "sleep 2" thingie, but i then solved it by adding "Reuse => 1" to the creation of Net::Server. It seemed that the socket wasnt released fast enough and adding "Reuse" should allow it to... Well.. Reuse the socket ;) Ive also had a similar problem with postgrey back in the days, which was due to the cleanup running for to long time which made postfix believe it was offline. (though i dont remember if the socket actually died). If Michaels problem persists, socket "Reuse" might be worth a try. - Dan Faerch |