Bug#728747: courier-mta won't start randomly at boot
This is definitely still an issue, a serious one, and trivial to fix. The problem is that the courier packages are basically orphaned. There have been some new people trying to pick it up, but basically we need a new maintainer. On 3/6/16 12:11, Thomas Mayer wrote: May be obsolete now, but I can confirm that some of courier's services randomly don't get started after rebooting a virtual server (presumably OpenVZ) after it was updated to Debian jessie and systemd. The system also got moved to a newer host system which now provides kernel 3.16. Besides courier, the system runs totally stable. All courier services run fine if I start services manually after reboots: service courier-authdaemon start service courier-mta start service courier-mta-ssl start service courier-pop start service courier-pop-ssl start ... The system is up-to-date so it seems that the issue still needs to be fixed (Ondřej Surý pointed that out already if I got it right). I can confirm that adding courier-authdaemon as a requirement solves this issue for me (tried 5 times whereas unstarted courier-services originally were quite common at about 50% of tries). The changed line 5 of /etc/init.d/courier-mta now reads: # Required-Start:$remote_fs $syslog courier-authdaemon So the fix should be small and trivial and solves a big problem which occurs randomly while people might not even be aware of it. I think this issue could be fixed without the necessity of larger changes in package management.
Bug#728747: courier-mta won't start randomly at boot
May be obsolete now, but I can confirm that some of courier's services randomly don't get started after rebooting a virtual server (presumably OpenVZ) after it was updated to Debian jessie and systemd. The system also got moved to a newer host system which now provides kernel 3.16. Besides courier, the system runs totally stable. All courier services run fine if I start services manually after reboots: service courier-authdaemon start service courier-mta start service courier-mta-ssl start service courier-pop start service courier-pop-ssl start ... The system is up-to-date so it seems that the issue still needs to be fixed (Ondřej Surý pointed that out already if I got it right). I can confirm that adding courier-authdaemon as a requirement solves this issue for me (tried 5 times whereas unstarted courier-services originally were quite common at about 50% of tries). The changed line 5 of /etc/init.d/courier-mta now reads: # Required-Start:$remote_fs $syslog courier-authdaemon So the fix should be small and trivial and solves a big problem which occurs randomly while people might not even be aware of it. I think this issue could be fixed without the necessity of larger changes in package management. -- Thomas Mayer 2bis10 IT-Services UG (haftungsbeschränkt) https://www.2bis10.de
Bug#728747: courier-mta won't start randomly at boot
I was having the same problem with jessie except that courier-mta never seemed to start. I see :; sudo systemctl status courier-mta.service -l * courier-mta.service - LSB: Courier SMTP server Loaded: loaded (/etc/init.d/courier-mta) Active: failed (Result: exit-code) since Sat 2015-07-25 15:19:51 CEST; 5h 8min ago Process: 579 ExecStart=/etc/init.d/courier-mta start (code=exited, status=1/FAILURE) Jul 25 15:19:51 foo courier-mta[579]: chgrp: cannot access ‘/var/run/courier’: No such file or directory Jul 25 15:19:51 foo systemd[1]: courier-mta.service: control process exited, code=exited status=1 Jul 25 15:19:51 foo systemd[1]: Failed to start LSB: Courier SMTP server. Jul 25 15:19:51 foo systemd[1]: Unit courier-mta.service entered failed state. I added courier-authdaemon to the Required-Start: line in /etc/init.d/courier-mta and rebooted twice. courier-mta started correctly each time. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728747: courier-mta won't start randomly at boot
Package: courier-mta Version: 0.68.2-1 Followup-For: Bug #728747 I believe that I am experiencing this same bug, but am not completely sure. I just set up an new host on an OpenVZ container, and I don't have access to the boot console messages, so I don't know if Courier-MTA and my other courier daemons are tossing errors during boot. I don't see anything in syslog, and I don't know of anything way I can get the console log without the help of my hosting provider, which isn't likely. I suspect the reason I am seeing this is because the host is a very fast OpenVZ container. I was having repeated and reliable problems with Courier-MTA starting at boot. Starting the init script manually after boot always resulted in a successful start. Courier-IMAP was often starting, but courier-mta and courier-mta-ssl would not start. Notably, occasionally courier-mta-ssl *would* successfully start at boot. I believe I have fixed the problem by adding courier-authdaemon to the Required-Start: line in the courier init scripts where appropriate and then running update-rc.d against the courier init scripts. Please change the courier daemon init scripts to include courier-authdaemon as a dependency. -- System Information: Debian Release: 7.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-042stab081.5 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages courier-mta depends on: ii courier-authlib0.63.0-6+b1 ii courier-base 0.68.2-1 ii debconf [debconf-2.0] 1.5.49 ii libc6 2.13-38+deb7u1 ii libgcc11:4.7.2-5 ii libgdbm3 1.8.3-11 ii libperl5.145.14.2-21+deb7u1 ii libstdc++6 4.7.2-5 courier-mta recommends no packages. Versions of packages courier-mta suggests: pn courier-doc none pn courier-filter-perl none pn couriergrey none ii emacs23 [mail-reader] 23.4+1-4 ii heirloom-mailx [mail-reader] 12.5-2 ii mutt [mail-reader]1.5.21-6.2+deb7u2 -- Configuration Files: /etc/courier/aliases/system [Errno 13] Permission denied: u'/etc/courier/aliases/system' /etc/courier/courierd changed [not included] /etc/courier/dsnheader.txt changed [not included] /etc/courier/esmtpauthclient [Errno 13] Permission denied: u'/etc/courier/esmtpauthclient' /etc/courier/esmtpd changed [not included] /etc/courier/esmtpd-msa changed [not included] /etc/courier/esmtpd.cnf [Errno 2] No such file or directory: u'/etc/courier/esmtpd.cnf' /etc/courier/smtpaccess/default [Errno 13] Permission denied: u'/etc/courier/smtpaccess/default' /etc/init.d/courier-mta changed [not included] -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728747: courier-mta won't start randomly at boot
Looks like /var/run/courier is missing resp. not yet created. Regards Racke Yes, but question is, why sometimes there is, and sometimes not. Maybe courier-authdaemon create /var/run/courier and when it's not started before courier-mta then problem occurs? Can be this problem with depend boot and startpar? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728747: courier-mta won't start randomly at boot
courier-authdaemon init script create /var/run/courier directory at start.
courier-mta not.
Solution is add this to courier-mta init script too, or start courier-mta after
courier-authdaemon on boot.
--- courier-mta 2013-11-05 18:47:49.570983400 +0100
+++ courier-mta_new 2013-11-05 18:48:20.942638100 +0100
@@ -15,2 +15,3 @@ sbindir=${exec_prefix}/sbin
libexecdir=${prefix}/lib/courier
+rundir_courier=/var/run/courier
DAEMON=${sbindir}/esmtpd
@@ -41,6 +42,11 @@ start)
cd /
+
+ if [ ! -d $rundir_courier ]; then
+ mkdir -m 0775 $rundir_courier
+ chown daemon:daemon $rundir_courier
+ fi
# ensure proper permissions on /var/run/courier
- chgrp daemon /var/run/courier
- chmod g+rwx /var/run/courier
+ chgrp daemon $rundir_courier
+ chmod g+rwx $rundir_courier
Bug#728747: courier-mta won't start randomly at boot
Package: courier-mta Version: 0.68.2-1 courier-mta (courierd) won't start randomly at boot. Random error is: - chgrp: cannot access `/var/run/courier': No such file or directory [ ok ] Starting Courier authentication services: authdaemond. [FAIL] startpar: service(s) returned failure: courier-mta ... failed! - Sometimes it's ok without errors. This can be some init problem with starpar and start order. I am using up to date wheezy. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728747: courier-mta won't start randomly at boot
On 11/05/2013 12:58 AM, punjab wrote: Package: courier-mta Version: 0.68.2-1 courier-mta (courierd) won't start randomly at boot. Random error is: - chgrp: cannot access `/var/run/courier': No such file or directory [ ok ] Starting Courier authentication services: authdaemond. [FAIL] startpar: service(s) returned failure: courier-mta ... failed! - Sometimes it's ok without errors. This can be some init problem with starpar and start order. I am using up to date wheezy. Looks like /var/run/courier is missing resp. not yet created. Regards Racke -- LinuXia Systems = http://www.linuxia.de/ Expert Interchange Consulting and System Administration ICDEVGROUP = http://www.icdevgroup.org/ Interchange Development Team -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
