-----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 at 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-----
Steffen, I checked 993 since I was using SSL for sending/receiving but imagine it?ll look the same if I check any of the other ports. When I tested via telnet, I checked from my home, not on the server to itself. ?telnet host.com imap? I don?t have an answer for you on the state yet since it?s working at the moment. As far as which processes, I try to connect and no matter what, I don?t get the greeting in this state. I?ll check again in the morning to see if it has changed. That should give it ample time to either just work now or fail then I can do the additional checks. Thanks, Steffan Cline steffan at hldns.com 602-793?0014 On 7/28/15, 10:53 PM, "dovecot on behalf of Steffen Kaiser" <dovecot-bounces at dovecot.org on behalf of skdovecot at smail.inf.fh-brs.de> wrote:>-----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 at 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----- >
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 28 Jul 2015, Steffan Cline wrote: please, don't top post.> I checked 993 since I was using SSL for sending/receiving but imagine it?ll look the same if I check any of the other ports. > > When I tested via telnet, I checked from my home, not on the server to itself. ?telnet host.com imap?Then take Chris's suggestion into account and re-try from localhost in order to rule out network problems.> I don?t have an answer for you on the state yet since it?s working at the moment. > > As far as which processes, I try to connect and no matter what, I don?t get the greeting in this state.Can you connect to other ports of the machine? Or perhaps ping? If the network simply drops all packets, you would get your described problem easily, incl. the SYN_RECV connections.> > On 7/28/15, 10:53 PM, "dovecot on behalf of Steffen Kaiser" <dovecot-bounces at dovecot.org on behalf of skdovecot at smail.inf.fh-brs.de> wrote: > >> -----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 at 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----- >> > >- -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBVbhxKHz1H7kL/d9rAQKsyQf/fHF2Avp2F7eD4h5n0cmdzLMTjolFeW28 tsw81m6o+cs5Vl6cqIzzDIDhC1zRjCOqZWQjv8TNx4S0EKIKscXvurvD2A2WdAOz yeYvQpc5sCABSKMLuUQ5wAR4Hv3pcnpJRN3c9pYRQ48Yxd3ORK8r4BzJ3Ol0RK0H Vn5C05pVYWo+Eh4vLWlWSOTgqaJBwQK9DjfhYZOUdzdx5cMKICn1IHQ9GUBSf6YR TwZMfbYfJYUcq/0s3c6POd9hCEOyQjk7SAhgiXL/LSJtXN39U+Ea2pYD+4/VIPHi FR6Pcb71kqNJmTdEvdPADeKT89l1o5yYju5MU+QKzh23iJ0oiUzPvw==Lgkl -----END PGP SIGNATURE-----