-
Notifications
You must be signed in to change notification settings - Fork 6
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
ASMARA stops relaying alerts after a few days #43
Comments
Its a bug where it won't relay due to it being a leap year |
Actually we don't fully know that due to how it was worded SSP, do you see any "ALERT VERY EXPIRED" in console? |
No. It does relay alerts, just after a few days it stops doing so without warning. |
Is this instance running on a home network, or a VPS? I have seen this issue occur when the monitors are flapping due to a small internet connection blip, but not long enough for ffmpeg to error out and try bringing the monitor back online |
It is running on a home network. The computer running ASMARA is connected to an ethernet switch, which is then connected to the router. |
So, ASMARA has an ongoing issue that has FFMPEG crash after a bit. It's gonna be awhile till I can do anything though, live has been hard as of late. |
thats not the issue the issue is that wxstream hates anyone who massmonitors them |
After a few days of running, it just refuses to relay any alert. There are no errors in the terminal, it just doesn't print out anything related to some error or EAS message or whatever. It requires me to restart the program every few days. Play out to Icecast still works.
The text was updated successfully, but these errors were encountered: