The AutoDJ should never be "kicked" using SHOUTcast/Icecast's "kick source" feature. 

Doing so causes the SHOUTcast/Icecast server to forcibly disconnect AutoDJ which in turn causes AutoDJ to stop running when it cannot reconnect.

This has a number of negative side-effects:

- This is interpreted by CentovaCast's monitoring as an unexpected AutoDJ outage (which is correct, because it is indistinguishable from a crash). This will cause AutoDJ to restart (and possibly the stream) which will disrupt your live broadcast.

- CentovaCast will periodically attempt to restart the AutoDJ to recover from the perceived outage. These attempts will fail during the live broadcast and be interpreted as further problems with the server.

- In some cases, the the kicked AutoDJ will remain running in the background and prevent proper control of the AutoDJ. 

If you lose control of AutoDJ, you will need to submit a ticket so that we can restore AutoDJ control for you.
Was this answer helpful? 1 Users Found This Useful (7 Votes)

Most Popular Articles

Autoconf failed for camomile.tar.gz; aborting - Error in installing Liquidsoap

Error :Installing cppo ...install -m 0755 cppo /usr/local/bin || \install -m 0755 cppo.exe...
Controlling Centova Cast

  Init Script Centova Cast includes an LSB-compliant init script in /etc/init.d/centovacast...
How to Update Centova

Update Utility Centova Cast includes a fully automated update utility to upgrade Centova Cast...
AutoDJ Crashing or Buffering

AutoDJ Restarts or Buffering can be caused by:- 'Kicking' AutoDJ from the SHOUTcast/Icecast Admin...
AutoDJ - CentovaCast shows "Source status: Remote"

If CentovaCast shows your source status as "Remote" and won't let you deactivate AutoDJ or...