im using Ubuntu 9.10 "Karmic Koala" Minimal CD
i have tried the unofficial package too, but i get the same problem.
i might just wipe everything and start from scratch...
thanks for all your help though.
Can't Connect to server 0.5.0Beta6
Forum rules
Help us help you:
Help us help you:
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
-
keepitscottie
- Newbie

- Posts: 18
- Joined: January 3rd, 2010, 10:27 pm
Re: Can't Connect to server 0.5.0Beta6
After installation you end up with a full system, don't you?
Are you using 32bit or 64bit?
I'll give it a try with VMWare.
Are you using 32bit or 64bit?
I'll give it a try with VMWare.
-
keepitscottie
- Newbie

- Posts: 18
- Joined: January 3rd, 2010, 10:27 pm
Re: Can't Connect to server 0.5.0Beta6
32bit, ya i mean, its basically a normal linux install, except no gui
Re: Can't Connect to server 0.5.0Beta6
I just installed Ubuntu-9.10 Minimal, selected "Minimal Server", "OpenSSH server".
Then:
Then I could use http://192.168.1.180:8080/sabnzbd on my PC to access the Wizard.
After completion of the Wizard, I can start the regular UI.
No problems here.
(Except that I did not install par2, unrar and unzip, for which I get three warnings)
Then:
Code: Select all
sudo apt-get install python-Cheetah
sudo apt-get install python-yEnc
wget http://downloads.sourceforge.net/project/sabnzbdplus/sabnzbdplus-beta/0.5.0RC3/SABnzbd-0.5.0RC3-src.tar.gz
tar zxf SABnzbd-0.5.0RC3-src.tar.gz
cd SABnzbd-0.5.0RC3
./SABnzbd -s 0.0.0.0:8080 -d -f /home/user/.sabnzbd/sabnzbd.ini
After completion of the Wizard, I can start the regular UI.
No problems here.
(Except that I did not install par2, unrar and unzip, for which I get three warnings)
Re: Can't Connect to server 0.5.0Beta6
I have the same problem
Version: Ex: 0.5.0 RC3
OS: Gentoo Linux 32bit
Install-type: Source
Skin (if applicable): N/A
Firewall Software: N/A
Are you using IPV6? No
Is the issue reproducible? Yes
I've tried all version of pyton from 2.4-2.6 and I get the error every time.
Is there anything else I can do to debug this ?
Version: Ex: 0.5.0 RC3
OS: Gentoo Linux 32bit
Install-type: Source
Skin (if applicable): N/A
Firewall Software: N/A
Are you using IPV6? No
Is the issue reproducible? Yes
I've tried all version of pyton from 2.4-2.6 and I get the error every time.
The weird thing is if you look at the time stamp sabnzbd starts for about 1 minute and works just fine. I can connect to the Web GUI and browse around for a bit, but then it just crashes. Even if I just start the service and let it sit there idle for 1 minute without touching the Web GUI it also crashes.sabnzbd@ismell ~ $ ./SABnzbd.py -w 1 -l 2 -b 0 -s 0.0.0.0:8080
2010-01-29 21:55:41,405::INFO::[SABnzbd:942] --------------------------------
2010-01-29 21:55:41,405::INFO::[SABnzbd:943] SABnzbd.py-0.5.0RC3 (rev=3240)
2010-01-29 21:55:41,405::INFO::[SABnzbd:953] Platform = posix
2010-01-29 21:55:41,405::INFO::[SABnzbd:954] Python-version = 2.6.4 (r264:75706, Jan 23 2010, 13:58:13)
[GCC 4.3.4]
....
2010-01-29 21:55:41,452::INFO::[SABnzbd:382] _yenc module... found!
2010-01-29 21:55:41,452::INFO::[SABnzbd:390] par2 binary... found (/usr/bin/par2)
2010-01-29 21:55:41,453::INFO::[SABnzbd:398] unrar binary... found (/usr/bin/unrar)
2010-01-29 21:55:41,453::INFO::[SABnzbd:403] unzip binary... found (/usr/bin/unzip)
2010-01-29 21:55:41,453::INFO::[SABnzbd:409] nice binary... found (/usr/bin/nice)
2010-01-29 21:55:41,453::INFO::[SABnzbd:413] ionice binary... found (/usr/bin/ionice)
2010-01-29 21:55:41,454::INFO::[SABnzbd:418] pyOpenSSL... found (True)
2010-01-29 21:55:41,454::INFO::[SABnzbd:1105] Starting web-interface on 0.0.0.0:8080
[29/Jan/2010:21:55:42] ENGINE Bus STARTING
2010-01-29 21:55:42,460::INFO::[_cplogging:55] [29/Jan/2010:21:55:42] ENGINE Bus STARTING
[29/Jan/2010:21:55:42] ENGINE Started monitor thread '_TimeoutMonitor'.
2010-01-29 21:55:42,463::INFO::[_cplogging:55] [29/Jan/2010:21:55:42] ENGINE Started monitor thread '_TimeoutMonitor'.
[29/Jan/2010:21:56:38] ENGINE Error in 'start' listener >
Traceback (most recent call last):
File "/var/lib/sabnzbd/cherrypy/process/wspbus.py", line 147, in publish
output.append(listener(*args, **kwargs))
File "/var/lib/sabnzbd/cherrypy/_cpserver.py", line 90, in start
ServerAdapter.start(self)
File "/var/lib/sabnzbd/cherrypy/process/servers.py", line 62, in start
self.wait()
File "/var/lib/sabnzbd/cherrypy/process/servers.py", line 103, in wait
wait_for_occupied_port(host, port)
File "/var/lib/sabnzbd/cherrypy/process/servers.py", line 275, in wait_for_occupied_port
raise IOError("Port %r not bound on %r" % (port, host))
IOError: Port 8080 not bound on '0.0.0.0'
2010-01-29 21:56:38,070::ERROR::[_cplogging:55] [29/Jan/2010:21:56:38] ENGINE Error in 'start' listener >
Traceback (most recent call last):
File "/var/lib/sabnzbd/cherrypy/process/wspbus.py", line 147, in publish
output.append(listener(*args, **kwargs))
File "/var/lib/sabnzbd/cherrypy/_cpserver.py", line 90, in start
ServerAdapter.start(self)
File "/var/lib/sabnzbd/cherrypy/process/servers.py", line 62, in start
self.wait()
File "/var/lib/sabnzbd/cherrypy/process/servers.py", line 103, in wait
wait_for_occupied_port(host, port)
File "/var/lib/sabnzbd/cherrypy/process/servers.py", line 275, in wait_for_occupied_port
raise IOError("Port %r not bound on %r" % (port, host))
IOError: Port 8080 not bound on '0.0.0.0'
Is there anything else I can do to debug this ?
Re: Can't Connect to server 0.5.0Beta6
First of all: upgrade to RC3, we no longer support any Beta.
Somehow your system doesn't know what to do with the special
address 0.0.0.0.
Instead try these:
-s :8080 This uses the hostname
-s hostname:8080 Replace 'hostname' by the name of your system
-s 192.168.1.4:8080 Replace the IP address by your system's IP address
The hostname may resolve to localhost, in which case you will only have local access
on the system where SABnzbd runs.
The last one (with IP address) will enable outside access to the system.
For local access you will need to use the IP address too.
Somehow your system doesn't know what to do with the special
address 0.0.0.0.
Instead try these:
-s :8080 This uses the hostname
-s hostname:8080 Replace 'hostname' by the name of your system
-s 192.168.1.4:8080 Replace the IP address by your system's IP address
The hostname may resolve to localhost, in which case you will only have local access
on the system where SABnzbd runs.
The last one (with IP address) will enable outside access to the system.
For local access you will need to use the IP address too.
Re: Can't Connect to server 0.5.0Beta6
Oh I guess I did hijack the thread. I'm running 0.5.0RC3.
I just tried all the different combinations and they all broke
Is there anything else I can do to help debug the problem ?
Thanks a lot,
Raul
I just tried all the different combinations and they all broke
I've even tried some random port numbers and none of them seem to be able to bind. I just tried the little script shypike posted and I got2010-01-30 09:18:02,067::INFO::[SABnzbd:1105] Starting web-interface on localhost:8080
[30/Jan/2010:09:18:03] ENGINE Bus STARTING
2010-01-30 09:18:03,071::INFO::[_cplogging:55] [30/Jan/2010:09:18:03] ENGINE Bus STARTING
[30/Jan/2010:09:18:03] ENGINE Started monitor thread '_TimeoutMonitor'.
2010-01-30 09:18:03,073::INFO::[_cplogging:55] [30/Jan/2010:09:18:03] ENGINE Started monitor thread '_TimeoutMonitor'.
[30/Jan/2010:09:18:03] ENGINE Error in HTTP server: shutting down
Traceback (most recent call last):
File "/var/lib/sabnzbd/cherrypy/process/servers.py", line 75, in _start_http_thread
self.httpserver.start()
File "/var/lib/sabnzbd/cherrypy/wsgiserver/__init__.py", line 1629, in start
raise socket.error, msg
error: [Errno 99] Cannot assign requested address
I tried using 0.0.0.0 and that worked just fine. So it doesn't seem to be a port error. From what I can tell its cherrypy. I'm using the cherrypy that came with RC3.sabnzbd@ismell ~ $ python test.py
Connected by ('192.168.0.71', 2454)
Is there anything else I can do to help debug the problem ?
Thanks a lot,
Raul
