Bug 523156
| Summary: | Dovecot fails to start when calling restart in init script | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Martin Steel <martin> |
| Component: | dovecot | Assignee: | Michal Hlavinka <mhlavink> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | qe-baseos-daemons |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 5.3 | CC: | ovasik, ralph |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-03-15 15:43:55 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
I'll look at this, but I can't reproduce this. I've run following command for four hours (approx. 10 000 dovecot's restarts) but everything has worked. while true; do service dovecot restart >restart.log ; sleep 1 ; service dovecot status >status; grep -q 'is running' <status || break; done (the 1 sec sleep is there to be sure dovecot has enough time to daemonize, it'd report "dovecot dead but subsys locked" otherwise) This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. This request was erroneously denied for the current release of Red Hat Enterprise Linux. The error has been fixed and this request has been re-proposed for the current release. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. I am sorry, but it is now too late in the RHEL-5 release cycle. RHEL-5.10 (the next RHEL-5 minor release) is going to be the first production phase 2 [1] release of RHEL-5. Since phase 2 we'll be addressing only security and critical issues. This issue should not exit in RHEL-6, therefore I am closing the bug as NEXTRELEASE. [1] https://access.redhat.com/support/policy/updates/errata/ |
Description of problem: Restarting Dovecot through the init script sometimes fails to start the dovecot daemon. There appears to be a similar issue with HUP signals but I'm unable to reproduce to a suitable level to file a bug. Version-Release number of selected component (if applicable): Dovecot version: 1.0.7 Redhat version: 5.3 How reproducible: Intermittent fault, Dovecot doesn't always fail to start on restart. Steps to Reproduce: 1. Restart dovecot using the init script i.e. /etc/init.d/dovecot restart 2. Repeat if necessary. Actual results: Dovecot daemon fails to start. /etc/init.d/dovecot restart Content of /var/log/dovecot: dovecot: Sep 14 09:54:27 Warning: Killed with signal 15 dovecot: Sep 14 09:54:27 Info: Dovecot v1.0.7 starting up dovecot: Sep 14 09:54:27 Error: Auth process died too early - shutting down dovecot: Sep 14 09:54:27 Error: auth(default): Socket already exists: /var/run/dovecot/auth-master dovecot: Sep 14 09:54:27 Error: child 3768 (auth) returned error 89 Expected results: Dovecot daemon to stop and then start. Expected log contents: dovecot: Sep 14 09:53:27 Warning: Killed with signal 15 dovecot: Sep 14 09:53:27 Info: Dovecot v1.0.7 starting up dovecot: Sep 14 09:53:28 Info: auth-worker(default): mysql: Connected to proddb.mediaburst.net (vmail) Additional info: Dovecot configuration (from dovecot -n): # 1.0.7: /etc/dovecot.conf log_path: /var/log/dovecot protocols: pop3 listen: * login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/pop3-login first_valid_uid: 150 last_valid_uid: 150 first_valid_gid: 150 last_valid_gid: 150 mail_location: maildir:/var/vmail/%d/%n/Maildir mail_executable: /usr/libexec/dovecot/pop3 mail_plugin_dir: /usr/lib/dovecot/pop3 auth default: user: vmail passdb: driver: pam passdb: driver: sql args: /etc/dovecot-mysql.conf userdb: driver: passwd userdb: driver: sql args: /etc/dovecot-mysql.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail MySQL authentication file /etc/dovecot-mysql.conf contains: driver = mysql connect = host=my_server port=3308 dbname=vmail user=vmail password=my_password password_query = SELECT password FROM mailbox WHERE username = '%n' AND domain = '%d' user_query = SELECT '/var/vmail/%d/%n' as home, 'maildir:/var/vmail/%d/%n' as mail, 150 AS uid, 150 AS gid FROM mailbox WHERE username ='%n' AND domain = '%d' AND active ='1'