-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Speedtest not running via cron #216
Comments
Same issue here. Although I noticed I also get this error when trying to run manually: "speedtest server id XXXX not recognized". But it sometimes work, sometimes not, it's strange. The list of available servers also changes each time I reload the page... |
@mihakralj any idea? |
I never encountered this issue, but I can see that some servers differs every time, so it could be totally possible that you are having this problem. |
It suddenly started working yesterday for me, I have no explanation. I think I changed the cron schedule from daily to hourly, that's it. I still get the "speedtest server id XXXX not recognized" error with multiple servers, when I trigger it manually. |
list of speedtest servers is pulled straight out from speedtest CLI. Which one do you use - the Python one or Ookla binary? |
Speedtest forgot server id after a year of permanent use..offered me locations from some different country. |
try changing the file permissions on the csv file as follows
and now trying the cronjob or watch the System > Log files > Backend for succesful or failure of cronjob if the job runs successfully look at Reports > Speedtest --> Enable showlogs you should see your speedtest results based on cronjob schedule PS: i was able to fix this with the 666 as the perms on the csv file |
Hi,
I setup a cron job via the web gui to run a speedtest every hour, but reading the logs it looks like it doesn't ever run. The cron service is up and running and other cron jobs seems running fine. What the problem could be?
Here is the configuration of the cron job:
I tried to find some logs from cron or from the tool, but I didn't find anything relevant.
The text was updated successfully, but these errors were encountered: