I’m running NextCloud on an ec2 instance with AWS S3 object storage.
I’m kind of in a rocky situation at the moment and I’m playing with NextCloud as a possible solution.
Backstory: I run a small video production company that live streams sporting events. While I have several NAS units at home with loads of data storage and I’m perfectly okay with doing things like scp and such, my video editors, aren’t able to do such things. We’re all also spread out. So we must transfer these files via the internet. combine that with my dwindling storage availability and I’m moving most of our archived recordings over to S3 object storage for now. Maybe one day we’ll get into a new NAS with more storage but for now S3 is our goal.
Anyway: NextCloud has been running great minus a few hickups. The only issue I’m seeing is with webdav. Using webdav, I’m trying to upload a large mp4, (257GiB) Every few hours I get an error http null. Clicking retry continues the upload, but it’s frustrating when you leave a file to upload and come back to an error.
So I’ve got a few questions:
What if anything can I do to solve the webdav issue above?
Is there any way to improve performance?
Am I barking up the wrong tree here trying to use NextCloud for this type of storage?
The thing is NextCloud checks all our boxes for everything else (mostly). So I was really hoping webdav could support these large files to just keep everything in one place, but I also recognize the limitations. An alternative might be S3 storage with some type of client side S3 browser, but that has it’s own troubles.
When you say “WebDAV” are you using a third-party client or doing this from the NC web UI? WebDAV is used in a lot of the pieces so just trying to get a better understanding of your setup before suggesting anything.
Also, can you provide the exact error (stack trace hopefully) from your Nextcloud log when you see these “http null” events (either from Administration->Logging then doing a Copy raw from the clipboard icon or from your nextcloud.log file itself)?
I’ll be honest, I’ve never used webdav a day in my life, so that’s new concept to me.
But if it helps, I’ve connected a “share” on my desktop (Linux) using the webdav address provided in the docs I think. So something like “davs://subdomain.domain.com/remote.php/dav/files/”
and now I feel like a dummy because I never even looked at the logs… I should know better.
I’m seeing 3 errors post in the logs:
fwrite(): Write of 4096 bytes failed with errno=28 No space left on device at /var/www/nextcloud/3rdparty/guzzlehttp/psr7/src/Stream.php#254
fwrite(): Write of 4096 bytes failed with errno=28 No space left on device at /var/www/nextcloud/3rdparty/guzzlehttp/psr7/src/Stream.php#254
fread(): Write of 8192 bytes failed with errno=28 No space left on device at /var/www/nextcloud/3rdparty/icewind/streams/src/Wrapper.php#55
Looking at the, I’m curious if I need to increase the block storage on the EC2 instance to give php a place to put this while transferring to S3 storage?
Also just noticed a warning in Administration Overview that wasn’t there before:
The PHP OPcache module is not properly configured.
The OPcache interned strings buffer is nearly full. To assure that repeating strings can be effectively cached, it is recommended to apply `opcache.interned_strings_buffer` to your PHP configuration with a value higher than `10`.