General NAS-Central Forums

Welcome to the NAS community
It is currently Mon May 29, 2017 5:56 am

All times are UTC




Post new topic Reply to topic  [ 119 posts ]  Go to page Previous  1, 2, 3, 4, 5, 6, 7, 8  Next
Author Message
PostPosted: Sun Oct 09, 2016 1:01 am 
Offline

Joined: Tue Oct 08, 2013 12:51 am
Posts: 94
Well, this just gets stranger and stranger...
I had a little time on my hands today so I did a little experimenting.
I set the script to a-x and re-booted.
The NAS booted normally in a very short time with no unusual flashing of the system LED.
I set it back to a+x but set the config to all "0", thereby running the script but starting no programs.
Again, the NAS booted normally and quickly.
I then started modifying the config to only install/start only one program at a time.
Here's what I found:

Boot #1
Start SAB only.
20 minutes flashing

~ # pgrep -f sab
4214
~ # netstat -tulpn | grep 4214
tcp 0 0 127.0.0.1:8080 0.0.0.0:* LISTEN 4214/python2

Refused to connect on 8080.

Boot #2
Start NZBget only
8 Minutes flashing
NZBGet log shows startup near end of that 8 minute period
Running OK

Boot #3
Start CouchPotato only
34 minutes flashing
Running OK

Boot #4
Start SickRage only
43 minutes flashing
Running OK

I looked at the SickRage log and found something that looks a little out of the ordinary. SickRage seems to be starting and stopping continuously. Here's two iterations:

2016-10-08 00:30:47 INFO MAIN :: 74691: Unable to find IMDb show info in the database
2016-10-08 00:30:47 INFO MAIN :: 259631: Unable to find IMDb show info in the database
2016-10-08 00:30:47 INFO MAIN :: 156641: Unable to find IMDb show info in the database
2016-10-08 00:30:47 INFO MAIN :: 257256: Unable to find IMDb show info in the database
2016-10-08 00:30:47 INFO MAIN :: 284893: Unable to find IMDb show info in the database
2016-10-08 00:30:46 INFO MAIN :: Writing PID: 21809 to /opt/usr/etc/config/sickbeard/SickRage.pid
2016-10-08 00:29:44 INFO EVENT-QUEUE :: Shutting down Tornado
2016-10-08 00:29:41 INFO EVENT-QUEUE :: Saving config file to disk
2016-10-08 00:29:41 INFO EVENT-QUEUE :: Saving all shows to the database
2016-10-08 00:29:41 INFO EVENT-QUEUE :: Waiting for the EVENT-QUEUE thread to exit
2016-10-08 00:29:41 INFO EVENT-QUEUE :: Waiting for the FINDSUBTITLES thread to exit
2016-10-08 00:29:41 INFO EVENT-QUEUE :: Waiting for the FINDPROPERS thread to exit
2016-10-08 00:29:41 INFO EVENT-QUEUE :: Waiting for the TRAKTCHECKER thread to exit
2016-10-08 00:29:41 INFO EVENT-QUEUE :: Waiting for the POSTPROCESSER thread to exit
2016-10-08 00:29:41 INFO EVENT-QUEUE :: Waiting for the SEARCHQUEUE thread to exit
2016-10-08 00:29:41 INFO EVENT-QUEUE :: Waiting for the SHOWQUEUE thread to exit
2016-10-08 00:29:41 INFO EVENT-QUEUE :: Waiting for the CHECKVERSION thread to exit
2016-10-08 00:29:41 INFO EVENT-QUEUE :: Waiting for the SHOWUPDATER thread to exit
2016-10-08 00:29:41 INFO EVENT-QUEUE :: Waiting for the BACKLOG thread to exit
2016-10-08 00:29:40 INFO EVENT-QUEUE :: Waiting for the DAILYSEARCHER thread to exit
2016-10-08 00:29:40 INFO EVENT-QUEUE :: Aborting all threads
2016-10-08 00:29:40 INFO MAIN :: Signal 15 caught, saving and exiting...
2016-10-08 00:28:45 INFO TORNADO :: Starting SickRage on http://0.0.0.0:8081/
2016-10-08 00:28:45 INFO CHECKVERSION :: Checking for updates using GIT
2016-10-08 00:28:45 INFO MAIN :: Starting SickRage [master] using '/opt/usr/etc/config/sickbeard/config.ini'
2016-10-08 00:28:45 INFO MAIN :: 74691: Unable to find IMDb show info in the database
2016-10-08 00:28:45 INFO MAIN :: 259631: Unable to find IMDb show info in the database
2016-10-08 00:28:45 INFO MAIN :: 156641: Unable to find IMDb show info in the database
2016-10-08 00:28:45 INFO MAIN :: 257256: Unable to find IMDb show info in the database
2016-10-08 00:28:45 INFO MAIN :: 284893: Unable to find IMDb show info in the database
2016-10-08 00:28:44 INFO MAIN :: Writing PID: 21270 to /opt/usr/etc/config/sickbeard/SickRage.pid
2016-10-08 00:27:44 INFO EVENT-QUEUE :: Shutting down Tornado
2016-10-08 00:27:42 INFO EVENT-QUEUE :: Saving config file to disk
2016-10-08 00:27:41 INFO EVENT-QUEUE :: Saving all shows to the database
2016-10-08 00:27:41 INFO EVENT-QUEUE :: Waiting for the EVENT-QUEUE thread to exit
2016-10-08 00:27:41 INFO EVENT-QUEUE :: Waiting for the FINDSUBTITLES thread to exit
2016-10-08 00:27:41 INFO EVENT-QUEUE :: Waiting for the FINDPROPERS thread to exit
2016-10-08 00:27:41 INFO EVENT-QUEUE :: Waiting for the TRAKTCHECKER thread to exit
2016-10-08 00:27:41 INFO EVENT-QUEUE :: Waiting for the POSTPROCESSER thread to exit
2016-10-08 00:27:41 INFO EVENT-QUEUE :: Waiting for the SEARCHQUEUE thread to exit
2016-10-08 00:27:41 INFO EVENT-QUEUE :: Waiting for the SHOWQUEUE thread to exit
2016-10-08 00:27:41 INFO EVENT-QUEUE :: Waiting for the CHECKVERSION thread to exit
2016-10-08 00:27:41 INFO EVENT-QUEUE :: Waiting for the SHOWUPDATER thread to exit
2016-10-08 00:27:41 INFO EVENT-QUEUE :: Waiting for the BACKLOG thread to exit
2016-10-08 00:27:40 INFO EVENT-QUEUE :: Waiting for the DAILYSEARCHER thread to exit
2016-10-08 00:27:40 INFO EVENT-QUEUE :: Aborting all threads
2016-10-08 00:27:40 INFO MAIN :: Signal 15 caught, saving and exiting...
2016-10-08 00:26:46 INFO TORNADO :: Starting SickRage on http://0.0.0.0:8081/
2016-10-08 00:26:46 INFO CHECKVERSION :: Checking for updates using GIT
2016-10-08 00:26:45 INFO MAIN :: Starting SickRage [master] using '/opt/usr/etc/config/sickbeard/config.ini'

It actually repeated 21 times before stabilizing. The Signal 15 seems to be the problem. I have no idea how to find the source.

This doesn't clear much up for me, I'm afraid.

Do we need to accept that this is the time takes? I'm not sure about that.

What's involved with starting from scratch? Should I start with a factory reset...again?


Top
 Profile  
 
PostPosted: Sun Oct 09, 2016 8:00 am 
Offline

Joined: Sun Feb 17, 2013 10:00 pm
Posts: 301
pitcritter wrote:
Boot #1
Start SAB only.
20 minutes flashing

Refused to connect on 8080.

For this can you go to /opt/usr/etc/config/sabnzbd and edit sabnzbd.ini, search for "port = 8080" and change it to 8085 or 0890 if nzbget is running on 8085. This probably wont speed up the boot time but should allow you to access sabnzbd on the port you altered it to.

Were there any messages in the couchpotato log? I know when either sickrage or couchpotato start up they go straight into a backlog search which takes a lot of processor time, and i noticed you are using an NSA310 which arent the quickest.

Does the Sickrage log repeat those messages over and over or do you get any out of memory messages anywhere? could you pastebin the full log?

I had a quick search for signal 15 lots of people have had this issue with no clear answer to fix it... Can you check the folder permissions for /opt/usr/etc, the config directories for everything is stored in that folder, if you cant write to that directory then that might be causing the delay during boot.

To start from scratch, maybe the easiest is to make sure the ffp package has been disabled, then uninstall the entware-ng package, then reboot, then check if the /usr/local/zy-pkgs/opt folder has been removed, if it is still there it should be safe to remove.
Reboot again, reinstall Entware-ng from the package manager. then follow the instructions in post 2 to install the script again,


Top
 Profile  
 
PostPosted: Sun Oct 09, 2016 8:21 am 
Offline

Joined: Tue Oct 08, 2013 12:51 am
Posts: 94
I'm using a 325, not a 310.

Here's the pastebin :http://pastebin.com/YyncFUaH

I didn't have a good look at the CP log. I can try that tomorrow.

I'll try again with changing the port in SAB, although I had no luck with that previously.

The permissions for /opt/usr/etc/ are drwxr-xr-x
The permissions for everything below that are drwxrwxrwx, except for nzbToMedia which is drwxr-xr-x.
These both look OK to my eye.

Something I haven't tried is running the script without a reboot. Assuming it's just the speed of my NAS, it should take the same time to run either way the way I see it.
That might be an interesting experiment.


Top
 Profile  
 
PostPosted: Sun Oct 09, 2016 8:30 am 
Offline

Joined: Sun Feb 17, 2013 10:00 pm
Posts: 301
that is odd then, i'm using a 325 too and boot takes 5-7 mins max here...

is there anything in the sickrage database or did you start from scratch there too? could you remove the sickrage database from /opt/usr/etc/config/sickbeard/ and restart it. It might just be database corruption, although id expect the log to complain about that.

My /etc folder permissions are:
drwxrwxrwx 3 root root 4096 Feb 24 2016 /opt/usr/etc

then /usr above that is drwxr-xr-x

Dont forget the shut down SAB before changing the port in the .ini file


Top
 Profile  
 
PostPosted: Sun Oct 09, 2016 8:39 am 
Offline

Joined: Tue Oct 08, 2013 12:51 am
Posts: 94
The SickRage database is pretty big. I've been building my collection for a couple of years. I could do as you ask, but that still wouldn't explain the same kind of timeframe on CP. That DB is absolutely empty. I haven't configured CP yet.

It might be a couple of days before I get to play with the system again.

In truth, I only reboot once a week and it's currently running fine.

I just may leave it alone.

It's a little frustrating, but I think I can live with it.

I'm still trying to figure out where my missing PP scripts are that are usually included stock with NZBGet. I've always used email.py, and logger.py for instance, and they're nowhere to be found.

I think I'll just D/L and add them to the nzbToMedia folder.


Top
 Profile  
 
PostPosted: Sun Oct 09, 2016 8:59 am 
Offline

Joined: Sun Feb 17, 2013 10:00 pm
Posts: 301
Ive never used either of those scripts, so didnt notice them disappearing! Its odd that they are still in the scripts folder in the github repo, but nut included in the entware-ng package.

As for reboots i do the same, i set the scheduler to reboot every sunday, to take care of any github updates.

You are right about couchpotato... it would be interesting to see the log.

Once sickrage has started can you see all you show info and can you make changes to the db?


Top
 Profile  
 
PostPosted: Sun Oct 09, 2016 9:25 am 
Offline

Joined: Tue Oct 08, 2013 12:51 am
Posts: 94
SickRage is working fine. It's happily downloading my new episodes. The database looks complete and I have made some changes. I have 2-2TB internal drives in the NAS, set up as JBOD and they're 90+% full.

I'm currently not using CouchPotato since my external 3TB drive died last week with no warning. Of course, it took about 2.5 TB of movies with it. I've got a new one coming. At that point, it's time to start re-building my collection. I will enable CP in the script again, but until my drive arrives, I won't actually set it up.


Top
 Profile  
 
PostPosted: Sun Oct 09, 2016 10:30 am 
Offline

Joined: Sun Feb 17, 2013 10:00 pm
Posts: 301
ok, signal 15 is a kill signal to SR, something is sending the kill command to it. Can you enable debugging in SR settings, general config, advanced settings.

restart SR then post the logs


Top
 Profile  
 
PostPosted: Sun Oct 09, 2016 10:51 pm 
Offline

Joined: Tue Oct 08, 2013 12:51 am
Posts: 94
OK, this makes no sense whatsoever.

I checked the SAB config. It was already set to 8085.

I ran the script without a reboot and it completed without issue in 5 minutes.

I still could not access SAB. With everything else running normally, I figured it was good enough and let it run.

A couple of hours later, I could not access NZBGet.

Enough.

I've started from scratch, again.

I took the NSA as far back to stock as possible.

I removed all packages and rebooted.

Now, I'm working on re-installation.

The saga continues.


Top
 Profile  
 
PostPosted: Mon Oct 10, 2016 6:14 am 
Offline

Joined: Sun Feb 17, 2013 10:00 pm
Posts: 301
It really isn't supposed to be this hard!

Saying that I have found nzbget has crashed/shutdown a few times on me lately... never had the problem with the previous version.

If you start completely from scratch, SAB may start for the fist time on port 8090, which as long as you don't enable Mylar should be ok, I've altered the script on GitHub to fix the conflict.

All I have done is change the startup argument on line 181 to read "-s 0.0.0.0:8085"


Top
 Profile  
 
PostPosted: Wed Oct 12, 2016 7:39 pm 
Offline

Joined: Sat Sep 24, 2016 2:22 pm
Posts: 22
I have an issue - my CPU is running constantly at 100% by the python2 process, subprocess Sickrage (Sickbeard). I have python 2.7.11 installed. I don't have any other versions of python installed as far as I know. Is the version incompatible with/to new for Sickrage? If so, how do I downgrade? Otherwise, what could be the cause of the problem? Have tried restarting Sickrage, restarting the server etc. The CPU usage is fine until Sickrage starts up.


Last edited by kramiz1 on Wed Oct 12, 2016 7:53 pm, edited 1 time in total.

Top
 Profile  
 
PostPosted: Wed Oct 12, 2016 7:52 pm 
Offline

Joined: Sun Feb 17, 2013 10:00 pm
Posts: 301
Which NAS do you have? Sickrage is processor happy, you need to set up the frequency of your searches, if you haven't already they are under search settings, episode search


Top
 Profile  
 
PostPosted: Wed Oct 12, 2016 7:57 pm 
Offline

Joined: Sat Sep 24, 2016 2:22 pm
Posts: 22
burbulence wrote:
Which NAS do you have? Sickrage is processor happy, you need to set up the frequency of your searches, if you haven't already they are under search settings, episode search


Sorry, NSA-325! I have set search frq to 30min and propers to 45min, backlog frq 720. Have also set advanced setting CPU throttling to High (lower CPU usage). Anything I should change there? I interpret your answer as that the python version is fine and Sickrage should work fine with it?


Top
 Profile  
 
PostPosted: Wed Oct 12, 2016 7:59 pm 
Offline

Joined: Sat Sep 24, 2016 2:22 pm
Posts: 22
I see now that I have both python process and python2 process, is that normal? python process is using some CPU but seems normal. It's python2 process that goes bonkers.


Top
 Profile  
 
PostPosted: Wed Oct 12, 2016 8:52 pm 
Offline

Joined: Sun Feb 17, 2013 10:00 pm
Posts: 301
I'm using 2.7.11 and currently 0% cpu usage. Ok I have Backlog to 3600 and dailys to 300.

Open terminal and use the top command to see which program is using the cpu time


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 119 posts ]  Go to page Previous  1, 2, 3, 4, 5, 6, 7, 8  Next

All times are UTC


Who is online

Users browsing this forum: Catboy, Google [Bot], haw3000, vlmaksime, Yahoo [Bot] and 36 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group