-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tue, 28 Jul 2015, Steffan Cline wrote:
When dovecot stops accepting connections, I checked netstat and found this:
[root@hosting1 ~]# netstat -an | grep 993 tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN tcp 0 0 65.39.x.x:993 184.101.x.x:36351 SYN_RECV tcp 0 0 65.39.x.x:993 107.212.x.x:51487 SYN_RECV tcp 0 0 65.39.x.x:993 107.212.x.x:51488 SYN_RECV tcp 0 0 65.39.x.x:993 184.101.x.x:44650 SYN_RECV
This told me it wasn’t too many connections causing dovecot to be unresponsive. So then I tried via telnet.
Dovecot seems to accept connections but then just sits there and does nothing. I used the appropriate commands to try and initiate a login but nothing happens. Typing any commands at all produce no response from dovecot.
I then do a “service dovecot restart” and then telnet again and get this:
- OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
from which host do you telnet to Dovecot and to which port? Do you get the greeting (last line of your quote), if you telnet? You show port 993 in above listing, which is the IMAP-over-SSL port, you should not see the greeting with telnet on this port at all.
In which state are the various dovecot processes in? Do they wait in non-interruptable sleep? ps -eopid,user,fname,state,wchan,args
Do all Dovecot processes hang or just new ones, that try to connect and auth?
Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1
iQEVAwUBVbhqXHz1H7kL/d9rAQJbKQgAlzwvfDNSlP2oliX1SaCFqeiE+mhcZCz/ XUe2ffnw5AYH0hW7jcur7BHpGZM7ajK1drcGy5OGPYTGEknaMRMnaiBza726Qyjc sDoVZD+YR25gtjNAGrqNYyMxNBLyx3JB3CeG0ljcqmxZ4BC1mOAdwjOSUaJsUqPX EOBC+PXE51GWxnPq7XwcEZ36mXAEmaLnyKWhA9CZuwfB9Q9yxJahc3u2yEnAVh+Y kFF/TJksmYQ+GfKAtTEi+S/e2+3xCq6XgS2daEjwr7SDrhV/0Lvz5PW18MqQtUjU IcF72VzJ1/BruU+eawL2G+JUJ1wdmmFBszPyjJtRTB2sMHk/KDXroQ== =7wRT -----END PGP SIGNATURE-----