Hi All,

I have a weird issue that's just cropped up. After a new install of
galaxy (checked out on Monday from github) on a ubuntu vm, using
postgres rather than sqlite as well as a few other production
recommendations, I started playing around with the Data Libraries
functionality. I linked a bunch of fastq.gz files into galaxy (around
150 in total) and everything was working fine. I went home and the
next day, it was down.

I tried to start it up as usual (using an init.d script), it worked
for less than a minute and then disappeared again. So I tried running
it as the galaxy user using ./run.sh and I get a seg fault;

Starting server in PID 23173.
serving on http://144.124.110.39:8080
Segmentation fault

Tried again with strace

Starting server in PID 23552.
serving on http://144.124.110.39:8080
[{WIFSIGNALED(s) && WTERMSIG(s) == SIGKILL}], 0, NULL) = 23552
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_KILLED, si_pid=23552,
si_status=SIGKILL, si_utime=1590, si_stime=1930} ---
rt_sigreturn()                          = 23552
write(2, "Killed\n", 7Killed
)                 = 7
read(10, "", 8192)                      = 0
exit_group(137)                         = ?
+++ exited with 137 +++

I can't see anything odd in the log file and I've turned debugging on
in galaxy.ini. I'm at a bit of a loss. Does anyone know what might be
causing it?

Cheers,