Hi Nate, all
I would like to add my own version of the problem to this.
I, or rather my (inherited) Galaxy instance (which should be running 15.05+, how do I find
out?), have/s similar symptoms as Richard's did. In my case it only occurs to a single
user and we are not able to execute the "Saved Histories" command any more.
Galaxy will fail with
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /history/list.
Reason: Error reading from remote server
Due to some problem with the psql-client I cannot find the potential perpetrators (my user
has lots of bam files in various histories) and since he cannot switch histories, we
cannot even update the metadata for his datasets. Is there a possibility to do that via
Any insight/help would be greatly appreciated!
On 08/07/15 21:04, Poole, Richard wrote:
I am having trouble right now with my own personal account on my production server. Grid
refreshes are taking a huge amount of time (e.g. when viewing ‘saved histories’ or even
generating the dataset list for a single history). My account is very full of data (1TB),
could it be this?
There are no obvious messages in the logs though so I am a bit stumped as to why.I do not
have the same trouble when impersonating other users with fairly full accounts. Perhaps a
database issue (I do not know how to ‘cleanup’ the database or indeed Galaxy user
accounts). Any thoughts?
Dr. Christian Schudoma
Bioinformatics Support Officer
The Sainsbury Laboratory
Norwich Research Park
Norwich NR4 7UH
+44 (0) 1603 450 601