Hide Forgot
From Bugzilla Helper: User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830 Description of problem: I am running squirrelmail-1.2.8-1 with imap-2001a-15 and xinetd-2.3.7-2. Periodically, imapd stops successfully responding to connection requests, and requires xinetd to be restarted. After restarting xinetd, imapd will respond properly for a while...but will eventually wedge again. Version-Release number of selected component (if applicable): imap-2001a-15 How reproducible: Sometimes Steps to Reproduce: 1.Set SquirrelMail to use imap: IMAP Server : localhost IMAP Port : 143 2.Enable imap using ntsysv and restart xinetd. 3.Let it run for a day or so, and watch it eventually fail. Actual Results: When wedged, /var/log/maillog gets this: Nov 12 20:22:38 gateway imapd[9936]: imap service init from 127.0.0.1 Nov 12 20:23:00 gateway imapd[9937]: imap service init from 127.0.0.1 Expected Results: When operating normally, /var/log/maillog records: Nov 12 20:26:19 gateway imapd[9971]: imap service init from 127.0.0.1 Nov 12 20:26:19 gateway imapd[9971]: Login user=vsmith host=gateway.codegnome.org [127.0.0.1] Nov 12 20:26:19 gateway imapd[9971]: Logout user=vsmith host=gateway.codegnome.org [127.0.0.1] Additional info: Enabling the -cc flag for xinetd creates the following errors in /var/log/messages. This error appears immediately, not just when imap gets wedged. Nov 11 19:16:21 gateway xinetd[15551]: descriptor 3 set in socket mask but there is no service for it Nov 11 19:16:21 gateway xinetd[15551]: Consistency check detected 1 errors
Same here on my production server---- Are there any workarounds?
Seen similar too - go back to the older xinetd seems to cure it Reassigned to xinetd
I've been having problems with my mailserver recently, although not identical to the above. When using mutt it would occasionally hang for a couple of minutes; I presume that during that time the connection would time out and be recreated. I've had nothing untoward in /var/log/{messages,maillog}. Anyway, I just downgraded to xinetd-2.3.4-0.8 and I'll let you know if the problems continue.
FYI my problems went away after downgrading to xinetd-2.3.4-0.8.
Reassigning bug to xinetd package maintainer.
Red Hat Linux is no longer supported by Red Hat, Inc. If you are still running Red Hat Linux, you are strongly advised to upgrade to a current Fedora Core release or Red Hat Enterprise Linux or comparable. Some information on which option may be right for you is available at http://www.redhat.com/rhel/migrate/redhatlinux/. Red Hat apologizes that these issues have not been resolved yet. We do want to make sure that no important bugs slip through the cracks. Please check if this issue is still present in a current Fedora Core release. If so, please change the product and version to match, and check the box indicating that the requested information has been provided. Note that any bug still open against Red Hat Linux on will be closed as 'CANTFIX' on September 30, 2006. Thanks again for your help.
Red Hat Linux is no longer supported by Red Hat, Inc. If you are still running Red Hat Linux, you are strongly advised to upgrade to a current Fedora Core release or Red Hat Enterprise Linux or comparable. Some information on which option may be right for you is available at http://www.redhat.com/rhel/migrate/redhatlinux/. Closing as CANTFIX.