Error when trying to run nzbhydra in jail

Status
Not open for further replies.

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
nice, I'll take a look. supporting these Python programs pulled from github aren't too bad if they have autopgrade built in.
 

Rudi Pittman

Contributor
Joined
Dec 22, 2015
Messages
161
It does auto upgrade. Let me know if there's any info I can provide should you want it and again thanks for all the help.
 

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
I might have time this weekend for a plugin hopefully
 

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
I just finished building this plugin. It should be available in the FreeNAS repository tomorrow.
 

Rudi Pittman

Contributor
Joined
Dec 22, 2015
Messages
161
I just finished building this plugin. It should be available in the FreeNAS repository tomorrow.


Thanks so much!

For those already running nzbhydra all you need to do is make a backup inside nzbhydra then restore the settings.cfg and nzbhydra.db to the new plugin version (probably to /var/db if I remember right). You will probably also have to ensure new jail/plugin gets same ip address via your router.
 

Rudi Pittman

Contributor
Joined
Dec 22, 2015
Messages
161
Tried the plugin tonight...would not let me enable it...saw this in the messages:

Nov 4 01:32:06 freenas manage.py: [plugins.utils:91] Couldn't retrieve http://192.168.3.116/plugins/nzbhydra/15/_s/status: No JSON object could be decoded
Nov 4 01:32:07 freenas manage.py: [freeadmin.navtree:631] An error occurred while unserializing from http://192.168.3.116/plugins/nzbhydra/15/_s/treemenu: No JSON object could be decoded
Nov 4 01:32:32 freenas manage.py: [plugins.utils:91] Couldn't retrieve http://192.168.3.116/plugins/nzbhydra/15/_s/status: No JSON object could be decoded
 

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
Tried the plugin tonight...would not let me enable it...saw this in the messages:

Nov 4 01:32:06 freenas manage.py: [plugins.utils:91] Couldn't retrieve http://192.168.3.116/plugins/nzbhydra/15/_s/status: No JSON object could be decoded
Nov 4 01:32:07 freenas manage.py: [freeadmin.navtree:631] An error occurred while unserializing from http://192.168.3.116/plugins/nzbhydra/15/_s/treemenu: No JSON object could be decoded
Nov 4 01:32:32 freenas manage.py: [plugins.utils:91] Couldn't retrieve http://192.168.3.116/plugins/nzbhydra/15/_s/status: No JSON object could be decoded
this usually isn't an issue with the plugin but your jail having unreliable networking. can you from the jail ping your computer?
 

Rudi Pittman

Contributor
Joined
Dec 22, 2015
Messages
161
Did you intend for it to be disabled by default? Could be I'm making the wrong assumption....

famewolf@freenas:/var/log % sudo jls
Password:
JID IP Address Hostname Path
1 - aria2_1 /mnt/volume1/jails/aria2_1
2 - couchpotato_1 /mnt/volume1/jails/couchpotato_1
3 - headphones_1 /mnt/volume1/jails/headphones_1
4 - htpc-manager_1 /mnt/volume1/jails/htpc-manager_1
5 - lazylibrarian_1 /mnt/volume1/jails/lazylibrarian_1
7 - sabnzbd_1 /mnt/volume1/jails/sabnzbd_1
8 - sickrage_1 /mnt/volume1/jails/sickrage_1
9 - transmission_1 /mnt/volume1/jails/transmission_1
10 - nextcloud_1 /mnt/volume1/jails/nextcloud_1
11 - nzbhydra_1 /mnt/volume1/jails/nzbhydra_1
famewolf@freenas:/var/log % sudo jexec 11 sh
# ls
.cshrc COPYRIGHT dev libexec proc sbin usr
.plugins bin etc media rescue sys var
.profile boot lib mnt root tmp
# ping 192.168.3.2
PING 192.168.3.2 (192.168.3.2): 56 data bytes
64 bytes from 192.168.3.2: icmp_seq=0 ttl=64 time=0.475 ms
64 bytes from 192.168.3.2: icmp_seq=1 ttl=64 time=0.272 ms
^C
--- 192.168.3.2 ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.272/0.373/0.475/0.102 ms
# /usr/local/etc/rc.d/nzbhydra restart
Cannot 'restart' nzbhydra. Set nzbhydra_enable to YES in /etc/rc.conf or use 'onerestart' instead of 'restart'.
 

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
yes, all plugins are disabled by default. you should be able to enable then from the Plugins > Installed tab. but sometimes that doesn't work because of unreliable jail networking.
 

Rudi Pittman

Contributor
Joined
Dec 22, 2015
Messages
161
yes, all plugins are disabled by default. you should be able to enable then from the Plugins > Installed tab. but sometimes that doesn't work because of unreliable jail networking.


That seems to be the case here..could not do from the gui. It might be a good contender for being enabled by default since all configurations is done via the web gui...typically the user shouldn't even need to ever go to the command line. In any case I'm doing the updates so I can install nano and edit manually. Thanks.
 

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
I m not going to enable any of the Plugins by default, ideally you wouldnt need to use the commandline to start them.

just run 'sysrc nzbhydra_enable=YES'
and 'service nzbhydra start' instead of editing that file.
 

Rudi Pittman

Contributor
Joined
Dec 22, 2015
Messages
161
Used your commands...started it...it shows it daemonizing....still does not show in list of installed plugins and I get connection refused trying to go to the ip assigned to the jail on port 5075. Giving up on this for now. Even more confusing it's showing the same ip address in the jail list for the nextcloud plugin I installed and for nzbhydra. I just created a new freenas boot usb and uploading the old config so everything should be up to date and working fine. I don't think it's something on my end...will look at later.
 
Last edited:

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
like I said earlier, networking is not working properly for your jail. even if the plugin is running you won't be able to connect to it.

try this for the plugin's jail...
disable VIMAGE and assign a network interface
restart the jail

now the icon for the plugin should show properly on the Jails > Installed tab
 

Rudi Pittman

Contributor
Joined
Dec 22, 2015
Messages
161
I recently "upgraded" to the plugin for this from the development version I had installed in a jail. I've noticed at random times the plugin "turns itself off". The jail is still running but the plugin shows itself in an "off" status. Turning it on fixes the problem till the next time. I do not see anything in the syslog nor can I find any entries in the nzbhydra log to indicate why the service is being stopped. It's to the point I'm just about to do a crontab to run a script that checks if nzbhydra is running every 2 minutes and starts it if it is not.
 

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
hmm, when the plugin shows as off, what does this command output
service jackett onestatus

so no relevant logs in /var/db/jackett?
 

Rudi Pittman

Contributor
Joined
Dec 22, 2015
Messages
161
hmm, when the plugin shows as off, what does this command output
service jackett onestatus

so no relevant logs in /var/db/jackett?

Assuming you meant nzbhydra. The only log I see is /var/log/messages and it's pretty short and sweet. You'll see some date gaps depending on when I noticed it was no longer responding to queries. I did some package updates in the hopes it might help but didn't change anything. The nzbhydra log just shows the last query it did. I'm assuming the problem is the nzbhydra app is dying on it's own rather than a plugin issue. I'll have to try the command after I disable the restart script I installed that checks to make sure it's running every 15 seconds and starts it if it's not. I had to do the same thing with polipo caching web proxy as it died at random times as well:

Code:
Apr 25 12:01:31 nzbhydra_1 newsyslog[30882]: logfile first created
Apr 25 12:01:31 nzbhydra_1 syslogd: kernel boot file is /boot/kernel/kernel
Apr 25 12:19:05 nzbhydra_1 syslogd: exiting on signal 15
Apr 25 12:23:19 nzbhydra_1 syslogd: kernel boot file is /boot/kernel/kernel
Apr 30 22:57:52 nzbhydra_1 python2.7: gethostby*.getanswer: asked for "newz69.keagaming.com IN AAAA", got type "A"
Apr 30 22:57:52 nzbhydra_1 python2.7: gethostby*.getanswer: asked for "* IN AAAA", got type "A"
Apr 30 22:57:52 nzbhydra_1 python2.7: gethostby*.getanswer: asked for "* IN AAAA", got type "A"
Apr 30 22:57:52 nzbhydra_1 python2.7: gethostby*.getanswer: asked for "* IN AAAA", got type "A"
Apr 30 22:57:52 nzbhydra_1 python2.7: gethostby*.getanswer: asked for "* IN AAAA", got type "A"
Apr 30 22:57:52 nzbhydra_1 python2.7: gethostby*.getanswer: asked for "* IN AAAA", got type "A"
Apr 30 22:57:52 nzbhydra_1 python2.7: gethostby*.getanswer: asked for "* IN AAAA", got type "A"
Apr 30 22:57:52 nzbhydra_1 python2.7: gethostby*.getanswer: asked for "* IN AAAA", got type "A"
Apr 30 22:58:05 nzbhydra_1 python2.7: gethostby*.getanswer: asked for "* IN AAAA", got type "A"
May  1 04:55:35 nzbhydra_1 syslogd: kernel boot file is /boot/kernel/kernel
May  4 03:31:51 nzbhydra_1 syslogd: kernel boot file is /boot/kernel/kernel
May  6 20:44:41 nzbhydra_1 pkg: pkg upgraded: 1.6.4_1 -> 1.10.1 
May  6 20:53:29 nzbhydra_1 pkg: indexinfo upgraded: 0.2.4 -> 0.2.6 
May  6 20:53:29 nzbhydra_1 pkg: gettext-runtime upgraded: 0.19.7 -> 0.19.8.1_1 
May  6 20:53:29 nzbhydra_1 pkg: gdbm upgraded: 1.11_2 -> 1.12 
May  6 20:53:30 nzbhydra_1 pkg: expat upgraded: 2.1.0_3 -> 2.2.0_1 
May  6 20:53:32 nzbhydra_1 pkg: db5 upgraded: 5.3.28_3 -> 5.3.28_6 
May  6 20:53:33 nzbhydra_1 pkg: apr upgraded: 1.5.2.1.5.4 -> 1.5.2.1.5.4_2 
May  6 20:53:33 nzbhydra_1 pkg: libunistring-0.9.7 installed
May  6 20:53:33 nzbhydra_1 pkg: sqlite3 upgraded: 3.11.1 -> 3.18.0 
May  6 20:53:33 nzbhydra_1 pkg: serf upgraded: 1.3.8_1 -> 1.3.9_1 
May  6 20:53:37 nzbhydra_1 pkg: perl5 upgraded: 5.20.3_8 -> 5.24.1_1 
May  6 20:53:37 nzbhydra_1 pkg: gettext-tools upgraded: 0.19.7 -> 0.19.8.1 
May  6 20:53:37 nzbhydra_1 pkg: libidn2-2.0.2 installed
May  6 20:53:37 nzbhydra_1 pkg: wget upgraded: 1.16.3_1 -> 1.19.1 
May  6 20:53:38 nzbhydra_1 pkg: subversion upgraded: 1.9.3_3 -> 1.9.5 
May  6 20:53:41 nzbhydra_1 pkg: python27 upgraded: 2.7.11_1 -> 2.7.13_3 
May  6 20:53:41 nzbhydra_1 pkg: pkgconf upgraded: 0.9.12_1 -> 1.3.5,1 
May  6 20:53:42 nzbhydra_1 pkg: pcre upgraded: 8.38 -> 8.40 
May  6 20:53:42 nzbhydra_1 pkg: m4 upgraded: 1.4.17_1,1 -> 1.4.18,1 
May  6 20:53:42 nzbhydra_1 pkg: lzo2 upgraded: 2.09 -> 2.10_1 
May  6 20:53:42 nzbhydra_1 pkg: libxml2 upgraded: 2.9.3 -> 2.9.4 
May  6 20:53:42 nzbhydra_1 pkg: libidn upgraded: 1.31 -> 1.33_1 
May  6 20:53:43 nzbhydra_1 pkg: libiconv upgraded: 1.14_9 -> 1.14_10 
May  6 20:53:43 nzbhydra_1 pkg: iconv reinstalled: 2.0_4 -> 2.0_4 
May  6 20:53:43 nzbhydra_1 pkg: gettext upgraded: 0.19.7 -> 0.19.8.1 
May  6 20:53:44 nzbhydra_1 pkg: compat9x-amd64 upgraded: 9.3.903000.20160128 -> 9.3.903000.20161027 
May  6 20:53:45 nzbhydra_1 pkg: ca_root_nss upgraded: 3.22.2 -> 3.30.2 
May 11 13:10:45 nzbhydra_1 pkg: nano-2.8.2 installed
 

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
hmm, was nzbhydra crashing before you switched to the plugin? And were they both using the same version of nzbhydra?
 

Rudi Pittman

Contributor
Joined
Dec 22, 2015
Messages
161
hmm, was nzbhydra crashing before you switched to the plugin? And were they both using the same version of nzbhydra?

Since I was running the "development" version they wouldn't match up to the stable (and yes the dev branch was running just fine). Ironically I did this to have a more stable setup but in fact it's been more of an issue that the development branch.
 

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
Since I was running the "development" version they wouldn't match up to the stable (and yes the dev branch was running just fine). Ironically I did this to have a more stable setup but in fact it's been more of an issue that the development branch.
I thought I read that from your previous comments. yeah, sometimes these not highly used/developed programs are actually more stable on develop branch since that's what the developer likely uses. =/
 

xvzacrw

Dabbler
Joined
Jan 3, 2018
Messages
11
I'm assuming you need to install py27-sqlite3

Please help! I've got py27-sqlite3 and still getting those messages. What else could it be?

Code:
root@nzbhydra:/usr/local/share/nzbhydra # pkg install py27-sqlite3
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The most recent version of packages are already installed
root@nzbhydra:/usr/local/share/nzbhydra # python nzbhydra.py --nobrowser
Traceback (most recent call last):
  File "nzbhydra.py", line 24, in <module>
	from nzbhydra import indexers
  File "/usr/local/share/nzbhydra/nzbhydra/indexers.py", line 11, in <module>
	from nzbhydra import config, database
  File "/usr/local/share/nzbhydra/nzbhydra/database.py", line 16, in <module>
	from playhouse.sqliteq import SqliteQueueDatabase
  File "/usr/local/share/nzbhydra/libs/playhouse/sqliteq.py", line 18, in <module>
	from playhouse.sqlite_ext import SqliteExtDatabase
  File "/usr/local/share/nzbhydra/libs/playhouse/sqlite_ext.py", line 75, in <module>
	FTS_VER = sqlite3.sqlite_version_info[:3] >= (3, 7, 4) and 'FTS4' or 'FTS3'
AttributeError: 'NoneType' object has no attribute 'sqlite_version_info'


Thanks!
 
Status
Not open for further replies.
Top