Too many `unexpected EOF` in geth.log

[3esmit]

trafficstars

On Status Desktop, geth.log is having lots of log errors at the same second.

example:

t=2018-11-27T12:32:59-0200 lvl=info msg=RequestMessages package=status-go/services/sshext.PublicAPI request="{MailServerPeer:enode://531e252ec966b7e83f5538c19bf1cde7381cc7949026a6e499b6e998e695751aadf26d4c98d5a4eabfb7cefd31c3c88d600a775f14ed5781520a88ecd25da3c6@35.225.227.79:30504 From:1543327141 To:1543329178 Limit:0 Cursor: Topic:[0 0 0 0] Topics:[[172 2 195 198] [58 22 48 97] [128 67 170 140] [23 86 159 125] [241 92 31 250] [205 66 55 96] [248 148 106 172]] SymKeyID:d3571efe441d80096c2ac016cb9baa07e8442b0e5b0a3e2cf93b462919e91143 Timeout:30ns}"
t=2018-11-27T12:32:59-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-11-27T12:32:59-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="proto: can't skip unknown wire type 6"
t=2018-11-27T12:32:59-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-11-27T12:33:00-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="proto: can't skip unknown wire type 7"
t=2018-11-27T12:33:00-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-11-27T12:33:00-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-11-27T12:33:00-0200 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-11-27T12:33:00-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-11-27T12:33:00-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-11-27T12:33:00-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-11-27T12:33:00-0200 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-11-27T12:33:00-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="proto: can't skip unknown wire type 7"
t=2018-11-27T12:33:00-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-11-27T12:33:00-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-11-27T12:33:00-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-11-27T12:33:00-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-11-27T12:33:00-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-11-27T12:33:00-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-11-27T12:33:00-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-11-27T12:33:00-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-11-27T12:33:00-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-11-27T12:33:00-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-11-27T12:35:06-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-11-27T12:37:27-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-11-27T12:39:10-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="proto: can't skip unknown wire type 7"
t=2018-11-27T12:39:50-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-11-27T12:42:01-0200 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-11-27T12:42:25-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-11-27T12:44:15-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-11-27T12:45:05-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-11-27T12:48:15-0200 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-11-27T12:55:48-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-11-27T12:57:32-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-11-27T13:00:04-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"
t=2018-11-27T13:03:03-0200 lvl=eror msg="Failed handling message with error" package=status-go/services/sshext.PublicAPI err="unexpected EOF"

Full log: https://file.io/lLhz8y

Version: https://status-im.ams3.digitaloceanspaces.com/StatusIm-181127-130220-f5a0c2-nightly.exe

This already happened in early versions, from my geth.log I can see it since day 23 this constants errors.

[cammellos]

This is my doing, the error is not a problem (we are just fingerprinting for protobuf messages), I can make it silent at this simply mean that is not a protobuf message.

[3esmit]

I just saw the messages because I was following everything the app is doing in PC. Not sure if should silent it, but having it multiple times per second the same messages is strange.

[status-github-bot[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[mandrigin]

it isn't stale and it is annoying tbh

[cammellos]

I believe this should have already been fixed in latest version of status-go, is there a way to check nowadays as geth.log is not created anymore?

[mandrigin]

the fix is almost there: https://github.com/status-im/status-react/pull/7585

[status-github-bot[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.