Why You Shouldn't "Kick" AutoDJ? Print

  • SHOUTcast, server, disruption, Icecast, AutoDJ, CentovaCast, monitoring, restart, disconnect, Kick AutoDJ
  • 5650

Using SHOUTcast/Icecast's "kick source" feature to disconnect AutoDJ might seem like a quick fix, but it can actually lead to more problems than it solves.

When you kick AutoDJ, the SHOUTcast/Icecast server forcibly disconnects it, causing AutoDJ to stop running. This abrupt halt can trigger a chain of negative consequences:

AutoDJ Outage Alerts: CentovaCast's monitoring system interprets the forced disconnection as an unexpected outage. As a result, AutoDJ is restarted automatically, potentially disrupting your live broadcast.

Repeated Restart Attempts: CentovaCast will make repeated attempts to restart AutoDJ to recover from the perceived outage. However, during a live broadcast, these attempts are futile and may be misinterpreted as further server issues.

Background AutoDJ: In some cases, the kicked AutoDJ may continue running in the background, complicating efforts to regain control and properly manage the AutoDJ.

If you find yourself in a situation where you've lost control of AutoDJ due to a kick or similar action, don't panic. Simply submit a ticket to our support team, and we'll promptly restore AutoDJ control, ensuring minimal disruption to your stream.

In conclusion, while it may be tempting to kick AutoDJ as a quick fix, it's best to avoid this action to maintain the stability and continuity of your stream. Trust in our support team to address any issues promptly and effectively, allowing you to focus on delivering top-quality content to your audience without interruptions.


Was this answer helpful?

« Back