Re: imapd problem.
On Tue, 2004-10-05 at 08:59 +0300, Perttu Laine wrote: I have problem with imapd. I can't start dovecot 'cause it says this: -- koaze# /usr/local/sbin/dovecot Fatal: listen(143) failed: Address already in use koaze# I appreciate your choice in IMAP servers. :) But I don't know what could be using that address. I had cyrus for a while, but I removed it and ps aux show nothing that could use imapd port. Only other email app running is postfix as smtp. `ps aux' doesn't show which ports are in use. For that, you should use the most wonderful sockstat(1). Running something like this should show you the Address already in use culprit: 'sockstat -4 | egrep :143\W' So. What could be wrong here? Exactly what the error message says: the address is already in use. Trust error messages: they're almost never wrong, especially when they're straight from libc. signature.asc Description: This is a digitally signed message part
Re: imapd problem.
Perttu Laine [EMAIL PROTECTED] writes: Hello! I have problem with imapd. I can't start dovecot 'cause it says this: -- koaze# /usr/local/sbin/dovecot Fatal: listen(143) failed: Address already in use koaze# -- But I don't know what could be using that address. I had cyrus for a while, but I removed it and ps aux show nothing that could use imapd port. Only other email app running is postfix as smtp. So. What could be wrong here? *Something* is holding the port. You can find out what with: sockstat | grep 143 -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org:8088/~lowell/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: imapd problem.
Here's my message to the mailing list too. For some reason my mailer replied to the person who replied and not to the mailing list even tho I tried to do that. :) Damn webmails.. 'sockstat -4 | egrep :143\W' -cut- root inetd 531 8 tcp4 *:143 *:* -cut- So. it's inetd. Now the question is why 'cause only ssh is not commented in inetd.conf (or then I should re-check it few times). And how I can stop that one? Regards, Perttu Laine ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: imapd problem.
On Tue, 2004-10-05 at 17:40 +0300, Perttu Laine wrote: 'sockstat -4 | egrep :143\W' -cut- root inetd 531 8 tcp4 *:143 *:* -cut- So. it's inetd. Now the question is why 'cause only ssh is not commented in inetd.conf (or then I should re-check it few times). And how I can stop that one? Something running under the name of 'inetd' is binding to port 143 on all inet4 addresses. Either that, or there's a bug in sockstat or the kernel structures that it manipulates, though I've not seen mention of that anywhere. Maybe it's an old instance of inetd from a changed configuration? Perhaps you changed its configuration but forgot to restart it? Trust your tools, for you are lost without them. By the way, please remember to CC the list when responding to people. That way, your responses get archived for all to see years from now when they have the same or similar problems. signature.asc Description: This is a digitally signed message part
Re: imapd problem.
Something running under the name of 'inetd' is binding to port 143 on all inet4 addresses. Either that, or there's a bug in sockstat or the kernel structures that it manipulates, though I've not seen mention of that anywhere. Maybe it's an old instance of inetd from a changed configuration? Perhaps you changed its configuration but forgot to restart it? Funny. killall -HUP inetd helped. I didn't even need to do changes in inetd.conf. I should've just tried to restart it instead of checking config. No idea what I've been doing. Too much vodka perhaps - I'm from Finland you know. ;P Regards, Perttu Laine ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
