I know this as posted ages ago however its the number 1 post in google and has no answer. NGINX uses a path relative to where it was started from when it comes to reading sockets at least. I am unsure if this affects additional functionality. At first I thought it was reading from the compile prefix but this doesnt seem to be the case and I also dont see any documentation on this. Here isby Nullivex - Nginx Mailing List - English
Actually, I did a little more testing it seems this is coming from video files that missed bytes on the upload. I was able to fix this by re-uploading the file. Thanksby Nullivex - Nginx Mailing List - English
Hey Guys, I am getting a ton of these errors on certain videos. "no mp4 trak atoms were found in" I have tried changing the mp4_max_buffer_size. However, this has not helped me solve the problem. Is there something else I can try to solve this? Version ~# /usr/local/nginx/sbin/nginx -v nginx version: nginx/1.0.15 OS Debian 6 x86_64 (Fully updated) Complete log entby Nullivex - Nginx Mailing List - English
I am Nullivex, I have been using Nginx for a couple years now and love everything about it. Talk to you all soon.by Nullivex - New Member Introductions