SABnzbd Forums

Hi all, this is my first post, please go easy on me...

I was sporting a 0.5.x version of SABnzbd for the longest time and recently decided to update to 0.6.9. Now, everytime I restart my computer, I find that there's a long delay before SAB is accessible. The SABnzbd.exe is running right away, but I can't access it through the browser for awhile. I've tried http://127.0.0.1:8080/sabnzbd and http://localhost:8080/sabnzbd, also without the trailing "sabnzbd", but nothing works. I also can't access it through my android apps until it works through the browser, which can sometimes take a half hour or so (I haven't actually timed it yet). This has only been happening since the update.

I'm running Win 7 Ultimate 64 bit on a 6 core AMD. I did a search but didn't find this issue (hopefully I'm not just blind). Any ideas what could be wrong? Seems like a timeout issue, so if you can give me some instructions for pulling up a log or any other way to troubleshoot I'd really appreciate it.

Thanks in advance!

Never seen this happen.
Is there some issue with DNS?
Do you use names or numeric IP addresses?
Fancy firewall software?

shypike wrote:Never seen this happen.
Is there some issue with DNS?
Do you use names or numeric IP addresses?
Fancy firewall software?

Should be no issue with DNS, nothing has changed. I use numeric IP addresses only, and only use the hardware firewall in my router (I've had far too many problems with Windows firewall in the past). The ports for SABnzbd have been opened as well through port forwarding in the router.

Any other ideas? Again, I do want to stress that this only has been happening since the update to 0.6.9. I'll update to 0.6.10 today, just in case, but the release notes don't seem to mention anything about this type of issue.

Go back to, say 0.6.8 and see whether that makes a difference.
At least when 0.6.10 doesn't solve your issue.
You can exchange 0.6.x versions at will.

shypike wrote:Go back to, say 0.6.8 and see whether that makes a difference.
At least when 0.6.10 doesn't solve your issue.
You can exchange 0.6.x versions at will.

Will do. I'll work my way back to find out where the problem arose since, as expected, 0.6.10 didn't fix the problem. I wasn't aware that I could revert to older 0.6.x versions, thanks for the info.

I just installed 0.6.0 and it still has the issue. I never recall having the problem in 0.5.6 though. Do you know if it's possible to revert to that version from 0.6.x to see if it helps?

Here's the SAB log from initially running the exe to actually being able to access it. As you can see, there's a 40 minute gap between it loading the initiation file (12:25:11) and actually starting (13:05:45).
-------------------------------------------------------------------------------------------------
2011-10-23 12:25:10,917::INFO::[sabnzbd:1148] SABnzbd.exe-0.6.0 (rev=2821)

2011-10-23 12:25:11,226::INFO::[sabnzbd:1157] Platform=Windows-Vista-6.1.7600 (=Vista+ x64) Class=nt

2011-10-23 12:25:11,227::INFO::[sabnzbd:1162] Python-version = 2.5.5 (r255:77872, Jan 31 2010, 15:49:35) [MSC v.1310 32 bit (Intel)]

2011-10-23 12:25:11,227::INFO::[sabnzbd:1175] Read INI file C:\Users\Aaron\AppData\Local\sabnzbd\sabnzbd.ini

2011-10-23 13:05:45,335::INFO::[__init__:843] Loading data for running.sab from C:\Users\Aaron\AppData\Local\sabnzbd\admin\running.sab

2011-10-23 13:05:45,335::INFO::[__init__:846] C:\Users\Aaron\AppData\Local\sabnzbd\admin\running.sab missing, trying old cache

2011-10-23 13:05:45,335::INFO::[__init__:849] C:\Users\Aaron\AppData\Local\sabnzbd\cache\running.sab missing

2011-10-23 13:05:45,335::INFO::[__init__:824] Saving data for running.sab in C:\Users\Aaron\AppData\Local\sabnzbd\admin\running.sab

2011-10-23 13:05:45,335::INFO::[__init__:843] Loading data for bookmarks.sab from C:\Users\Aaron\AppData\Local\sabnzbd\admin\bookmarks.sab

2011-10-23 13:05:45,335::INFO::[__init__:843] Loading data for rss_data.sab from C:\Users\Aaron\AppData\Local\sabnzbd\admin\rss_data.sab

2011-10-23 13:05:45,336::INFO::[__init__:843] Loading data for totals9.sab from C:\Users\Aaron\AppData\Local\sabnzbd\admin\totals9.sab

2011-10-23 13:05:45,336::INFO::[postproc:89] Loading postproc queue

2011-10-23 13:05:45,336::INFO::[__init__:843] Loading data for postproc1.sab from C:\Users\Aaron\AppData\Local\sabnzbd\admin\postproc1.sab

2011-10-23 13:05:45,342::INFO::[__init__:843] Loading data for queue9.sab from C:\Users\Aaron\AppData\Local\sabnzbd\admin\queue9.sab

2011-10-23 13:05:45,871::INFO::[__init__:843] Loading data for watched_data.sab from C:\Users\Aaron\AppData\Local\sabnzbd\admin\watched_data.sab

2011-10-23 13:05:45,878::INFO::[downloader:194] Resuming

2011-10-23 13:05:45,878::INFO::[downloader:238] Bandwidth limit set to 550

2011-10-23 13:05:45,880::INFO::[__init__:284] All processes started

2011-10-23 13:05:45,880::INFO::[sabnzbd:326] Web dir is C:\Program Files (x86)\SABnzbd\interfaces\smpl

2011-10-23 13:05:45,881::INFO::[sabnzbd:326] Web dir is C:\Program Files (x86)\SABnzbd\interfaces\smpl

2011-10-23 13:05:45,903::INFO::[sabnzbd:1219] Starting SABnzbd.exe-0.6.0

2011-10-23 13:05:45,920::INFO::[dirscanner:263] Dirscanner starting up

2011-10-23 13:05:45,921::INFO::[sabnzbd:449] _yenc module... found!

2011-10-23 13:05:45,921::INFO::[urlgrabber:75] URLGrabber starting up

2011-10-23 13:05:45,921::INFO::[sabnzbd:457] par2 binary... found (C:\Program Files (x86)\SABnzbd\win\par2\x64\par2.exe)

2011-10-23 13:05:45,923::INFO::[sabnzbd:462] par2-classic binary... found (C:\Program Files (x86)\SABnzbd\win\par2\par2-classic.exe)

2011-10-23 13:05:45,923::INFO::[sabnzbd:465] unrar binary... found (C:\Program Files (x86)\SABnzbd\win\unrar\x64\UnRAR.exe)

2011-10-23 13:05:45,924::INFO::[sabnzbd:470] unzip binary... found (C:\Program Files (x86)\SABnzbd\win\unzip\unzip.exe)

2011-10-23 13:05:45,924::INFO::[sabnzbd:485] pyOpenSSL... found (True)

2011-10-23 13:05:45,973::INFO::[sabnzbd:1327] Starting web-interface on 0.0.0.0:8080

2011-10-23 13:05:47,976::INFO::[_cplogging:55] [23/Oct/2011:13:05:47] ENGINE Bus STARTING

2011-10-23 13:05:47,986::INFO::[_cplogging:55] [23/Oct/2011:13:05:47] ENGINE Started monitor thread '_TimeoutMonitor'.

2011-10-23 13:05:48,289::INFO::[_cplogging:55] [23/Oct/2011:13:05:48] ENGINE Serving on 0.0.0.0:8080

2011-10-23 13:05:48,289::INFO::[_cplogging:55] [23/Oct/2011:13:05:48] ENGINE Bus STARTED

What's the size of C:\Users\Aaron\AppData\Local\sabnzbd\sabnzbd.ini ? And can you open it in an editor (notepad) and does it show normal content?

What happens if you stop SABnzbd, rename / move C:\Users\Aaron\AppData\Local\sabnzbd\sabnzbd.ini , then start SABnzbd, fillout the wizard, and restart SABnzbd ... ?

sander wrote:What's the size of C:\Users\Aaron\AppData\Local\sabnzbd\sabnzbd.ini ? And can you open it in an editor (notepad) and does it show normal content?

What happens if you stop SABnzbd, rename / move C:\Users\Aaron\AppData\Local\sabnzbd\sabnzbd.ini , then start SABnzbd, fillout the wizard, and restart SABnzbd ... ?

sabnzbd.ini is 3.39kB and does show normal stuff. If nobody has other ideas, I'll try renaming it and re-entering everything, but it'll take me awhile to record all the settings...

Try starting up with --clean as an extra option one time.
This will clear the queue. Maybe it's become corrupted.
The ini file should be ok, but do make a backup of it.

shypike wrote:Try starting up with --clean as an extra option one time.

Will that take care of "C:\Users\Aaron\AppData\Local\sabnzbd\admin\running.sab missing"

Interesting, I missed seeing that in the log. The file is there and was when it started, but I noticed that it updated the file the last time that SAB fired up and the file size is only 5 bytes. I apologize for being so "green" in all of this, but what is that file for? Is it a standard file that I could grab from someone else? It apparently isn't something that's refreshed when updating the program since, if that's the problem, it didn't go away when I installed the last couple versions.

Anyway, thanks for helping me figure this out. As for starting with --clean, can you give me a bit more information on how to do this? My greenness is getting in the way again. I assume it means running sabnzbd.exe through command line, but can you give me the full syntax?

The running.sab log entry is just a forgotten left over of a failed feature that was removed.
You can safely ignore that.

WindowsKey-R
"c:\program files (x86)\sabnzbd\sabnzbd.exe" --clean
Enter

Well, I ran it and it didn't make a difference (I actually couldn't run it from the run prompt, I kept getting errors that it linked to an unavailable resource, so I ran it through a command shell).

After running it with the --clean, the log is showing the same thing as before... it read the ini, then nothing (for now). Should there be any mention of the cleaning process in the new log? All of the old logs are now gone, so it definitely seems that the cleaning process happened anyway.

Brute force:

Stop SABnzbd
Rename (or remove) the directory structure C:\Users\Aaron\AppData\Local\sabnzbd
Maybe also rename (or remove) sabnzbd.ini
Start SABnzbd