Pugins won't start: Bad Gateway

[Child]

Hi there,

I got an issue with the plugin on my freenas machine. Plex isrunning smoothly but sickbeard and sabnzb+ plugins won't start. Log looks like this:

Nov 18 20:38:07 ChildVault manage.py: [freeadmin.navtree:526] Couldn't retrieve http://192.168.0.50/plugins/sickbeard/2/_s/treemenu: HTTP Error 502: Bad Gateway
Nov 18 20:38:07 ChildVault manage.py: [freeadmin.navtree:526] Couldn't retrieve http://192.168.0.50/plugins/htpc-manager/4/_s/treemenu: HTTP Error 502: Bad Gateway
Nov 18 20:38:11 ChildVault rtsold[1668]: <rtsock_input_ifannounce> interface epair0a removed
Nov 18 20:38:11 ChildVault kernel: epair0a: link state changed to DOWN
Nov 18 20:38:11 ChildVault kernel: epair0b: link state changed to DOWN
Nov 18 20:38:14 ChildVault kernel: ifa_del_loopback_route: deletion failed
Nov 18 20:38:14 ChildVault kernel: Freed UMA keg (udp_inpcb) was not empty (20 items). Lost 2 pages of memory.
Nov 18 20:38:14 ChildVault kernel: Freed UMA keg (udpcb) was not empty (336 items). Lost 2 pages of memory.
Nov 18 20:38:14 ChildVault kernel: hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
Nov 18 20:38:14 ChildVault kernel: hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
Nov 18 20:38:16 ChildVault manage.py: [freeadmin.navtree:526] Couldn't retrieve http://192.168.0.50/plugins/sickbeard/2/_s/treemenu: HTTP Error 502: Bad Gateway
Nov 18 20:38:36 ChildVault manage.py: [plugins.utils:92] Couldn't retrieve http://192.168.0.50/plugins/sickbeard/2/_s/status: HTTP Error 502: Bad Gateway
Nov 18 20:38:44 ChildVault manage.py: [plugins.utils:92] Couldn't retrieve http://192.168.0.50/plugins/sickbeard/2/_s/status: HTTP Error 502: Bad Gateway
Nov 18 20:39:05 ChildVault notifier: Performing sanity check on nginx configuration:
Nov 18 20:39:05 ChildVault notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
Nov 18 20:39:05 ChildVault notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful
Nov 18 20:39:06 ChildVault manage.py: [plugins.utils:92] Couldn't retrieve http://192.168.0.50/plugins/sickbeard/2/_s/status: HTTP Error 502: Bad Gateway
Nov 18 20:39:06 ChildVault manage.py: [freeadmin.navtree:526] Couldn't retrieve http://192.168.0.50/plugins/sickbeard/2/_s/treemenu: HTTP Error 502: Bad Gateway
Nov 18 20:39:18 ChildVault notifier: Performing sanity check on nginx configuration:
Nov 18 20:39:18 ChildVault notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
Nov 18 20:39:18 ChildVault notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful
Nov 18 20:39:19 ChildVault manage.py: [plugins.utils:92] Couldn't retrieve http://192.168.0.50/plugins/sickbeard/2/_s/status: HTTP Error 502: Bad Gateway
Nov 18 20:39:19 ChildVault manage.py: [freeadmin.navtree:526] Couldn't retrieve http://192.168.0.50/plugins/sickbeard/2/_s/treemenu: HTTP Error 502: Bad Gateway
Nov 18 20:39:40 ChildVault manage.py: [freeadmin.navtree:526] Couldn't retrieve http://192.168.0.50/plugins/sickbeard/2/_s/treemenu: HTTP Error 502: Bad Gateway
Nov 18 20:39:51 ChildVault manage.py: [plugins.utils:92] Couldn't retrieve http://192.168.0.50/plugins/sickbeard/2/_s/status: HTTP Error 502: Bad Gateway
Nov 18 20:41:06 ChildVault manage.py: [freeadmin.navtree:526] Couldn't retrieve http://192.168.0.50/plugins/sickbeard/2/_s/treemenu: HTTP Error 502: Bad Gateway
Nov 18 20:41:29 ChildVault manage.py: [plugins.utils:92] Couldn't retrieve http://192.168.0.50/plugins/sickbeard/2/_s/status: HTTP Error 502: Bad Gateway
Nov 18 20:41:45 ChildVault manage.py: [plugins.utils:92] Couldn't retrieve http://192.168.0.50/plugins/sickbeard/2/_s/status: HTTP Error 502: Bad Gateway
Nov 18 20:42:48 ChildVault manage.py: [plugins.utils:92] Couldn't retrieve http://192.168.0.50/plugins/sickbeard/2/_s/status: HTTP Error 502: Bad Gateway

Anyone any suggestions?
It worked fine until I rebooted the system ...

 

[psyon001]

I'm also having an issue when trying to load up sickbeard and sabnzb. The plugins show active and I didn't have any issues earlier today. OP how did you pull those logs? I can check mine to see if I'm getting a similar error.

*FYI - I've disabled/enabled the plugins and rebooted the system.

 

[psyon001]

Resolved my issue. Not sure exactly what fixed my problem but one of the following seemed to kickstart it again:
* Rebooted FreeNAS
* Rebooted Router (fixed sabnzb)
* Disabled Plugin & Stopped Service
* Restarted Service and Enabled Plugin

I also played around with my IP settings but that did nothing so I set them back to original config. The only reason I checked this was because sickbeard was actually running still. I got my prowl notification of a new download and once sabnzb was working I could see the download as well but the sickbeard web gui wouldn't load. After Stopping/Starting Service and Disabling/Enabling Plugin both seem to be working fine.

Not sure if this helps your issue because I searched forever to find logs with similar messaging but nothing came up so we may have separate issues but good luck anyway.

 

[Child]

I've got the described issue with all plugins except for plexserver ... nothing of the suggested solutions I found seem to work for me.

 

[Joshua Parker Ruehlig]

I've got the described issue with all plugins except for plexserver ... nothing of the suggested solutions I found seem to work for me.

so no plugins work for you except plex?

 

[Child]

Things went like this: I've plex installed for some time runnning without any problems. Then I decided to incorporate sickbeard & sabnzb - which worked fine after install.
I didn't do any reboots at this point though.

Next thing I tried a couple of days later: HTPC-Manger and Media-Browser.
Just for a sneak peek so to speak ... those plugins started with the described error right away. In an attempt to fix this,
I rebooted the system for the first time since install of sickb. & sabnzb.

Result: Only plex is working as intended.
In the meantime I removed HTPC-Manager and Media-Browser.
Still - only plex.

 

[Joshua Parker Ruehlig]

can you try running 'service sabnzbd onestart' in your sabnzbd jail. im curious if I can solve this issue and make sure future plugin releases don't have it

 

[Child]

root@sabnzbd_1:/ # service sabnzbd onestart
Starting sabnzbd.
su: pam_start: system error
/usr/local/etc/rc.d/sabnzbd: WARNING: failed to start sabnzbd
root@sabnzbd_1:/ #

:( I'm lost with this ... mostly cause it just came out of nowhere ...

 

[Joshua Parker Ruehlig]

what happens when you run 'su media' in that same jail?

what version of freenas do you have installed?

 

[Child]

root@sabnzbd_1:/ # su media
su: pam_start: system error
root@sabnzbd_1:/ #

I've 9.2.1.7 installed.

 

[Joshua Parker Ruehlig]

so it seems like something on the jail OS level that broke pam. im not sure what the solution is, maybe your jail template has an issue somehow?

does installing a second instance of plex work?

 

[caiazpa]

I am having the identical issue. My system was working fine for quite some time. I went on vacation for a week, came back to find that Plex is the only plugin that is working. SAB, CP and SB are not working. Plugins will not start, the logs indicate a 502 Bad Gateway, and when i try to start a plugin, i get a brief flash "Some error occurred".

Any ideas?

 

[Joshua Parker Ruehlig]

I am having the identical issue. My system was working fine for quite some time. I went on vacation for a week, came back to find that Plex is the only plugin that is working. SAB, CP and SB are not working. Plugins will not start, the logs indicate a 502 Bad Gateway, and when i try to start a plugin, i get a brief flash "Some error occurred".

Any ideas?

mind installing another instance of sabnzbd and post if it's working or not. I recently copied over some code related to ipv6 and dns stuff that may have fixed this.

 

[caiazpa]

mind installing another instance of sabnzbd and post if it's working or not. I recently copied over some code related to ipv6 and dns stuff that may have fixed this.

Hi -
Yes, I just installed a second instance, and that one does start, and seems to work. Is there any way I can import settings from the old on to the new one? Thanks so much for your help.

While I don't relish re-installing and reconfiguring all of these plugins, it is sure better than nothing.

 

[Joshua Parker Ruehlig]

Hi -
Yes, I just installed a second instance, and that one does start, and seems to work. Is there any way I can import settings from the old on to the new one? Thanks so much for your help.

While I don't relish re-installing and reconfiguring all of these plugins, it is sure better than nothing.

EDIT
you should have an update button next to your broken sabnzbd install. that may be your simplest fix.
####

if you copy over the datadirectories and set the correct ownership 'media' (UID=816) everything should be as it was. for sabnzbd it's /var/db/sabnzbd.

I haven't released updates to the other plugins with the mentioned fixes.

 

[Joshua Parker Ruehlig]

mind helping me debug a little. on your broken sabnzbd install can you run 'service sabnzbd onestart' and tell me if it starts?

 

[caiazpa]

EDIT
you should have an update button next to your broken sabnzbd install. that may be your simplest fix.
####

if you copy over the datadirectories and set the correct ownership 'media' (UID=816) everything should be as it was. for sabnzbd it's /var/db/sabnzbd.

I haven't released updates to the other plugins with the mentioned fixes.

I actually tried the update first, before I posted my issue. That did not solve the problem. I will try as you mentioned, copying over data dirs and setting ownership to media. I will report back.

 

[caiazpa]

mind helping me debug a little. on your broken sabnzbd install can you run 'service sabnzbd onestart' and tell me if it starts?

Sure - It did not start. Here is the output:

root@sabnzbd_1:/ # service sabnzbd onestart
Starting sabnzbd.
su: pam_start: system error
/usr/local/etc/rc.d/sabnzbd: WARNING: failed to start sabnzbd
root@sabnzbd_1:/ #

 

[Joshua Parker Ruehlig]

Sure - It did not start. Here is the output:

root@sabnzbd_1:/ # service sabnzbd onestart
Starting sabnzbd.
su: pam_start: system error
/usr/local/etc/rc.d/sabnzbd: WARNING: failed to start sabnzbd
root@sabnzbd_1:/ #

OK same issue the other guy got, thanks.

I don't think the updates I added made a difference, I believe the issue is somewhere at the jail level. not sure of a guaranteed fix

 

[caiazpa]

OK same issue the other guy got, thanks.

I don't think the updates I added made a difference, I believe the issue is somewhere at the jail level. not sure of a guaranteed fix

Hey, while I have your attention, I don't seem to have a /var/db/sabnzbd. Nothing in that dir corresponding to sab. Other ideas? Thanks so much for your time.