Error when starting

Support for the freeBSD package, created by dbrooks
Post Reply
technogroup
Newbie
Newbie
Posts: 6
Joined: June 22nd, 2012, 1:29 am

Error when starting

Post by technogroup » June 22nd, 2012, 1:34 am

Starting with a fresh install of NAS4Free.

I installed the package with pkg_add -r sabnzbdplus

I then added sabnzbd_enable="YES" to the rc.conf file

When I go to start SAB I get the following:

nas4free:~# /usr/local/etc/rc.d/sabnzbd start

Fatal error:
Cannot create INI file /usr/local/sabnzbd/sabnzbd.ini
Specify a correct file or delete this file.
Starting sabnzbd.


When I check the directory there is nothing listed.

I am unable to connect to anything at all.

Any ideas?

User avatar
shypike
Administrator
Administrator
Posts: 20998
Joined: January 18th, 2008, 12:49 pm

Re: Error when starting

Post by shypike » June 22nd, 2012, 2:01 am

You will have to ask the one who created the package.
Those are not made by the SABnzbd team.
It looks like some access rights issue.
Shouldn't you be starting with the "sudo" command?

technogroup
Newbie
Newbie
Posts: 6
Joined: June 22nd, 2012, 1:29 am

Re: Error when starting

Post by technogroup » June 22nd, 2012, 8:01 am

I dont think I need to sudo but I will erase the installation, start fresh and try it.

Thanks.

technogroup
Newbie
Newbie
Posts: 6
Joined: June 22nd, 2012, 1:29 am

Re: Error when starting

Post by technogroup » June 22nd, 2012, 3:35 pm

sudo not recognized as a command. I used bash instead and received the same error.

User avatar
shypike
Administrator
Administrator
Posts: 20998
Joined: January 18th, 2008, 12:49 pm

Re: Error when starting

Post by shypike » June 22nd, 2012, 4:44 pm

I'm afraid you have to ask around on the unraid forum.

technogroup
Newbie
Newbie
Posts: 6
Joined: June 22nd, 2012, 1:29 am

Re: Error when starting

Post by technogroup » June 24th, 2012, 11:35 pm

Was able to not get the error by changing some permissions. Now the issue is that there is no ini file for me to change the host from localhost to the IP address of the machine. I try to goto http://ip:8080 and nothing comes up. I have even tried IP:8080/sabnzbd and get the same result.

User avatar
shypike
Administrator
Administrator
Posts: 20998
Joined: January 18th, 2008, 12:49 pm

Re: Error when starting

Post by shypike » June 25th, 2012, 5:22 am

Try to find the startup script.
Then add -s ip:port to the line that starts SABnzbd.py

technogroup
Newbie
Newbie
Posts: 6
Joined: June 22nd, 2012, 1:29 am

Re: Error when starting

Post by technogroup » June 27th, 2012, 8:22 pm

Will do. I have no idea where it is.

dbrooks
Newbie
Newbie
Posts: 19
Joined: June 23rd, 2011, 11:19 pm

Re: Error when starting

Post by dbrooks » June 30th, 2012, 8:24 pm

Note that this package is tested against vanilla FreeBSD releases, and not NAS4Free/FreeNAS, or other appliance-type installations. So, in terms of that, I can't really help much in terms of what's going on. I suspect your issue is likely due to the root file system being mounted read-only in these types of systems which are designed to be appliances with their root partitions on solid state media, and as such, the ini file cannot be properly created. Without knowing more, I can only speculate.

I suggest mounting the root partition read-write (mount -u /, or whatever partition /usr/local happens to be on) and attempting to start SABnzbd+ once again (/usr/local/etc/rc.d/sabndbplus onestart).

technogroup
Newbie
Newbie
Posts: 6
Joined: June 22nd, 2012, 1:29 am

Re: Error when starting

Post by technogroup » June 30th, 2012, 8:33 pm

Wow! It worked. I tried everything and that did the trick. Something so easy was so difficult. I guess I was getting so frustrated and missed thinking of doing that.

dbrooks
Newbie
Newbie
Posts: 19
Joined: June 23rd, 2011, 11:19 pm

Re: Error when starting

Post by dbrooks » June 30th, 2012, 8:37 pm

technogroup wrote:Wow! It worked. I tried everything and that did the trick. Something so easy was so difficult. I guess I was getting so frustrated and missed thinking of doing that.
Note that if the read-write issue was causing your problem, you may be best advised to symlink /usr/local/sabnzbd (or even /usr/local, provided you copy everything else in there over, too) to a directory on your writable disks and re-mount your root partition as read-only to preserve integrity of the system. Those systems are designed to have a read-only root partition.

In any case, cheers.

Post Reply