-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HLS cleanup not working #265
Comments
|
what's in error.log? |
|
Unfortunately the error.log is empty. |
|
Then full debug log |
|
He got the config from me: It's posted here (sorry for the bad colors) We checked the GOP period also. The cam sends a keyframe every 250 frames at 25 fps so that should divide into neat 10s chunks. |
|
So now i made a full debug log for a time period of approx. 12 min. (started at 18:34, ended at 18:46), 71 fagments where made in this time with the above posted settings, with 'grep cleanup' i get the following output: [root@alarmpi tmp]# grep cleanup nginx.error.log Are there more interesting parts you may want to see? Thanks, |
|
Here's the full log he sent me in email (3MB gzipped) http://ftp.tuebingen.mpg.de/pub/kyb/towolf/raspberry-camera-streaming/resources/nginx.error.log.gz |
|
Err, why does it say:
|
|
Does it matter that on startup the clock is still set to 1970-01-01? It might be that NTP network time comes later. It is visible in the log. |
|
Indeed the time seems to be the problem. Many thanks to towolf and arut. |
|
I have the same issue. |
|
why closed? |
Hi,
i have the problem that hls_cleanup is not working at all, nginx does not delete anything, the path with the fragments is getting bigger and bigger until the is no space left on the disk
Here is my config:
I used different settings for hls_fragment and hls_playlist_length but that does not change anything. Even with the above settings in a short time i get easily over 100 fragments without one of them is getting deleted.
Nginx is running on an RaspberryPi with an Arch-Linux.
Any ideas?
Thanks,
hpms1972
The text was updated successfully, but these errors were encountered: