Ulf,
Thanks for all the information, hopefully it helps me replicate this issue
so I can figure out a better fix.
I can work on some better documentation for this, but there aren't any
Galaxy-specific instructions that I know of. Using the basic configuration
for setting up the rabbitmq server
Hi all again
Seems I am not so fortunate that this would just go away.
It appear to be happening sometimes at start-up time for one of the
handler processes. The first thing that appears to go wrong is this just
after starting the job handler queue:
---
galaxy.jobs.handler INFO 2014-10-06
Hi again Ulf,
Thanks for the info. A few questions to help me track this down:
Does the postgres database reside on a remote box from galaxy? And is it
very large?
Running the latest galaxy may not change anything related to this
particular issue, but you could always try it.
Sqlalchemy is
Hi Dannon
Yes. The database is running on a different server from the server
running Galaxy. They are both VMs running Centos (6.5 on the Galaxy
server, 6.2 on the database server). The postgres version is 8.4.9 and
the database size is 712,161,040. I suspect that is not very large
compared
Dear all
Maybe one of you can shed some light on this error message that I see in
the log file for one of my handler processes. I get about one of them
per second. The effect is that most of the jobs remain in the waiting
to run stage.
The postgres database is running on a separate server and
Hi Dannon
I am running 6 handler and 6 web processes. I have the latest stable
version of the code (from June 2nd 2014). My postgres database (version
8.4.9) is running on a different server on the same subnet. Both servers
are Centos (6.5 on the Galaxy server, 6.2 on the database server).
Update:
The usual switching it off and on again (server reboot) has resolved the
problem (for now), albeit in a rather unsatisfactory manner.
If there are any insights what caused this behaviour and how it can be
avoided in the future I'd be more than happy to hear them.
Cheers
Ulf
On
