Finally upgraded to 11, destroyed SabNZB

[diskdiddler]

"Sep 11 15:30:40 freenas uwsgi: [plugins.utils:88] Couldn't retrieve http://192.168.0.9/plugins/sabnzbd/9/_s/status: timed out"

Full of that in the log file.

Jail is started, plugin won't start.
I thought it was due to an update so I clicked the button to "upgrade" or "update" or whatever it is in the plugins [installed] menu, nope - still won't start.

Can reboot jail but can't flick the switch over to a started jail.
:/


Not great, I had that pretty well setup, any ideas? or just re-install it again (sigh)

 

[dlavigne]

Did the IP address of the jail/plugin change? Anything else in /var/log/messages when you try to start the plugin?

 

[diskdiddler]

For the jail or the system itself?


root@sabnzbd_1:/var/log # ls -l mess*.*
-rw-r--r-- 1 root wheel 873 Jan 1 2017 messages.0.bz2
-rw-r--r-- 1 root wheel 983 Jan 1 2016 messages.1.bz2
-rw-r--r-- 1 root wheel 304 Jan 1 2015 messages.2.bz2


I'm a bit confused, should I even bother poking inside those files?

 

[diskdiddler]

Ok so the server itself however, does have an up to date /var/log/ folder - and there's a file dated yesterday, it turned over at 200k unfortunately around midnight.
I'm unsure how to view the data for today.


I do have the console enabled at the bottom of my WebUI and in that the only thing I see is :

Code:

Sep 12 10:42:14 freenas uwsgi: [freeadmin.navtree:562] Couldn't retrieve http://192.168.0.9/plugins/sabnzbd/9/_s/treemenu: timed out
Sep 12 10:42:20 freenas uwsgi: [plugins.utils:88] Couldn't retrieve http://192.168.0.9/plugins/sabnzbd/9/_s/status: timed out
Sep 12 10:50:14 freenas uwsgi: [plugins.utils:88] Couldn't retrieve http://192.168.0.9/plugins/sabnzbd/9/_s/status: timed out

I also get "some error occurred" in the top banner (which disappears), when I attempt to start the plugin.

Sorry to be dumb, do you know how I pull a more comprehensive report for you?

 

[diskdiddler]

(I'd forward a port on my router for 22 / 23 to the jail IP so you could SSH in but I just tried, it looks to me like remoting in via a terminal session doesn't even work internally - is this just a smart security feature? you can only shell into the jails from the FreeNAS UI itself?)

 

[dlavigne]

You have to setup SSH access: http://doc.freenas.org/11/jails.html#accessing-a-jail-using-ssh.

You can view older files using bzcat, such as bzcat /var/log/messages.0.bz2.

 

[diskdiddler]

You have to setup SSH access: http://doc.freenas.org/11/jails.html#accessing-a-jail-using-ssh.

You can view older files using bzcat, such as bzcat /var/log/messages.0.bz2.

I followed that to the letter, confirmed the service is running and putty still can't connect, - what could I be doing wrong?

 

[dlavigne]

Anything in the FreeNAS /var/log/auth.log when you try to connect?

 

[diskdiddler]

Hey guys,
Apologies.

No point trying to telnet / ssh into a jail, with or without the SSH service enabled, if it won't even respond to a ping.
Plot thickens.

Code:

root@sabnzbd_1:/ # ifconfig													 
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384			   
		options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>				   
		inet6 ::1 prefixlen 128												 
		inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1							 
		inet 127.0.0.1 netmask 0xff000000									   
		nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>							   
epair4b: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500	 
		options=8<VLAN_MTU>													 
		ether 02:95:c5:00:11:0b												 
		nd6 options=9<PERFORMNUD,IFDISABLED>									
		media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)					 
		status: active														 
root@sabnzbd_1:/ #															 
							   

 

[dlavigne]

Also hard to SSH without an IP address....