Bug#512369: fails to configure when an IMAP server is not available
On 16/11/10 00:57, José Luis Tallón wrote: > Thanks. Will apply. Great, thanks! > Even though the fix can't possibly enter Squeeze (unfortunately), I will > try and have it in the next version. > Mind sponsoring the upload ? Talk to the release-team. Installation problems are something they might be willing to let through. If they aren't it may be a good idea to wait until squeeze's release (usual argument about uploading to unstable during a freeze). As for sponsoring: sure, no problem, but still considering the argumets above. Cheers -- Leo "costela" Antunes [insert a witty retort here] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#512369: fails to configure when an IMAP server is not available
severity #512369 normal tags #512369 +patch thanks Leo 'costela' Antunes wrote: > Hi, > > [snip] > How about calling dh_installinit with "--no-start" and manually calling > "invoke-rc.d imapproxy start || true" on fresh installs? Possibly > throwing a warning? > I just think its unnecessary to botch the whole install for failing to > start up (which is OTH totally understandable when the default fresh > config doesn't match reality) > Thanks. Will apply. Even though the fix can't possibly enter Squeeze (unfortunately), I will try and have it in the next version. Mind sponsoring the upload ? Cheers, J.L. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#512369: fails to configure when an IMAP server is not available
Hi, Just my two cents on this relatively old bug which just happen to hit me: I understand the need for avoiding user interaction on install and all, but simply failing the installation with the standard debconf priority seems a bit sloppy IMHO, specially considering it's not that rare to have imapproxy running in a different machine as the IMAP server (or even having an IMAP server with TSL/SSL, etc). How about calling dh_installinit with "--no-start" and manually calling "invoke-rc.d imapproxy start || true" on fresh installs? Possibly throwing a warning? I just think its unnecessary to botch the whole install for failing to start up (which is OTH totally understandable when the default fresh config doesn't match reality) Cheers -- Leo "costela" Antunes [insert a witty retort here] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#512369: fails to configure when an IMAP server is not available
severity 512369 normal thanks On Tue, Jan 20, 2009 at 01:59:24PM +0100, Thijs Kinkhorst wrote: > > subprocess post-installation script returned error exit status 1 > > > I'd expect retrying in the background or even leaving it disabled, but > > postinst failure seems too intrusive. > > Well, you supplied it with localhost as the IMAP server name, or installed > it with a too high debconf priority and thus implicitly accepted this > setting: Yes. Possibly the medium priority is too low, but that's fine tuning. > So the same things happens in all packages that use > debhelper to take care of init script installation and encounter some kind > of configuration that is not compatible with the local situation. It could be a remote situation as well if it's not 'localhost': network outage, remote server downtime etc. > I think that it's logical that a service that can't be started after > installation causes the installation to give an error. You are then given > the option to correct the situation and finish the installation later. The keyword for me here is 'proxy'. I think a proxy should be able to start even when the remote server is (possibly temporarily) unavailable. Just issuing a warning at startup would be fine. If the server refuses the connection, so should the proxy. But OK, I can see this probably shouldn't be RC. Thanks and sorry for the noise. -- Niko Tyni nt...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#512369: fails to configure when an IMAP server is not available
Hi Niko, > Setting up imapproxy (1.2.6-4) ... > Starting IMAP proxy: invoke-rc.d: initscript imapproxy, action "start" > failed. > dpkg: error processing imapproxy (--configure): > subprocess post-installation script returned error exit status 1 > I'd expect retrying in the background or even leaving it disabled, but > postinst failure seems too intrusive. Well, you supplied it with localhost as the IMAP server name, or installed it with a too high debconf priority and thus implicitly accepted this setting: > -- debconf information: > imapproxy/imap-server: localhost It is customary for Debian packages to start a service right after installation. In fact, the code that does this in the imapproxy package is inserted by debhelper. So the same things happens in all packages that use debhelper to take care of init script installation and encounter some kind of configuration that is not compatible with the local situation. I think that it's logical that a service that can't be started after installation causes the installation to give an error. You are then given the option to correct the situation and finish the installation later. If you think services should not be started after installation, or that if such a service errors installation should be continued regardless, I think you should reassign the bug to debhelper. I'm not sure what should be changed on the imapproxy package since 'localhost' seems like a sensible default for me if the user skips the debconf questions, and I do not know of a better default that would solve your problem. cheers, Thijs -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#512369: fails to configure when an IMAP server is not available
Package: imapproxy Version: 1.2.6-4 Severity: serious This package fails to configure with the default settings when an IMAP server can't be reached on localhost:143. Setting up imapproxy (1.2.6-4) ... Starting IMAP proxy: invoke-rc.d: initscript imapproxy, action "start" failed. dpkg: error processing imapproxy (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: imapproxy Jan 20 09:10:38 testhost imapproxyd: main(): Using configuration file '/etc/imapproxy.conf' Jan 20 09:10:38 testhost imapproxyd: Using syslog facility 'LOG_MAIL' for logging. Jan 20 09:10:38 testhost in.imapproxyd[18812]: No syslog priority mask specified. Jan 20 09:10:38 testhost in.imapproxyd[18812]: main(): SELECT caching is disabled Jan 20 09:10:38 testhost in.imapproxyd[18812]: main(): Internal admin commands are disabled Jan 20 09:10:38 testhost in.imapproxyd[18812]: main(): Allocating 3072 IMAP connection structures. Jan 20 09:10:38 testhost in.imapproxyd[18812]: ServerInit(): Using '/var/log/imapproxy_protocol.log' for global protocol logging file. Jan 20 09:10:38 testhost in.imapproxyd[18812]: ServerInit(): proxying to IMAP server 'localhost'. Jan 20 09:10:38 testhost in.imapproxyd[18812]: ServerInit(): Proxying to IMAP port 143 Jan 20 09:10:38 testhost in.imapproxyd[18812]: ServerInit(): Connection refused -- exiting I'd expect retrying in the background or even leaving it disabled, but postinst failure seems too intrusive. See also #512272, which makes the postinst hang if configured with an invalid hostname. Release team, please downgrade if this is considered acceptable for the release. -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-xen-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages imapproxy depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii libc6 2.7-16 GNU C Library: Shared libraries ii libncurses5 5.7+20081213-1 shared libraries for terminal hand ii libssl0.9.8 0.9.8g-14 SSL shared libraries ii libwrap0 7.6.q-16 Wietse Venema's TCP wrappers libra ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip imapproxy recommends no packages. imapproxy suggests no packages. -- debconf information: imapproxy/imap-server: localhost -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
