Bug#528818: fdm: stale lock file remains present
Hi Nicholas, The bug triggered today. I'll be sending you the log (run with -) is a separate mail personally. Ritesh On Saturday 16 May 2009 22:55:05 Nicholas Marriott wrote: Okay, thanks. Let me know. On Sat, May 16, 2009 at 10:13:44PM +0530, Ritesh Raj Sarraf wrote: On Saturday 16 May 2009 13:51:00 Nicholas Marriott wrote: fdm will only remove the lock file if it exits normally (success or a normal error), it will not remove it on a fatal error (which means a bug) or on SIGKILL, and it is never going to since I want to know about these cases and fix them. Please send me the - log of a session (don't forget to remove passwords and anything else sensitive) when it is interrupted and leaves behind a lock file. I suspected that you'd ask me to do this. :-) No problem. I'll set it to run with - and wait for the next trigger. Ritesh -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention. -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention. signature.asc Description: This is a digitally signed message part.
Bug#528818: fdm: stale lock file remains present
fdm will only remove the lock file if it exits normally (success or a normal
error), it will not remove it on a fatal error (which means a bug) or on
SIGKILL, and it is never going to since I want to know about these cases and
fix them. Please send me the - log of a session (don't forget to remove
passwords and anything else sensitive) when it is interrupted and leaves behind
a lock file.
On Sat, May 16, 2009 at 01:50:00AM +0530, Ritesh Raj Sarraf wrote:
Package: fdm
Version: 1.6-1
Severity: normal
Hi Frank,
There seems to be a problem with the lock file in fdm.
I currently have fdm configured to fetch emails fromi a pop3 server every
10 minutes, using a cron job.
In .fdm.conf, I'm using the following to ensure that there's only one
instance of fdm running.
# Lock file path.
set lock-file ${base}/lock
Since I run it on a laptop, which I frequently keep
connecting/disconnecting and hibernating, at some point this gets
triggered while fdm is running.
I guess that is when sometime fdm is dying and is leaving a stale lock
file.
This then leads to no further fdm processes running because they
see the lock file and assume that an fdm process is already running.
Thus I end up with receiving no email messages until I realise that fdm
has left a stale lock file. Once I manually remove it, every thing runs
as normal.
IMO fdm should handle such error conditions and remove the lock file
when such circumstances trigger.
Ritesh
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.29-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages fdm depends on:
ii adduser 3.110 add and remove users and groups
ii libc62.9-12 GNU C Library: Shared libraries
ii libpcre3 7.8-2+b1Perl 5 Compatible Regular
Expressi
ii libssl0.9.8 0.9.8g-16 SSL shared libraries
ii libtdb1 1.1.3~git20090221-1 Trivial Database - shared library
ii zlib1g 1:1.2.3.3.dfsg-13 compression library - runtime
fdm recommends no packages.
fdm suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528818: fdm: stale lock file remains present
On Saturday 16 May 2009 13:51:00 Nicholas Marriott wrote: fdm will only remove the lock file if it exits normally (success or a normal error), it will not remove it on a fatal error (which means a bug) or on SIGKILL, and it is never going to since I want to know about these cases and fix them. Please send me the - log of a session (don't forget to remove passwords and anything else sensitive) when it is interrupted and leaves behind a lock file. I suspected that you'd ask me to do this. :-) No problem. I'll set it to run with - and wait for the next trigger. Ritesh -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention. signature.asc Description: This is a digitally signed message part.
Bug#528818: fdm: stale lock file remains present
Okay, thanks. Let me know. On Sat, May 16, 2009 at 10:13:44PM +0530, Ritesh Raj Sarraf wrote: On Saturday 16 May 2009 13:51:00 Nicholas Marriott wrote: fdm will only remove the lock file if it exits normally (success or a normal error), it will not remove it on a fatal error (which means a bug) or on SIGKILL, and it is never going to since I want to know about these cases and fix them. Please send me the - log of a session (don't forget to remove passwords and anything else sensitive) when it is interrupted and leaves behind a lock file. I suspected that you'd ask me to do this. :-) No problem. I'll set it to run with - and wait for the next trigger. Ritesh -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528818: fdm: stale lock file remains present
Package: fdm
Version: 1.6-1
Severity: normal
Hi Frank,
There seems to be a problem with the lock file in fdm.
I currently have fdm configured to fetch emails fromi a pop3 server every
10 minutes, using a cron job.
In .fdm.conf, I'm using the following to ensure that there's only one
instance of fdm running.
# Lock file path.
set lock-file ${base}/lock
Since I run it on a laptop, which I frequently keep
connecting/disconnecting and hibernating, at some point this gets
triggered while fdm is running.
I guess that is when sometime fdm is dying and is leaving a stale lock
file.
This then leads to no further fdm processes running because they
see the lock file and assume that an fdm process is already running.
Thus I end up with receiving no email messages until I realise that fdm
has left a stale lock file. Once I manually remove it, every thing runs
as normal.
IMO fdm should handle such error conditions and remove the lock file
when such circumstances trigger.
Ritesh
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.29-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages fdm depends on:
ii adduser 3.110 add and remove users and groups
ii libc62.9-12 GNU C Library: Shared libraries
ii libpcre3 7.8-2+b1Perl 5 Compatible Regular Expressi
ii libssl0.9.8 0.9.8g-16 SSL shared libraries
ii libtdb1 1.1.3~git20090221-1 Trivial Database - shared library
ii zlib1g 1:1.2.3.3.dfsg-13 compression library - runtime
fdm recommends no packages.
fdm suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
