Bonjour,
### Identifiants
Device ID 10c1519e-7b1e-4b97-8198-e407602820cd
Service name overthebox.36996f1d-4136-4544-a790-b3a77313590b
### Problème rencontré
J'ai sans arrêt des timeouts dans les logs.
Fri Sep 28 08:01:12 2018 daemon.err otb-tracker[3551]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 08:15:59 2018 daemon.err ss-redir[3750]: 2018-09-28 08:15:59 ERROR: server recv: Operation timed out
Fri Sep 28 08:16:24 2018 daemon.err ss-redir[3750]: 2018-09-28 08:16:24 ERROR: server recv: Operation timed out
Fri Sep 28 08:19:32 2018 daemon.err otb-tracker[3550]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 08:20:17 2018 daemon.err otb-tracker[3552]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 08:21:15 2018 daemon.err otb-tracker[3551]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 08:21:59 2018 daemon.err otb-tracker[3553]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 08:29:34 2018 daemon.err otb-tracker[3550]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 08:34:37 2018 daemon.err otb-tracker[3550]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 08:36:19 2018 daemon.err otb-tracker[3551]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 08:41:35 2018 daemon.err ss-redir[3749]: 2018-09-28 08:41:35 ERROR: server recv: Operation timed out
Fri Sep 28 08:42:01 2018 daemon.err otb-tracker[3553]: curl: (28) Operation timed out after 1002 milliseconds with 0 bytes received
Fri Sep 28 08:44:39 2018 daemon.err otb-tracker[3550]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 08:47:02 2018 daemon.err otb-tracker[3553]: curl: (28) Operation timed out after 1000 milliseconds with 0 bytes received
Fri Sep 28 08:49:40 2018 daemon.err otb-tracker[3550]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 08:52:04 2018 daemon.err otb-tracker[3553]: curl: (28) Operation timed out after 1002 milliseconds with 0 bytes received
Fri Sep 28 08:55:23 2018 daemon.err otb-tracker[3552]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 08:56:27 2018 daemon.err otb-tracker[3551]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 08:59:45 2018 daemon.err otb-tracker[3550]: curl: (28) Operation timed out after 1000 milliseconds with 0 bytes received
Fri Sep 28 09:04:47 2018 daemon.err otb-tracker[3550]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 09:06:28 2018 daemon.err otb-tracker[3551]: curl: (28) Operation timed out after 1000 milliseconds with 0 bytes received
Fri Sep 28 09:07:07 2018 daemon.err otb-tracker[3553]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 09:12:09 2018 daemon.err otb-tracker[3553]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 09:17:12 2018 daemon.err otb-tracker[3553]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 09:19:50 2018 daemon.err otb-tracker[3550]: curl: (28) Operation timed out after 1002 milliseconds with 0 bytes received
Fri Sep 28 09:20:53 2018 daemon.err ss-redir[3750]: 2018-09-28 09:20:53 ERROR: remote recv: Connection reset by peer
Fri Sep 28 09:24:52 2018 daemon.err otb-tracker[3550]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 09:25:29 2018 daemon.err otb-tracker[3552]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 09:26:30 2018 daemon.err otb-tracker[3551]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 09:27:15 2018 daemon.err otb-tracker[3553]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 09:29:55 2018 daemon.err otb-tracker[3550]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 09:30:30 2018 daemon.err otb-tracker[3552]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 09:32:16 2018 daemon.err otb-tracker[3553]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 09:36:31 2018 daemon.err otb-tracker[3551]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 09:43:12 2018 daemon.err ss-redir[3749]: 2018-09-28 09:43:12 ERROR: send: Connection reset by peer
Fri Sep 28 09:46:38 2018 daemon.err ss-redir[3747]: 2018-09-28 09:46:38 ERROR: send: Connection reset by peer
Fri Sep 28 09:51:33 2018 daemon.err otb-tracker[3551]: curl: (28) Operation timed out after 1000 milliseconds with 0 bytes received
Fri Sep 28 10:05:36 2018 daemon.err otb-tracker[3552]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 10:10:04 2018 daemon.err otb-tracker[3550]: curl: (28) Operation timed out after 1000 milliseconds with 0 bytes received
Fri Sep 28 10:10:38 2018 daemon.err otb-tracker[3552]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 10:11:35 2018 daemon.err otb-tracker[3551]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 10:12:23 2018 daemon.err otb-tracker[3553]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 10:15:41 2018 daemon.err otb-tracker[3552]: curl: (28) Operation timed out after 1002 milliseconds with 0 bytes received
Fri Sep 28 10:20:07 2018 daemon.err otb-tracker[3550]: curl: (28) Operation timed out after 1002 milliseconds with 0 bytes received
Fri Sep 28 10:21:36 2018 daemon.err otb-tracker[3551]: curl: (28) Operation timed out after 1000 milliseconds with 0 bytes received
Fri Sep 28 10:26:37 2018 daemon.err otb-tracker[3551]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 10:28:02 2018 daemon.err ss-redir[3748]: 2018-09-28 10:28:02 ERROR: remote recv: Connection reset by peer
Fri Sep 28 10:30:44 2018 daemon.err otb-tracker[3552]: curl: (28) Operation timed out after 1002 milliseconds with 0 bytes received
Fri Sep 28 10:35:10 2018 daemon.err otb-tracker[3550]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 10:37:22 2018 daemon.err ss-redir[3747]: 2018-09-28 10:37:22 ERROR: remote recv: Connection reset by peer
Fri Sep 28 10:41:44 2018 daemon.err otb-tracker[3551]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 10:42:27 2018 daemon.err otb-tracker[3553]: curl: (28) Operation timed out after 1002 milliseconds with 0 bytes received
Fri Sep 28 10:43:19 2018 daemon.err ss-redir[3748]: 2018-09-28 10:43:19 ERROR: remote recv: Connection reset by peer
Fri Sep 28 10:50:14 2018 daemon.err otb-tracker[3550]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 10:50:46 2018 daemon.err otb-tracker[3552]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 10:56:49 2018 daemon.err otb-tracker[3551]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Fri Sep 28 10:58:22 2018 daemon.err ss-redir[3748]: 2018-09-28 10:58:22 ERROR: server recv: Operation timed out
Fri Sep 28 10:58:27 2018 daemon.err ss-redir[3748]: 2018-09-28 10:58:27 ERROR: server recv: Operation timed out
Fri Sep 28 11:02:28 2018 daemon.err ss-redir[3750]: 2018-09-28 11:02:28 ERROR: server recv: Operation timed out
Fri Sep 28 11:02:32 2018 daemon.err otb-tracker[3553]: curl: (28) Operation timed out after 1002 milliseconds with 0 bytes received
Mon Oct 1 16:39:31 2018 daemon.err otb-tracker[3551]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 16:39:59 2018 daemon.err otb-tracker[3553]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 16:41:26 2018 daemon.err ss-redir[3748]: 2018-10-01 16:41:26 ERROR: remote recv: Operation timed out
Mon Oct 1 16:43:48 2018 daemon.err ss-redir[3749]: 2018-10-01 16:43:48 ERROR: remote recv: Connection reset by peer
Mon Oct 1 16:49:33 2018 daemon.err otb-tracker[3551]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 16:50:01 2018 daemon.err otb-tracker[3553]: curl: (28) Operation timed out after 1002 milliseconds with 0 bytes received
Mon Oct 1 16:54:35 2018 daemon.err otb-tracker[3551]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 16:54:39 2018 daemon.err otb-tracker[3552]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 17:04:38 2018 daemon.err otb-tracker[3551]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 17:04:40 2018 daemon.err otb-tracker[3552]: curl: (28) Operation timed out after 1000 milliseconds with 0 bytes received
Mon Oct 1 17:09:41 2018 daemon.err otb-tracker[3551]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 17:09:42 2018 daemon.err otb-tracker[3551]: curl: (28) Resolving timed out after 1514 milliseconds
Mon Oct 1 17:09:42 2018 daemon.err otb-tracker[3552]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 17:09:45 2018 daemon.err otb-tracker[3551]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 17:14:44 2018 daemon.err otb-tracker[3552]: curl: (28) Operation timed out after 1000 milliseconds with 0 bytes received
Mon Oct 1 17:15:06 2018 daemon.err otb-tracker[3553]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 17:17:03 2018 daemon.err ss-redir[3750]: 2018-10-01 17:17:03 ERROR: remote recv: Connection reset by peer
Mon Oct 1 17:19:48 2018 daemon.err otb-tracker[3551]: curl: (28) Operation timed out after 1000 milliseconds with 0 bytes received
Mon Oct 1 17:20:09 2018 daemon.err otb-tracker[3553]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 17:24:49 2018 daemon.err otb-tracker[3551]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 17:29:49 2018 daemon.err otb-tracker[3552]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 17:29:51 2018 daemon.err otb-tracker[3551]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 17:30:06 2018 daemon.err ss-redir[3750]: 2018-10-01 17:30:06 ERROR: remote recv: Connection reset by peer
Mon Oct 1 17:34:50 2018 daemon.err otb-tracker[3552]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 17:35:13 2018 daemon.err otb-tracker[3553]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 17:39:53 2018 daemon.err otb-tracker[3551]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 17:44:51 2018 daemon.err otb-tracker[3552]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 17:45:16 2018 daemon.err otb-tracker[3553]: curl: (28) Operation timed out after 1002 milliseconds with 0 bytes received
Mon Oct 1 17:50:17 2018 daemon.err otb-tracker[3553]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 17:59:56 2018 daemon.err otb-tracker[3551]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 18:00:19 2018 daemon.err otb-tracker[3553]: curl: (28) Operation timed out after 1000 milliseconds with 0 bytes received
Mon Oct 1 18:05:20 2018 daemon.err otb-tracker[3553]: curl: (28) Operation timed out after 1002 milliseconds with 0 bytes received
Mon Oct 1 18:09:58 2018 daemon.err otb-tracker[3551]: curl: (28) Operation timed out after 1000 milliseconds with 0 bytes received
Mon Oct 1 18:10:20 2018 daemon.err ss-redir[3750]: 2018-10-01 18:10:20 ERROR: server recv: Operation timed out
Mon Oct 1 18:10:21 2018 daemon.err otb-tracker[3553]: curl: (28) Connection timed out after 1000 milliseconds
Mon Oct 1 18:10:25 2018 daemon.err ss-redir[3748]: 2018-10-01 18:10:25 ERROR: server recv: Operation timed out
Mon Oct 1 18:10:35 2018 daemon.err ss-redir[3748]: 2018-10-01 18:10:35 ERROR: server recv: Operation timed out
Mon Oct 1 18:10:55 2018 daemon.err ss-redir[3747]: 2018-10-01 18:10:55 ERROR: server recv: Operation timed out
Mon Oct 1 18:15:22 2018 daemon.err otb-tracker[3553]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 18:18:50 2018 daemon.err ss-redir[3747]: 2018-10-01 18:18:50 ERROR: send: Connection reset by peer
Mon Oct 1 18:19:12 2018 daemon.err ss-redir[3747]: 2018-10-01 18:19:12 ERROR: remote recv: Connection reset by peer
Mon Oct 1 18:20:23 2018 daemon.err otb-tracker[3553]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 18:30:25 2018 daemon.err otb-tracker[3553]: curl: (28) Operation timed out after 2002 milliseconds with 0 bytes received
Mon Oct 1 18:30:26 2018 daemon.err otb-tracker[3553]: curl: (7) Failed to connect to ipaddr.ovh port 80: Operation timed out
Mon Oct 1 18:30:29 2018 daemon.err otb-tracker[3553]: curl: (28) Operation timed out after 1002 milliseconds with 0 bytes received
Mon Oct 1 18:34:27 2018 daemon.warn dnsmasq[4088]: possible DNS-rebind attack detected: ucs02.engageya.com
Mon Oct 1 18:34:27 2018 daemon.warn dnsmasq[4088]: possible DNS-rebind attack detected: ucs02.engageya.com
Mon Oct 1 18:34:57 2018 daemon.err otb-tracker[3552]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 18:35:31 2018 daemon.err otb-tracker[3553]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 18:35:38 2018 daemon.err ss-redir[3747]: 2018-10-01 18:35:38 ERROR: remote recv: Connection reset by peer
Mon Oct 1 18:43:27 2018 daemon.err ss-redir[3749]: 2018-10-01 18:43:27 ERROR: remote recv: Connection reset by peer
Mon Oct 1 18:45:00 2018 daemon.err otb-tracker[3552]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 18:45:32 2018 daemon.err otb-tracker[3553]: curl: (28) Operation timed out after 1000 milliseconds with 0 bytes received
Mon Oct 1 18:51:18 2018 daemon.err graph[32734]: curl: (28) Connection timed out after 10000 milliseconds
Mon Oct 1 18:51:29 2018 daemon.err otb-daemon[3631]: curl: (28) Connection timed out after 5001 milliseconds
Mon Oct 1 18:51:33 2018 daemon.err graph[32675]: curl: (28) Operation timed out after 10000 milliseconds with 0 out of 0 bytes received
Mon Oct 1 18:51:36 2018 daemon.err otb-daemon[3631]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
Mon Oct 1 18:51:42 2018 daemon.err otb-daemon[3631]: curl: (28) Connection timed out after 5001 milliseconds
Mon Oct 1 18:51:48 2018 daemon.err graph[1126]: curl: (28) Operation timed out after 10000 milliseconds with 0 out of 0 bytes received
Mon Oct 1 18:51:48 2018 daemon.err otb-daemon[3631]: curl: (28) Connection timed out after 5000 milliseconds
Mon Oct 1 18:51:54 2018 daemon.err otb-daemon[3631]: curl: (28) Connection timed out after 5001 milliseconds
Mon Oct 1 18:52:01 2018 daemon.err otb-daemon[3631]: curl: (28) Connection timed out after 5000 milliseconds
Mon Oct 1 18:52:03 2018 daemon.err graph[1854]: curl: (28) Operation timed out after 10000 milliseconds with 0 out of 0 bytes received
Mon Oct 1 18:52:07 2018 daemon.err otb-daemon[3631]: curl: (28) Connection timed out after 5001 milliseconds
Mon Oct 1 18:52:13 2018 daemon.err otb-daemon[3631]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
Mon Oct 1 18:52:18 2018 daemon.err graph[2621]: curl: (28) Operation timed out after 10000 milliseconds with 0 out of 0 bytes received
Mon Oct 1 18:52:19 2018 daemon.err otb-daemon[3631]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
Mon Oct 1 18:52:48 2018 daemon.warn dnsmasq[4088]: possible DNS-rebind attack detected: ucs02.engageya.com
Mon Oct 1 19:00:03 2018 daemon.err otb-tracker[3552]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 19:00:06 2018 daemon.err otb-tracker[3551]: curl: (28) Operation timed out after 1002 milliseconds with 0 bytes received
Mon Oct 1 19:00:52 2018 daemon.err ss-redir[3749]: 2018-10-01 19:00:52 ERROR: remote recv: Connection reset by peer
Mon Oct 1 19:05:36 2018 daemon.err otb-tracker[3553]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 19:10:06 2018 daemon.err otb-tracker[3552]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Punaise j'ai EXACTEMENT la même chose !
exemple :
Mon Oct 1 20:13:13 2018 daemon.err otb-tracker[3965]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 20:13:26 2018 daemon.err otb-tracker[3962]: curl: (28) Operation timed out after 1000 milliseconds with 0 bytes received
Mon Oct 1 20:18:30 2018 daemon.err otb-tracker[3963]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 20:23:16 2018 daemon.err otb-tracker[3965]: curl: (28) Operation timed out after 1000 milliseconds with 0 bytes received
Mon Oct 1 20:23:28 2018 daemon.err otb-tracker[3962]: curl: (28) Operation timed out after 1000 milliseconds with 0 bytes received
Mon Oct 1 20:27:43 2018 daemon.err otb-tracker[3964]: curl: (28) Operation timed out after 1000 milliseconds with 0 bytes received
Mon Oct 1 20:28:31 2018 daemon.err otb-tracker[3962]: curl: (28) Operation timed out after 1001 milliseconds with 0 bytes received
Mon Oct 1 20:32:44 2018 daemon.err otb-tracker[3964]: curl: (28) Operation timed out after 1000 milliseconds with 0 bytes received
Identifiant du périphérique :
6f9b9563-5427-4d2f-a44b-c7332c426bcb
Nom du service : overthebox.72ec66f8-094d-4be5-bb7b-94cea65022db
Si ça peut aider un admin OVH qui passe dans le coin sur nos deux soucis similaire… 
Bonjour,
On avait pas mal de timeouts lors des requêtes sur `ifconfig.ovh`. Ce service sert uniquement à afficher l'IP publique des interfaces et ne doit pas impacter le service d'agrégation.
Je viens de voir avec les personnes gérant ce service, il devrait de nouveau être 100% opérationnel et le nombre de timeout devrait grandement se réduire dans les logs.
mouais, rien de mieux de mon coté…
Sat Oct 6 22:17:26 2018 daemon.err graph[12148]: curl: (28) Operation timed out after 10000 milliseconds with 0 bytes received
Sat Oct 6 22:17:28 2018 daemon.err otb-daemon[3822]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
Sat Oct 6 22:17:34 2018 daemon.err otb-daemon[3822]: curl: (28) Connection timed out after 5000 milliseconds
Sat Oct 6 22:17:40 2018 daemon.err otb-daemon[3822]: curl: (28) Connection timed out after 5001 milliseconds
Sat Oct 6 22:17:41 2018 daemon.err graph[14432]: curl: (28) Operation timed out after 10000 milliseconds with 0 out of 0 bytes received
Sat Oct 6 22:17:46 2018 daemon.err otb-daemon[3822]: curl: (28) Connection timed out after 5001 milliseconds
Sat Oct 6 22:17:52 2018 daemon.err otb-daemon[3822]: curl: (28) Operation timed out after 5001 milliseconds with 0 out of 0 bytes received
Sat Oct 6 22:17:56 2018 daemon.err graph[16478]: curl: (28) Operation timed out after 10001 milliseconds with 0 out of 0 bytes received
Sat Oct 6 22:17:59 2018 daemon.err otb-daemon[3822]: curl: (28) Connection timed out after 5001 milliseconds
Sat Oct 6 22:18:05 2018 daemon.err otb-daemon[3822]: curl: (28) Operation timed out after 5001 milliseconds with 0 out of 0 bytes received
Sat Oct 6 22:18:11 2018 daemon.err otb-daemon[3822]: curl: (28) Connection timed out after 5001 milliseconds
Sat Oct 6 22:18:11 2018 daemon.err graph[18729]: curl: (28) Operation timed out after 10000 milliseconds with 0 out of 0 bytes received
Sat Oct 6 22:18:17 2018 daemon.err otb-daemon[3822]: curl: (28) Connection timed out after 5001 milliseconds
Sat Oct 6 22:18:23 2018 daemon.err otb-daemon[3822]: curl: (28) Operation timed out after 5001 milliseconds with 0 out of 0 bytes received
Sat Oct 6 22:18:26 2018 daemon.err graph[20873]: curl: (28) Operation timed out after 10001 milliseconds with 0 out of 0 bytes received
Sat Oct 6 22:18:29 2018 daemon.err otb-daemon[3822]: curl: (28) Connection timed out after 5001 milliseconds
Sat Oct 6 22:18:35 2018 daemon.err otb-daemon[3822]: curl: (28) Connection timed out after 5001 milliseconds
Sat Oct 6 22:18:41 2018 daemon.err otb-daemon[3822]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
Sat Oct 6 22:18:41 2018 daemon.err graph[23059]: curl: (28) Operation timed out after 10001 milliseconds with 0 out of 0 bytes received
Sat Oct 6 22:18:47 2018 daemon.err otb-daemon[3822]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
Sinon aussi, des que je télécharge un petit truc, ma ligne est de suite saturée ! je ne peux plus rien faire…
un soucis sur le tunnel ??? mon ping est souvent affreux de chez affreux aussi… un changement possible maybe ?
c'est même inutilisable tellement y'a du ping ce soir…
1000 de ping dans les jeux…
sur mes modems en direct : 60…
svp si un commu OVH pourrais faire quelques choses… ?
me changer la localisation ou la techno du tunnel peut être ?
ça à l'air de bien marcher pour certain !
Merci
Hello @FabienS8,
Je vois que quelqu'un du support à fait des actions sur ton device. Tu vois une amélioration ?