can't connect to mailserver

[flexsurfer]

I have this each time i open status desktop, and when i try to quit the app it doesn't quit by itself i have to force quit
https://youtu.be/k6LpYS1GIMU

Status-debug-logs.zip

[mandrigin]

A few interesting lines in the logs (at different times):
t=2019-04-23T08:43:45+0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="no payload"

t=2019-04-20T17:24:34+0200 lvl=info msg="message loop" peer=2721ca3e5c87d73ce892bd0710f9a78eef4c800f92aeaa7feec8b9b86b62c131 err=EOF
t=2019-04-20T17:24:34+0200 lvl=info msg="message loop" peer=8f7e7c599f831d153f5a8ef24a1c5333f4e3320cfa0474be2f64cacc11d29e68 err=EOF
t=2019-04-20T17:24:37+0200 lvl=info msg="message loop" peer=b3db5b57ddc03be24094603a073b407ceaafc5b78dd6ffb55d4d8d3f5e9cc034 err=EOF
t=2019-04-20T17:24:39+0200 lvl=info msg="message loop" peer=0e969556ca4bf2a0266aed93582ea55f01c09f2431fe84d22d2b7acdf2acb592 err=EOF
t=2019-04-20T17:24:39+0200 lvl=warn msg="failed to deliver envelopes" peer=0e969556ca4bf2a0266aed93582ea55f01c09f2431fe84d22d2b7acdf2acb592 error="write tcp 192.168.0.16:50140->206.189.243.176:30305: write: broken pipe"
t=2019-04-20T17:24:40+0200 lvl=info msg="message loop" peer=40a8cfd21a3a2a45ff6b18c6db3ba5dfe4acd8d4be6c17e84554d648365e7547 err=EOF
t=2019-04-20T17:24:40+0200 lvl=warn msg="failed to deliver envelopes" peer=40a8cfd21a3a2a45ff6b18c6db3ba5dfe4acd8d4be6c17e84554d648365e7547 error="write tcp 192.168.0.16:50136->206.189.243.178:30305: write: broken pipe"
t=2019-04-20T17:24:42+0200 lvl=info msg="message loop" peer=16fc848ef217398e00d82144617c86a2f97b994bacccbbf8cd6e9c8c58615a61 err=EOF
t=2019-04-20T17:24:42+0200 lvl=warn msg="failed to deliver envelopes" peer=16fc848ef217398e00d82144617c86a2f97b994bacccbbf8cd6e9c8c58615a61 error="write tcp 192.168.0.16:50147->206.189.243.179:30305: write: broken pipe"
t=2019-04-20T17:24:45+0200 lvl=info msg="message loop" peer=84d828cecc6d7fa6e4f831501e528f8593999d9972d4e5b46a22defb5fe554b2 err=EOF
t=2019-04-20T17:24:46+0200 lvl=warn msg="failed to deliver envelopes" peer=84d828cecc6d7fa6e4f831501e528f8593999d9972d4e5b46a22defb5fe554b2 error="write tcp 192.168.0.16:50146->47.91.155.62:30305: write: broken pipe"

t=2018-12-21T09:19:08+0100 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-12-21T09:19:08+0100 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-12-21T09:19:08+0100 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-12-21T09:19:08+0100 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="proto: can't skip unknown wire type 4"
t=2018-12-21T09:19:08+0100 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="proto: can't skip unknown wire type 7"

@adambabik @cammellos does that ring a bell to you?

[cammellos]

t=2018-12-21T09:19:08+0100 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-12-21T09:19:08+0100 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-12-21T09:19:08+0100 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-12-21T09:19:08+0100 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="proto: can't skip unknown wire type 4"
t=2018-12-21T09:19:08+0100 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="proto: can't skip unknown wire type 7"

This are not related, should be downgraded to debug (I thought I did, depends on which version of the app they are running)

[adambabik]

Nothing interesting in the first part of logs.

t=2019-04-20T17:24:39+0200 lvl=warn msg="failed to deliver envelopes" peer=0e969556ca4bf2a0266aed93582ea55f01c09f2431fe84d22d2b7acdf2acb592 error="write tcp 192.168.0.16:50140->206.189.243.176:30305: write: broken pipe"

is from Whisper package and it means that the connection was broken.

Also, how the title of this issues is connected with the description? I see on the video that connection to mail server is pretty unstable but finally it stabilizes. That's the problem?

[flexsurfer]

it's really random, it may take a long time to establish a connection in auto mode, but it's not possible to connect in manual mode, before last week it was more stable and fast

[cammellos]

andrey, do you have status logs? they might be more telling

…

On Tue, Apr 23, 2019, 09:57 Andrey ***@***.***> wrote: it's really random, it may take a long time to establish a connection in auto mode, but it's not possible to connect in manual mode, before last week it was more stable and fast — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#8015 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAHYJMCD6ESK6G5OP7AFSH3PR26PZANCNFSM4HHVCISQ> .

[annadanchenko]

@flexsurfer is it still the issue? if so, can you attach Status logs when it happens, please?

[flexsurfer]

yes, it's a big issue for me, unfortunately, there are no logs, but I've sent js logs to @cammellos directly

[cammellos]

I had the same issue at some point, can't replicate yet, but I will take a look at it, generally it looks like we get disconnected from the mailserver periodically and we have to restart the request