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 9, 2013, at 3:51 PM, Langhorst, Brad wrote:
grr - actually - no it's not fixed
I didn't see it on a few refreshes, but apparently it was temporary - or I
was hallucinating.
These problems are tricky to debug because they involve a lot of config
fiddling and retrying. I'd suggest
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
