Sabnzbd 1.0 webgui refusing connection

Status
Not open for further replies.

diskdiddler

Wizard
Joined
Jul 9, 2014
Messages
2,377
Actually the problem was I had the jail in a stopped state (I'd forgotten which state was best for the upgrade)
I ran it again, it took AGES but did infact work.

My box will probably not live out the week mind you but that's another issue, thanks regardless Josh.
 

muaysub

Cadet
Joined
Nov 9, 2015
Messages
6
I´m having the same problem again after updating to 1.0.1
Code:
root@sabnzbd_1:/ # sockstat                                                    
USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS      
root     python2.7  50572 3  tcp4   192.168.1.201:12352   *:*                  
root     cron       50332 4  dgram  -> /var/run/logpriv                        
root     syslogd    50273 4  dgram  /var/run/log                               
root     syslogd    50273 5  dgram  /var/run/logpriv                           
root     syslogd    50273 6  udp4   192.168.1.201:514     *:*                  
root@sabnzbd_1:/ # service sabnzbd start                                       
Starting sabnzbd.                                                              
                                                                               
Fatal error:                                                                   
  "/var/db/sabnzbd/sabnzbd.ini" is not a valid configuration file<br>Error messa
ge: [Errno 13] Permission denied: '/var/db/sabnzbd/sabnzbd.ini'                
Specify a correct file or delete this file.                                    
/usr/local/etc/rc.d/sabnzbd: WARNING: failed to start sabnzbd                  
root@sabnzbd_1:/ #     
 

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
I´m having the same problem again after updating to 1.0.1
Code:
root@sabnzbd_1:/ # sockstat                                                   
USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS     
root     python2.7  50572 3  tcp4   192.168.1.201:12352   *:*                 
root     cron       50332 4  dgram  -> /var/run/logpriv                       
root     syslogd    50273 4  dgram  /var/run/log                              
root     syslogd    50273 5  dgram  /var/run/logpriv                          
root     syslogd    50273 6  udp4   192.168.1.201:514     *:*                 
root@sabnzbd_1:/ # service sabnzbd start                                      
Starting sabnzbd.                                                             
                                                                              
Fatal error:                                                                  
  "/var/db/sabnzbd/sabnzbd.ini" is not a valid configuration file<br>Error messa
ge: [Errno 13] Permission denied: '/var/db/sabnzbd/sabnzbd.ini'               
Specify a correct file or delete this file.                                   
/usr/local/etc/rc.d/sabnzbd: WARNING: failed to start sabnzbd                 
root@sabnzbd_1:/ #     
How is this the same? Your error is completely different, regardless if the symptom of sabnzbd not starting is the same.
Looks like the ownershup of your data-directory changed. sabnzbd user (default "media") should own /var/db/sabnzbd
 

muaysub

Cadet
Joined
Nov 9, 2015
Messages
6
How is this the same? Your error is completely different, regardless if the symptom of sabnzbd not starting is the same.
Looks like the ownershup of your data-directory changed. sabnzbd user (default "media") should own /var/db/sabnzbd
Ok, I´m not using the default user, I´ve changed the user with the help of your tutorial (Solution 2) or do i have to change the user again after the update?
 

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
Ok, I´m not using the default user, I´ve changed the user with the help of your tutorial (Solution 2) or do i have to change the user again after the update?
you shouldn't have to, but I'd just chown that folder to the correct user again.

##EDIT##
Actually I know why this isn't working. I rebased this plugin on the official freebsd port, so I had to workaround the default user by overwriting it.
Anytime you update sabnzbd (until FreeNAS10), you'll need to set your user again with 'sysrc sabnzbd_user="USER"'
sorry about the issue
 

muaysub

Cadet
Joined
Nov 9, 2015
Messages
6
you shouldn't have to, but I'd just chown that folder to the correct user again.

##EDIT##
Actually I know why this isn't working. I rebased this plugin on the official freebsd port, so I had to workaround the default user by overwriting it.
Anytime you update sabnzbd (until FreeNAS10), you'll need to set your user again with 'sysrc sabnzbd_user="USER"'
sorry about the issue
No problems, it works now! Thank you :) I will just have to remember to set my user after updating :)
 

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
No problems, it works now! Thank you :) I will just have to remember to set my user after updating :)
sweet, didn't think about this issue when I made the change
 

mchias

Dabbler
Joined
May 3, 2015
Messages
12
I am not sure how my error fits into this, but I have been running the 0.7.20 version up until today when I decided to update to 1.0.1 via the FreeNAS GUI. Now SABnzbd won't start. If you click on the button in the GUI, it looks like it wants to start but stays "OFF".

When I attempt via the command line, I get the following error.

Code:
root@customplugin_1:/ # service sabnzbd start
Starting sabnzbd.
Traceback (most recent call last):
  File "/usr/pbi/sabnzbd-amd64/bin/SABnzbd.py", line 88, in <module>
    import sabnzbd
  File "/usr/pbi/sabnzbd-amd64/bin/sabnzbd.py", line 89, in <module>
    import sabnzbd.lang
ImportError: No module named lang
/usr/local/etc/rc.d/sabnzbd: WARNING: failed to start sabnzbd


Again, I was running the prior version until a few hours ago when I opted to update the plugin via the GUI. Any ideas?
 

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
I am not sure how my error fits into this, but I have been running the 0.7.20 version up until today when I decided to update to 1.0.1 via the FreeNAS GUI. Now SABnzbd won't start. If you click on the button in the GUI, it looks like it wants to start but stays "OFF".

When I attempt via the command line, I get the following error.

Code:
root@customplugin_1:/ # service sabnzbd start
Starting sabnzbd.
Traceback (most recent call last):
  File "/usr/pbi/sabnzbd-amd64/bin/SABnzbd.py", line 88, in <module>
    import sabnzbd
  File "/usr/pbi/sabnzbd-amd64/bin/sabnzbd.py", line 89, in <module>
    import sabnzbd.lang
ImportError: No module named lang
/usr/local/etc/rc.d/sabnzbd: WARNING: failed to start sabnzbd


Again, I was running the prior version until a few hours ago when I opted to update the plugin via the GUI. Any ideas?
I'd follow the steps I outlined here
https://forums.freenas.org/index.php?threads/couch-potato-wont-start-no-mo.43148/#post-283056
 

mchias

Dabbler
Joined
May 3, 2015
Messages
12

I followed the steps you outlined, but I still get the same error message when I attempt to start the plugin. The btsync plugin has no problem starting. None of my other plugins(CouchPotato, Plex, Crashplan, Headphones, & Transmission) have any issues, granted they are in different jails.

I am going to revert back to 0.7.20 unless you can think of something else.
 

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
I followed the steps you outlined, but I still get the same error message when I attempt to start the plugin. The btsync plugin has no problem starting. None of my other plugins(CouchPotato, Plex, Crashplan, Headphones, & Transmission) have any issues, granted they are in different jails.

I am going to revert back to 0.7.20 unless you can think of something else.
I think someone else mentioned a similar issue recently. And a possibly solution was setting the plugin to use UTF8, but I don't know know exactly.
goodluck
 
Status
Not open for further replies.
Top