Amahi Forums

Ok guys,

Everything works pretty much out of the box guys. But there are some configuration steps that need to be done.

You might have some issues with it not unraring. The reason for this is unrar is not installed by default you will need to install unrar for it to work properly.

Anther issues is user's permissions. Since sabnzbd runs as apache you will need to edit the sabnzbd to run as a differnt user that has access to shared dir.

The config file is in. /etc/init.d/sabnzbd
vi sabnzbd.confg
edit the line here:
Replace apache in YOUR_USER_NAME by your user name.

By doing this is will give the correct permissions levels for the sabnzbd to access your folder shares.
You also need to set sabnzbd with 0777 permissions in the folders tab of sabnzbd

If I missed anything please post here I will try to help out as best I can or you can catch me in the IRC chat.

I installed this application from the dashboard setup. It seemed to install fine and I am able to start tthe application. But it don't seem to work. So I searched this forum and I tried to implement the sabnzbd.conf recommended. But I can't find the file in /etc/init.d.
Maybe the application has not been installed properly or missing some other components it depends on. I checked the Service configuration and it shows sabnzbd is installed and enabeled but it says also "This service is dead".

Is there a way to fix this?

Thanks for the work around. The problem I ran into is the following.

After changing the username, when trying to restart sabnzbd i get the following error: I refuse to fork without a log directory!

If I change the username back to apache, error goes away and everything plays nice. Any ideas on how to fix? Thanks!

search for the log directory (it's probably the httpd.log files it's complaining about) in the config file.
if you find it you can do 2 things:
1 - create a directory with the proper permissions and use that as the logging directory
2 - change the permissions of the default directory

of course #1 is more elegant, and actually the way it should be set up
perhaps this is something for the API documentation?

This means your user does not have the correct permissions to write to the log dir. What i did is change the user to root and you dont have to worry about permissions. Im trying to find out where the log dir is.