Uploading Large Files - Present in media folder, fail processing and don't show on site. #1074
Replies: 4 comments 6 replies
-
Okay, this is getting weird. I was able to reproduce this behavior with the server installation on a fresh Ubuntu 22.04 VM. I am once again getting the I'm starting to become skeptical of my edits to the config or my SMB share, but I've been browsing through this repo's discussions and issues and I see a lot of similar issues, so I'm not sure where to look here. Edit: One more thing. Not sure if this is significant, but I see that every time I reboot/shutdown the server there is a stop job for MediaCMS uwsgi, and it always times out at 1m 30s. |
Beta Was this translation helpful? Give feedback.
-
looks as some sort of permissions issue, not sure if any or both of the two (SMB / Proxmox) play role on it, but this is not something happening on other installations so they are suspect. |
Beta Was this translation helpful? Give feedback.
-
I have exactly the same problem here. However, I'm not using Docker. I had already reported this previously in another post. In my case, I noticed that only files larger than 2MB have this error. |
Beta Was this translation helpful? Give feedback.
-
Hi @MAXimized490 , can you also share what is the output of |
Beta Was this translation helpful? Give feedback.
-
My Environment
I am using the Docker installation!
Proxmox, Docker VM, Ubuntu 24.04
Xeon X5687 @ 3.6GHz (8 cores) / 16GB ECC DDR3 @ 1333MHz
media_files/ is mounted via fstab to an SMB share:
<server> <user-home>/mediacms/media_files cifs credentials=<file>,uid=33,gid=1000,file_mode=0775,dir_mode=0775 0 0
My Configs
I wanted to share everything but didn't want a wall of text here, so I put everything on Pastebin.
docker-compose.yaml - https://pastebin.com/YYZs6Paf
I haven't changed anything here other than credentials and the timezone for the DB.
cms/settings.py - https://pastebin.com/yHrG10J5
The main things I changed here are the UPLOAD_MAX_SIZE, MINIMUM_RESOLUTIONS_TO_ENCODE, and CONCURRENT_UPLOADS.
deploy/docker/nginx.conf - https://pastebin.com/cirRYe7y
I added some things here from another discussion post on this topic, such as changing client_max_body_size and adding proxy_request_buffering off.
My own nginx
I am using Nginx Proxy Manager in front of MediaCMS and it handles the certificates. I have mirrored some of the configuration I added to MediaCMS's nginx config, under NPM's Advanced section for the host:
proxy_send_timeout 12000;
client_header_timeout 12000;
client_body_timeout 12000;
proxy_request_buffering off;
proxy_read_timeout 12000;
client_max_body_size 102400M;
deploy/docker/uwsgi.ini - https://pastebin.com/cd2S7gd9
I added the two lines at the bottom, also from the aforementioned discussion.
Issue
Most files I try to upload will seemingly complete their upload, then retry twice, and then state "Upload failed."
Observations
mediacms/media_files/
and can be played from here without issue. MediaCMS is seemingly failing its "processing" stage and so they never show on the site or in the administration page under Medias, but they are present in the folder in their entirety and can be played manually.ls -la
in media_files/ shows that the ownership of everything is www-data:tempgroup. The actual group here is my user's group as specified in fstab, but I guess Docker shows a placeholder since it doesn't recognize the group, so it's possible that's causing issues? But I wouldn't imagine that's the case since files can upload without issue, just not large ones, but I wanted to mention it.debug.log
Here is the output that gets added to debug.log. This shows twice, seemingly for each of the two retries, and the error is the same across all of the files I tested (approx. 30 with varying sizes).
Occasionally, another error will show which seems to be complaining about a chunk file missing for larger uploads. In this case, it's looking for
4a0e1e8f-33b5-45b8-b56a-845b5ac40496/0
but says it doesn't exist. Checking manually from within the web container, I can see that this file does indeed exist at the specified location of/home/mediacms.io/mediacms/media_files/chunks/4a0e1e8f-33b5-45b8-b56a-845b5ac40496/0
.In another instance of this same error, the file it was looking ofr actually does not exist. In this case, it was
f98c1c05-3b20-41ea-adb5-c38f8a17c800/0
and that dir and file are not present.Beta Was this translation helpful? Give feedback.
All reactions