This can be prevented by stopping the autoDJ properly rather than kicking it. Once a kicked autoDJ has "gone remote", however, you will need to either reboot your server (which will solve the problem automatically) or login to your server via SSH and perform the following steps to terminate it:
ps aux | grep ices | grep USERNAME
Replace USERNAME with the username of the affected stream. That should give you some output that looks like:
centovacast 1354 11.4 0.3 4536 2020 ? Ss Aug07 4841:33 /usr/local/ices/bin/ices -v -c /home/centovacast/vhosts/USERNAME/etc/source.conf
Now, take the number in the second column (in the above example it was 1354, but in your case it will be different) and run:
kill -9 1354
Replace 1354 with the number from the second column. If you received more than one line of numbers above, repeat the "kill" command for each of them.
Find the original article at https://secure.centova.com/pages/faqs/display/kicking_the_autodj_103
- Email, SSL
- 247 Users Found This Useful
The autoDJ should never be "kicked" using ShoutCast's "kick source" feature. Doing so causes the...
Centova Cast v2 Servers have 2 passwords. The Source(DJ) Password is the password used by...
Setting up your Centova Cast Auto DJ is easier than you think. We have made some step-by-step...
You are correct the Amazon buy now imports are broken on Centova Cast 2.2.4. There are two things...
Powered by WHMCompleteSolution