[Treebase-devel] Can we do a new build? and proxy timeout?

[William P. <wil...@ya...>]

Hi all,

Can we do a new build on production? (and dev or stage, if you have time)

Youjun recently fixed the delete-tree function, and that will be useful for this guy's issue (see below). Also Youjun fixed the MacFirefox-PhyloWidget problem on the browse side of the equation.  For that, we now pass the tree to the latest version of phylowidget stored on the phylowidget.org website (which doesn't have a problem with Mac-Firefox). 

We still have a problem with MacFirefox-PhyloWidget on the Submit side, but that can't be solved just by pointing to the latest copy on phylowidget.org because we have made custom changes to the code (for saving rerooted trees back the database). 

Finally, Michael Pirie's problem (below) seems to be the result of a time-out on headless-Mesquite ingest. Can we increase the time allotted to this process so as to avoid the time-out? (And, I should mention that when I deleted his extra matrix, I also got a proxy-timeout problem -- but when I came back to the submission, the matrix had been deleted. So again, the functions appear to go to completion eventually even though the browser shows a proxy error. If we could avoid the timeout, it would be better).

Bill



On Mar 31, 2010, at 3:18 PM, William Piel wrote:

> Dear Michael Pirie:
> 
> I think that the proxy error came from a time-out because the parser was taking too long to commit the inserts (e.g. 298 x 11810 = 3,519,380 inserts, not including all the other bits) -- but the inserts happened anyway despite the time-out. And it looks like you backed-up and re-clicked, so there were two matrices and two sets of trees. I deleted one of the matrices -- but I don't want to delete the extra set of trees until we've done a rebuild on our deployment (we recently fixed some code having to do with deleting trees). By tomorrow, feel free to delete the extra set of trees. 
> 
> So everything looks okay, despite the fact that the ingest did  a time-out on you. I'm going to suggest that our server gets reset to allow for longer ingest times. 
> 
> regards,
> 
> Bill
> 
> 
> On Mar 31, 2010, at 10:54 AM, Michael D. Pirie via RT wrote:
> 
>> 
>> Wed Mar 31 10:54:10 2010: Request 7708 was acted upon.
>> Transaction: Ticket created by mp...@su...
>>      Queue: Treebase-help
>>    Subject: File upload problem submission 10367
>>      Owner: Nobody
>> Requestors: mp...@su...
>>     Status: new
>> Ticket <URL: https://help.nescent.org/Ticket/Display.html?id=7708 >
>> 
>> 
>> Dear Sir/Madam,
>> I get the following error when attempting to upload a file to my 
>> submission 10367:
>> 
>> 
>> Proxy Error
>> 
>> The proxy server received an invalid response from an upstream server.
>> The proxy server could not handle the request POST 
>> /treebase-web/user/uploadFile.html.
>> 
>> Reason: Error reading from remote server
>> 
>> Apache/2.2.3 (CentOS) Server at www.treebase.org Port 80
>> 
>> 
>> I'm attaching a zipped copy of the file - would it be possible to add 
>> this for me?
>> Thanks and best wishes,
>> 
>> -- 
>> Dr Michael D. Pirie
>> Department of Biochemistry
>> University of Stellenbosch
>> Private Bag X1, MATIELAND 7602
>> Stellenbosch, Western Cape
>> South Africa
>> 
>> Tel: +27-21-8085841
>> Fax: +27-21-8085863
>> 
>> 
>> 
>> <TreeBASE 10367.zip>
>