OverThebox-old - [Résolu] Upload trop bas
... / [Résolu] Upload trop bas
< Previous question   -   Next question >
BMPCreated with Sketch.BMPZIPCreated with Sketch.ZIPXLSCreated with Sketch.XLSTXTCreated with Sketch.TXTPPTCreated with Sketch.PPTPNGCreated with Sketch.PNGPDFCreated with Sketch.PDFJPGCreated with Sketch.JPGGIFCreated with Sketch.GIFDOCCreated with Sketch.DOC Error Created with Sketch.
Frage

[Résolu] Upload trop bas

S
Von
SangaB
Erstellungsdatum 2018-04-13 22:15:18 (edited on 2024-09-04 11:24:38) in OverThebox-old

Bonjour,

Mon Upload est trop bas voir erreur sur speedtest.
Mais je ne vois pas d'erreur sur les system de log

Vous pouvez m'aider svp.


Merci,
sanga
Positive Bewertungen (0)
1843 Ansichten
6 Antworten ( Latest reply on 2018-04-18 20:38:30 Von
SangaB
)

@SangaB, tu devrais mettre ici ton **_NIC-Handle_** et/ou ton **_n° de ticket d'incident_** en cas qu'il y ait de gentils membres de la Team OVH qui passent par là.

_(Ils sont bénévoles et en général très efficaces)_
Hilfreich (0)
S

Bonjour,

Nom du service : overthebox.089027d8-0087-4dd6-9339-facab46c2f11
Incident : ticket 9847505330
Hilfreich (0)
G

Bonjour,

Je vois que tu as deux ADSL sur ton OTB avec de la QoS sur les deux à 800 Kbit/s, du coup tu peux avoir max 1.6Mbit/s.
Quand tu fais tes tests tu as quelle valeur ? Tu t'attends à avoir quelle valeur ?
Hilfreich (0)
S

Bonjour,

Normalement j'ai plus que 0.500 mbiten Montant mais sa fait depuis presque 1 semaine que sa bug.
http://prntscr.com/j621qx
Hilfreich (0)
G

Bonjour @SangaB,

J'ai fait des tests de débit et des tests d'upload, tout me semble correct...
Voilà les résultats du test qui montrent bien que les deux interfaces sont utilisés au maximum de leur capacité.
```
bwm-ng v0.6.1 (delay 0.500s); press 'ctrl-c' to end this
/proc/net/dev
/ iface Rx Tx Total
==============================================================================
if1: 45.29 kb/s 911.04 kb/s 956.33 kb/s
if2: 31.27 kb/s 745.49 kb/s 776.75 kb/s
------------------------------------------------------------------------------
total: 76.55 kb/s 1656.53 kb/s 1733.08 kb/s
```
Hilfreich (0)
S

C'est marquer sa sur les logs est ce que c'est normal :
Tue Apr 17 10:43:16 2018 user.notice otb-qos: starting QoS
Tue Apr 17 10:43:16 2018 user.notice otb-qos: setting upload QoS on if1 [if1] to 800kbps
Tue Apr 17 10:43:16 2018 user.notice otb-qos: sending download QoS on if1 [if1] - maximum download 12000kbps
Tue Apr 17 10:43:16 2018 user.notice otb-qos: setting upload QoS on if2 [if2] to 800kbps
Tue Apr 17 10:43:16 2018 user.notice otb-qos: sending download QoS on if2 [if2] - maximum download 8000kbps
Tue Apr 17 10:43:27 2018 user.notice otb-qos: stopping QoS
Tue Apr 17 10:43:27 2018 user.notice otb-qos: upload QoS deleted on if1 [if1]
Tue Apr 17 10:43:27 2018 user.notice otb-qos: upload QoS deleted on if2 [if2]
Tue Apr 17 10:43:42 2018 user.notice otb-qos: stopping QoS
Tue Apr 17 10:43:42 2018 user.notice otb-qos: starting QoS
Tue Apr 17 10:43:42 2018 user.notice otb-qos: setting upload QoS on if1 [if1] to 800kbps
Tue Apr 17 10:43:42 2018 user.notice otb-qos: sending download QoS on if1 [if1] - maximum download 12000kbps
Tue Apr 17 10:43:42 2018 user.notice otb-qos: setting upload QoS on if2 [if2] to 800kbps
Tue Apr 17 10:43:42 2018 user.notice otb-qos: sending download QoS on if2 [if2] - maximum download 8000kbps
Tue Apr 17 10:43:52 2018 user.notice otb-qos: stopping QoS
Tue Apr 17 10:43:52 2018 user.notice otb-qos: upload QoS deleted on if1 [if1]
Tue Apr 17 10:43:52 2018 user.notice otb-qos: upload QoS deleted on if2 [if2]
Tue Apr 17 10:44:08 2018 user.notice otb-qos: stopping QoS
Tue Apr 17 10:44:08 2018 user.notice otb-qos: starting QoS
Tue Apr 17 10:44:08 2018 user.notice otb-qos: setting upload QoS on if1 [if1] to 800kbps
Tue Apr 17 10:44:08 2018 user.notice otb-qos: sending download QoS on if1 [if1] - maximum download 12000kbps
Tue Apr 17 10:44:08 2018 user.notice otb-qos: setting upload QoS on if2 [if2] to 800kbps
Tue Apr 17 10:44:08 2018 user.notice otb-qos: sending download QoS on if2 [if2] - maximum download 8000kbps
Tue Apr 17 10:44:22 2018 user.notice otb-qos: stopping QoS
Tue Apr 17 10:44:22 2018 user.notice otb-qos: upload QoS deleted on if1 [if1]
Tue Apr 17 10:44:22 2018 user.notice otb-qos: upload QoS deleted on if2 [if2]
Tue Apr 17 10:44:22 2018 user.notice otb-qos: starting QoS
Tue Apr 17 10:44:22 2018 user.notice otb-qos: setting upload QoS on if1 [if1] to 900kbps
Tue Apr 17 10:44:22 2018 user.notice otb-qos: sending download QoS on if1 [if1] - maximum download 11300kbps
Tue Apr 17 10:44:22 2018 user.notice otb-qos: setting upload QoS on if2 [if2] to 780kbps
Tue Apr 17 10:44:22 2018 user.notice otb-qos: sending download QoS on if2 [if2] - maximum download 7500kbps
Tue Apr 17 10:44:23 2018 user.info ss-redir-initd: Starting service...
Tue Apr 17 10:44:23 2018 daemon.info glorytun-udp: starting glorytun-udp instance xtun0
Tue Apr 17 10:44:23 2018 daemon.info glorytun: starting glorytun instance tun0
Tue Apr 17 10:44:29 2018 user.info ss-redir-initd: Plugging shadowsocks cable in...
Tue Apr 17 10:44:55 2018 user.notice otb-qos: stopping QoS
Tue Apr 17 10:44:55 2018 user.notice otb-qos: upload QoS deleted on if1 [if1]
Tue Apr 17 10:44:55 2018 user.notice otb-qos: upload QoS deleted on if2 [if2]
Tue Apr 17 10:44:55 2018 user.notice otb-qos: stopping QoS
Tue Apr 17 10:44:55 2018 user.notice otb-qos: starting QoS
Tue Apr 17 10:44:55 2018 user.notice otb-qos: setting upload QoS on if1 [if1] to 900kbps
Tue Apr 17 10:44:55 2018 user.notice otb-qos: sending download QoS on if1 [if1] - maximum download 11300kbps
Tue Apr 17 10:44:55 2018 user.notice otb-qos: setting upload QoS on if2 [if2] to 780kbps
Tue Apr 17 10:44:55 2018 user.notice otb-qos: sending download QoS on if2 [if2] - maximum download 7500kbps
Tue Apr 17 10:48:28 2018 authpriv.info dropbear[7195]: Child connection from 127.0.0.1:24654
Tue Apr 17 10:48:29 2018 authpriv.notice dropbear[7195]: Pubkey auth succeeded for 'root' with key md5 64:ca:3c:5c:21:73:cb:63:40:5d:ed:de:9a:47:b9:11 from 127.0.0.1:24654
Tue Apr 17 10:55:10 2018 authpriv.info dropbear[2603]: Exit (root): Disconnect received
Tue Apr 17 10:55:12 2018 authpriv.info dropbear[10724]: Exit (root): Disconnect received
Tue Apr 17 10:56:37 2018 authpriv.info dropbear[7195]: Exit (root): Disconnect received
Tue Apr 17 11:14:57 2018 kern.err kernel: [303132.623044] mptcp_verif_dss_csum csum is wrong: 0x80a2 data_seq 3258401271 dss_csum_added 1 overflowed 0 iterations 1
Tue Apr 17 12:38:06 2018 kern.err kernel: [308122.810996] mptcp_verif_dss_csum csum is wrong: 0xb1ed data_seq 4101345087 dss_csum_added 1 overflowed 0 iterations 1
Tue Apr 17 13:03:39 2018 daemon.err ss-redir[3802]: 2018-04-17 13:03:39 ERROR: send: Connection reset by peer
Tue Apr 17 13:03:40 2018 daemon.err ss-redir[3802]: 2018-04-17 13:03:40 ERROR: send: Connection reset by peer
Tue Apr 17 13:52:45 2018 kern.err kernel: [312602.723527] mptcp_verif_dss_csum csum is wrong: 0xa9f7 data_seq 2528624975 dss_csum_added 1 overflowed 0 iterations 1
Tue Apr 17 14:42:24 2018 daemon.err ss-redir[3802]: 2018-04-17 14:42:24 ERROR: server recv: Operation timed out
Tue Apr 17 14:42:39 2018 daemon.err ss-redir[3802]: 2018-04-17 14:42:39 ERROR: server recv: Operation timed out
Tue Apr 17 14:49:27 2018 kern.err kernel: [316005.805257] mptcp_verif_dss_csum csum is wrong: 0xfb34 data_seq 4244028699 dss_csum_added 1 overflowed 0 iterations 1
Tue Apr 17 17:01:45 2018 kern.err kernel: [323946.234217] mptcp_verif_dss_csum csum is wrong: 0x100 data_seq 2372618853 dss_csum_added 1 overflowed 0 iterations 1
Tue Apr 17 17:01:45 2018 kern.err kernel: [323946.269869] mptcp_verif_dss_csum csum is wrong: 0x100 data_seq 3402001901 dss_csum_added 1 overflowed 0 iterations 1
Tue Apr 17 17:01:46 2018 daemon.err glorytun[2592]: read: Connection reset by peer
Tue Apr 17 17:01:46 2018 daemon.info glorytun[2592]: STOPPED tun0
Tue Apr 17 17:01:47 2018 daemon.err glorytun[2592]: 109.190.216.206.5006: connected
Tue Apr 17 17:01:48 2018 daemon.info glorytun[2592]: STARTED tun0
Tue Apr 17 17:28:09 2018 kern.err kernel: [325529.752149] mptcp_verif_dss_csum csum is wrong: 0x9b25 data_seq 4107605638 dss_csum_added 1 overflowed 0 iterations 1
Tue Apr 17 18:12:59 2018 daemon.err graph[27733]: curl: (6) Could not resolve host: opentsdb.gra1.metrics.ovh.net
Tue Apr 17 18:13:01 2018 daemon.err glorytun[2592]: read: Operation timed out
Tue Apr 17 18:13:01 2018 daemon.info glorytun[2592]: STOPPED tun0
Tue Apr 17 18:13:02 2018 daemon.err glorytun[2592]: 109.190.216.206.5006: connected
Tue Apr 17 18:13:07 2018 daemon.err glorytun[2592]: 109.190.216.206.5006: key exchange failed
Tue Apr 17 18:13:07 2018 daemon.info glorytun[2592]: STOPPED tun0
Tue Apr 17 18:13:08 2018 daemon.err glorytun[2592]: 109.190.216.206.5006: connected
Tue Apr 17 18:13:10 2018 daemon.err graph[2371]: curl: (6) Could not resolve host: opentsdb.gra1.metrics.ovh.net
Tue Apr 17 18:13:13 2018 daemon.err glorytun[2592]: 109.190.216.206.5006: key exchange failed
Tue Apr 17 18:13:13 2018 daemon.info glorytun[2592]: STOPPED tun0
Tue Apr 17 18:13:14 2018 daemon.err glorytun[2592]: 109.190.216.206.5006: connected
Tue Apr 17 18:13:19 2018 daemon.err glorytun[2592]: 109.190.216.206.5006: key exchange failed
Tue Apr 17 18:13:19 2018 daemon.info glorytun[2592]: STOPPED tun0
Tue Apr 17 18:13:20 2018 daemon.err glorytun[2592]: 109.190.216.206.5006: connected
Tue Apr 17 18:13:21 2018 daemon.err graph[2843]: curl: (6) Could not resolve host: opentsdb.gra1.metrics.ovh.net
Tue Apr 17 18:13:22 2018 daemon.err otb-daemon[3314]: curl: (28) Connection timed out after 5001 milliseconds
Tue Apr 17 18:13:25 2018 daemon.err glorytun[2592]: 109.190.216.206.5006: key exchange failed
Tue Apr 17 18:13:25 2018 daemon.info glorytun[2592]: STOPPED tun0
Tue Apr 17 18:13:26 2018 daemon.err glorytun[2592]: 109.190.216.206.5006: connected
Tue Apr 17 18:13:28 2018 daemon.err otb-daemon[3314]: curl: (28) Connection timed out after 5001 milliseconds
Tue Apr 17 18:13:31 2018 daemon.err graph[3592]: curl: (6) Could not resolve host: opentsdb.gra1.metrics.ovh.net
Tue Apr 17 18:13:31 2018 daemon.err glorytun[2592]: 109.190.216.206.5006: key exchange failed
Tue Apr 17 18:13:31 2018 daemon.info glorytun[2592]: STOPPED tun0
Tue Apr 17 18:13:32 2018 daemon.err glorytun[2592]: 109.190.216.206.5006: connected
Tue Apr 17 18:13:34 2018 daemon.err otb-daemon[3314]: curl: (28) Connection timed out after 5001 milliseconds
Tue Apr 17 18:13:37 2018 daemon.err glorytun[2592]: 109.190.216.206.5006: key exchange failed
Tue Apr 17 18:13:37 2018 daemon.info glorytun[2592]: STOPPED tun0
Tue Apr 17 18:13:38 2018 daemon.err glorytun[2592]: 109.190.216.206.5006: connected
Tue Apr 17 18:13:40 2018 daemon.err otb-daemon[3314]: curl: (28) Connection timed out after 5000 milliseconds
Tue Apr 17 18:13:42 2018 daemon.err graph[4367]: curl: (6) Could not resolve host: opentsdb.gra1.metrics.ovh.net
Tue Apr 17 18:13:43 2018 daemon.err glorytun[2592]: 109.190.216.206.5006: key exchange failed
Tue Apr 17 18:13:43 2018 daemon.info glorytun[2592]: STOPPED tun0
Tue Apr 17 18:13:44 2018 daemon.err glorytun[2592]: 109.190.216.206.5006: connected
Tue Apr 17 18:13:47 2018 daemon.err otb-daemon[3314]: curl: (28) Connection timed out after 5001 milliseconds
Tue Apr 17 18:13:49 2018 daemon.err glorytun[2592]: 109.190.216.206.5006: key exchange failed
Tue Apr 17 18:13:49 2018 daemon.info glorytun[2592]: STOPPED tun0
Tue Apr 17 18:13:50 2018 daemon.err glorytun[2592]: 109.190.216.206.5006: connected
Tue Apr 17 18:13:50 2018 daemon.info glorytun[2592]: STARTED tun0
Tue Apr 17 18:13:51 2018 daemon.err ssh[28372]:
Tue Apr 17 18:13:51 2018 daemon.err ssh[28372]: /usr/bin/ssh: Connection to limited-user@167.114.245.74:46850 exited: Error reading: Connection reset by peer
Tue Apr 17 18:13:52 2018 daemon.err graph[4990]: curl: (6) Could not resolve host: opentsdb.gra1.metrics.ovh.net
Tue Apr 17 18:13:53 2018 daemon.err otb-daemon[3314]: curl: (28) Connection timed out after 5001 milliseconds
Tue Apr 17 19:13:00 2018 daemon.err otb-daemon[3314]: curl: (28) Connection timed out after 5001 milliseconds
Tue Apr 17 19:13:06 2018 daemon.err otb-daemon[3314]: curl: (28) Operation timed out after 5000 milliseconds with 0 out of 0 bytes received
Tue Apr 17 19:18:52 2018 kern.err kernel: [332174.485568] mptcp_verif_dss_csum csum is wrong: 0x3721 data_seq 4028056839 dss_csum_added 1 overflowed 0 iterations 1
Tue Apr 17 19:53:09 2018 daemon.err ss-redir[3802]: 2018-04-17 19:53:09 ERROR: send: Connection reset by peer
Tue Apr 17 19:53:09 2018 daemon.err ss-redir[3802]: 2018-04-17 19:53:09 ERROR: send: Connection reset by peer
Tue Apr 17 19:53:10 2018 daemon.err ss-redir[3802]: 2018-04-17 19:53:10 ERROR: send: Connection reset by peer
Tue Apr 17 20:00:06 2018 kern.err kernel: [334649.157871] mptcp_verif_dss_csum csum is wrong: 0xe6d9 data_seq 1933022715 dss_csum_added 1 overflowed 0 iterations 1
Tue Apr 17 20:05:58 2018 kern.err kernel: [335001.566319] mptcp_verif_dss_csum csum is wrong: 0x15e2 data_seq 1042368277 dss_csum_added 1 overflowed 0 iterations 1
Tue Apr 17 20:30:03 2018 daemon.err ss-redir[3802]: 2018-04-17 20:30:03 ERROR: server recv: Operation timed out
Tue Apr 17 20:32:33 2018 kern.err kernel: [336597.063238] mptcp_verif_dss_csum csum is wrong: 0xf1c0 data_seq 1654565528 dss_csum_added 1 overflowed 0 iterations 1
Tue Apr 17 20:34:10 2018 kern.err kernel: [336693.670569] mptcp_verif_dss_csum csum is wrong: 0x833a data_seq 2844624883 dss_csum_added 1 overflowed 0 iterations 1
Tue Apr 17 20:36:10 2018 kern.err kernel: [336814.264478] mptcp_verif_dss_csum csum is wrong: 0xa647 data_seq 3464618912 dss_csum_added 1 overflowed 0 iterations 1
Tue Apr 17 20:38:23 2018 kern.err kernel: [336947.539634] mptcp_verif_dss_csum csum is wrong: 0x5385 data_seq 3069284436 dss_csum_added 1 overflowed 0 iterations 1
Tue Apr 17 20:51:23 2018 daemon.err ss-redir[3802]: 2018-04-17 20:51:23 ERROR: server recv: Operation timed out
Tue Apr 17 21:11:05 2018 kern.err kernel: [338909.511959] mptcp_verif_dss_csum csum is wrong: 0x4f2a data_seq 3512423046 dss_csum_added 1 overflowed 0 iterations 1
Tue Apr 17 21:11:51 2018 kern.err kernel: [338955.469371] mptcp_verif_dss_csum csum is wrong: 0xe3c9 data_seq 3446668138 dss_csum_added 1 overflowed 0 iterations 1
Tue Apr 17 21:17:39 2018 daemon.err uhttpd[2442]: /usr/lib/lua/luci/dispatcher.lua:452: Failed to execute call dispatcher target for entry '/admin/overthebox/bandwidth_status/all'.
Tue Apr 17 21:17:39 2018 daemon.err uhttpd[2442]: The called action terminated with an exception:
Tue Apr 17 21:17:39 2018 daemon.err uhttpd[2442]: /usr/lib/lua/luci/controller/admin/overthebox.lua:511: bad argument #1 to 'len' (string expected, got nil)
Tue Apr 17 21:17:39 2018 daemon.err uhttpd[2442]: stack traceback:
Hilfreich (0)
G

Les premiers logs proviennent de mes tests, tu constates des problèmes ?
Hilfreich (0)
S

Non tout marche
merci beaucoup
Hilfreich (0)
S

Quand on télécharge un fichier de 1Go par exemple, c'est le débit montant ou descendant qui est utiliser ?
Hilfreich (0)

An Diskussion teilnehmen