Follow up question. What's the deal with the 2GB limit it mentions? I think it would be pretty convienent to allow larger uploads. We're on a fast local network so even 10 or 20 GB uploads pretty fast.
Can I increase the limit in Apache? Which browsers are limited? This is an internal install so I can tell users to only use certain browsers for uploads. -Greg On Thu, Nov 29, 2012 at 11:01 AM, Nate Coraor <n...@bx.psu.edu> wrote: > On Nov 29, 2012, at 10:54 AM, greg wrote: > >> Thanks. That seemed to have worked. Can you explain what happened? >> (I'm curious) > > It's due to a bug that we've done quite a bit of work to investigate, but > haven't yet found the cause. It seems to have cropped up more frequently in > the past few weeks, so we'll be working on it in depth in the next few days. > > --nate > >> >> -Greg >> >> On Thu, Nov 29, 2012 at 8:43 AM, Nate Coraor <n...@bx.psu.edu> wrote: >>> On Nov 28, 2012, at 1:23 PM, greg 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. >>> >>> Hi Greg, >>> >>> Could you try the following: >>> >>> Open tools/data_source/upload.xml >>> >>> In the following line, set 'ajax-upload="false"': >>> >>> <param name="file_data" type="file" size="30" label="File" >>> ajax-upload="false" help="TIP: Due to browser limitations, uploading files >>> larger than 2GB is guaranteed to fail. To upload large files, use the URL >>> method (below) or FTP (if enabled by the site administrator)."> >>> >>> Then restart Galaxy and retry the upload and let us know if it succeeds. >>> >>> --nate >>> >>>> >>>> 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 >>>> ___________________________________________________________ >>>> Please keep all replies on the list by using "reply all" >>>> in your mail client. To manage your subscriptions to this >>>> and other Galaxy lists, please use the interface at: >>>> >>>> http://lists.bx.psu.edu/ >>> >> > ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
