On Jan 11, 2013, at 4:49 AM, Rémy Dernat wrote:
Hi Nate,
Could you push these patch on the galaxy-dist repository ?
Hi Rémy,
Unfortunately, this change just missed the cutoff for today's galaxy-dist, so
it will have to wait for the next one, which should be in two weeks. You are
welcome
Hi,
indeed, you are right. In the database, the job_runner_external_id
column is empty for all jobs causing the crash of Galaxy when they are
stopped. I tried to launch the instance without the --daemon option and
I have got this segmentation fault as you suspected:
run.sh: line 77: 19622
On Jan 10, 2013, at 4:43 AM, MONJEAUD wrote:
Hi,
indeed, you are right. In the database, the job_runner_external_id column
is empty for all jobs causing the crash of Galaxy when they are stopped. I
tried to launch the instance without the --daemon option and I have got this
segmentation
Hello All,
after more researchs, I found that the crash of the galaxy server was
caused by stopping jobs. We are working with our own SGE cluster.
It's weird because we can kill jobs via history or administration panel
without problem.
In the paster.log, we just got this message before the
Hi Cyril,
If you start the server in the foreground (no --daemon option), is there a
segfault when the process dies? If so, this is most likely a problem where a
job is attempting to be stopped that does not have an external job ID set.
Could you check this in the database for one of the
