Kash76

Ah! Only your containers since you have the health check. Thank you!! I have converted to your containers. I really appreciate the help!!

I'm also having problems where none of my containers restart. Thanks for any guidance you can provide. My hunch is my permissions on the docker.sock need to be updated to allow r/w access to user:nobody? Based on the prior questions, here are some details: root@unRAID:~# ls -al /var/run/docker.sock srw-rw---- 1 root docker 0 Mar 24 07:48 /var/run/docker.sock= docker run -d --name='binhex-healarr' --net='bridge' --pids-limit 2048 -e TZ="America/Chicago" -e HOST_OS="Unraid" -e HOST_HOSTNAME="unRAID" -e HOST_CONTAINERNAME="binhex-healarr" -e 'DOCKER_HOST'='' -e 'MONITOR_INTERVAL'='60' -e 'RETRY_COUNT'='3' -e 'RETRY_DELAY'='10' -e 'ACTION'='restart' -e 'CONTAINER_LABEL'='' -e 'CONTAINER_ENV_VAR'='MONITOR_ENABLED=true' -e 'CONTAINER_NAME'='' -e 'APPRISE_NOTIFICATION_SERVICES'='' -e 'LOG_LEVEL'='1' -e 'ENABLE_HEALTHCHECK'='yes' -e 'HEALTHCHECK_COMMAND'='' -e 'HEALTHCHECK_ACTION'='' -e 'HEALTHCHECK_HOSTNAME'='google.com' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='000' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/healarr-icon.png' -v '/mnt/user/appdata/binhex-healarr':'/config':'rw' -v '/var/run/docker.sock':'/var/run/docker.sock':'rw' --restart=always 'ghcr.io/binhex/arch-healarr' Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2026-04-03 08:32:15.249214 [info] Host is running unRAID 2026-04-03 08:32:15.269035 [info] System information: Linux ea450202c871 6.12.54-Unraid #1 SMP PREEMPT_DYNAMIC Tue Oct 21 15:58:46 PDT 2025 x86_64 GNU/Linux 2026-04-03 08:32:15.289080 [info] Image architecture: 'amd64' 2026-04-03 08:32:15.307815 [info] Application name: 'healarr' 2026-04-03 08:32:15.327875 [info] Base image release tag: '2025122801' 2026-04-03 08:32:15.347837 [info] Application image release tag: '1.0.25-01' 2026-04-03 08:32:15.371331 [info] PUID defined as '99' 2026-04-03 08:32:15.398007 [info] Executing usermod for PUID '99'... 2026-04-03 08:32:15.433845 [info] usermod completed successfully 2026-04-03 08:32:15.457512 [info] PGID defined as '100' 2026-04-03 08:32:15.479901 [info] Executing groupmod for PGID '100'... 2026-04-03 08:32:15.518542 [info] groupmod completed successfully 2026-04-03 08:32:15.538752 [info] UMASK defined as '000' 2026-04-03 08:32:15.562347 [info] Permissions file '/config/perms.txt' exists, skipping setting ownership and permissions on '/config' and '/data' 2026-04-03 08:32:15.589881 [info] Deleting files in /tmp (non recursive)... 2026-04-03 08:32:15.651967 [info] Applying chown to paths '/home/nobody'... 2026-04-03 08:32:15.681156 [info] Starting Supervisor... 2026-04-03 08:32:15,800 INFO Included extra file "/etc/supervisor/conf.d/healarr.conf" during parsing 2026-04-03 08:32:15,800 INFO Set uid to user 0 succeeded 2026-04-03 08:32:15,803 INFO RPC interface 'supervisor' initialized 2026-04-03 08:32:15,804 INFO supervisord started with pid 7 2026-04-03 08:32:16,806 INFO spawned: 'healarr-script' with pid 81 2026-04-03 08:32:16,807 INFO reaped unknown pid 8 (exit status 0) 2026-04-03 08:32:16,859 DEBG 'healarr-script' stdout output: [INFO] 2026-04-03 08:32:16 :: Docker socket at '/var/run/docker.sock' is accessible 2026-04-03 08:32:16,859 INFO success: healarr-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2026-04-03 08:32:16,862 DEBG 'healarr-script' stdout output: [INFO] 2026-04-03 08:32:16 :: Docker CLI and Apprise CLI found and accessible 2026-04-03 08:32:16,866 DEBG 'healarr-script' stdout output: [INFO] 2026-04-03 08:32:16 :: MONITOR_INTERVAL set to '60' seconds 2026-04-03 08:32:16,870 DEBG 'healarr-script' stdout output: [INFO] 2026-04-03 08:32:16 :: RETRY_COUNT set to '3' 2026-04-03 08:32:16,874 DEBG 'healarr-script' stdout output: [INFO] 2026-04-03 08:32:16 :: RETRY_DELAY set to '10' seconds 2026-04-03 08:32:16,879 DEBG 'healarr-script' stdout output: [INFO] 2026-04-03 08:32:16 :: ACTION set to 'restart' 2026-04-03 08:32:16,883 DEBG 'healarr-script' stdout output: [INFO] 2026-04-03 08:32:16 :: Filtering containers by environment variable: MONITOR_ENABLED=true 2026-04-03 08:32:16,887 DEBG 'healarr-script' stdout output: [INFO] 2026-04-03 08:32:16 :: Starting healarr (interval: 60 seconds)... 2026-04-03 08:32:16,931 DEBG 'healarr-script' stdout output: [INFO] 2026-04-03 08:32:16 :: Healarr self-health check passed (status: starting). Proceeding with container monitoring... 2026-04-03 08:32:16,950 DEBG 'healarr-script' stdout output: [INFO] 2026-04-03 08:32:16 :: No unhealthy containers found 2026-04-03 08:32:16,955 DEBG 'healarr-script' stdout output: [INFO] 2026-04-03 08:32:16 :: Sleeping for 60 seconds before next check... 2026-04-03 08:33:17,001 DEBG 'healarr-script' stdout output: [INFO] 2026-04-03 08:33:16 :: Healarr self-health check passed (status: healthy). Proceeding with container monitoring... 2026-04-03 08:33:17,023 DEBG 'healarr-script' stdout output: [INFO] 2026-04-03 08:33:17 :: No unhealthy containers found

Hey all, I am suddenly having issues with bitmagnet. I recently replaced my cache pool and restored from backup from CA tools AND I use the container behind a GlutunVPN container. I have removed the image, removed my appdata directory and the problem still exists. I see the database being created on a fresh load followed by failed pings. Has anyone experienced this? I am probably missing something obvious, thank you for another set of eyes. 2026-03-23 20:51:56,523 INFO spawned: 'start' with pid 494 2026-03-23 20:51:56,532 DEBG 'start' stdout output: [info] bitmagnet classifier.yml not found 2026-03-23 20:51:56,534 DEBG 'start' stdout output: [info] bitmagnet config.yml file already exists, skipping copy... 2026-03-23 20:51:56,536 DEBG 'start' stdout output: [info] bitmagnet classifier.yml file already exists, skipping copy... 2026-03-23 20:51:56,539 DEBG 'start' stdout output: [info] Deleting /config/postgres/data/postmaster.pid from previous run... 2026-03-23 20:51:56,551 DEBG 'start' stdout output: [info] Waiting for PostgreSQL to be ready... 2026-03-23 20:51:56,569 DEBG 'start' stderr output: 2026-03-23 20:51:56.569 CDT [501] LOG: starting PostgreSQL 16.11 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 15.2.1 20251112, 64-bit 2026-03-23 20:51:56.569 CDT [501] LOG: listening on IPv4 address "127.0.0.1", port 5432 2026-03-23 20:51:56,573 DEBG 'start' stderr output: 2026-03-23 20:51:56.573 CDT [501] LOG: listening on Unix socket "/run/postgresql/.s.PGSQL.5432" 2026-03-23 20:51:56,583 DEBG 'start' stderr output: 2026-03-23 20:51:56.583 CDT [506] LOG: database system was shut down at 2026-03-23 20:51:56 CDT 2026-03-23 20:51:56,594 DEBG 'start' stderr output: 2026-03-23 20:51:56.594 CDT [501] LOG: database system is ready to accept connections 2026-03-23 20:51:57,577 DEBG 'start' stdout output: [info] PostgreSQL is ready. 2026-03-23 20:51:57,577 INFO success: start entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2026-03-23 20:51:57,612 DEBG 'start' stdout output: [info] Database bitmagnet has been created. 2026-03-23 20:51:57,613 DEBG 'start' stdout output: [info] Database restore skipped (set POSTGRES_RESTORE_DB=true to enable) [info] FULL VACUUM skipped (set POSTGRES_VACUUM_DB=true to enable) [info] REINDEX skipped (set POSTGRES_REINDEX_DB=true to enable) 2026-03-23 20:51:58,649 DEBG 'start' stdout output: WARN postgres/postgres.go:102 failed to ping database, retrying... {"error": "failed to connect to user=postgres database=bitmagnet:\n\t[::1]:5432 (localhost): tls error: server refused TLS connection\n\t127.0.0.1:5432 (localhost): tls error: server refused TLS connection\n\t[::1]:5432 (localhost): failed SASL auth: FATAL: password authentication failed for user \"postgres\" (SQLSTATE 28P01)"} 2026-03-23 20:51:59,657 DEBG 'start' stdout output: WARN postgres/postgres.go:102 failed to ping database, retrying... {"error": "failed to connect to user=postgres database=bitmagnet:\n\t[::1]:5432 (localhost): tls error: server refused TLS connection\n\t127.0.0.1:5432 (localhost): tls error: server refused TLS connection\n\t[::1]:5432 (localhost): failed SASL auth: FATAL: password authentication failed for user \"postgres\" (SQLSTATE 28P01)"} 2026-03-23 20:52:00,665 DEBG 'start' stdout output: WARN postgres/postgres.go:102 failed to ping database, retrying... {"error": "failed to connect to user=postgres database=bitmagnet:\n\t[::1]:5432 (localhost): tls error: server refused TLS connection\n\t127.0.0.1:5432 (localhost): tls error: server refused TLS connection\n\t[::1]:5432 (localhost): failed SASL auth: FATAL: password authentication failed for user \"postgres\" (SQLSTATE 28P01)"} 2026-03-23 20:52:01,673 DEBG 'start' stdout output: WARN postgres/postgres.go:102 failed to ping database, retrying... {"error": "failed to connect to user=postgres database=bitmagnet:\n\t[::1]:5432 (localhost): tls error: server refused TLS connection\n\t127.0.0.1:5432 (localhost): tls error: server refused TLS connection\n\t[::1]:5432 (localhost): failed SASL auth: FATAL: password authentication failed for user \"postgres\" (SQLSTATE 28P01)"} 2026-03-23 20:52:02,681 DEBG 'start' stdout output: WARN postgres/postgres.go:102 failed to ping database, retrying... {"error": "failed to connect to user=postgres database=bitmagnet:\n\t[::1]:5432 (localhost): tls error: server refused TLS connection\n\t127.0.0.1:5432 (localhost): tls error: server refused TLS connection\n\t[::1]:5432 (localhost): failed SASL auth: FATAL: password authentication failed for user \"postgres\" (SQLSTATE 28P01)"} 2026-03-23 20:52:03,689 DEBG 'start' stdout output: WARN postgres/postgres.go:102 failed to ping database, retrying... {"error": "failed to connect to user=postgres database=bitmagnet:\n\t[::1]:5432 (localhost): tls error: server refused TLS connection\n\t127.0.0.1:5432 (localhost): tls error: server refused TLS connection\n\t[::1]:5432 (localhost): failed SASL auth: FATAL: password authentication failed for user \"postgres\" (SQLSTATE 28P01)"} 2026-03-23 20:52:04,697 DEBG 'start' stdout output: WARN postgres/postgres.go:102 failed to ping database, retrying... {"error": "failed to connect to user=postgres database=bitmagnet:\n\t[::1]:5432 (localhost): tls error: server refused TLS connection\n\t127.0.0.1:5432 (localhost): tls error: server refused TLS connection\n\t[::1]:5432 (localhost): failed SASL auth: FATAL: password authentication failed for user \"postgres\" (SQLSTATE 28P01)"} 2026-03-23 20:52:05,705 DEBG 'start' stdout output: WARN postgres/postgres.go:102 failed to ping database, retrying... {"error": "failed to connect to user=postgres database=bitmagnet:\n\t[::1]:5432 (localhost): tls error: server refused TLS connection\n\t127.0.0.1:5432 (localhost): tls error: server refused TLS connection\n\t[::1]:5432 (localhost): failed SASL auth: FATAL: password authentication failed for user \"postgres\" (SQLSTATE 28P01)"} 2026-03-23 20:52:06,714 DEBG 'start' stdout output: WARN postgres/postgres.go:102 failed to ping database, retrying... {"error": "failed to connect to user=postgres database=bitmagnet:\n\t[::1]:5432 (localhost): tls error: server refused TLS connection\n\t127.0.0.1:5432 (localhost): tls error: server refused TLS connection\n\t[::1]:5432 (localhost): failed SASL auth: FATAL: password authentication failed for user \"postgres\" (SQLSTATE 28P01)"} 2026-03-23 20:52:07,721 DEBG 'start' stdout output: WARN postgres/postgres.go:102 failed to ping database, retrying... {"error": "failed to connect to user=postgres database=bitmagnet:\n\t[::1]:5432 (localhost): tls error: server refused TLS connection\n\t127.0.0.1:5432 (localhost): tls error: server refused TLS connection\n\t[::1]:5432 (localhost): failed SASL auth: FATAL: password authentication failed for user \"postgres\" (SQLSTATE 28P01)"} 2026-03-23 20:52:07,729 DEBG 'start' stdout output: ERROR worker/worker.go:211 error starting worker {"key": "dht_crawler", "error": "timed out waiting for ping: failed to connect to user=postgres database=bitmagnet:\n\t[::1]:5432 (localhost): tls error: server refused TLS connection\n\t127.0.0.1:5432 (localhost): tls error: server refused TLS connection\n\t[::1]:5432 (localhost): failed SASL auth: FATAL: password authentication failed for user \"postgres\" (SQLSTATE 28P01)"} github.com/bitmagnet-io/bitmagnet/internal/worker.(*registry).Start /tmp/bitmagnet/internal/worker/worker.go:211 github.com/bitmagnet-io/bitmagnet/internal/app/cmd/workercmd.New.func1 /tmp/bitmagnet/internal/app/cmd/workercmd/command.go:44 github.com/urfave/cli/v2.(*Command).Run /home/nobody/go/pkg/mod/github.com/urfave/cli/[email protected]/command.go:276 github.com/urfave/cli/v2.(*Command).Run /home/nobody/go/pkg/mod/github.com/urfave/cli/[email protected]/command.go:269 github.com/urfave/cli/v2.(*Command).Run /home/nobody/go/pkg/mod/github.com/urfave/cli/[email protected]/command.go:269 github.com/urfave/cli/v2.(*App).RunContext /home/nobody/go/pkg/mod/github.com/urfave/cli/[email protected]/app.go:333 github.com/bitmagnet-io/bitmagnet/internal/app/cli.New.func4.1 /tmp/bitmagnet/internal/app/cli/cli.go:67 2026-03-23 20:52:07,731 DEBG 'start' stderr output: panic: timed out waiting for ping: failed to connect to user=postgres database=bitmagnet: [::1]:5432 (localhost): tls error: server refused TLS connection 127.0.0.1:5432 (localhost): tls error: server refused TLS connection [::1]:5432 (localhost): failed SASL auth: FATAL: password authentication failed for user "postgres" (SQLSTATE 28P01) goroutine 85 [running]: github.com/bitmagnet-io/bitmagnet/internal/app/cli.New.func4.1() /tmp/bitmagnet/internal/app/cli/cli.go:68 +0xdc 2026-03-23 20:52:07,731 DEBG 'start' stderr output: created by github.com/bitmagnet-io/bitmagnet/internal/app/cli.New.func4 in goroutine 84 /tmp/bitmagnet/internal/app/cli/cli.go:60 +0xad 2026-03-23 20:52:07,737 DEBG 'start' stderr output: 2026-03-23 20:52:07.737 CDT [501] LOG: received smart shutdown request 2026-03-23 20:52:07,738 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 22385099402704 for <Subprocess at 22385099571952 with name start in state RUNNING> (stdout)> 2026-03-23 20:52:07,738 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22385099736464 for <Subprocess at 22385099571952 with name start in state RUNNING> (stderr)> 2026-03-23 20:52:07,738 WARN exited: start (exit status 2; not expected) 2026-03-23 20:52:07,738 DEBG received SIGCHLD indicating a child quit 2026-03-23 20:52:07,740 INFO spawned: 'start' with pid 544 2026-03-23 20:52:07,749 DEBG 'start' stdout output: [info] bitmagnet classifier.yml not found 2026-03-23 20:52:07,751 DEBG 'start' stdout output: [info] bitmagnet config.yml file already exists, skipping copy... 2026-03-23 20:52:07,754 DEBG 'start' stdout output: [info] bitmagnet classifier.yml file already exists, skipping copy... 2026-03-23 20:52:07,756 DEBG 'start' stdout output: [info] Deleting /config/postgres/data/postmaster.pid from previous run... 2026-03-23 20:52:07,769 DEBG 'start' stdout output: [info] Waiting for PostgreSQL to be ready... 2026-03-23 20:52:07,787 DEBG 'start' stderr output: 2026-03-23 20:52:07.787 CDT [551] LOG: starting PostgreSQL 16.11 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 15.2.1 20251112, 64-bit 2026-03-23 20:52:07,787 DEBG 'start' stderr output: 2026-03-23 20:52:07.787 CDT [551] LOG: listening on IPv4 address "127.0.0.1", port 5432 2026-03-23 20:52:07,796 DEBG 'start' stderr output: 2026-03-23 20:52:07.796 CDT [551] LOG: listening on Unix socket "/run/postgresql/.s.PGSQL.5432" 2026-03-23 20:52:07,806 DEBG 'start' stderr output: 2026-03-23 20:52:07.806 CDT [556] LOG: database system was shut down at 2026-03-23 20:52:07 CDT 2026-03-23 20:52:07,817 DEBG 'start' stderr output: 2026-03-23 20:52:07.817 CDT [551] LOG: database system is ready to accept connections 2026-03-23 20:52:08,793 DEBG 'start' stdout output: [info] PostgreSQL is ready. 2026-03-23 20:52:08,793 INFO success: start entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2026-03-23 20:52:08,828 DEBG 'start' stdout output: [info] Database bitmagnet has been created. 2026-03-23 20:52:08,828 DEBG 'start' stdout output: [info] Database restore skipped (set POSTGRES_RESTORE_DB=true to enable) [info] FULL VACUUM skipped (set POSTGRES_VACUUM_DB=true to enable) [info] REINDEX skipped (set POSTGRES_REINDEX_DB=true to enable) 2026-03-23 20:52:09,865 DEBG 'start' stdout output: WARN postgres/postgres.go:102 failed to ping database, retrying... {"error": "failed to connect to user=postgres database=bitmagnet:\n\t[::1]:5432 (localhost): tls error: server refused TLS connection\n\t127.0.0.1:5432 (localhost): tls error: server refused TLS connection\n\t[::1]:5432 (localhost): failed SASL auth: FATAL: password authentication failed for user \"postgres\" (SQLSTATE 28P01)"} 2026-03-23 20:52:10,873 DEBG 'start' stdout output: WARN postgres/postgres.go:102 failed to ping database, retrying... {"error": "failed to connect to user=postgres database=bitmagnet:\n\t[::1]:5432 (localhost): tls error: server refused TLS connection\n\t127.0.0.1:5432 (localhost): tls error: server refused TLS connection\n\t[::1]:5432 (localhost): failed SASL auth: FATAL: password authentication failed for user \"postgres\" (SQLSTATE 28P01)"} 2026-03-23 20:52:11,882 DEBG 'start' stdout output: WARN postgres/postgres.go:102 failed to ping database, retrying... {"error": "failed to connect to user=postgres database=bitmagnet:\n\t[::1]:5432 (localhost): tls error: server refused TLS connection\n\t127.0.0.1:5432 (localhost): tls error: server refused TLS connection\n\t[::1]:5432 (localhost): failed SASL auth: FATAL: password authentication failed for user \"postgres\" (SQLSTATE 28P01)"} 2026-03-23 20:52:12,890 DEBG 'start' stdout output: WARN postgres/postgres.go:102 failed to ping database, retrying... {"error": "failed to connect to user=postgres database=bitmagnet:\n\t[::1]:5432 (localhost): tls error: server refused TLS connection\n\t127.0.0.1:5432 (localhost): tls error: server refused TLS connection\n\t[::1]:5432 (localhost): failed SASL auth: FATAL: password authentication failed for user \"postgres\" (SQLSTATE 28P01)"} 2026-03-23 20:52:13,891 WARN received SIGTERM indicating exit request 2026-03-23 20:52:13,891 DEBG killing start (pid 544) with signal SIGTERM 2026-03-23 20:52:13,891 INFO waiting for start to die

Hey everyone, using threadfin with Emby I am having 1204 errors related to FFMPEG. This error happens randomly a few minutes in or even close to an hour. Does anyone else have this issue? I’m wondering if it might be my IPTV provider. I’ve seen a lot of people have issues with FFMPEG and I’m not sure how to overcome it. Thanks! [Threadfin] [ERROR] FFMPEG error (Streaming was stopped by third party transcoder (FFmpeg / VLC)) - EC: 1204

I never got it working; I used my Raspberry Pi.

I have the container up and running but flight aware is not seeing any data. I find it interesting the ini and conf 'files' are directories?! Does this log look normal? There are lots of errors. 2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[110]: INFO Backend set to env 2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[110]: INFO Starting confd 2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[110]: INFO Backend source(s) set to 2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[113]: INFO Backend set to env 2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[113]: INFO Starting confd 2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[113]: INFO Backend source(s) set to s6-rc: info: service adsbexchange-stats successfully started s6-rc: info: service adsbexchange-mlat successfully started 2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[110]: INFO /usr/lib/fr24/public_html/config.js has UID 99 should be 0 2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[110]: INFO /usr/lib/fr24/public_html/config.js has GID 100 should be 0 2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[110]: INFO /usr/lib/fr24/public_html/config.js has mode drwxr-xr-x should be -rwxr-xr-x 2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[110]: INFO /usr/lib/fr24/public_html/config.js has md5sum yyyy should be xxx 2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[110]: INFO Target config /usr/lib/fr24/public_html/config.js out of sync 2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[110]: ERROR rename /usr/lib/fr24/public_html/.config.js735717544 /usr/lib/fr24/public_html/config.js: file exists 2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[110]: FATAL rename /usr/lib/fr24/public_html/.config.js735717544 /usr/lib/fr24/public_html/config.js: file exists 2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[113]: INFO /etc/fr24feed.ini has UID 99 should be 0 2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[113]: INFO /etc/fr24feed.ini has GID 100 should be 0 2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[113]: INFO /etc/fr24feed.ini has mode drwxr-xr-x should be -rwxr-xr-x 2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[113]: INFO /etc/fr24feed.ini has md5sum d41d8cd98f00b204e9800998ecf8427e should be 580dbab8e19fa85c97e7bb3603840914 2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[113]: INFO Target config /etc/fr24feed.ini out of sync 2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[113]: ERROR rename /etc/.fr24feed.ini803908162 /etc/fr24feed.ini: file exists 2024-09-30T23:12:30-05:00 18a4476a0b0c /opt/confd/bin/confd[113]: FATAL rename /etc/.fr24feed.ini803908162 /etc/fr24feed.ini: file exists s6-rc: warning: unable to start service confd-html: command exited 1 s6-rc: warning: unable to start service confd-fr24feed: command exited 1 [dump1090] Mon Sep 30 23:12:30 2024 CDT dump1090-fa v9.0 starting up. [dump1090] rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000001) [dump1090] Found Rafael Micro R820T tuner [dump1090] rtlsdr: tuner gain set to 49.6 dB (gain step 28) [dump1090] Allocating 4 zero-copy buffers Thanks!

Update - Someone in the flightaware forum helped me force the claim command by adding /feeder_id to the claim URL.

Hey all, I am having issues getting piaware to see my device. I purchased this receiver and antenna on Amazon. I can see the USB device Bus 001 Device 017: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T and when I run the following docker command docker run -it --rm \ -e 'SERVICE_ENABLE_DUMP1090=false' \ -e 'SERVICE_ENABLE_HTTP=false' \ -e 'SERVICE_ENABLE_FR24FEED=false' \ -e 'SERVICE_ENABLE_PIAWARE=false' \ thomx/fr24feed-piaware /usr/bin/piaware -plainlog I see the following piaware version 9.0.1 is running, process ID 213 your system info is: Linux 36c4029f021a 6.1.106-Unraid #1 SMP PREEMPT_DYNAMIC Wed Aug 21 23:36:07 PDT 2024 x86_64 GNU/Linux Connecting to FlightAware adept server at piaware.flightaware.com/1200 Connection with adept server at piaware.flightaware.com/1200 established TLS handshake with adept server at piaware.flightaware.com/1200 completed FlightAware server certificate validated encrypted session established with FlightAware logged in to FlightAware as user guest my feeder ID is c852714e-7c92-4f82-ad60-xxxxx no ADS-B data program seen listening on port 30005 for 3 seconds, next check in 60s UAT support disabled by local configuration setting: uat-receiver-type 0 msgs recv'd from dump1090; 0 msgs sent to FlightAware no ADS-B data program seen listening on port 30005 for 63 seconds, next check in 60s no ADS-B data program seen listening on port 30005 for 123 seconds, next check in 60s no ADS-B data program seen listening on port 30005 for 183 seconds, next check in 60s no ADS-B data program seen listening on port 30005 for 243 seconds, next check in 60s no ADS-B data program seen listening on port 30005 for 303 seconds, next check in 60s 0 msgs recv'd from dump1090 (0 in last 5m); 0 msgs sent to FlightAware no ADS-B data program seen listening on port 30005 for 363 seconds, trying to start it... attempting to start dump1090.. can't start dump1090, no services that look like dump1090 found When I visit https://fr.flightaware.com/adsb/piaware/claim, it never shows me a device. Any ideas? Thanks for any help you can offer!

Same for me. Hoping for a solution to this awesome solution!

I'm interested in decentralized storage and contributing to the network. Is this still a workable solution? Thanks!

I have also been having some issues. It's running again for me now but a couple of weeks ago I could only get it to run with the VPN off or oddly with debug logging enabled?! It's working now but only after a restart from last week - seems like it's gotten flaky

Thanks. What version of unRAID are you on? Sent from my iPhone using Tapatalk Pro

Are you all running the beta BIOS? I just setup my upgraded server and do not have the temp reading even after updating the most current non-beta. Thanks!

Well this is embarrassing. I had the http and https ports for LetsEncrypt crossed. Thanks for the support and sorry for the bother!!

Thank you! Making progress, did that and am now getting "ERR_SSL_PROTOCOL_ERROR" in Chrome and "SSL_ERROR_RX_RECORD_TOO_LONG" in Firefox. I usually do not have issues like this but am having a hell of a time troubleshooting this. Nothing in my error log, access log has entries like this... 10.x.x.x - - [27/Nov/2019:12:15:12 -0600] "\x16\x03\x01\x01.\x01\x00\x01*\x04\x03H\xC4z\xDE\x0B(\xF8\x9E-\x88\xD0l0\x8EC\xC9\x14\xBD\xC2\xD0\xFEq{\xE8\x07H\x9EX\xFDs\xF6D\x00\x00\x88\xC00\xC0,\xC0(\xC0$\xC0\x14\xC0" 400 157 "-" "-"