On 1/12/07, Matt Good <[EMAIL PROTECTED]> wrote:
>
> Jorge Vargas wrote:
> > I'm running a test installation with the following setup
> >
> > I'm on a shared account on webfaction, which has an apache server
> > using mod_proxy to send requests to a tracd instance listening on
> > another port, all of this is over SSL which is provided by apache.
>
> Since Trac is one of the apps officially supported by WebFaction have
> you tried contacting them for support?
>
actually they have it as CGI, and they told me to ask here ;) case it
seems like a trac bug.

> > Proxy Error
> >
> > The proxy server received an invalid response from an upstream server.
> > The proxy server could not handle the request GET /trac.
> >
> > Reason: Error reading from remote server
> >
> > Additionally, a 404 Not Found error was encountered while trying to
> > use an ErrorDocument to handle the request.
>
> Do you have logging enabled?  Is there anything in the Trac or Apache
> error logs to give some more information about this?  Also try piping
> the output of tracd to a file so you can monitor its output for errors.
I'll try to reproduce that with logging in debug, currently all I have
is apache access logs.

>
> How does WebFaction handle long-running processes?  Their shared
> hosting accounts support a limited number of long-running processes, so
> maybe the way you're running tracd is not the "right" way and it's
> getting killed by WebFaction to prevent you from exceeding the
> long-running process limit.

no this is not the case the long running process policy is not handle
that way, on the other hand the tracd process is still running ones I
log back in.

>
> -- Matt Good
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
 You received this message because you are subscribed to the Google Groups 
"Trac Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to