SABnzbd Forums

Version: 0.6.5
OS: Windows Server 2003 R2
Install-type: Windows zip
Skin (if applicable): Plush
Firewall Software: NOD32 v4.2.35.0 (running directory added as exception)
Are you using IPV6? no
Is the issue reproducible? maybe

Hey Guys I was hoping you could point me in the right direction.
Since a reboot a couple of months ago I have been unable to start Sabnzbd for more than a few seconds, unless I run it in console mode.
and now, following an unexpected server shutdown I cannot get even the console mode to restart.

Here is a section of the log that might allow someone to see where I am going wrong and what my issue is.
I was thinking it might be something to do with the httpserver not shutting down properly, but even with another couple of system reboots I am at a loss as to why it will not start.

Can anyone enlighten me please?

2011-07-25 21:00:37,342::INFO::[sabnzbd:1159] --------------------------------
2011-07-25 21:00:37,375::INFO::[sabnzbd:1160] SABnzbd-console.exe-0.6.5 (rev=2916)
2011-07-25 21:00:37,375::INFO::[sabnzbd:1169] Platform=Windows-2003Server-5.2.3790-SP2 Class=nt
2011-07-25 21:00:37,375::INFO::[sabnzbd:1174] Python-version = 2.5.5 (r255:77872, Jan 31 2010, 15:49:35) [MSC v.1310 32 bit (Intel)]
2011-07-25 21:00:37,390::INFO::[sabnzbd:1187] Read INI file S:\NewsGroups\SABnzbd-App\sabnzbd.ini
2011-07-25 21:00:37,390::INFO::[__init__:847] Loading data for running.sab from S:\NewsGroups\SABnzbd-App\admin\running.sab
2011-07-25 21:00:37,390::INFO::[__init__:850] S:\NewsGroups\SABnzbd-App\admin\running.sab missing, trying old cache
2011-07-25 21:00:37,390::INFO::[__init__:853] S:\NewsGroups\SABnzbd-App\cache\running.sab missing
2011-07-25 21:00:37,405::INFO::[__init__:828] Saving data for running.sab in S:\NewsGroups\SABnzbd-App\admin\running.sab
2011-07-25 21:00:37,405::INFO::[__init__:847] Loading data for bookmarks.sab from S:\NewsGroups\SABnzbd-App\admin\bookmarks.sab
2011-07-25 21:00:37,405::INFO::[__init__:847] Loading data for rss_data.sab from S:\NewsGroups\SABnzbd-App\admin\rss_data.sab
2011-07-25 21:00:37,405::INFO::[__init__:847] Loading data for totals9.sab from S:\NewsGroups\SABnzbd-App\admin\totals9.sab
2011-07-25 21:00:37,937::INFO::[__init__:288] All processes started
2011-07-25 21:00:37,937::INFO::[sabnzbd:328] Web dir is S:\NewsGroups\SABnzbd-App\interfaces\Plush
2011-07-25 21:00:37,967::INFO::[sabnzbd:328] Web dir is S:\NewsGroups\SABnzbd-App\interfaces\smpl
2011-07-25 21:00:38,030::INFO::[sabnzbd:1228] Starting SABnzbd-console.exe-0.6.5
2011-07-25 21:00:38,030::DEBUG::[__init__:299] Starting postprocessor
2011-07-25 21:00:38,030::DEBUG::[__init__:302] Starting assembler
2011-07-25 21:00:38,030::DEBUG::[__init__:305] Starting downloader
2011-07-25 21:00:38,030::DEBUG::[scheduler:172] Starting scheduler
2011-07-25 21:00:38,030::DEBUG::[__init__:310] Starting dirscanner
2011-07-25 21:00:38,030::INFO::[dirscanner:263] Dirscanner starting up
2011-07-25 21:00:38,030::DEBUG::[__init__:315] Starting urlgrabber
2011-07-25 21:00:38,030::INFO::[sabnzbd:451] _yenc module... found!
2011-07-25 21:00:38,030::INFO::[urlgrabber:75] URLGrabber starting up
2011-07-25 21:00:38,030::INFO::[sabnzbd:459] par2 binary... found (S:\NewsGroups\SABnzbd-App\win\par2\par2.exe)
2011-07-25 21:00:38,030::INFO::[sabnzbd:464] par2-classic binary... found (S:\NewsGroups\SABnzbd-App\win\par2\par2-classic.exe)
2011-07-25 21:00:38,030::INFO::[sabnzbd:467] unrar binary... found (S:\NewsGroups\SABnzbd-App\win\unrar\UnRAR.exe)
2011-07-25 21:00:38,030::INFO::[sabnzbd:472] unzip binary... found (S:\NewsGroups\SABnzbd-App\win\unzip\unzip.exe)
2011-07-25 21:00:38,046::INFO::[sabnzbd:487] pyOpenSSL... found (True)
2011-07-25 21:00:38,092::INFO::[sabnzbd:1336] Starting web-interface on server:8081
2011-07-25 21:00:38,092::ERROR::[sabnzbd:1351] Failed to start web-interface:
Traceback (most recent call last):
File "SABnzbd.py", line 1342, in main
File "cherrypy\process\servers.pyo", line 240, in check_port
IOError: Port 8081 is in use on 'server'; perhaps the previous httpserver did not shut down properly.
2011-07-25 21:00:38,092::ERROR::[sabnzbd:298] Failed to start web-interface : Port 8081 is in use on 'server'; perhaps the previous httpserver did not shut down properly.
2011-07-25 21:00:38,092::INFO::[__init__:324] SABnzbd shutting down...
2011-07-25 21:00:38,092::INFO::[__init__:828] Saving data for bookmarks.sab in S:\NewsGroups\SABnzbd-App\admin\bookmarks.sab
2011-07-25 21:00:38,092::DEBUG::[__init__:331] Stopping URLGrabber
2011-07-25 21:00:38,108::INFO::[urlgrabber:70] URLGrabber shutting down
2011-07-25 21:00:43,030::DEBUG::[__init__:338] Stopping Newzbin-Grabber
2011-07-25 21:00:43,030::DEBUG::[newzbin:143] Stopping MSGIDGrabber
2011-07-25 21:00:43,030::DEBUG::[__init__:345] Stopping dirscanner
2011-07-25 21:00:43,030::INFO::[__init__:828] Saving data for watched_data.sab in S:\NewsGroups\SABnzbd-App\admin\watched_data.sab
2011-07-25 21:00:43,030::INFO::[dirscanner:254] Dirscanner shutting down
2011-07-25 21:00:44,030::DEBUG::[__init__:354] Stopping downloader
2011-07-25 21:00:44,030::INFO::[downloader:375] Shutting down
2011-07-25 21:00:44,030::DEBUG::[__init__:357] Stopping assembler
2011-07-25 21:00:44,030::INFO::[assembler:70] Shutting down
2011-07-25 21:00:44,030::DEBUG::[__init__:364] Stopping postprocessor
2011-07-25 21:00:44,030::INFO::[postproc:83] Saving postproc queue
2011-07-25 21:00:44,030::INFO::[__init__:828] Saving data for postproc1.sab in S:\NewsGroups\SABnzbd-App\admin\postproc1.sab
2011-07-25 21:00:44,312::INFO::[__init__:828] Saving data for queue9.sab in S:\NewsGroups\SABnzbd-App\admin\queue9.sab
2011-07-25 21:00:44,312::INFO::[__init__:828] Saving data for totals9.sab in S:\NewsGroups\SABnzbd-App\admin\totals9.sab
2011-07-25 21:00:44,312::INFO::[__init__:828] Saving data for rss_data.sab in S:\NewsGroups\SABnzbd-App\admin\rss_data.sab
2011-07-25 21:00:44,312::INFO::[__init__:828] Saving data for bookmarks.sab in S:\NewsGroups\SABnzbd-App\admin\bookmarks.sab
2011-07-25 21:00:44,312::INFO::[__init__:828] Saving data for watched_data.sab in S:\NewsGroups\SABnzbd-App\admin\watched_data.sab
2011-07-25 21:00:44,312::INFO::[postproc:83] Saving postproc queue
2011-07-25 21:00:44,312::INFO::[__init__:828] Saving data for postproc1.sab in S:\NewsGroups\SABnzbd-App\admin\postproc1.sab
2011-07-25 21:00:44,328::INFO::[__init__:847] Loading data for running.sab from S:\NewsGroups\SABnzbd-App\admin\running.sab
2011-07-25 21:00:44,328::DEBUG::[scheduler:213] Terminating scheduler
2011-07-25 21:00:44,328::INFO::[__init__:380] All processes stopped

madbandit wrote:
2011-07-25 21:00:38,092::INFO::[sabnzbd:1336] Starting web-interface on server:8081
2011-07-25 21:00:38,092::ERROR::[sabnzbd:1351] Failed to start web-interface:
Traceback (most recent call last):
File "SABnzbd.py", line 1342, in main
File "cherrypy\process\servers.pyo", line 240, in check_port
IOError: Port 8081 is in use on 'server'; perhaps the previous httpserver did not shut down properly.
2011-07-25 21:00:38,092::ERROR::[sabnzbd:298] Failed to start web-interface : Port 8081 is in use on 'server'; perhaps the previous httpserver did not shut down properly.

So: port 8081 is already in use.
Step 1: Check if it is SABnzbd self that's running on port 8081? Check via http://localhost:8081/ .
Step 2: if not, start SABnzbd on another port. Go into the SABnzbd folder ("C:\Program Files\SABnzbd\" ?), then start by hand: SABnzbd-console.exe --server 127.0.0.1:8085. If that does not work, SABnzbd-console.exe --server localhost:8899
Step 3: if that does not work, de-activate your firewall, and try again.

Well, something is blocking port 8081. Could be even be your NOD32.
Check out the tool "NetLimiter 3 Monitor". It will tell you what uses which port).
(You can also use the older NetLimiter 2 Monitor, that one needs no registration email address).

Thanks for the quick responses guys.
- Sander, I've tried that running it with several different ports but it reports that, whichever port I use, is already in use.
I have tried with the firewall disabled too, but it makes no difference.

- Shypike, I've downloaded NL3M and installed it. I'll look at the results following the reboot.

madbandit wrote:Thanks for the quick responses guys.
whichever port I use, is already in use.

I'd put my money on NOD32.
It's simply not possible that all ports are blocked.
BTW: isn't rebooting the magic Windows cure?

BTW: isn't rebooting the magic Windows cure?

You would have thought so, but alas, several reboots later it does not appear to have solved the issue, nor can I find what thinks it is using any of the ports.
NOD32 has been solid for a couple of years for me, but maybe it is time to assess other options...

madbandit wrote:

BTW: isn't rebooting the magic Windows cure?

You would have thought so, but alas, several reboots later it does not appear to have solved the issue, nor can I find what thinks it is using any of the ports.
NOD32 has been solid for a couple of years for me, but maybe it is time to assess other options...

So, have you de-activated NOD32 and tried again? If that doesn't work, de-install NOD32 and try again.

Sorry for the delayed response.
Yes I deactivated and disabled the entirety of ESET Smart Security, to no avail.
I have just also uninstalled it and wallah, i have a working sabnzbd again.
Now to replace the AV & firewall....

Thanks for all of your help guys.

I had exactly the same problem and it annoyed the crap out of me for two days, so if anyone else gets this issue this is how I resolved it;
Open the console (interface now opens)
Config > General > Changed HTTPS port to something else eg 8083 > Save
Exit Web interface, Exit console, Close any running SAB processes.
Clicked the Web interface button (FireFox Errors)
Change the address to https://localhost:8083/sabnzbd/#
Firefox now asks for you to add a permanent exception.
It works now properly.