5 hours ago, binhex said:

i should be able to add some code in to pass a flag to the healthcheck script i wrote to turn off healthchecking if a vacuum/reindex/backup/restore process is in operation.

That sounds like a sensible addition and would likely avoid my problem in the future.

The restore from (the new, container-internal) backup worked well, by the way, and had the added benefit that it essentially took care of vacuuming as well. My DB shrank from 100gb to 75Gb. All is well.

By the way, would you mind posting your current set of filters? Keeping your DB this slim is impressive.

2 minutes ago, csb said:

The restore from (the new, container-internal) backup worked well, by the way, and had the added benefit that it essentially took care of vacuuming as well. My DB shrank from 100gb to 75Gb. All is well.

Ah excellent!, I love a good ending to a story :-)

2 minutes ago, csb said:

By the way, would you mind posting your current set of filters? Keeping your DB this slim is impressive

Sure, it is highly tailored to what i want, which is the following:

1. no porn whatsoever

2. i am into emulation, so i classify rom file types.

3. no unknown torrents, if bitmagnet cannot clasifiy it i don't want it.

Gist

bitmagnet classifier.yml

bitmagnet classifier.yml. GitHub Gist: instantly share code, notes, and snippets.

This gives me a pretty clean library of just what i want.

21 hours ago, binhex said:

i should be able to add some code in to pass a flag to the healthcheck script i wrote to turn off healthchecking if a vacuum/reindex/backup/restore process is in operation.

This has now been done and is included in the latest image, please pull down at your convienience.

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

I got bored of torrents with zero seed counts popping up so i have added filtering in my classifier.yml file, i decided to enhance the example clssifier too, if you are interested in filtering dead torrents then check out the following code section here, any questions let me know, it's working well for me.

Had to move the db back to array. The size had gotten up to >300GB and it was taking over my m.2 cache drive.

3 minutes ago, wgstarks said:

Had to move the db back to array. The size had gotten up to >300GB and it was taking over my m.2 cache drive.

44GB for me, 5.1 Million torrents so far, 300GB is wild!

Actually that may not be totally accurate. That was the size of the postgres folder. I think it’s just data in there but may not be. I have it limited to just movies and tv. Wish I could tweak it some more.

11 hours ago, wgstarks said:

Actually that may not be totally accurate. That was the size of the postgres folder. I think it’s just data in there but may not be. I have it limited to just movies and tv. Wish I could tweak it some more.

The biggest win for me was removing all uncategorised torrents, so my uknown torrents = 0, this is a big saving but does mean you need to ensure you get as much positives tagged as possible before you dump the unknowns, take a look here:- https://forums.unraid.net/topic/174999-support-binhex-bitmagnet/page/9/#findComment-1598038

2 hours ago, binhex said:

The biggest win for me was removing all uncategorised torrents, so my uknown torrents = 0, this is a big saving but does mean you need to ensure you get as much positives tagged as possible before you dump the unknowns, take a look here:- https://forums.unraid.net/topic/174999-support-binhex-bitmagnet/page/9/#findComment-1598038

I notice your classifier.yml doesn't have a banned section. Do I need to update mine?

classifier.yml

I also don't see the section for removing torrents with 0 seeders.