Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.4: xinetd wedged!!' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.4: xinetd wedged!!
Authored by: tinker on Jun 05, '05 12:54:37AM
I've done the above, and I've run into a curious situation. If anyone has any suggestions, I'd appreciate it.

The deal is this: I'm running a brand new installation of UW-IMAP on my server. This worked under 10.3.x, but not under 10.4, in the following way. When I run Mail.app at the console, it syncs perfectly with the IMAP server. When I run Mail.app on a remote machine and log in, however, it syncs up to a certain point and then freezes. Net traffic drops to zero, Mail.app stops updating, and eventually it gives up and all folders for that server go grey.

The curious thing is that I can restart the process by typing

sudo kill -9 `cat /var/run/xinetd.pid`

(To give you a sense of how bad things are, I have this command aliased in my .login file.) The xinetd process dies and restarts itself, and Mail.app starts syncing again, for a little while, and then freezes again. Killing xinetd again buys about 20-30 seconds of additional sync time, then freeze. If I want to sync, I have to play this constant game of sync-freeze-kill-sync-freeze-kill. And it's getting old.

I've managed to replicate this behavior with Thunderbird, unfortunately. Actually, all the gory details of this week-long time-waster are on the Apple discussion boards, for the masochistic or morbidly curious.

I've reached the end of my tether. Something seems to be wedging xinetd, but I can't figure out what it is, and I have no idea how to make it stop. Help!!!

[ Reply to This | # ]
10.4: xinetd wedged!!
Authored by: babbage on Jun 09, '05 12:22:20AM

I keep seeing the same thing, and damn if I know why.

Every time I reboot, I've pretty much got a 50/50 chance that IMAP will be working when the system comes back up. It either all works fine, or it's completely inert: the log file shows no activity, attempts to telnet to the IMAP or IMAPS ports fail, and no mail client gets anywhere.

After a lot of painful trial and error, I've more or less got it narrowed down to something choking with xinetd, but who knows what the problem is. If IMAP is wedged, a quick killall -HUP xinetd does the trick, but I can't for the life of me figure out why this is necessary in the first place, or, more mysteriously, why it works half the time and fails half the time.

For now, my oh-so-elegant solution is to just desperately avoid reboots :-/

---

--
DO NOT LEAVE IT IS NOT REAL

[ Reply to This | # ]

10.4: xinetd wedged!!
Authored by: tinker on Nov 20, '05 07:24:56PM
I've discovered an even more inelegant solution to my mail-freeze program -- add

0-55/5 * * * * launchctl unload /Library/launchdaemons/imap3.plist;launchctl unload /Library/launchdaemons/imaps.plist; launchctl load /Library/launchdaemons/imap3.plist;launchctl load /Library/launchdaemons/imaps.plist

to the root crontab. Whatever is causing this freezing behavior rarely happens within the first five minutes of these daemons' execution....

[ Reply to This | # ]