Antmedia AUTO RESTART Schedule and Stop-Sigterm TIMEOUT caused antmedia.service stop

[Rift]

Hi Team,

 

This is the log extracted from Ant Media Enterprise 2.5.3, recently there is a bug when antmedia is being restarted, but the stream won't auto start up and we are required to manually put in settings."streamFetcherAutoStart=true" at the file of "/usr/local/antmedia/webapps/WebRTCAppEE/WEB-INF/red5-web.properties" to make sure the stream auto start broadcasting after antmedia.service restart. 

 

I went and dig deeper into the log file and realized some UNPLANNED restart was scheduled but there are no cron jobs from our side or [TIMER] script in the antmedia.service file that will schedule the auto restart sequence for antmedia.

Also there is Stop-Sigterm TIMEOUT that will cause antmedia to stop and start service as well. 

Hoping to solve these issues as they happened a couple times during critical moments of broadcast sessions. Here is the log file attached for your reference. 

Edited February 23 by Rift

[Yash]

Hi @Rift
I hope you are fine.

1. Not starting stream sources automatically is not a bug, and this feature was implemented in response to a user request to not start the stream automatically when the server restarted in order to avoid unnecessary bandwidth consumption.

As a solution, there is a flag that users can enable/disable based on their use case.

2. There is no scheduled cron job on the server to restart it. Could you please share your full system logs as well as the distribution you are using? Additionally, if possible can we have SSH access to your system? If yes, you can share access on the support ticket that you have raised. It seems there is some system related issue.

[Rift]

Hi @Yash
I'm fine thank you, hope you're fine too.

1. That's a good idea but is/will there a button where to stop all or start all? Cause we have like 100 streams on one antmedia server, it's very time consuming if we were to start each of them.

2. I apologized but we are not able to share access as there is a lot of NDA involving multiple parties, we're using Linux ubuntu18.04. As for syslog files (full system logs), I'm not able to share it here but I'm able to screenshot specified part of log that you may requires, maybe you can tell us particularly what specified logs or response to be look out for, so that I can particularly take it out.

[Yash]

@Rift

1. As you have enabled auto start so now you do not have to start them manually. You streams will start automatically now after server restart. There is no such button to start/stop all streams at a time.

One of my colleagues is working on a solution to stop the stream if there is no viewer and start it again if anyone tries to play. Here is the Git Hub issue for reference: https://github.com/ant-media/Ant-Media-Server/issues/4404

2. No worries.
Can you please explain this 2nd issue in more detail? Is your server not running or is it getting stopped after sometime?
Also please share the server logs. You can collect the server logs from /usr/local/antmedia directory.
 

[Rift]

@Yash
 

1. No worries, we're just wondering if it's possible to have button, as many of the operators that will managing on the antmedia webpage are not IT background, so they do not have any idea on how to set the script in for AutoStart, or how to close all stream at once by shutting down the server. Hoping for easier alternative.

2. I did not monitor the server the whole time but based on the operators that managed the server, it is on the whole time, as all of the stream is required to be up for 24/7. Based on this screen shot, which particular file that you need according to the date.

[Connessione]

On 2/23/2023 at 4:53 PM, Rift said:

@Yash
 

1. No worries, we're just wondering if it's possible to have button, as many of the operators that will managing on the antmedia webpage are not IT background, so they do not have any idea on how to set the script in for AutoStart, or how to close all stream at once by shutting down the server. Hoping for easier alternative.

2. I did not monitor the server the whole time but based on the operators that managed the server, it is on the whole time, as all of the stream is required to be up for 24/7. Based on this screen shot, which particular file that you need according to the date.

@Rift I hope your issue was resolved. You can easily build automation around the functionality you have described. If there are any specific functions that you feel must be there for newbies, please do let the community know.