have this weird issue where uploading 1GB+ file takes forever to upload and upload systems browser semi freezes[takes long time to open other web pages]
explored all logs but nothing inside apart from NC log:
Level
App Message Time
Debug cron Finished OCA\Files_Sharing\ExpireSharesJob job with ID 14 2017-03-09T00:30:01+1300
Debug cron Run OCA\Files_Sharing\ExpireSharesJob job with ID 14 2017-03-09T00:30:01+1300
Debug cron Finished OCA\Files_Sharing\DeleteOrphanedSharesJob job with ID 13 2017-03-09T00:30:01+1300
Debug cron Run OCA\Files_Sharing\DeleteOrphanedSharesJob job with ID 13 2017-03-09T00:30:01+1300
Debug cron Finished OC\Authentication\Token\DefaultTokenCleanupJob job with ID 10 2017-03-09T00:30:01+1300
Debug no app in context Invalidating remembered session tokens older than 2017-02-21T11:30:01+00:00 2017-03-09T00:30:01+1300
Debug no app in context Invalidating session tokens older than 2017-03-07T11:30:01+00:00 2017-03-09T00:30:01+1300
Debug cron Run OC\Authentication\Token\DefaultTokenCleanupJob job with ID 10 2017-03-09T00:30:01+1300
Debug cron Finished OCA\DAV\CardDAV\SyncJob job with ID 9 2017-03-09T00:30:01+1300
Debug cron Run OCA\DAV\CardDAV\SyncJob job with ID 9 2017-03-09T00:30:01+1300
Debug cron Finished OCA\Files\BackgroundJob\DeleteOrphanedItems job with ID 7 2017-03-09T00:30:01+1300
Debug cron Run OCA\Files\BackgroundJob\DeleteOrphanedItems job with ID 7 2017-03-09T00:30:01+1300
Debug cron Finished OCA\Files\BackgroundJob\ScanFiles job with ID 6 2017-03-09T00:30:01+1300
Debug cron Run OCA\Files\BackgroundJob\ScanFiles job with ID 6 2017-03-09T00:30:01+1300
Debug cron Finished OCA\Files\BackgroundJob\CleanupFileLocks job with ID 5 2017-03-09T00:30:01+1300
Debug cron Run OCA\Files\BackgroundJob\CleanupFileLocks job with ID 5
Info cli Memcache \OC\Memcache\APCu not available for distributed cache 2017-03-09T00:30:01+1300
Info cli Memcache \OC\Memcache\APCu not available for local cache 2017-03-09T00:30:01+1300
Debug cron Finished OCA\Files_Sharing\ExpireSharesJob job with ID 14 2017-03-09T00:15:01+1300
Debug cron Run OCA\Files_Sharing\ExpireSharesJob job with ID 14 2017-03-09T00:15:01+1300
Debug cron Finished OCA\Files_Sharing\DeleteOrphanedSharesJob job with ID 13 2017-03-09T00:15:01+1300
Debug DeleteOrphanedSharesJob 0 orphaned share(s) deleted 2017-03-09T00:15:01+1300
Debug cron Run OCA\Files_Sharing\DeleteOrphanedSharesJob job with ID 13 2017-03-09T00:15:01+1300
Debug cron Finished OC\Authentication\Token\DefaultTokenCleanupJob job with ID 10 2017-03-09T00:15:01+1300
Debug no app in context Invalidating remembered session tokens older than 2017-02-21T11:15:01+00:00 2017-03-09T00:15:01+1300
Debug no app in context Invalidating session tokens older than 2017-03-07T11:15:01+00:00 2017-03-09T00:15:01+1300
Debug cron Run OC\Authentication\Token\DefaultTokenCleanupJob job with ID 10 2017-03-09T00:15:01+1300
Debug cron Finished OCA\DAV\CardDAV\SyncJob job with ID 9 2017-03-09T00:15:01+1300
Debug cron Run OCA\DAV\CardDAV\SyncJob job with ID 9
Are you trying to upload those huge files through a web browser? Did you look at your Apache access logs? What is your max upload size set to (you can find this in the Nextcloud Admin settings, and change it in php.ini)?
This might not be the answer you want to hear, but why do you want to upload such large files through the browser? There are a lot of different technologies working together, and to me I would need a really good reason to want to do this before spending time figuring out how to get it all working. There are other much better options such as using the sync client, using FTP, SAMBA, NFS, etc. I can’t imagine uploading a 90GB file through a web browser (maybe it’s possible though). Have a look at this:
Do you think you could accomplish this using another method?
It’s interesting that you say there’s nothing in the Apache access logs. I have a hunch you’re looking in the wrong location, because the fact that you are able to log into Nextcloud and use it means that you are accessing Apache. Unless you turned access logging off, there should be something in there. On Ubuntu server (and probably Linux Mint as well), the default Apache log location would be /var/log/apache2/access.log and Apache error logs are usually at /var/log/apache2/error.log
Try running sudo tail -f /var/log/apache2/access.log, then browse to Nextcloud and see if anything new appears in the terminal.
Web sessions are fragile, if there’s any network issue during an upload, you have to completely start over. This might explain why large uploads are flaky for you, because one little hiccup breaks the entire thing. I actually like the idea of having the possibility for people to send large uploads to my cloud because it is easy for them (and for me to explain to non technical people), but it’s just not reliable.
That’s why for larger files, it’s always ideal to use some kind of software client (FTP, Webdav, Nextcloud client, etc.) because they can handle network interruptions unlike the browser.
Even though I imagine that most likely your issue stems from the web browser, you can’t rule out some other configuration issues either with Apache, available server memory, etc. But before you can go any further you need to be able to track down those log files.
Can you try another browser? When you say the browser semi freezes and other tabs/ web sites load very slowly, it sounds like a weird behavior.
When I upload bigger files I can still work with the browser without any problems. I’m using Firefox. Maybe the portable version of another browser would be good for some tests.
What happens when you use the NC app or another Webdav app to upload big files? Meaning do you only see the problem of uploading big files with your current browser or different applications as well?
Maybe there is just a browser addon (for web security?) which causes problems.
The apache log you posted didn’t seem to contain anything useful, especially because it didn’t include one of your upload attempts. Remember, you need to find the logs for when your upload failed, so you can track down why. You might also find something useful in the error log. It requires you to monitor the logs during your uploads, and as soon as it fails, comb through the logs to find any information about why.
tail -f /var/apache2/access.log
You also mentioned that you wouldn’t need to upload anything over 2GB, but now you’re saying a 3.1GB file fails. There is obviously a point at which you can’t expect this to work, which is why I think you need to use a client of some sort which handles sending smaller chunks of data to avoid exactly these types of issues.
This is honestly beyond my level of knowledge, but after researching what the theoretical max is for posting files using PHP, I found this PHP bug: https://bugs.php.net/bug.php?id=44522&edit=1
I think unless you dive much deeper into this, you are stuck with a hard limit of 2047MB
I’d be interested if you’re able to upload a file that is exactly 2047MB or thereabout.
I just tested with my setup (Debian 8, php 7.0 with dot deb packages, mod_php, apache). I just uploadad a zip file of 2.7 GB without any problems (verified the checksum). Also check your tmp folders if they are large enough for uploads.
Do you run php as apache module or via fcgi? >>> apache module
You php is 64 bit? >>> 64-bit version of PHP
Did you try with php 5.6 or 7.0? PHP 7.1 is pretty new and I’m not sure if it has been fully tested with NC 11 (NC 12 will have full PHP 7.1 support). >>> Have tried both 5.6 and 7.0 with same results. will wait for NC12 to come out
