HLS m3u8 file contain some outrageous file segments

[lexy10]

I am confused on what is going on, when streaming hls and uploading to s3 or on local server, after streaming for 10mins, the m3u8 #EXTINF: file contains some large number. Example below

#EXTINF:2.800000,
livestream_b2c9a158-0c91-4860-9cb0-ed248997689d_1080p2500kbps000000036.ts
#EXTINF:1.433333,
livestream_b2c9a158-0c91-4860-9cb0-ed248997689d_1080p2500kbps000000037.ts
#EXTINF:1.333333,
livestream_b2c9a158-0c91-4860-9cb0-ed248997689d_1080p2500kbps000000038.ts
#EXTINF:2.766667,
livestream_b2c9a158-0c91-4860-9cb0-ed248997689d_1080p2500kbps000000039.ts
#EXTINF:1.400000,
livestream_b2c9a158-0c91-4860-9cb0-ed248997689d_1080p2500kbps000000040.ts
#EXTINF:2.433333,
livestream_b2c9a158-0c91-4860-9cb0-ed248997689d_1080p2500kbps000000041.ts
#EXTINF:89483.400000,
livestream_b2c9a158-0c91-4860-9cb0-ed248997689d_1080p2500kbps000000042.ts
#EXTINF:2.400000,

the average is 2.4, but then we have #EXTINF:89483.400000,

And it happens in like 3 places depending on how long the stream is, how can this be solved please? I am using adaptive rate too.

[lastpeony]

Can you share your publish settings, enviroment and ams version?
Specifically, your encoder, FPS, GOP, and bitrate.
Which software are you using to publish?
Are you publishing from an IP camera?
What protocol are you using for publishing (RTMP, RTSP, WebRTC, SRT)?

[filip-ams]

Hi @lexy10,

This message usually indicates permission issues, did you run the command with sudo privileges? Also to keep your settings you can follow the Upgrading with the Installation Script in our documentation. I hope this helps.

[lexy10]

I am running the upgrade inside of a docker container so there's no sudo needed. But still shows the error...
I will try to make use of the installation script then.

[lexy10]

Hello @filip-ams

I have tried the installation script too, I got the same error. I am so confused on what to do now. I think the issue is running inside docker since there's no sudo inside docker container.

[filip-ams]

Hi @lexy10,

Could you try to run your docker container with --privileged flag ? The command should look something like this:

docker run --privileged --restart=always -d --name antmedia --network=host -it antmediaserver

You can read more about the --privileged flag here.

[lexy10]

Hello @filip-ams

Thank you for the response, I have tried everything possible including the --privileged flag, i still get the same thing. This is my command below

docker run --privileged --restart=always -d --name antmedia --mount source=antmedia_volume,target=/usr/local/antmedia/ --network=host -it antmediaserver

And I still get this response:

mv: cannot move '/usr/local/antmedia' to '/usr/local/antmedia-backup-2024-10-02_10-47-16': Device or resource busy
There is a problem in installing the ant media server. Please send the log of this console to [email protected]