Classic Error with Rocket - can't launch web2py any more

[Dansant vzw]

I'am again trying (after several earlier and succesfull atempts) to learn some web2py. In the past I just got the framework up and running without any problem at all.

Unless I tryed it recently again and got the following error, which seems to be a classic:

ERROR:Rocket.Errors.Port8000:Socket 127.0.0.1:8000 in use by other process and it won't share.
WARNING:Rocket.Errors.Port8000:Listener started when not ready.

I'am working on a Debian Linux machine (Wheezy) and have the Python IDLE 2.6, 2.7 and 3.2 installed on my machine.

I also recently did some experiments with wordpress running on my desktop, but I uninstalled everything (incl. Apache).

And it is still not running properly. The only thing I can think off is the fact that I installed a virus protection clamav. But even when I uninstalled that one, it didn't work.

It is even not working when I'am trying to use it offline (shutting down my home wifi for a while)

[LightDot]

The error is pretty self-explanatory. Another service (or another instance of the same one) is already using port 8000.

So, the solution is to:

- find out which service is it (execute the command 'netstat -lnptu' in your terminal)
- shut that service down.

BTW, installing or uninstalling clamav won't have any effect on running services, nor will disconnecting from your home wi-fi.

Regards

[samuel bonill]

try:

python web2py.py -i 127.0.0.1 -p 500

[Dansant vzw]

I finally tried it and received the following message:

web2py Web Framework
Created by Massimo Di Pierro, Copyright 2007-2014
Version 2.9.5-stable+timestamp.2014.03.16.02.35.39
Database drivers available: SQLite(sqlite3), MySQL(pymysql), PostgreSQL(pg8000), IMAP(imaplib)
please visit:
        http://127.0.0.1:500/
starting browser...

(process:5361): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(process:5361): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(process:5361): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
QGtkStyle was unable to detect the current GTK+ theme.
Qt: Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
konqueror(5361)/kdeui (kdelibs): Session bus not found
To circumvent this problem try the following command (with Linux and bash)
export $(dbus-launch)
KCrash: Application 'x-www-browser' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
sock_file=/root/.kde/socket-debian/kdeinit4__0
Warning: connect() failed: : Bestand of map bestaat niet
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi directly

(process:5364): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(process:5364): GConf-WARNING **: Client failed to connect to the D-BUS daemon:                                                                                                                
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.                                                                                                                                                                             
                                                                                                                                                                                               
(process:5364): GConf-WARNING **: Client failed to connect to the D-BUS daemon:                                                                                                                
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
QGtkStyle was unable to detect the current GTK+ theme.
drkonqi(5364)/kdeui (kdelibs): Session bus not found
To circumvent this problem try the following command (with Linux and bash)
export $(dbus-launch)

Op maandag 21 april 2014 23:53:41 UTC+2 schreef samuel bonill:

[Massimo Di Pierro]

Does this help?

http://askubuntu.com/questions/135573/gconf-error-no-d-bus-daemon-running-how-to-reinstall-or-fix