Bonjour,
Suite à la réinitialisation de mon OTB effectuée au début du mois, j'ai remarqué certaines erreurs dans les logs système.
Ce sont principalement des pertes de connexion du tunnel et des erreurs timed out, mais cela affecte beaucoup la qualité de la navigation.
Voici une partie des logs système que j'ai récupéré :
> Sun Apr 21 06:32:26 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 06:36:45 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5001 milliseconds
> Sun Apr 21 06:36:51 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 06:43:23 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5001 milliseconds
> Sun Apr 21 06:43:29 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5001 milliseconds
> Sun Apr 21 06:47:52 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5001 milliseconds
> Sun Apr 21 06:47:58 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5001 milliseconds
> Sun Apr 21 06:48:04 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5001 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 06:50:16 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5001 milliseconds
> Sun Apr 21 06:50:22 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 06:52:35 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5001 milliseconds
> Sun Apr 21 06:52:41 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 06:52:47 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 06:55:00 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5000 milliseconds
> Sun Apr 21 06:55:01 2019 daemon.err graph[15953]: curl: (28) Operation timed out after 10000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 06:55:06 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 06:55:12 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5000 milliseconds
> Sun Apr 21 06:55:16 2019 daemon.err graph[7406]: curl: (28) Operation timed out after 10000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 06:55:18 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5001 milliseconds
> Sun Apr 21 06:57:30 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5001 milliseconds
> Sun Apr 21 06:57:32 2019 daemon.err graph[8827]: curl: (28) Operation timed out after 10001 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 06:57:36 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 06:57:42 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5001 milliseconds
> Sun Apr 21 06:57:47 2019 daemon.err graph[20900]: curl: (28) Operation timed out after 10000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 06:57:48 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 07:00:01 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5001 milliseconds
> Sun Apr 21 07:00:03 2019 daemon.err graph[22238]: curl: (28) Operation timed out after 10001 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 07:00:07 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5001 milliseconds
> Sun Apr 21 07:04:31 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5000 milliseconds
> Sun Apr 21 07:08:56 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5001 milliseconds
> Sun Apr 21 07:13:21 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5000 milliseconds
> Sun Apr 21 07:15:33 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5001 milliseconds
> Sun Apr 21 07:15:36 2019 daemon.err graph[2001]: curl: (28) Operation timed out after 10000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 07:15:39 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5001 milliseconds
> Sun Apr 21 07:17:55 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5002 milliseconds
> Sun Apr 21 07:18:02 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5000 milliseconds
> Sun Apr 21 07:18:08 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 07:18:14 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5001 milliseconds
> Sun Apr 21 07:20:26 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5001 milliseconds
> Sun Apr 21 07:24:53 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5001 milliseconds
> Sun Apr 21 07:24:59 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 07:25:00 2019 daemon.err graph[20281]: curl: (28) Operation timed out after 10000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 07:29:18 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5000 milliseconds
> Sun Apr 21 07:29:18 2019 daemon.err graph[5867]: curl: (28) Operation timed out after 10000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 07:29:24 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5000 milliseconds
> Sun Apr 21 07:29:30 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 07:30:54 2019 daemon.info ss-redir-track: Shadowsocks is down
> Sun Apr 21 07:30:54 2019 user.info ss-redir-initd: Unplugging shadowsocks cable...
> Sun Apr 21 07:31:03 2019 user.notice post-tracking-mptcp: if1 switched off
> Sun Apr 21 07:31:03 2019 user.notice post-tracking-otb-autoroute: del default route for if1 using gateway 192.168.1.1 and metric 30
> Sun Apr 21 07:31:03 2019 user.notice post-tracking-otb-autoroute: del 109.190.128.248 route for if1 using gateway 192.168.1.1 and metric 30
> Sun Apr 21 07:31:03 2019 user.notice post-tracking-otb-autoroute: del 192.168.1.1 route for if1 using gateway 192.168.1.1 and metric 30
> Sun Apr 21 07:31:03 2019 user.notice post-tracking-store-state: if1 tracking status changed to ERROR
> Sun Apr 21 07:31:04 2019 daemon.info ss-redir-track: Shadowsocks is up
> Sun Apr 21 07:31:05 2019 user.info ss-redir-initd: Plugging shadowsocks cable in...
> Sun Apr 21 07:32:28 2019 daemon.err ss-redir[4398]: 2019-04-21 07:32:28 ERROR: remote recv: Operation timed out
> Sun Apr 21 07:32:46 2019 daemon.err ss-redir[4398]: 2019-04-21 07:32:46 ERROR: remote recv: Operation timed out
> Sun Apr 21 07:33:40 2019 user.notice post-tracking-mptcp: if1 switched to on
> Sun Apr 21 07:33:40 2019 user.notice post-tracking-otb-autoroute: add default route for if1 using gateway 192.168.1.1 and metric 30
> Sun Apr 21 07:33:40 2019 user.notice post-tracking-otb-autoroute: add 109.190.128.248 route for if1 using gateway 192.168.1.1 and metric 30
> Sun Apr 21 07:33:40 2019 user.notice post-tracking-otb-autoroute: add 192.168.1.1 route for if1 using gateway 192.168.1.1 and metric 30
> Sun Apr 21 07:33:40 2019 user.notice post-tracking-store-state: if1 tracking status changed to OK
> Sun Apr 21 09:01:17 2019 user.notice post-tracking-mptcp: if1 switched off
> Sun Apr 21 09:01:17 2019 user.notice post-tracking-otb-autoroute: del default route for if1 using gateway 192.168.1.1 and metric 30
> Sun Apr 21 09:01:17 2019 user.notice post-tracking-otb-autoroute: del 109.190.128.248 route for if1 using gateway 192.168.1.1 and metric 30
> Sun Apr 21 09:01:17 2019 user.notice post-tracking-otb-autoroute: del 192.168.1.1 route for if1 using gateway 192.168.1.1 and metric 30
> Sun Apr 21 09:01:17 2019 user.notice post-tracking-store-state: if1 tracking status changed to ERROR
> Sun Apr 21 09:01:22 2019 user.notice post-tracking-mptcp: if1 switched to on
> Sun Apr 21 09:01:22 2019 user.notice post-tracking-otb-autoroute: add default route for if1 using gateway 192.168.1.1 and metric 30
> Sun Apr 21 09:01:22 2019 user.notice post-tracking-otb-autoroute: add 109.190.128.248 route for if1 using gateway 192.168.1.1 and metric 30
> Sun Apr 21 09:01:22 2019 user.notice post-tracking-otb-autoroute: add 192.168.1.1 route for if1 using gateway 192.168.1.1 and metric 30
> Sun Apr 21 09:01:22 2019 user.notice post-tracking-store-state: if1 tracking status changed to OK
> Sun Apr 21 09:01:36 2019 daemon.err ss-redir[4397]: 2019-04-21 09:01:36 ERROR: getpeername: Socket not connected
> Sun Apr 21 09:01:36 2019 daemon.info ss-redir-track: Shadowsocks is down
> Sun Apr 21 09:01:36 2019 user.info ss-redir-initd: Unplugging shadowsocks cable...
> Sun Apr 21 09:01:38 2019 daemon.err ss-redir[4397]: 2019-04-21 09:01:38 ERROR: getpeername: Socket not connected
> Sun Apr 21 09:01:38 2019 daemon.err ss-redir[4398]: 2019-04-21 09:01:38 ERROR: getpeername: Socket not connected
> Sun Apr 21 09:01:38 2019 daemon.err ss-redir[4398]: 2019-04-21 09:01:38 ERROR: getpeername: Socket not connected
> Sun Apr 21 09:01:38 2019 daemon.err ss-redir[4398]: 2019-04-21 09:01:38 ERROR: getpeername: Socket not connected
> Sun Apr 21 09:01:39 2019 daemon.err ss-redir[4397]: 2019-04-21 09:01:39 ERROR: getpeername: Socket not connected
> Sun Apr 21 09:01:39 2019 daemon.err ss-redir[4397]: 2019-04-21 09:01:39 ERROR: getpeername: Socket not connected
> Sun Apr 21 09:01:39 2019 daemon.err ss-redir[4398]: 2019-04-21 09:01:39 ERROR: getpeername: Socket not connected
> Sun Apr 21 09:01:39 2019 daemon.err ss-redir[4397]: 2019-04-21 09:01:39 ERROR: getpeername: Socket not connected
> Sun Apr 21 09:01:39 2019 daemon.err ss-redir[4397]: 2019-04-21 09:01:39 ERROR: getpeername: Socket not connected
> Sun Apr 21 09:01:39 2019 daemon.err ss-redir[4398]: 2019-04-21 09:01:39 ERROR: getpeername: Socket not connected
> Sun Apr 21 09:01:39 2019 daemon.err ss-redir[4398]: 2019-04-21 09:01:39 ERROR: getpeername: Socket not connected
> Sun Apr 21 09:01:39 2019 daemon.err ss-redir[4397]: 2019-04-21 09:01:39 ERROR: getpeername: Socket not connected
> Sun Apr 21 09:01:39 2019 daemon.err ss-redir[4398]: 2019-04-21 09:01:39 ERROR: getpeername: Socket not connected
> Sun Apr 21 09:01:46 2019 daemon.err ss-redir[4398]: 2019-04-21 09:01:46 ERROR: getpeername: Socket not connected
> Sun Apr 21 09:01:46 2019 user.notice post-tracking-mptcp: if1 switched off
> Sun Apr 21 09:01:46 2019 user.notice post-tracking-otb-autoroute: del default route for if1 using gateway 192.168.1.1 and metric 30
> Sun Apr 21 09:01:46 2019 user.notice post-tracking-otb-autoroute: del 109.190.128.248 route for if1 using gateway 192.168.1.1 and metric 30
> Sun Apr 21 09:01:46 2019 user.notice post-tracking-otb-autoroute: del 192.168.1.1 route for if1 using gateway 192.168.1.1 and metric 30
> Sun Apr 21 09:01:46 2019 user.notice post-tracking-store-state: if1 tracking status changed to ERROR
> Sun Apr 21 09:01:56 2019 daemon.info ss-redir-track: Shadowsocks is up
> Sun Apr 21 09:01:56 2019 user.info ss-redir-initd: Plugging shadowsocks cable in...
> Sun Apr 21 09:01:56 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 09:02:36 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5001 milliseconds
> Sun Apr 21 09:02:37 2019 daemon.err graph[28847]: curl: (28) Operation timed out after 10000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 09:04:04 2019 user.notice post-tracking-mptcp: if1 switched to on
> Sun Apr 21 09:04:05 2019 user.notice post-tracking-otb-autoroute: add default route for if1 using gateway 192.168.1.1 and metric 30
> Sun Apr 21 09:04:05 2019 user.notice post-tracking-otb-autoroute: add 109.190.128.248 route for if1 using gateway 192.168.1.1 and metric 30
> Sun Apr 21 09:04:05 2019 user.notice post-tracking-otb-autoroute: add 192.168.1.1 route for if1 using gateway 192.168.1.1 and metric 30
> Sun Apr 21 09:04:05 2019 user.notice post-tracking-store-state: if1 tracking status changed to OK
> Sun Apr 21 09:06:26 2019 daemon.err otb-tracker[22526]: curl: (28) Connection timed out after 1000 milliseconds
> Sun Apr 21 09:06:26 2019 daemon.err otb-tracker[22526]: curl: (7) Failed to connect to ipaddr.ovh port 80: Operation timed out
> Sun Apr 21 11:14:10 2019 daemon.err ss-redir[4397]: 2019-04-21 11:14:10 ERROR: remote recv: Connection reset by peer
> Sun Apr 21 11:14:44 2019 daemon.err ss-redir[4398]: 2019-04-21 11:14:44 ERROR: remote recv: Connection reset by peer
> Sun Apr 21 11:38:54 2019 daemon.err ss-redir[4397]: 2019-04-21 11:38:54 ERROR: server recv: Operation timed out
> Sun Apr 21 12:10:25 2019 daemon.err ss-redir[4397]: 2019-04-21 12:10:25 ERROR: remote recv: Connection reset by peer
> Sun Apr 21 12:10:46 2019 daemon.err ss-redir[4397]: 2019-04-21 12:10:46 ERROR: remote recv: Connection reset by peer
> Sun Apr 21 12:10:54 2019 daemon.err ss-redir[4397]: 2019-04-21 12:10:54 ERROR: remote recv: Connection reset by peer
> Sun Apr 21 12:10:56 2019 daemon.err ss-redir[4398]: 2019-04-21 12:10:56 ERROR: remote recv: Connection reset by peer
> Sun Apr 21 12:11:03 2019 daemon.err ss-redir[4398]: 2019-04-21 12:11:03 ERROR: remote recv: Connection reset by peer
> Sun Apr 21 12:11:09 2019 daemon.err ss-redir[4397]: 2019-04-21 12:11:09 ERROR: remote recv: Connection reset by peer
> Sun Apr 21 12:13:03 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 12:13:10 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 bytes received
> Sun Apr 21 12:13:50 2019 daemon.err ss-redir[4397]: 2019-04-21 12:13:50 ERROR: remote recv: Connection reset by peer
> Sun Apr 21 12:17:41 2019 daemon.err graph[9244]: curl: (28) Operation timed out after 10000 milliseconds with 0 bytes received
> Sun Apr 21 12:20:00 2019 daemon.err graph[25859]: curl: (28) Operation timed out after 10000 milliseconds with 0 bytes received
> Sun Apr 21 12:26:28 2019 daemon.err ss-redir[4397]: 2019-04-21 12:26:28 ERROR: remote recv: Connection reset by peer
> Sun Apr 21 12:31:55 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 12:32:01 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 12:32:04 2019 daemon.err otb-tracker[22526]: curl: (28) Operation timed out after 5000 milliseconds with 0 bytes received
> Sun Apr 21 12:32:08 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 12:32:14 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 bytes received
> Sun Apr 21 12:32:23 2019 daemon.err ss-redir[4397]: 2019-04-21 12:32:23 ERROR: server recv: Host is unreachable
> Sun Apr 21 12:33:43 2019 daemon.err graph[5569]: curl: (28) Operation timed out after 10000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 12:33:58 2019 daemon.err graph[13062]: curl: (28) Operation timed out after 10000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 12:33:58 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 12:34:05 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 12:34:11 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5002 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 12:34:13 2019 daemon.err graph[14386]: curl: (28) Operation timed out after 10000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 12:34:17 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 12:34:23 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5001 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 12:34:28 2019 daemon.err graph[15661]: curl: (28) Operation timed out after 10000 milliseconds with 0 bytes received
> Sun Apr 21 12:35:05 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 bytes received
> Sun Apr 21 12:35:11 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 12:35:49 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5001 milliseconds with 0 bytes received
> Sun Apr 21 12:35:55 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 bytes received
> Sun Apr 21 12:37:14 2019 daemon.err otb-tracker[22526]: curl: (28) Connection timed out after 4000 milliseconds
> Sun Apr 21 12:37:16 2019 daemon.err otb-tracker[22526]: curl: (7) Failed to connect to ipaddr.ovh port 80: Operation timed out
> Sun Apr 21 12:38:39 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5001 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 12:38:45 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5001 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 12:39:23 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 bytes received
> Sun Apr 21 13:31:54 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5001 milliseconds with 0 bytes received
> Sun Apr 21 13:33:41 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5001 milliseconds
> Sun Apr 21 13:33:47 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 13:37:10 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 13:38:24 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 13:44:52 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5001 milliseconds
> Sun Apr 21 13:46:02 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5001 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 13:46:08 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5002 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 13:46:47 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 13:57:58 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 14:30:39 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 14:33:00 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 14:33:37 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5001 milliseconds
> Sun Apr 21 14:33:44 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 14:33:50 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 14:33:56 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 14:34:02 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5000 milliseconds
> Sun Apr 21 14:34:08 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 14:34:11 2019 daemon.err graph[17063]: curl: (28) Operation timed out after 10000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 14:34:14 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5000 milliseconds
> Sun Apr 21 14:34:20 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 14:34:26 2019 daemon.err graph[13702]: curl: (28) Operation timed out after 10000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 14:34:26 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5001 milliseconds
> Sun Apr 21 14:34:32 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 14:34:38 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 14:34:41 2019 daemon.err graph[15020]: curl: (28) Operation timed out after 10002 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 14:34:45 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5000 milliseconds
> Sun Apr 21 14:34:51 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5000 milliseconds
> Sun Apr 21 14:34:53 2019 daemon.err ssh[6309]:
> Sun Apr 21 14:34:53 2019 daemon.err ssh[6309]: /usr/bin/ssh: Connection to limited-user@51.68.42.116:30080 exited: Remote closed the connection
> Sun Apr 21 14:34:56 2019 daemon.err graph[16389]: curl: (28) Connection timed out after 10001 milliseconds
> Sun Apr 21 14:34:57 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5001 milliseconds
> Sun Apr 21 14:35:03 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5001 milliseconds
> Sun Apr 21 14:35:09 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5001 milliseconds
> Sun Apr 21 14:35:11 2019 daemon.err graph[17666]: curl: (28) Operation timed out after 10000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 14:35:15 2019 daemon.err otb-daemon[3638]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 14:35:21 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5000 milliseconds
> Sun Apr 21 14:35:26 2019 daemon.err graph[19037]: curl: (28) Operation timed out after 10001 milliseconds with 0 out of 0 bytes received
> Sun Apr 21 14:35:27 2019 daemon.err otb-daemon[3638]: curl: (28) Connection timed out after 5001 milliseconds
> Sun Apr 21 14:35:29 2019 user.notice post-tracking-mptcp: if3 switched off
> Sun Apr 21 14:35:29 2019 user.notice post-tracking-otb-autoroute: del default route for if3 using gateway 192.168.4.1 and metric 32
> Sun Apr 21 14:35:29 2019 user.notice post-tracking-otb-autoroute: del 109.190.128.248 route for if3 using gateway 192.168.4.1 and metric 32
> Sun Apr 21 14:35:29 2019 user.notice post-tracking-otb-autoroute: del 192.168.4.1 route for if3 using gateway 192.168.4.1 and metric 32
> Sun Apr 21 14:35:29 2019 user.notice post-tracking-store-state: if3 tracking status changed to ERROR
> Sun Apr 21 14:35:31 2019 user.notice post-tracking-mptcp: if3 switched to on
> Sun Apr 21 14:35:31 2019 user.notice post-tracking-otb-autoroute: add default route for if3 using gateway 192.168.4.1 and metric 32
> Sun Apr 21 14:35:31 2019 user.notice post-tracking-otb-autoroute: add 109.190.128.248 route for if3 using gateway 192.168.4.1 and metric 32
> Sun Apr 21 14:35:31 2019 user.notice post-tracking-otb-autoroute: add 192.168.4.1 route for if3 using gateway 192.168.4.1 and metric 32
> Sun Apr 21 14:35:31 2019 user.notice post-tracking-store-state: if3 tracking status changed to OK
> Sun Apr 21 14:35:36 2019 user.notice post-tracking-mptcp: if2 switched off
> Sun Apr 21 14:35:36 2019 user.notice post-tracking-otb-autoroute: del default route for if2 using gateway 192.168.3.1 and metric 31
> Sun Apr 21 14:35:36 2019 user.notice post-tracking-otb-autoroute: del 109.190.128.248 route for if2 using gateway 192.168.3.1 and metric 31
> Sun Apr 21 14:35:36 2019 user.notice post-tracking-otb-autoroute: del 192.168.3.1 route for if2 using gateway 192.168.3.1 and metric 31
> Sun Apr 21 14:35:36 2019 user.notice post-tracking-store-state: if2 tracking status changed to ERROR
> Sun Apr 21 14:35:40 2019 user.notice post-tracking-mptcp: if2 switched to on
> Sun Apr 21 14:35:40 2019 user.notice post-tracking-otb-autoroute: add default route for if2 using gateway 192.168.3.1 and metric 31
> Sun Apr 21 14:35:40 2019 user.notice post-tracking-otb-autoroute: add 109.190.128.248 route for if2 using gateway 192.168.3.1 and metric 31
> Sun Apr 21 14:35:40 2019 user.notice post-tracking-otb-autoroute: add 192.168.3.1 route for if2 using gateway 192.168.3.1 and metric 31
> Sun Apr 21 14:35:40 2019 user.notice post-tracking-store-state: if2 tracking status changed to OK
> Sun Apr 21 14:35:56 2019 user.notice post-tracking-otb-autoroute: del rule matching 0x7874756e using table 101 and pref 30000
> Sun Apr 21 14:35:56 2019 user.notice post-tracking-store-state: xtun0 tracking status changed to ERROR
> Sun Apr 21 14:36:00 2019 user.notice post-tracking-otb-autoroute: add rule matching 0x7874756e using table 101 and pref 30000
> Sun Apr 21 14:36:00 2019 user.notice post-tracking-store-state: xtun0 tracking status changed to OK
Ces erreurs et déconnexions reviennent très souvent, et je n'ai pourtant pas effectué de changement dans ma configuration que ce soit avant ou après la réinitialisation.
Jusqu'alors, il n'y avait aucun soucis de ce type (j'utilise OverTheBox depuis 2017...)
Un membre d'OVH Community Techies peut-il m'aider à résoudre ces problèmes car j'ai passé une dizaine de jours à en chercher la cause et là, je n'ai plus d'idée.
(Si besoin, je vous communique le Device ID.)
D'avance merci pour votre réponse et pour votre aide.
Nombreuses déconnexion tunnel et erreurs timed out sur mon OTB
Welcome to OVHcloud Community
Ask questions, search for information, post content, and interact with other OVHcloud Community members.
Question
Nombreuses déconnexion tunnel et erreurs timed out sur mon OTB
Upvotes (0)
2008 Views
Related questions
- [Résolu] Routeur Ubiquiti Unifi USG‑PRO‑4 + Overthebox (OVH & Freebox)
24178 
16.04.2017 16:44
- Débit sur DMZ très faibles
24048 09.01.2026 11:04
- OTB en 4G uniquement
19839 21.10.2016 18:21
- Problèmes de ping avec Discord
19477 15.02.2018 22:12
- Perte Upload 4G
19112 03.04.2019 20:57
- Liste de tous mes bugs rencontrés avec OTB
17216 14.01.2017 14:53
- [Résolu] OverTheBox qui récupère l'ip public de ma box au lieu de la sienne
16648 26.07.2018 10:37
- [Résolu] Installation sur raspberry PI 3
15830 14.12.2017 00:51
- [Résolu] Redirection de ports OTB
15529 03.01.2017 21:38
- Version et mise à jour
15159 21.11.2017 16:49
Bonjour @InfObject
Peux tu me donner ton device ID que je check ta config ?
merci
Bonjour @Benoit.D
Voici le Device ID : 60859756-cf5f-4591-a979-a6beff1fcedc
A noter : J'ai 3 liens : 1 accès ADSL en if1, et 2 accès 4G+ en if2 et if3
Par contre, la limite de l'enveloppe data de la connexion 4G+ (sur if2) est atteinte…
Normal donc que les débits soient bridés sur cette interface ;)
-> renouvellement de l'enveloppe data le 7 du mois prochain.
Mais cela ne pose pas de problème car la connexion 4G+ sur if3 est pleinement opérationnelle
Si besoin d'autres précisions, je suis à votre disposition !
Merci pour le retour, je regarde.
Merci @Benoit.D
Autres problèmes (constatés aujourd'hui même) :
-> J'ai remarqué également que lorsque je tape "overthebox.ovh" sur un navigateur internet (depuis un PC local,) cela renvoyait vers un autre de mes équipements du réseau local (un NAS) et non plus vers l'OTB.
Par contre, aucun problème d'accès à l'OTB en tapant l'IP locale (192.168.1.3) ...
-> Absence aussi d'IPv6 (avant réinitialisation de l'OTB, l'IPv6 était disponible. Je m'en suis rendu compte lors de tests à l'aide de proof.ovh.net)
Est-ce lié au problème de perte du tunnel ou est-ce autre chose ???
Merci de votre retour.
Bonjour @Benoit.D
Juste pour vous indiquer que le problème d'accès à l'OTB via "overthebox.ovh" à été solutionné par un reboot de l'OTB effectué ce jour en début d'après-midi.
Pas de changement pour le reste...
J'ai toujours des erreurs et des plantages Shadowsocks et mptcp.
J'ai regardé le log kernel et je suis tombé sur ça :
> [ 7085.572064] mptcp_verif_dss_csum csum is wrong: 0x100 data_seq 1748740724 dss_csum_added 1 overflowed 0 iterations 1
> [ 7085.575531] mptcp_verif_dss_csum csum is wrong: 0x100 data_seq 794662076 dss_csum_added 1 overflowed 0 iterations 1
> [ 7085.689940] mptcp_verif_dss_csum csum is wrong: 0x100 data_seq 1982572657 dss_csum_added 1 overflowed 0 iterations 1
> [13982.851958] mptcp_verif_dss_csum csum is wrong: 0x100 data_seq 115210656 dss_csum_added 1 overflowed 1 iterations 1
> [13983.861318] mptcp_verif_dss_csum csum is wrong: 0x100 data_seq 1013338253 dss_csum_added 1 overflowed 1 iterations 1
> [13985.876315] mptcp_verif_dss_csum csum is wrong: 0x100 data_seq 263573319 dss_csum_added 1 overflowed 1 iterations 1
Cela se produit lors des plantages mptcp apparemment...
Avez-vous eu le temps de regarder ma config ?
Merci d'avance pour votre aide.
Bonjour @InfObject
Les erreurs semblent venir de ta 4G+ (principale).
Celle-ci a des monter de ping jusqu'a 1500 ms. Du coup l'otb perd des paquets.
J'ai réduit la MTU à 1432, qui est plus adaptée pour la 4G Free, afin de réduire ce phénomène.
Je te laisse me dire si il y a du mieux de ton coté.
Bonne journée,
Benoit
Bonjour @Benoit.D
Malgré le changement de la valeur MTU que vous avez effectué sur les if2 et if3, je ne constate malheureusement pas de réelle amélioration.
Les latences observées sont toujours identiques lors de mes tests sur "proof.ovh.net" (j'ai effectué le dernier à 18h30 environ). Mes débits en download et upload semblent bridés. (voir capture ci-dessous.)
-> Avant réinitialisation de mon OTB, je n'avais pas toutes ces erreurs dans les logs système et kernel, et mes débits étaient de l'ordre de 130Mb/s en download et 30Mb/s en upload. (avec une connexion 4G+ ayant son enveloppe data épuisée, et lorsque l'antenne 4G était fortement utilisée.)
Avec les 2 connexions 4G+ fonctionnelles, mes débits atteignaient même parfois les 190 Mb/s en download et 37 Mb/s en upload !
Je précise que ma configuration hardware est restée la même et que mon offre OverTheBox "Basic" est une offre logicielle. L'antenne Free utilisée est à 500m a vol d'oiseau de mon installation ;)
Merci