unrecoverable error

dimitri pater wrote:
> Hi Christian,
> If I understand you correctly, setting logToScreen=True
was the reason 
> that the Googlebot wasn't indexing you site? 

Well, having server.logToScreen=True on my server was
causing any CP 
exception (even NotFound, aka 404) to foul up something
internal and 
generate the internal server error, thus the 500 HTTP status
code.

I usually ssh into my box after starting it up and do a
"python 
myserver.py &" to get the server running in the
background.  Then I quit 
the ssh session, and the CP server keeps running.  I think
it loses its 
terminal or something like that when I end my ssh session
though.

I then have Apache proxy requests for projects.dowski.com to
my CP app.

The reason the Googlebot was staying away had to do with it
getting a 
500 status when trying to read robots.txt.  Your setup might
be 
different enough from mine that you aren't getting exactly
the same 
behavior as I was.

It just sounded like a similar situation.

Christian
http://www.dowski.com


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "cherrypy-users" group.
To post to this group, send email to cherrypy-usersgooglegroups.com
To unsubscribe from this group, send email to
cherrypy-users-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.com/group/cherrypy-users
-~----------~----~----~----~------~----~------~--~---

dimitri pater <dimitri.patergmail.com> writes:

> On 2/16/06, Christian Wyglendowski <christiandowski.com> wrote:
>
>     I usually ssh into my box after starting it up and
do a "python
>     myserver.py &" to get the server running
in the background.  Then I quit
>     the ssh session, and the CP server keeps running. 
I think it loses its
>     terminal or something like that when I end my ssh
session though.
>
>     It just sounded like a similar situation.
>
> and it *does* sound like a similar situation, I also
ssh to start
> the server and probably that loses the terminal when
exiting the
> session

You guys need to take a look at using screen.  Not only does
screen
provide a terminal to programs, but you can reconnect to
them if the
connection gets cut.  I generally keep any number of remote
terminals
open and then reconnect to them after I have sshed in with a
simple
screen -x.

Just a thought.

Jason Earl

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "cherrypy-users" group.
To post to this group, send email to cherrypy-usersgooglegroups.com
To unsubscribe from this group, send email to
cherrypy-users-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.com/group/cherrypy-users
-~----------~----~----~----~------~----~------~--~---