bugtrack at dbmail
Jul 28, 2009, 10:08 PM
Post #1 of 1
(491 views)
Permalink
|
|
[DBMail 0000600]: killall -HUP dbmail-imapd sometimes kills process
|
|
The following issue has been CLOSED
======================================================================
http://dbmail.org/mantis/view.php?id=600
======================================================================
Reported By: bjohnson
Assigned To:
======================================================================
Project: DBMail
Issue ID: 600
Category: IMAP daemon
Reproducibility: unable to reproduce
Severity: minor
Priority: normal
Status: closed
target:
Resolution: open
Fixed in Version:
======================================================================
Date Submitted: 23-May-07 19:54 CEST
Last Modified: 29-Jul-09 07:08 CEST
======================================================================
Summary: killall -HUP dbmail-imapd sometimes kills process
Description:
Reported against dbmail-2.2.5rc3.
I have been getting reports that the package I make for Fedora/CentOS has
a problem that the daemon(s) die every Sunday morning. This led me to look
at the log rotation script which rotates the logs on Sunday morning.
After the rotation, it does a "/usr/bin/killall -HUP dbmail-lmtpd
dbmail-imapd dbmail-pop3d dbmail-timsieved &> /dev/null" to have the
processes switch to the new empty logs.
Apparently, at least under some circumstances, this actually kills the
daemons. Today I was able to reproduce this on the imap daemon with:
/usr/bin/killall -HUP dbmail-imapd which made the entire imap process
die.
I don't know if I can extract some log information or not, but I'll give
it a try.
======================================================================
----------------------------------------------------------------------
(0002219) aaron (administrator) - 28-May-07 17:39
http://dbmail.org/mantis/view.php?id=600#c2219
----------------------------------------------------------------------
I haven't reproduced the problem yet, but even so, try this instead:
kill -HUP `cat /var/run/dbmail-<daemon>.pid`
Or wrap it in a for loop:
for i in `ls /var/run/dbmail*pid &>/dev/null`; do kill -HUP `cat $i`; done
----------------------------------------------------------------------
(0002232) bjohnson (reporter) - 05-Jun-07 17:41
http://dbmail.org/mantis/view.php?id=600#c2232
----------------------------------------------------------------------
Aaron, I think you meant this, right?
for pid in `ls /var/run/dbmail*\.pid`; do kill -HUP `cat $pid` &>
/dev/null; done
I haven't been able to reproduce the probem recently, but I'll update to
your method and see how it goes.
----------------------------------------------------------------------
(0002252) bjohnson (reporter) - 23-Jun-07 09:19
http://dbmail.org/mantis/view.php?id=600#c2252
----------------------------------------------------------------------
I was able to trigger this again today using your method of kill (by pid
file). Everytime that I've managed to trigger it so far, it's been when
the service has been running for days or weeks.
----------------------------------------------------------------------
(0002255) aaron (administrator) - 23-Jun-07 20:59
http://dbmail.org/mantis/view.php?id=600#c2255
----------------------------------------------------------------------
I added the freopen call you need for log rotation. Perhaps something about
how your log rotator is doing its job that did not interact well with us
hanging onto the original log file in spite of the HUP?
Hopefully after 2.2.6 this bug will be moot!
----------------------------------------------------------------------
(0002256) bjohnson (reporter) - 23-Jun-07 21:26
http://dbmail.org/mantis/view.php?id=600#c2256
----------------------------------------------------------------------
Actually, this last time I triggered it, it had nothing to do with the log
rotation - I was running the kill -HUP loop by and and the dbmail-imapd
just died.
----------------------------------------------------------------------
(0002274) paul (administrator) - 03-Jul-07 22:27
http://dbmail.org/mantis/view.php?id=600#c2274
----------------------------------------------------------------------
Is this still happening? I'm setting this report to unreproduceable.
Without further reports this issue will be closed...
----------------------------------------------------------------------
(0002281) bjohnson (reporter) - 04-Jul-07 00:21
http://dbmail.org/mantis/view.php?id=600#c2281
----------------------------------------------------------------------
Yes, it's still happening. It's happened as recent as Jul 1.
I've tried a couple of times to connect a debugger to the process and send
a SIGHUP by hand, but I've never been able to trigger it when the debugger
is attached.
----------------------------------------------------------------------
(0002874) netvulture (developer) - 29-Jul-09 07:08
http://dbmail.org/mantis/view.php?id=600#c2874
----------------------------------------------------------------------
Paul and reporter was unable to reproduce with debugger. I am unable to
reproduce in the 2.3.x branch. Closing ticket
Issue History
Date Modified Username Field Change
======================================================================
23-May-07 19:54 bjohnson New Issue
28-May-07 17:39 aaron Note Added: 0002219
05-Jun-07 17:41 bjohnson Note Added: 0002232
19-Jun-07 22:02 nethzt Issue Monitored: nethzt
23-Jun-07 09:19 bjohnson Note Added: 0002252
23-Jun-07 20:59 aaron Note Added: 0002255
23-Jun-07 21:26 bjohnson Note Added: 0002256
03-Jul-07 22:27 paul Note Added: 0002274
03-Jul-07 22:27 paul Severity major => minor
03-Jul-07 22:27 paul Reproducibility random => unable to
reproduce
03-Jul-07 22:27 paul Status new => feedback
04-Jul-07 00:21 bjohnson Note Added: 0002281
29-Jul-09 07:08 netvulture Note Added: 0002874
29-Jul-09 07:08 netvulture Status feedback => closed
======================================================================
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
|
