You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hi there and thanks for your attention
Installed latest icecast-kh version on debian 12 bookwurm to function as a secondary relay / slave expecting it to sun smooth n reliable - which it does.. until blammo - icecast quietly dies after segfaults occur as per kern log.
nothing specifically evident in icecast access or error logs at those times.
Server gladly servers 500+ concurrent listeners across umpteen mounts without a sweat, yet seems bound to conk-out within the coming 24 hours.. it's a pernisious dillemna with no know arning signs to monitor.
Can anyone make recommendation or give insight into why this would happend on a stable OS & stable mature icecast-kh release now?
Ireally dont know where to start troubleshooting besides getting the debug info / crash dumps out - which I must still figure out how to do ;)
many thanks and much love for icecasting!
marek
The text was updated successfully, but these errors were encountered:
hi there and thanks for your attention
Installed latest icecast-kh version on debian 12 bookwurm to function as a secondary relay / slave expecting it to sun smooth n reliable - which it does.. until blammo - icecast quietly dies after segfaults occur as per kern log.
nothing specifically evident in icecast access or error logs at those times.
Server gladly servers 500+ concurrent listeners across umpteen mounts without a sweat, yet seems bound to conk-out within the coming 24 hours.. it's a pernisious dillemna with no know arning signs to monitor.
Can anyone make recommendation or give insight into why this would happend on a stable OS & stable mature icecast-kh release now?
Ireally dont know where to start troubleshooting besides getting the debug info / crash dumps out - which I must still figure out how to do ;)
many thanks and much love for icecasting!
marek
The text was updated successfully, but these errors were encountered: