October 28, 20241 yr On 9/17/2022 at 10:12 AM, AGuyInTheWrongRoom said: Hi My binhex-prowlarr container keeps stopping for no apparent reason. The logs show this: 2022-09-12 03:00:11,095 WARN received SIGTERM indicating exit request 2022-09-12 03:00:11,095 DEBG killing start-script (pid 65) with signal SIGTERM 2022-09-12 03:00:11,095 INFO waiting for start-script to die 2022-09-12 03:00:11,230 DEBG 'start-script' stdout output: [Info] ConsoleApp: Exiting main. 2022-09-12 03:00:11,231 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23285748612304 for <Subprocess at 23285748610336 with name start-script in state STOPPING> (stdout)> 2022-09-12 03:00:11,231 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23285749057616 for <Subprocess at 23285748610336 with name start-script in state STOPPING> (stderr)> 2022-09-12 03:00:11,231 INFO stopped: start-script (exit status 143) 2022-09-12 03:00:11,231 DEBG received SIGCHLD indicating a child quit Does anybody have any idea what this could be? Thanks. Did updating your unraid version fix this? I am having the same issue and running on 7.0.0-beta.2. Crashes around 30 seconds after starting to the container: 2024-10-28 06:20:12,425 INFO reaped unknown pid 57 (terminated by SIGTERM) 2024-10-28 06:20:12,426 WARN received SIGTERM indicating exit request 2024-10-28 06:20:12,426 DEBG killing start-script (pid 62) with signal SIGTERM 2024-10-28 06:20:12,426 INFO waiting for start-script to die 2024-10-28 06:20:12,456 DEBG 'start-script' stdout output: [Info] Microsoft.Hosting.Lifetime: Application is shutting down... 2024-10-28 06:20:12,457 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23331880080096 for <Subprocess at 23331897015328 with name start-script in state STOPPING> (stdout)> 2024-10-28 06:20:12,457 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23331878559504 for <Subprocess at 23331897015328 with name start-script in state STOPPING> (stderr)> 2024-10-28 06:20:12,457 WARN stopped: start-script (exit status 143) 2024-10-28 06:20:12,458 DEBG received SIGCHLD indicating a child quit
November 17, 20241 yr @binhex, I'm seeing pretty much the exact same error now, any clues for me? The app starts ok, and I can use the GUI, right up until one of the connected apps sends a query, and prowlarr just dies. Well, apparently something about the connection wasn't right, I reestablished the VPN and no more crashes. Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2024-11-17 13:31:49.357468 [info] Host is running unRAID 2024-11-17 13:31:49.381668 [info] System information: Linux c266c5fda074 6.1.79-Unraid #1 SMP PREEMPT_DYNAMIC Fri Mar 29 13:34:03 PDT 2024 x86_64 GNU/Linux 2024-11-17 13:31:49.415567 [info] Image tags: BASE_RELEASE_TAG=2024110703,IMAGE_RELEASE_TAG=1.25.4.4818-6-01 2024-11-17 13:31:49.444624 [info] PUID defined as '99' 2024-11-17 13:31:49.478424 [info] PGID defined as '100' 2024-11-17 13:31:49.545501 [info] UMASK defined as '000' 2024-11-17 13:31:49.572215 [info] Permissions already set for '/config' 2024-11-17 13:31:49.604039 [info] Deleting files in /tmp (non recursive)... 2024-11-17 13:31:49.655690 [info] SHARED_NETWORK defined as 'yes' 2024-11-17 13:31:49.680858 [info] Starting Supervisor... 2024-11-17 13:31:49,859 INFO Included extra file "/etc/supervisor/conf.d/prowlarr.conf" during parsing 2024-11-17 13:31:49,859 INFO Set uid to user 0 succeeded 2024-11-17 13:31:49,862 INFO supervisord started with pid 7 2024-11-17 13:31:50,864 INFO spawned: 'start-script' with pid 61 2024-11-17 13:31:50,865 INFO reaped unknown pid 8 (exit status 0) 2024-11-17 13:31:51,389 DEBG 'start-script' stdout output: [Info] Bootstrap: Starting Prowlarr - /usr/lib/prowlarr/bin/Prowlarr - Version 1.25.4.4818 2024-11-17 13:31:51,410 DEBG 'start-script' stdout output: [Info] AppFolderInfo: Data directory is being overridden to [/config/prowlarr] 2024-11-17 13:31:51,428 DEBG 'start-script' stdout output: [Debug] Bootstrap: Console selected 2024-11-17 13:31:51,429 DEBG 'start-script' stdout output: [Info] AppFolderInfo: Data directory is being overridden to [/config/prowlarr] 2024-11-17 13:31:51,774 DEBG 'start-script' stdout output: [Info] AppFolderInfo: Data directory is being overridden to [/config/prowlarr] 2024-11-17 13:31:51,941 DEBG 'start-script' stdout output: [Info] MigrationController: *** Migrating data source=/config/prowlarr/prowlarr.db;cache size=-20000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3;busytimeout=100 *** 2024-11-17 13:31:51,941 INFO success: start-script entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-11-17 13:31:52,053 DEBG 'start-script' stdout output: [Info] FluentMigrator.Runner.MigrationRunner: DatabaseEngineVersionCheck migrating 2024-11-17 13:31:52,065 DEBG 'start-script' stdout output: [Info] FluentMigrator.Runner.MigrationRunner: PerformDBOperation 2024-11-17 13:31:52,066 DEBG 'start-script' stdout output: [Info] NzbDrone.Core.Datastore.Migration.Framework.NzbDroneSQLiteProcessor: Performing DB Operation 2024-11-17 13:31:52,117 DEBG 'start-script' stdout output: [Info] DatabaseEngineVersionCheck: SQLite 3.46.1 2024-11-17 13:31:52,119 DEBG 'start-script' stdout output: [Info] FluentMigrator.Runner.MigrationRunner: => 0.0517257s 2024-11-17 13:31:52,119 DEBG 'start-script' stdout output: [Info] FluentMigrator.Runner.MigrationRunner: DatabaseEngineVersionCheck migrated 2024-11-17 13:31:52,120 DEBG 'start-script' stdout output: [Info] FluentMigrator.Runner.MigrationRunner: => 0.0538289s 2024-11-17 13:31:52,157 DEBG 'start-script' stdout output: [Info] MigrationController: *** Migrating data source=/config/prowlarr/logs.db;cache size=-20000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3;busytimeout=100 *** 2024-11-17 13:31:52,163 DEBG 'start-script' stdout output: [Info] FluentMigrator.Runner.MigrationRunner: DatabaseEngineVersionCheck migrating 2024-11-17 13:31:52,164 DEBG 'start-script' stdout output: [Info] FluentMigrator.Runner.MigrationRunner: PerformDBOperation 2024-11-17 13:31:52,164 DEBG 'start-script' stdout output: [Info] NzbDrone.Core.Datastore.Migration.Framework.NzbDroneSQLiteProcessor: Performing DB Operation 2024-11-17 13:31:52,165 DEBG 'start-script' stdout output: [Info] DatabaseEngineVersionCheck: SQLite 3.46.1 2024-11-17 13:31:52,165 DEBG 'start-script' stdout output: [Info] FluentMigrator.Runner.MigrationRunner: => 0.0010176s 2024-11-17 13:31:52,165 DEBG 'start-script' stdout output: [Info] FluentMigrator.Runner.MigrationRunner: DatabaseEngineVersionCheck migrated 2024-11-17 13:31:52,165 DEBG 'start-script' stdout output: [Info] FluentMigrator.Runner.MigrationRunner: => 0.0011843s 2024-11-17 13:31:52,470 DEBG 'start-script' stdout output: [Info] Microsoft.Hosting.Lifetime: Now listening on: http://[::]:9696 2024-11-17 13:31:52,624 DEBG 'start-script' stdout output: [Info] CommandExecutor: Starting 3 threads for tasks. 2024-11-17 13:31:52,934 DEBG 'start-script' stdout output: [Info] ManagedHttpDispatcher: IPv4 is available: True, IPv6 will be disabled 2024-11-17 13:31:54,739 DEBG 'start-script' stdout output: [Info] Microsoft.Hosting.Lifetime: Application started. Press Ctrl+C to shut down. 2024-11-17 13:31:54,739 DEBG 'start-script' stdout output: [Info] Microsoft.Hosting.Lifetime: Hosting environment: Production 2024-11-17 13:31:54,739 DEBG 'start-script' stdout output: [Info] Microsoft.Hosting.Lifetime: Content root path: / 2024-11-17 13:34:00,865 INFO reaped unknown pid 56 (terminated by SIGTERM) 2024-11-17 13:34:00,865 WARN received SIGTERM indicating exit request 2024-11-17 13:34:00,865 DEBG killing start-script (pid 61) with signal SIGTERM 2024-11-17 13:34:00,865 INFO waiting for start-script to die 2024-11-17 13:34:00,867 DEBG 'start-script' stdout output: [Info] Microsoft.Hosting.Lifetime: Application is shutting down... 2024-11-17 13:34:00,867 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22429965173152 for <Subprocess at 22429947052000 with name start-script in state STOPPING> (stdout)> 2024-11-17 13:34:00,867 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22429961142592 for <Subprocess at 22429947052000 with name start-script in state STOPPING> (stderr)> 2024-11-17 13:34:00,868 WARN stopped: start-script (exit status 143) 2024-11-17 13:34:00,868 DEBG received SIGCHLD indicating a child quit Edited November 18, 20241 yr by JonathanM Solved (ish?)
November 26, 20241 yr I have all my dockers running into a separate vlan and it is impossible for me to setup prowlarr on the custom Br, is there a special config to do ? When specifying br, the docker does not get an IP ( Manual or DHCP )
November 27, 20241 yr 7 hours ago, chocorem said: I have all my dockers running into a separate vlan and it is impossible for me to setup prowlarr on the custom Br, is there a special config to do ? When specifying br, the docker does not get an IP ( Manual or DHCP ) Its an unraid bug. IP won't show, web UI link won't work from menu, but an IP is assigned and the UI will work if you specify the right IP
January 30, 20251 yr Trying to add the Readarr docker in Settings>Apps but when I test it just times out. Not sure what I'm missing? Using the same setup as I used for Sonarr/Radarr.
January 30, 20251 yr 35 minutes ago, wgstarks said: Trying to add the Readarr docker in Settings>Apps but when I test it just times out. Not sure what I'm missing? Using the same setup as I used for Sonarr/Radarr. is prowlarr and readarr on the same docker network?
January 30, 20251 yr Just now, ijuarez said: is prowlarr and readarr on the same docker network? mine is here is my config
January 30, 20251 yr 1 minute ago, ijuarez said: is prowlarr and readarr on the same docker network? Prowlarr is running on the binhex-shared network IIRC.
January 30, 20251 yr Just now, wgstarks said: Prowlarr is running on the binhex-shared network IIRC. So they are on two separate networks To me you have to add readarr to the binhex-network other wise it will not work. I do this using portainer to add multiple networks to one docker.
January 30, 20251 yr Author 6 minutes ago, ijuarez said: To me you have to add readarr to the binhex-network other wise it will not work This is not strictly true, you can either run it outside or inside of the vpn, the trick is getting the VPN_OUTPUT_PORT correct, i run reader on the default bridge and prowlarr is inside a shared vpn network, here is the magic, from my setup:- Keep in mind prowlarr communicates with reader, thus the port is defined for VPN_OUTPUT_PORTS
January 30, 20251 yr It’s not really separate networks. The binhex-shared network is being routed through binhex-privoxyvpn which is also on 10.0.1.20. Sonarr and Radarr both connect just fine in Prowlarr with the same configuration except for port numbers.
January 30, 20251 yr oh i stand corrected, you using binhex-vpn apps I do not I have whole vlan for vpn. sorry i will recuse my posts
January 30, 20251 yr 8 minutes ago, binhex said: This is not strictly true, you can either run it outside or inside of the vpn, the trick is getting the VPN_OUTPUT_PORT correct, i run reader on the default bridge and prowlarr is inside a shared vpn network, here is the magic, from my setup:- Keep in mind prowlarr communicates with reader, thus the port is defined for VPN_OUTPUT_PORTS Worked. Thx for the info.
February 2, 20251 yr On 10/26/2024 at 2:19 PM, Lien1454 said: I'm not sure what this is then? I've tried again today and I still get the same error. Only difference is the... /var/lib/docker/btrfs/subvolumes/bd4761a5f06c1f7309225dbcb10f9bec60d9e5e67c3d765ea19e21a3b8f7853c number changes each time. Anyone have any suggestions please? i have the same problem for some time now
March 11, 20251 yr hi, I have set up radarr, sonarr and prowlarr and would like them to go through my NordVPN ? Could anyone assist me in configuring this ? Much appreciated
April 22, 20251 yr Hi there, I have a problem with Prowlarr indexes. I get this message. " Unable to connect to indexer, please check your DNS settings and ensure IPv6 is working or disabled. An error occurred while sending the request " I have checked and my IPv6 is working fine. I'm using AdGuard and disabling it to check didn't resolve it. How can I resolve it please? Thanks.
April 27, 20251 yr On 3/11/2025 at 10:43 AM, Punisher said: hi, I have set up radarr, sonarr and prowlarr and would like them to go through my NordVPN ? Could anyone assist me in configuring this ? Much appreciate There are tutorials on YouTube about these subjects. Search for Spaceinvader One's video on these subjects.
May 3, 20251 yr On 4/22/2025 at 12:10 PM, Yannoviche said: Unable to connect to indexer, please check your DNS settings and ensure IPv6 is working or disabled. An error occurred while sending the request I couldn't find any solution for this, using custom network (vlan). Ended up migrating config to linuxserver version of prowlarr container and this issue went away.
May 3, 20251 yr Author On 4/22/2025 at 3:40 AM, Yannoviche said: Hi there, I have a problem with Prowlarr indexes. I get this message. " Unable to connect to indexer, please check your DNS settings and ensure IPv6 is working or disabled. An error occurred while sending the request " I have checked and my IPv6 is working fine. I'm using AdGuard and disabling it to check didn't resolve it. How can I resolve it please? Thanks. Im running prowlarr myself, no issues here, have you tried deleting the config and starting from fresh?
May 5, 20251 yr On 5/3/2025 at 9:59 AM, binhex said: Im running prowlarr myself, no issues here, have you tried deleting the config and starting from fresh? Hi Binhex, No I have not tried it yet. How do you actually do that as I have never done this before? Thank you.
June 8, 20251 yr Hello,I am also having trouble getting Prowlarr to connect to the Radarr and Sonarr. The indexers are testing with a green checkmark, but when i go and try to add the apps they dont want to connect. Message states that i have an invalid URL. I am not sure what i am doing wrong. Any advice here?prowlarr.debug.txt
June 13, 20251 yr On 6/9/2025 at 4:15 AM, ScottyBoom said:Hello,I am also having trouble getting Prowlarr to connect to the Radarr and Sonarr. The indexers are testing with a green checkmark, but when i go and try to add the apps they dont want to connect. Message states that i have an invalid URL. I am not sure what i am doing wrong. Any advice here?prowlarr.debug.txtRadarr is normally on port 7878, try using that instead
June 19, 20251 yr On 6/12/2025 at 6:39 PM, tjb_altf4 said:Radarr is normally on port 7878, try using that insteadThank you for your reply, I have Radarr on Host port 7877, i tried again on 7878, but it still was not working. I was able to figure out the indexer issues that occurring using SAB, so at this point i am hesitant to start changing things. I do appreciate you taking the time to repond.
July 17, 2025Jul 17 Im very sorry if this is obvious but im trying to setup this container and i just simply dont understand the 2 blank variable spaces and what is suppose to go there.
July 17, 2025Jul 17 52 minutes ago, Sinister said:Im very sorry if this is obvious but im trying to setup this container and i just simply dont understand the 2 blank variable spaces and what is suppose to go there.The Prowlarr docker allows for certain health checks. If you are not familiar with the process I would recommend just using the defaults (leave the fields blank).
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.