FWIW, I've been running web2py from a Terminal shell prompt quite a bit, and starting/stopping works fine (with the source release, or a trunk clone).
You might try comparing the output of ps before and after stopping the server (or use Activity Monitor).
I looked at this very briefly (1.92.1).
The first server-start via the Tcl interface works normally.
A stop and then another start yields this cli message:
ERROR:Rocket.Errors.Port8000:Socket 127.0.0.1:8000 in use by other process and it won't share.
please visit:
http://127.0.0.1:8000
starting browser...
WARNING:Rocket.Errors.Port8000:Listener started when not ready.
Another stop and start works OK.
So the stop call isn't really stopping everything. No idea why.
Restarting web server does not restart web2py, i think.Not sure if it should restart it or not, but... same here
I do not.
My guess is that it's related to the Rocket stop method. The first stop isn't effective, and something about the second start, or its associated stop, or its page load, fixes the problem, so that the second stop and third start work OK.
The message sequence is a little strange:
ERROR:Rocket.Errors.Port8000:Socket 127.0.0.1:8000 in use by other process and it won't share.
please visit:
http://127.0.0.1:8000
starting browser...
WARNING:Rocket.Errors.Port8000:Listener started when not ready.
The WARNING is a consequence of the ERROR, I think. But why isn't .stop killing the listener?
Martin raises an interesting question, though: what's the reason for bothering to stop and start Rocket from the Tcl interface? It's sometimes useful to restart web2py, but that's not what happens here. Sure, it'd be nice if the stop function worked, but even if it did, it's probably not doing what the user expects.
my web2py died in my raspberry pi yesterday when i was following through the "killer web development" tutorial... somewhere regarding the selenium. the server webpage did not show anything. i panicked and removed the whole web2py folder.
then i downloaded the source code and run python 2.6 web2py.py
now i can't use my public IP to start server. same rocket.errors.port8000:socket 10.0.0.189:8000 in use by other process and it wont share. but the local IP works fine. However i cant access the server from another computer.
so how should i solve the problem?? there isn't any solutions in this discussion?
please help. thank you.
--
---
You received this message because you are subscribed to the Google Groups "web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to web2py+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.