Hello Adam, Thanks for your answer! I have a cluster of arches Docker containers running in AWS ECS. For file storage I use Elastic File System, which (like S3) has also unlimited space, so we can rule that out.
Because the error only occurred in Firefox and not in Chrome I assumed it had nothing to do with AWS. I'm on the free tier, which allows EC2 instances of only 1 GB memory, and at the moment I don't want to dig into the larger instances, especially because I am about to migrate my web containers to on-premise servers. These will be larger and will allow me to test further. Will report here. It will be an interesting hybrid environment with Django on-premise and postgres and elasticsearch in the cloud. :) Thanks again, Vincent On Thursday, 11 August 2016 13:21:28 UTC-4, Adam Cox wrote: > > Hi Vincent. Based on this q/a > https://forums.aws.amazon.com/thread.jspa?threadID=122410, and some > others I found, my first thought (hope) is that it either has to do with > your available disk space or your available memory. Are you storing > uploaded files in your EC2 instance or in an S3 bucket? If the latter, I > assume you can rule out a disk space problem, because S3 doesn't really > have limits on that. If the former, log into the EC2 instance and run df > -h to see how much available disk space you have. > > If you know you have enough disk space, I'd try temporarily changing your > instance type to one with a lot more memory/RAM, and then trying the upload > again. > > If you need to upgrade to a larger volume for more disk space, follow > these steps: > > 1. stop the instance > 2. create a snapshot of the volume attached to it. > 3. detach the volume > 4. create new volume with a higher amount of gb, and choosing your new > snapshot > 5. attach the new larger volume to the instance > 6. restart the instance > > Some of these steps take a few minutes on the AWS end of things, so it > will probably take about 30 minutes overall. > > Let us know how it works! > > Adam > > > On Thu, Aug 11, 2016 at 11:58 AM, Vincent Meijer <[email protected] > <javascript:>> wrote: > >> I am trying to upload a 'large' file (253 MB), but after about a minute >> of loading I get this error: >> >> DatabaseError at >> /resources/HERITAGE_RESOURCE.E18/related-files/ffc19bdb-7f85-427c-b62c-23658e681217 >> >> >> SSL SYSCALL error: EOF detected >> >> >> >> This only happens when I try it on my environment in the AWS cloud using >> Firefox. It works fine using Chrome or using Firefox in a local development >> env (laptop). >> >> >> Does anyone know where this error is coming from? >> >> >> I tried these Firefox settings, but no luck: >> >> accessibility.typeaheadfind.enabletimeout;false >> >> network.http.keep-alive.timeout;600 >> >> network.http.connection-timeout;600 >> >> >> Much appreciated! >> >> Vincent >> >> -- >> -- To post, send email to [email protected] <javascript:>. To >> unsubscribe, send email to [email protected] <javascript:>. >> For more information, visit >> https://groups.google.com/d/forum/archesproject?hl=en >> --- >> You received this message because you are subscribed to the Google Groups >> "Arches Project" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- -- To post, send email to [email protected]. To unsubscribe, send email to [email protected]. For more information, visit https://groups.google.com/d/forum/archesproject?hl=en --- You received this message because you are subscribed to the Google Groups "Arches Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
