I apologize for potentially sending this 2 (or 3?) times. I just realized I might have sent it to the wrong address? galaxy-dev@lists.bx.psu.edu != galaxy-dev@bx.psu.edu? Thanks again, Greg On Wed, Nov 28, 2012 at 1:23 PM, greg <margeemail@gmail.com> wrote:
I just finished setting up a local install on our cluster but I'm having trouble uploading files.
I was able to (successfully?) upload one 160MB fasta file. But any further uploads I try, they just hang.
Here's the information from the log file:
paste.httpserver.ThreadPool INFO 2012-11-28 12:15:18,190 kill_hung_threads status: 10 threads (0 working, 10 idle, 0 starting) ave time N/A, max time 0.00sec, killed 0 workers galaxy.tools.actions.upload_common INFO 2012-11-28 12:20:36,597 tool upload1 created job id 4 galaxy.jobs.handler INFO 2012-11-28 12:20:38,386 (4) Job dispatched galaxy.jobs.runners.drmaa INFO 2012-11-28 12:20:38,930 (4) queued as 3718641 galaxy.objectstore CRITICAL 2012-11-28 12:21:03,071 /home/galaxy/job_working_directory/000/4 delete error [Errno 39] Directory not empty: '/home/galaxy/job_working_directory/000/4' paste.httpserver.ThreadPool INFO 2012-11-28 12:21:55,763 kill_hung_threads status: 10 threads (0 working, 10 idle, 0 starting) ave time N/A, max time 0.00sec, killed 0 workers paste.httpserver.ThreadPool INFO 2012-11-28 12:28:26,466 kill_hung_threads status: 10 threads (0 working, 10 idle, 0 starting) ave time N/A, max time 0.00sec, killed 0 workers paste.httpserver.ThreadPool INFO 2012-11-28 12:35:09,662 kill_hung_threads status: 10 threads (0 working, 10 idle, 0 starting) ave time N/A, max time 0.00sec, killed 0 workers paste.httpserver.ThreadPool INFO 2012-11-28 12:46:35,565 kill_hung_threads status: 10 threads (0 working, 10 idle, 0 starting) ave time N/A, max time 0.00sec, killed 0 workers
The first upload that worked was around 12:20 (above), and the second failed one was at 12:40. The log file doesn't seem to even mention it? Could that error have killed the server somehow?
Let me know if I can provide more info.
Thanks,
Greg