Page 1 of 1
Can't use custom location of par2cmdline on a seedbox
Posted: January 7th, 2019, 3:31 pm
by vdown
I have Sabnzbd installed on a Seedbox with no root access,
I've installed the latest version of par2cmdline to ~/bin but Sabnzbd insists on using the version in /usr/bin/. Is there an easy solution to this, I can't see anywhere in settings for a custom path and I have ensured that the ~/bin folder is first in $PATH
Thanks.
Re: Can't use custom location of par2cmdline on a seedbox
Posted: January 7th, 2019, 4:18 pm
by safihre
It should look for "par2" in the path. Are you sure Sab is started with a path in which that's available?
And does the Sab user have permissions to access and execute it?
Re: Can't use custom location of par2cmdline on a seedbox
Posted: January 7th, 2019, 4:31 pm
by sander
vdown wrote: ↑January 7th, 2019, 3:31 pm
I have ensured that the ~/bin folder is first in $PATH
What is the output of:
and
and how do you start sabnzbd?
Re: Can't use custom location of par2cmdline on a seedbox
Posted: January 7th, 2019, 4:44 pm
by vdown
They both point to the latest version in my home folder.
Startup parameters (however it's inside a docker i think)
/usr/bin/sabnzbdplus --pidfile /home/*****/******/.sabnzbd/.sabnzbd.pid -d
Having said all that, I assume it's the docker. I'll check with my seedbox provider. I'll post back if I get it fixed.
Re: Can't use custom location of par2cmdline on a seedbox
Posted: January 8th, 2019, 4:45 am
by vdown
It was the docker image, I got the provider to update par2cmdline it and all is working fine now.
Thanks for the responses and pointing me in the right direction.
Re: Can't use custom location of par2cmdline on a seedbox
Posted: January 8th, 2019, 5:58 am
by sander
So a seedbox provider that uses docker? Nice. Can you tell which seedbox provider that is? Here, or via PM?
Re: Can't use custom location of par2cmdline on a seedbox
Posted: January 8th, 2019, 6:06 am
by vdown
It’s bytesized. I could be wrong about Docker, it’s more of an assumption on my part.