Replies: 1 comment
-
the same problem |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
This is what my error and warning log looks like for 24 hours. Before the update, there were 0-5 such errors.
2022-05-14 08:58:33 WARNING Was not able to get peername from 118.150.162.190 - closing connection
2022-05-14 09:37:00 WARNING [Errno 32] Broken pipe 220.184.199.245
2022-05-14 09:41:16 WARNING [Errno 104] Connection reset by peer 61.85.117.82
2022-05-14 10:54:26 WARNING [Errno 32] Broken pipe 113.103.63.128
2022-05-14 11:46:54 WARNING Cannot write to closing transport 183.220.83.33
2022-05-14 11:46:59 WARNING Cannot write to closing transport 183.220.83.33
2022-05-14 12:01:49 WARNING _process: InvalidIdentifierError Invalid identifier: Actual {'message_id': 1, 'sync_id': 1652518866, 'timestamp': 1652518907}, Expected {'message_id': 2, 'sync_id': 1652518866, 'timestamp': 1652518907}
2022-05-14 12:01:54 WARNING _process: InvalidIdentifierError Invalid identifier: Actual {'message_id': 1, 'sync_id': 1652518866, 'timestamp': 1652518907}, Expected {'message_id': 2, 'sync_id': 1652518866, 'timestamp': 1652518907}
2022-05-14 12:04:40 WARNING Cannot write to closing transport 51.174.90.235
2022-05-14 13:57:17 WARNING Cannot write to closing transport 69.132.12.125
2022-05-14 15:59:55 WARNING Cannot write to closing transport 85.21.84.178
2022-05-14 17:22:44 WARNING Cannot write to closing transport 47.219.93.122
2022-05-14 17:22:49 WARNING Cannot write to closing transport 47.219.93.122
2022-05-14 17:25:26 WARNING Banning 190.193.63.173 for 10 seconds
2022-05-14 17:25:26 WARNING Invalid handshake with peer. Maybe the peer is running old software.
2022-05-14 17:25:31 WARNING Invalid handshake with peer. Maybe the peer is running old software.
2022-05-14 19:09:27 WARNING [Errno 32] Broken pipe 223.157.60.166
2022-05-14 19:10:32 WARNING [Errno 104] Connection reset by peer 101.86.81.142
2022-05-14 20:26:31 WARNING Cannot write to closing transport 153.232.119.31
2022-05-14 20:26:36 WARNING Cannot write to closing transport 153.232.119.31
2022-05-14 20:29:53 WARNING [Errno 32] Broken pipe 182.200.32.7
2022-05-14 20:38:57 WARNING [Errno 32] Broken pipe 106.117.98.123
2022-05-14 20:52:04 WARNING [Errno 104] Connection reset by peer 120.227.30.137
2022-05-14 21:28:00 WARNING Error while handling message: Traceback (most recent call last):
2022-05-14 21:28:41 WARNING Cannot write to closing transport 186.19.91.71
2022-05-14 21:28:46 WARNING Cannot write to closing transport 186.19.91.71
2022-05-14 21:37:40 ERROR Task exception was never retrieved
2022-05-14 22:06:39 WARNING Cannot write to closing transport 62.93.4.33
2022-05-14 22:06:44 WARNING Cannot write to closing transport 62.93.4.33
2022-05-14 22:23:07 WARNING Cannot write to closing transport 166.70.242.208
2022-05-14 23:53:41 WARNING Banning 75.105.233.247 for 10 seconds
2022-05-14 23:53:41 WARNING Invalid handshake with peer. Maybe the peer is running old software.
2022-05-15 00:06:13 WARNING _process: InvalidIdentifierError Invalid identifier: Actual {'message_id': 1, 'sync_id': 1652562303, 'timestamp': 1652562369}, Expected {'message_id': 2, 'sync_id': 1652562303, 'timestamp': 1652562369}
2022-05-15 00:06:18 WARNING _process: InvalidIdentifierError Invalid identifier: Actual {'message_id': 1, 'sync_id': 1652562303, 'timestamp': 1652562369}, Expected {'message_id': 2, 'sync_id': 1652562303, 'timestamp': 1652562369}
2022-05-15 00:26:28 WARNING [Errno 32] Broken pipe 123.144.63.7
2022-05-15 01:37:19 WARNING Cannot write to closing transport 109.240.245.20
2022-05-15 01:37:24 WARNING Cannot write to closing transport 109.240.245.20
2022-05-15 01:37:29 WARNING Cannot write to closing transport 109.240.245.20
2022-05-15 01:48:15 WARNING [Errno 32] Broken pipe 186.148.127.229
2022-05-15 01:54:38 WARNING _process: InvalidIdentifierError Invalid identifier: Actual {'message_id': 0, 'sync_id': 1652568854, 'timestamp': 1652568874}, Expected {'message_id': 1, 'sync_id': 1652568854, 'timestamp': 1652568874}
2022-05-15 02:12:48 WARNING _process: InvalidIdentifierError Invalid identifier: Actual {'message_id': 0, 'sync_id': 1652569937, 'timestamp': 1652569957}, Expected {'message_id': 1, 'sync_id': 1652569937, 'timestamp': 1652569957}
2022-05-15 02:12:53 WARNING _process: InvalidIdentifierError Invalid identifier: Actual {'message_id': 0, 'sync_id': 1652569937, 'timestamp': 1652569957}, Expected {'message_id': 1, 'sync_id': 1652569937, 'timestamp': 1652569957}
2022-05-15 05:27:35 WARNING Was not able to get peername from 190.193.63.173 - closing connection
2022-05-15 05:27:40 WARNING Was not able to get peername from 190.193.63.173 - closing connection
2022-05-15 06:04:51 WARNING Cannot write to closing transport 36.110.58.83
2022-05-15 06:42:02 WARNING [Errno 104] Connection reset by peer 125.79.116.249
2022-05-15 06:42:13 WARNING Cannot write to closing transport 88.235.216.105
2022-05-15 07:15:52 WARNING Cannot write to closing transport 195.248.161.16
Beta Was this translation helpful? Give feedback.
All reactions