binhex

hmm those errors do look database related, you could leave it, it may sort itself out, if not then the easiest course of action would be nuke the db (as in delete /config/postgres). if you are going to go for the nuke option you may want to ensure the filtering is as you want as this is the time to sort it if you want a nice clean database.

yeah don't do that, config.yml and classifier.yml are similar but not the same, if you try to simply rename you will get errors in bitmagnet and it will not start, as shown in your log:- 2024-09-30 10:32:34,743 DEBG 'start' stdout output: [31mERROR[0m worker/worker.go:190 error starting worker {"key": "queue_server", "error": "1 error(s) decoding:\n\n* '' has invalid keys: classifier"} github.com/bitmagnet-io/bitmagnet/internal/boilerplate/worker.(*registry).Start /tmp/bitmagnet/internal/boilerplate/worker/worker.go:190 github.com/bitmagnet-io/bitmagnet/internal/boilerplate/app/cmd/worker.New.func1 /tmp/bitmagnet/internal/boilerplate/app/cmd/worker/command.go:42 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/boilerplate/cli.New.func4.1 /tmp/bitmagnet/internal/boilerplate/cli/cli.go:53 2024-09-30 10:32:34,743 DEBG 'start' stdout output: [34mINFO[0m worker/worker.go:218 stopped worker {"key": "http_server"} 2024-09-30 10:32:34,745 DEBG 'start' stderr output: panic: 1 error(s) decoding: * '' has invalid keys: classifier goroutine 30 [running]: github.com/bitmagnet-io/bitmagnet/internal/boilerplate/cli.New.func4.1() /tmp/bitmagnet/internal/boilerplate/cli/cli.go:54 +0x47 created by github.com/bitmagnet-io/bitmagnet/internal/boilerplate/cli.New.func4 in goroutine 29 /tmp/bitmagnet/internal/boilerplate/cli/cli.go:52 +0xb8 2024-09-30 10:32:34,754 DEBG 'start' stderr output: 2024-09-30 10:32:34.754 EDT [107] LOG: received smart shutdown request Also ensure you pull down the latest image, this includes an example classifier.yml and symlinks to the correct location inside the container.

'Torrent Tag' on the left hand side, expand it and you should see your named tag there with any matches.

Take a look here, the main meat of the filtering happens on line 45, you probably will want to tweak this to your prefererence:- https://github.com/binhex/documentation/blob/master/docker/configs/bitmagnet/classifier.yml Edit - if you want to see what it would delete without actually deleting anything then uncomment these lines:- https://github.com/binhex/documentation/blob/126eecd01f39402f440b149c22374c2600a6a92b/docker/configs/bitmagnet/classifier.yml#L47-L48 and comment https://github.com/binhex/documentation/blob/126eecd01f39402f440b149c22374c2600a6a92b/docker/configs/bitmagnet/classifier.yml#L46

I've been beavering away on filtering for bitmagnet and now have a working filter to reduce the crud and thus reduce the size of the database, I'm happy to share if anybody is interested.

hmm from your log i see it erroring due to pre-existing postmaster.pid, i will put some cleanup code in to delete the file on startup. 2024-09-29 17:42:11.704 EDT [67] FATAL: lock file "postmaster.pid" already exists

My postgres database is currently 27 GB, startup is around 1 second (located on NVMe), i would think its probably due to this @wgstarks although 10 minutes is mental even if it is located on the array!.

Are you running flaresolverr via VPN shared network? If so the timeout is probably due to failed VPN connection, restart the VPN container in that case.

fixed it :-), the prowlarr definition is incorrect for bitmagnet, the solution is to remove the imdb and tmdb from the search query in the prowlarr definition, so you end up with a definition looking like the attached. keep in mind this is a custom definition for now, otherwise the change could get overwritten, you will need to follow this see heading 'Adding a custom YML definition':- https://wiki.servarr.com/prowlarr/indexers custombitmagnet.yml once you have put the custom definition in place remove the old 'BitMagnet (Local DHT)' index site and select the 'Custom BitMagnet (Local DHT)' then give prowlarr a damn good restart and try sonarr again, works for me!. The magic sauce is line 35: it was tv-search: [q, season, ep, imdbid, tmdbid] changed to tv-search: [q, season, ep] so i have stripped out the imdbid and tmdbid from the query, this stops the garbage result. P.S. i have also altered the number of results returned to 500, feel free to drop this back down if you want fewer results.

Also interesting although old

Hmm this looks interesting in regards to garbage results:- https://forums.sonarr.tv/t/prowlarr-search-interactive-search-inaccurate/33692

ok did query in prowlarr and that also looks good, the results are relevant, so maybe this is bug in sonarr?, seems a fairly big bug though, unlikely based on the maturity of sonarr *shrug*.

rookie numbers 😁currently at 400,000, total for me is now over 3m and increasing still interesting!! i see the same thing, if i go to sonarr and try doing an interactive search it comes back with a load of bollox, basically nothing matches the show name!, so i though, ok lets see what the result is if i query bitmagnet directly, and sure enough that is fine!, for example try going to this url:- view-source:http://<your server ip>:3333/torznab/api?t=search&q=all%20creatures%20great%20and%20small&limit=200 and you should see matches but if i do a search in sonarr i get completely unrelated shows!

when you were listing it in the web ui what was the sort order? was it relevance or was it published?, reason i ask is i have switched the sort order to published, see my previous post:- Sadly there is no current way to choose the sort order via the torznap api 😞

that's surprising!, have you found a pattern to this or does it seem random?.

you can download the magnet via the info hash, click on an item in the web ui to expand it, copy the info hash and paste into your favourite torrent clients 'add torrent' function.

Ignore it, i see the same, i believe they are old DHT bootstrap endpoints that no longer exist, i would assume they will be removed in the next release.

this is what my prowlarr app settings for sonarr look like, do yours look similar?:- Also keep in mind you will need to permit prowlarr (inside the vpn) to talk to sonarr (outside the vpn), this is done by adding sonarr port to VPN_OUTPUT_PORTS list, like so:-

it should do, yes, prowlarr pushes index configuration to radarr/sonarr, so if you can see the indexers appearing in radarr/sonarr then the chances are its configured correctly, hit the 'test' button to confirm but you should be good.

proxy will add complexity to this and is no longer required, remember jackett/prowlarr now do the metadata downloading here not sonarr/radarr so no need to proxy.

One other comment, from your screenshot it looks like you are making things a little more complex than they need to be, prowlarr already has a pre-defined index site for bitmagnet. no need to define custom:-

Nope it doesn't need to be but it makes things simpler if it does, fyi this is what i have inside the vpn network (privoxyvpn):- Prowlarr Jackett bitmagnet flaresolverr nicotine+ Then in a separate vpn tunnel is qbittorrentvpn, all other containers are on the standard host/bridge network, basically IMO you should only be putting applications inside the vpn network that either download files (torrent client) or download/interact with index sites. But if you do want prowlarr to talk to bitmagnet then you will need to use the ip address of your server NOT 'localhost', you only use localhost if you are performing communication between two applications inside the same (vpn) network, so this is wrong:- From the FAQ:- This is not the case for you (as things currently stand).

FYI you don't need to delete all files/folders if you change PUID/PGID, you can simply delete the file /config/perms.txt instead and then restart the container.

You can move it no problems, but the array will no doubt be slower leading to possible queues and the constant write will keep your disks spinning, if that's not a problem then go for it.

Take a look here https://github.com/bitmagnet-io/bitmagnet/discussions/307#discussioncomment-10652710