Invalid Date

[OhjeezwhathaveIdone]

Intermittently when tests are run either manually or via schedule the test will fail with an 'Invalid Date' in the time field.

[1Nexus1]

Having exactly the same issue here. Is it linked to European versus US format?

[PhilippeSch]

Having the same issue, but only on about 10% off all speedtests. Seems to occur randomly, which is very strange...

[007seb]

Same here, with a Timezone environment variable set to TZ=Europe/Paris. It's more like 95% of Invalid Date lines and 5% ok. It started to show "Invalidate Date" from 23/08/2021, 16:00:27. Then it was ok starting from 09/01/2021, 00:00:01 until 09/12/2021, 22:00:02. Starting from that date, I only got about 5% good tests ok. Starting from 10/01/2021, 00:00:01, I don't see "Invalid Date" error message anymore, but sppedtests are KO 95% of the time.

[fdegraeve]

Same issue for me. 100% of my tests failed. Do you have an idea to solve this ?

[PhilippeSch]

In the last 7 days I did not experience the issue anymore. I believe it is related to the removal of one unreliable test server. I suggest to use only one single test server which seems ok to see if this is really related to the test servers :).

[KongGal]

Try and check logs, mine apparently had lost its acceptance for EULA / GDPR
ran docker exec -it speedtest php /config/www/artisan speedtest:eula
or bash into the container and run the command manually from there. that should accept the EULA and after that it worked all fine for me again.

[Misioslav]

Try and check logs, mine apparently had lost its acceptance for EULA / GDPR ran docker exec -it speedtest php /config/www/artisan speedtest:eula or bash into the container and run the command manually from there. that should accept the EULA and after that it worked all fine for me again.

It did work, thanks!

[Chr1ssi]

could someone give a more detailed discription to fix this? i cant get it working

[KongGal]

could someone give a more detailed discription to fix this? i cant get it working

Run this command, replace speedtest with what you have called your container and then try and restart the container

docker exec -it speedtest php /config/www/artisan speedtest:eula

[Chr1ssi]

im still getting the same error... also getting this error when accepting Eula: Acceping EULA timeout: failed to run command ‘/config/www/app/Bin/speedtest’: Exec format error

[Chr1ssi]

I always have this error in the logs on startup: s6-applyuidgid: fatal: unable to exec /config/www/app/Bin/speedtest: Exec format error and this everytimne I try to run a speedtest: /config/www/app/Bin/speedtest: line 1: syntax error: unexpected ";"

[PhilippeSch]

I once again encountered the problem. The problem is that I am using a custom list of speedtest.net servers. Only one of those servers returned always this invalid date or whatever this is. After removing this faulty server once again (id=34267) all tests are good again...

[Chr1ssi]

I once again encountered the problem. The problem is that I am using a custom list of speedtest.net servers. Only one of those servers returned always this invalid date or whatever this is. After removing this faulty server once again (id=34267) all tests are good again...

But I’m not using a custom server list everything is default

[PhilippeSch]

But I’m not using a custom server list everything is default

Which means you are assigned a random server based on ping, location etc, which than again can be server which provide those unreadable results. Try using also a custom server list to see if this really is related to some strange server…

[Jayy001]

Using docker compose, haven't modified anything: I can run the 1st test with no problems what so ever, its always the second that gets it. Even if I remove all the config file for it to configure everything, once again it can only do the first one - Tried using docker exec -it speedtest php /config/www/artisan speedtest:eula to no avail....any ideas?

[Jayy001]

Yeah very weird...

[canoben]

I'm having the same problem (invalid date) every time a test is executed. I'm using defualt settings. The docker command mentioned above does not work on my Synology docker installation (docker command not found).

[KongGal]

in that case you need to figure out the correct command for the Synology The above command takes it that you called your docker container for speedtest but find the right way for synology to execute a command inside a container or in the above case to execute bash so you enter the container, once your inside the container you run php /config/www/artisan speedtest:eula

What i can find from looking around you can select the container, select export from the settings menu and just export the settings and save it to your local computer, when you open the json file in a text editor there should be a cmd line thats empty such as "cmd" : "",

Try and put in php /config/www/artisan speedtest:eula so its "cmd" : "php /config/www/artisan speedtest:eula",

that should make it run that command
after that you upload the file to the Synology using file station. go back to the Docker UI and stop the container and delete it, now select Import from the settings menu and import the settings file you just uploaded

This should tell docker to run this command everytime you start the container

https://community.synology.com/enu/forum/1/post/140204
If this doesn't work i am not sure, never played around with a Synology before

[canoben]

Firstly, thank you for your help. There is a way to start a terminal inside a docker session in Synology, but strangely enough it doesn't accept the docker command.So I tried your suggestion, but now I always get the following error:

s6-applyuidgid: fatal: unable to exec /site/app/Bin/speedtest: No such file or directory
cp: cannot stat 'speedtest': No such file or directory
tar: can't open 'speedtest.tgz': No such file or directory
wget: error getting response: Connection reset by peer
Connecting to install.speedtest.net (151.101.66.219:443)
Ookla GDPR and EULA accepted. Downloading Speedtest CLI.
[cont-init.d] 50-speedtest: executing... 
[cont-init.d] 40-config: exited 0.
"Starting 2019/12/30, GeoIP2 databases require personal license key to download. Please manually download/update the GeoIP2 db and save as /config/geoip2db/GeoLite2-City.mmdb"
[cont-init.d] 40-config: executing... 
[cont-init.d] 30-keygen: exited 0.
-----
writing new private key to '/config/keys/cert.key'
..................................................................+++++
.................................+++++
Generating a RSA private key
"generating self-signed keys in /config/keys, you can replace these with your own keys if required"
[cont-init.d] 30-keygen: executing... 
[cont-init.d] 20-config: exited 0.
[cont-init.d] 20-config: executing... 
[cont-init.d] 10-adduser: exited 0.
-------------------------------------
User gid:    911
User uid:    911
-------------------------------------
GID/UID
-------------------------------------
https://www.linuxserver.io/donate/
To support LSIO projects visit:
-------------------------------------
Brought to you by linuxserver.io


         |_| |___/ |_|  \__/
         | | \__ \ | | | () |
         | | / __| | |  /  \ 
         | |  ___   _    __
          _         ()
-------------------------------------
usermod: no changes
[cont-init.d] 10-adduser: executing... 
[cont-init.d] 01-envfile: exited 0.
[cont-init.d] 01-envfile: executing... 
[cont-init.d] executing container initialization scripts...
[fix-attrs.d] done.
[fix-attrs.d] applying ownership & permissions fixes...
[s6-init] ensuring user provided files have correct perms...exited 0.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.

I initially named the container speedtest-tracker, but getting this error ("no such file or directory") I chnaged every reference of speedtest-tracker to speedtest (except the repository name of course), but the error still persists.

[philharmonie]

Same error here. Get it randomly.

[tiritibambix]

Try and check logs, mine apparently had lost its acceptance for EULA / GDPR ran docker exec -it speedtest php /config/www/artisan speedtest:eula or bash into the container and run the command manually from there. that should accept the EULA and after that it worked all fine for me again.

This worked in my case. Thank you.

[meyergru]

It loses the acceptance once in a while. You can automate the process by bashing into the process, call "crontab -u root -e" and add a line like this:

0 7 1 * * php /config/www/artisan speedtest:eula

[js-ka]

Not possible to get things working:

I installed Speedtest via Synology Docker Image henrywhitaker3/speedtest-tracker:latest Start Container

name speedtest
Restart automatically
Port mapping 8765:80
Mount path /docker/speedtest > /config
Add OOKLA_EULA_GDPR true

Start Container Do a test at MY_IP:8765

No Result > Ping/Download/Upload > NaN InvalidDate / x / x / x

Tried accepting Eula manually

bash: php /config/www/artisan speedtest:eula
Accepting EULA
timeout: failed to run command '/config/www/app/Bin/speedtest': No such file or directory

Reason: Folder /config/www/app/Bin is empty.

Download https://install.speedtest.net/app/cli/ookla-speedtest-1.0.0-x86_64-linux.tgz Create folder /config/www/app/Bin/speedtest Extract archive I have three files: speedtest speedtest.5 speedtest.md

Again:

bash: php /config/www/artisan speedtest:eula
Accepting EULA
timeout: failed to run command '/config/www/app/Bin/speedtest': permission denied

but permissions are: -rwxrwxrwx

Restart Container Do a test at MY_IP:8765

Again: Result > Ping/Download/Upload > NaN InvalidDate / x / x / x

Also tried: Adding a dedicated speedtest server id Set the time zone to TZ Europe/Paris

Nothing was successful. Always the same result.

Any ideas?

[js-ka]

Logfile says: sh: /config/www/app/Bin/speedtest: Permission denied

But permissions are: speedtest folder: drwxrwxrwx speedtest files: -rwxrwxrwx

[js-ka]

I have found the reason. The files must be extracted directly into the bin folder. Then it works. :-)

[meyergru]

1. You should never have to download or install anything into a docker container, it will pull anything neccessary by itself.
2. I do not know why your initial call did not suceed.
3. The EULA must be accepted once in a while, so your manual call will only last so long. The crontab entry will fix it forever.