speedtest-tracker: Scheduled test is not running at the correct, scheduled time

In general settings, I have 0 5 * * * as my scheduled speed test, which should be every day at 5 AM. However, it is running the speed test every day at 22:00, which is 10 PM. I don’t believe it’s a timezone issue because when I manually run a test, the shown last run time is correct.

About this issue

Original URL
State: closed
Created a year ago
Comments: 15 (9 by maintainers)

Most upvoted comments

TZ: America/Los_Angeles

PR submitted: https://github.com/alexjustesen/speedtest-tracker-docs/pull/14

alexdelprete on Jul 3, 2023

Binding /etc/localtime fixed it, I already had TZ: America/Los_Angeles - I believe it was actually running at 5AM PST but displaying 22:00. Adding the /etc/localtime bind seems to have updated the time on the tests to be 5AM

Thanks!

ampersandru on Jun 30, 2023

I don’t believe it’s a timezone issue because when I manually run a test, the shown last run time is correct.

Configure TZ env variable in docker-compose and also the localtime volume mapping:

version: '3.3'
services:
  speedtest-tracker:
    image: ghcr.io/alexjustesen/speedtest-tracker:v0.5.0
    container_name: speedtest-tracker
    restart: unless-stopped
    ports:
      - 8008:443
    environment:
      TZ: Europe/Rome
      PUID: 1000
      PGID: 1000
      DB_CONNECTION: mysql
      DB_HOST: mariadb.axel.dom
      DB_PORT: 3306
      DB_DATABASE: speedtest_tracker
      DB_USERNAME: xxxxxxxxxx
      DB_PASSWORD: **********
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - $PWD/config:/config
      - $PWD/certs:/etc/ssl/web

alexdelprete on Jun 30, 2023