Bug#941129: fetchmail: pidfile behavior changed
On Sat, Sep 28, 2019 at 12:28 PM Alex Andreotti wrote: > On Sat, Sep 28, 2019 at 09:15:42AM +0200, László Böszörményi (GCS) wrote: > > Can you revert to 6.4.0~rc3-1 and check it? But I'm going to update > > the packaging to the fixed upstream release. Please test that anyway. > > I tried, 6.4.0~rc3-1 worked, from 6.4.0~rc4-1 it doesn't work anymore. Ouch. It seems it's upstream matter then and Matthias already fixed that with the stable release. > As far as I'm concerned you can close the bug, I'm also happy with > --pidfile, I opened it for your information. OK, already done. Cheers, Laszlo/GCS
Bug#941129: fetchmail: pidfile behavior changed
On Sat, Sep 28, 2019 at 03:22:51AM +0200, Matthias Andree wrote: [cut] > fetchmail behaved inconsistently between daemon and non-detaching modes > in the upstream version without Debian patches already until 6.4.0-rc4, > and that needed fixing, and is what I've fixed. > > If there are additional issues, I hope the package maintainer (Laszlo) > can see to them. I assume that for some reason with the old versions the script I am using was not affected, it worked with relative path, I hadn't modified it for years before finding the problem a few days ago. On Sat, Sep 28, 2019 at 09:15:42AM +0200, László Böszörményi (GCS) wrote: [cut] > Can you revert to 6.4.0~rc3-1 and check it? But I'm going to update > the packaging to the fixed upstream release. Please test that anyway. I tried, 6.4.0~rc3-1 worked, from 6.4.0~rc4-1 it doesn't work anymore. As far as I'm concerned you can close the bug, I'm also happy with --pidfile, I opened it for your information. Many thanks to you both for your time and support
Bug#941129: fetchmail: pidfile behavior changed
On Sat, Sep 28, 2019 at 1:03 AM Alex Andreotti wrote: > Attention, I was using it with a relative path and it worked, the > behavior change is that it stopped working, I believe with one of the > two updates below: This would be strange, but let's see the changes. > September 4 > > fetchmail (6.4.0~rc4-1) unstable; urgency=medium This removed several patches, all of those merged upstream previously I believe. 02_fetchmail-mode.el.diff: it was for the contrib/fetchmail-mode.el emacs hook, no effect on fetchmail working. 03_typo-manpage.diff: it's a typo in the manpage. 06_sni-support.patch: support SNI for servers like GMail has. > September 6 > > fetchmail (6.4.0~rc4-2) unstable; urgency=medium Removed the fetchmailconf binary and its manpage from the package, this doesn't alter fetchmail itself. Can you revert to 6.4.0~rc3-1 and check it? But I'm going to update the packaging to the fixed upstream release. Please test that anyway. Thanks, Laszlo/GCS
Bug#941129: fetchmail: pidfile behavior changed
Am 28.09.19 um 00:59 schrieb Alex Andreotti: > Attention, I was using it with a relative path and it worked, the > behavior change is that it stopped working, I believe with one of the > two updates below: fetchmail behaved inconsistently between daemon and non-detaching modes in the upstream version without Debian patches already until 6.4.0-rc4, and that needed fixing, and is what I've fixed. If there are additional issues, I hope the package maintainer (Laszlo) can see to them. > > September 4 > > fetchmail (6.4.0~rc4-1) unstable; urgency=medium > > * New major upstream RC release. > * Remove outdated and Python 2 only fetchmailconf package (closes: > #936512). > * Drop merged in patches. > * Update remaining patches. > * Remove old upgrade code from postinst. > > September 6 > > fetchmail (6.4.0~rc4-2) unstable; urgency=medium > > * Remove all parts of fetchmailconf (closes: #939522).
Bug#941129: fetchmail: pidfile behavior changed
Attention, I was using it with a relative path and it worked, the behavior change is that it stopped working, I believe with one of the two updates below: September 4 fetchmail (6.4.0~rc4-1) unstable; urgency=medium * New major upstream RC release. * Remove outdated and Python 2 only fetchmailconf package (closes: #936512). * Drop merged in patches. * Update remaining patches. * Remove old upgrade code from postinst. September 6 fetchmail (6.4.0~rc4-2) unstable; urgency=medium * Remove all parts of fetchmailconf (closes: #939522).
Bug#941129: fetchmail: pidfile behavior changed
Control: tags -1 confirmed upstream Alex, thanks for your report, you've found a very long-standing inconsistency in fetchmail's behaviour. The workaround is to give an *absolute* path for FETCHMAILHOME in daemon mode. This will be fixed in 6.4.0.
Bug#941129: fetchmail: pidfile behavior changed
Package: fetchmail Version: 6.4.0~rc4-2 Severity: normal Dear Maintainer, * What led up to the situation? I have been using fetchmail for several years to download mail from multiple accounts, one instance for each account using the FETCHMAILHOME variable. I realized only today that it was a few days since it was no longer downloading mail. The script that I use enters the directories of the various accounts, sets the variable FETCHMAILHOME and uses the default values Looking at the log file I saw this message (ACCOUNT is the email): ./ACCOUNT/fetchmail.pid: No such file or directory fetchmail: lock creation failed. If I create the file, before launching fetchmail, is correctly removed: fetchmail: removing stale lockfile but later the lock fails (ACCOUNT is the email): 7426 openat(AT_FDCWD, "./ACCOUNT/fetchmail.pid", O_WRONLY|O_CREAT|O_EXCL, 0666) = -1 ENOENT (No such file or directory) 7426 dup(2)= 4 7426 fcntl(4, F_GETFL) = 0x8401 (flags O_WRONLY|O_APPEND|O_LARGEFILE) 7426 close(4) = 0 7426 write(2, "./ACCOUNT/fetch"..., 68) = 68 7426 write(2, "fetchmail: lock creation failed."..., 33) = 33 7426 exit_group(8) = ? 7426 +++ exited with 8 +++ To make fetchmail work again I had to specify the pidfile as argument (FETCHMAILHOME is relative, not an absolute path) --pidfile "$FETCHMAILHOME/fetchmail.pid" -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fetchmail depends on: ii adduser 3.118 ii debianutils 4.9 ii libc6 2.29-2 ii libcom-err2 1.45.3-4 ii libgssapi-krb5-2 1.17-6 ii libkrb5-3 1.17-6 ii libssl1.1 1.1.1d-1 ii lsb-base 11.1.0 Versions of packages fetchmail recommends: ii ca-certificates 20190110 Versions of packages fetchmail suggests: pn fetchmailconf ii postfix [mail-transport-agent] 3.4.7-1 ii resolvconf 1.79 -- no debconf information
