From: William P. <wil...@ya...> - 2010-03-21 17:48:46
|
Sorry!! This was a false warning. I think Yale's wireless went down right in the middle of transfer -- and that was the cause of the "Bad Gateway." I jumped to the gun prematurely. I uploaded the file again -- worked fine. bp On Mar 21, 2010, at 1:41 PM, William Piel wrote: > > On Mar 21, 2010, at 10:37 AM, Jon Auman wrote: > >> The database disk volume was thrown offline. This is not good. I had this happen before and I'm fairly certain that the application query issues is throwing the database into a deadlock. I've submitted a bug for this that has been deemed not critical, but I think that decision should be reconsidered. >> >> Meanwhile, I will look to see if postgresql has options to limit the time a query will run. Alternately, I will need to right a cron job that will kill the processes of hung queries. >> >> -Jon > > > I tried uploading a fairly modest file (43 taxa x 1727 characters) but after some time I got the (below) time-out. A few days earlier I had uploaded the exact same file to stage, and it worked fine. In this case I didn't time how long it took to generate the "Bad Gateway" response, but it didn't feel very long (2 min?) -- so for a starter perhaps the server's time-out parameter should be increased. > > bp > > Bad Gateway > > The proxy server received an invalid response from an upstream server. > Apache/2.2.3 (CentOS) Server at www.treebase.org Port 80 > > |