Proxy Error: error reading from remote server

[Seb Duggan]

I have a CentOS 6 VPS running Railo 4 and MySQL 5.6; dedicated RAM is 2GB.

On this, I have 2 web contexts, and have been transferring across 2 instances of MuraCMS to the new server, one to each context.

The first instance, with 3 sites, is up and running fine.

I am trying to set up the second instance, but while setting up Mura I get the message:

Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /index.cfm.
Reason: Error reading from remote server

The error appears every time after exactly 60 seconds.

The installation of Railo is via the installer, so is using all the default proxy settings. However, I have upped the Tomcat memory settings a bit:

JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=396m";

Does anyone have any suggestions?

-- Seb

[Seb Duggan]

If it helps, I found the following in my Apache logs:

[Sat Mar 09 11:29:01 2013] [error] [client xxx.xxx.xxx.xxx] (70007)The timeout specified has expired: proxy: error reading status line from remote server 127.0.0.1, referer: http://xxxxxxxxxxxx/admin/index.cfm?muraAction=cSettings.editSite&siteid=en

 

[Sat Mar 09 11:29:01 2013] [error] [client xxx.xxx.xxx.xxx] proxy: Error reading from remote server returned by /admin/index.cfm, referer: http://xxxxxxxxxxxx/admin/index.cfm?muraAction=cSettings.editSite&siteid=en

-- Seb

[David Panzarella]

Are using the Mura rewrites?

--
Sincerely,

David Panzarella
Senior Web Developer
SB InnerWeb Development

--
You received this message because you are subscribed to the Google Groups "Railo" group.
To unsubscribe from this group and stop receiving emails from it, send an email to railo+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Seb Duggan]

Yes, using Mura rewrites.

I discovered the problem, though. I edited the httpd.conf file and set ProxyTimeout to 300 seconds.

Ran the Mura setup again and it worked fine - it just took longer than 60 seconds. I then ran the "deploy bundle" process to import a site, which had also been causing problems, and it ran successfully, but taking 2 minutes.

The problem is that setting request timeout in a CFML page or in Railo admin doesn't actually help, because the Apache proxy setup defaults to a 60 seconds timeout. So even if you have a long CF timeout, the page will still fail if it hasn't completed in 60 seconds.

-- Seb