[BUG] Intermittent test failures

[pauljwilliams1976]

Is there an existing issue for this?

• [X] I have searched the existing issues

Current Behavior

(Saw this behaviour with the pre linuxserver container, is replicated with the new one)

Im seeing intermittent failures to run a scheduled speedtest. When I click on details of the failed tests I see:

{"type":"log","timestamp":"2024-02-09T20:05:29Z","message":"Path used: /root/.config/ookla/speedtest-cli.json","level":"error"}

Expected Behavior

Speedtests should run on schedule without failures

Steps To Reproduce

Click on 'Run test' Test fails to run.

Failure is intermittent, maybe 2/3rds of tests fail. Possibly an Ookla issue?

Environment

- OS: Unraid
- How docker service was installed: distro package

CPU architecture

x86-64

Docker creation

Compose snippet:

  speedtest-tracker:
    image: 'lscr.io/linuxserver/speedtest-tracker:latest'
    container_name: speedtest-tracker
    ports:
        - '9009:80'
        - '9010:443'
    environment:
      - PUID=$PUID
      - PGID=$PGID
      - TZ=$TZ
      - DB_CONNECTION=pgsql
      - DB_HOST=db
      - DB_PORT=5432
      - DB_DATABASE=speedtest_tracker
      - DB_USERNAME=speedy
      - DB_PASSWORD=password
      - LOG_LEVEL=debug
    volumes:
      - $ROOTDIR/config/speedtest-app:/config
      - $ROOTDIR/config/speedtest-app/web:/etc/ssl/web'
    restart: always
    depends_on:
        - db
  db:
      image: postgres:15
      container_name: postgres
      restart: always
      environment:
          - POSTGRES_DB=speedtest_tracker
          - POSTGRES_USER=speedy
          - POSTGRES_PASSWORD=password
      volumes:
          - $ROOTDIR/config/speedtest-db:/var/lib/postgresql/dat

Container logs

root@Tower:~# docker logs speedtest-tracker
[migrations] started
[migrations] 01-nginx-site-confs-default: executing...
[migrations] 01-nginx-site-confs-default: succeeded
[migrations] done
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support the app dev(s) visit:
speedtest-tracker: https://github.com/sponsors/alexjustesen

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1000
User GID:    100
───────────────────────────────────────

Setting resolver to  127.0.0.11
Setting worker_processes to 2
generating self-signed keys in /config/keys, you can replace these with your own keys if required
...+.+..+...+++++++++++++++++++++++++++++++++++++++*..+.+..+.........+.........+....+..+.+...+...........+.+.................+.+.....+++++++++++++++++++++++++++++++++++++++*......+..+...+...+....++++++
.........+...+..+....+.....+...+.+..+++++++++++++++++++++++++++++++++++++++*......+...+....+...+.....+.+..+....+...+............+........+.+..+....+++++++++++++++++++++++++++++++++++++++*...+..+.+..+...+....+......+.....+.+..............+.+...........+...+....+......+...........+.+...+......+.....+.............+...+..+.+..+.........+.+...++++++
-----
Waiting for DB to be available
An application key was generated at start up, as no environment variable was set.
To set an application key that persists, read the docs: https://docs.speedtest-tracker.dev/
[custom-init] No custom files found, skipping...
[ls.io-init] done.
[2024-02-09 20:05:33] production.INFO: Absolute threshold notifications disabled.

[github-actions[bot]]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[thespad]

This is unlikely to be a container-specific issue and so you'll need to open an issue against the upstream repo - we're building and supporting the container but Alex is still maintaining the application.