WARNING: failed to start prowlarr

[chuck990]

Hi all,

I've just tried installing prowlarr alongside working instances of sonarr, lidarr and radarr in an existing jail, and the process won't even start.

I followed the instructions here:

Prowlarr Installation

Instructions and Guides for Installation of Prowlarr

wiki.servarr.com

but that's basically just doing a 'pkg install' as a first step. Even after just that, the process just won't start..

Any tips for first steps in troubleshooting please?

 

[JohnDigital]

Make sure the directories are owned by the user you are using.

 

[chuck990]

I've done the usr/local folder, is theer anything else I missed? Other 'arr apps have a usr/local/share folder but prowlarr doesn't look to.

chown -R Jail:Jail /usr/local/prowlarr

In the rc.conf I've also set

prowlarr_user=testnewmedia

 

[JohnDigital]

So if your user is set to testnewmedia you should use that instead of Jail:Jail. I dont think the share directory is created until you run it successfully.

chown -R testnewmedia:testnewmedia /usr/local/prowlarr

I suppose its also possible that you do have a user named Jail, in which case you should change the rc.conf prowlarr_user=Jail
One of those should work for you.

Then try starting it again

 

[chuck990]

Sorry, that's a copy paste error - there is a user called Jail, and the rc.conf sets the user as such.
No joy in starting the process, is there anywhere/way to get more verbose output than just "failed to start"?

 

[JohnDigital]

You can add the verbose flag service prowlarr start -v should give you a little more info. Look in the /usr/local/prowlarr for a log file and read it for more hints.

 

[JohnDigital]

So i have it up and working in like 1 minute, heres my exact steps.

Code:

pkg install prowlarr
sysrc prowlarr_enable=YES
sysrc prowlarr_user=USER
sysrc prowlarr_group=GROUP
service prowlarr start -v

It started and ran 1st go, I've never used it before and I've also installed it in a jail with some of the companion software you mentioned.

 

[JohnDigital]

Actually it doesnt seem to be working, however the service starts, reports as running and has a process. I cant pull up the web interface though and strange enough the /usr/local/prowlarr directory is empty

 

[JohnDigital]

Ok so i got to the bottom of this. In the jail properties you need to allow_mlock=1. Once I did this and restarted the jail the interface came up immediately.

 

[chuck990]

The jail has allow_mlock enabled, the rc.conf sets the user as Jail, and I've checked the 'usr/local/prowlarr' directory is appropriately owned by the Jail user (same as radarr and readarr which both work):

I still however, even with the '-v' command, just get the single line

/usr/local/etc/rc.d/prowlarr: WARNING failed to start prowlarr

the usr/local/prowlarr folder is empty, no logs no nothing

any other tips sorry?

 

[JohnDigital]

Did you have to set allow mlock or was it already there?

I had to restart the jail after I did it.

 

[JohnDigital]

Can i see your rc.conf

 

[chuck990]

allow_mlock was I think already there, but I may have enabled it at some point. Either way, the jail has restarted since.

Here's the rc.conf:

 

[TYFLOOZY]

I''m having an issue with Prowlarr not deploying, has not deployed ever, tried deleting it multiple times along with the dataset to start fresh. Also it used to have this error when stopping and would stay there(Waiting for pods to be scaled to 0 replica(s), but not sure if I fixed that when messing with network configurations. Not sure if this is a network issue or dataset issue. Still trying to make sure my network configs are perfect as I dont feel solid about them.

On current trueNAS Scale

 

[TYFLOOZY]

Seems to be happening to Jackett as well, I did have jackett active, but then moved it from PVC to Host Path to a dataset I created. Still running into errors.