[BUG] Internet Outage, Tests stopped.

[buliwyf42]

Describe the bug Yesterday i had an internet Outage with a lot of packet loss and high latency. The Speedtests stopped sometime during the outage and did not restart until I did a manual test this morning.

To Reproduce

Expected behavior I expect the speedtest to go on and always try to execute a test. If it fails, so be it.

Screenshots

Context

• OS: Docker on Synology. 2021-05-04 15:43:02
• Speedtest-Tracker Version: 1.10.4

[buliwyf42]

Yesterday the same happend again. I found this in the logfiles: ` ld jobs from queue

[cont-init.d] 50-speedtest: exited 0.

[cont-init.d] 99-custom-files: executing...

[custom-init] no custom files found exiting...

[cont-init.d] 99-custom-files: exited 0.

[cont-init.d] done.

[services.d] starting services

[services.d] done.

{"type":"log","timestamp":"2021-05-19T10:45:39Z","message":"Trying to get interface information on non-initialized socket.","level":"error"}

{"type":"log","timestamp":"2021-05-19T12:15:38Z","message":"Trying to get interface information on non-initialized socket.","level":"error"}

{"type":"log","timestamp":"2021-05-19T15:30:38Z","message":"Trying to get interface information on non-initialized socket.","level":"error"}

{"type":"log","timestamp":"2021-05-19T15:45:30Z","message":"Trying to get interface information on non-initialized socket.","level":"error"}

{"type":"log","timestamp":"2021-05-19T16:00:39Z","message":"Trying to get interface information on non-initialized socket.","level":"error"}

[2021-05-19 19:15:13.154] [error] Trying to get interface information on non-initialized socket.

{"type":"log","timestamp":"2021-05-19T17:15:55Z","message":"Trying to get interface information on non-initialized socket.","level":"error"}

{"type":"log","timestamp":"2021-05-19T18:45:44Z","message":"Trying to get interface information on non-initialized socket.","level":"error"}

{"type":"log","timestamp":"2021-05-19T19:00:39Z","message":"Trying to get interface information on non-initialized socket.","level":"error"}

{"type":"log","timestamp":"2021-05-19T20:00:25Z","message":"Error: [11] Cannot read: Resource temporarily unavailable","level":"error"}

{"type":"log","timestamp":"2021-05-19T20:00:25Z","message":"Error: [11] Cannot read: Resource temporarily unavailable","level":"error"}

{"type":"log","timestamp":"2021-05-19T20:00:25Z","message":"Error: [11] Cannot read: Resource temporarily unavailable","level":"error"}

{"type":"log","timestamp":"2021-05-19T20:00:25Z","message":"Error: [11] Cannot read: Resource temporarily unavailable","level":"error"}

{"type":"log","timestamp":"2021-05-19T20:00:26Z","message":"Error: [11] Cannot read: Resource temporarily unavailable","level":"error"}

{"type":"log","timestamp":"2021-05-19T20:00:29Z","message":"Error: [11] Cannot read: Resource temporarily unavailable","level":"error"}

{"type":"log","timestamp":"2021-05-19T20:00:30Z","message":"Error: [11] Cannot read: Resource temporarily unavailable","level":"error"}

{"type":"log","timestamp":"2021-05-19T20:00:30Z","message":"Error: [11] Cannot read: Resource temporarily unavailable","level":"error"}

[cont-finish.d] executing container finish scripts...

[cont-finish.d] done.

[s6-finish] waiting for `

[OliverRC]

Just ran across this, it seems if a test errors with a socket level error it does not recover, and therefore all the tests stop running. Even manually triggering tests does not work.