Centova Technologies Forum

Centova Cast v3 => Bugs and issues => Topic started by: wisez on March 04, 2013, 09:57:08 am

Title: AutoDJ stopped working after update
Post by: wisez on March 04, 2013, 09:57:08 am
I use shoutcast 1 with ices-cc for autodj.

It worked flawlessly until now. (I didn't expect it  ;D )

But after an update today when I try to start a station I get:
Stream could not be started: Application icescc exited immediately after startup.

Checked logs and diagnostic mode but nothing shows up. Like there is no log.
Title: Re: AutoDJ stopped working after update
Post by: My Auto DJ on March 08, 2013, 03:44:15 pm
did you try to change the port number?, I have had this problem with various accounts here and there for months, it's rare however, I think the port is not being fully removed when you delete a account and then when you create a new one on the same port it cause this problem.
Title: Re: AutoDJ stopped working after update
Post by: wisez on March 08, 2013, 08:13:39 pm
I don't know why, the system, the update, honestly I don't know the reason.
But doing a ices-cc recompile / reinstall from sources then it worked.
All back to normal!
Title: Re: AutoDJ stopped working after update
Post by: rihosts on March 08, 2013, 10:59:25 pm
Hi, Run /usr/local/centovacast/sbin/update  in SSH. Then in client panel open settings page and click save.

Now start stream and autodj will start. Also Make sure there is no intro file or fallback file enable.

The intro files are making autodj process run rouge.
Title: Re: AutoDJ stopped working after update
Post by: My Auto DJ on March 09, 2013, 04:18:02 am
If a reseller deletes a account, then recreates (very common), the system automatically puts the new account on the same port,  but a reseller cannot run any command because they do not have root access so that is not really a solution
Title: Re: AutoDJ stopped working after update
Post by: Centova - Steve B. on March 09, 2013, 05:07:27 pm
If a reseller deletes a account, then recreates (very common), the system automatically puts the new account on the same port,  but a reseller cannot run any command because they do not have root access so that is not really a solution
If the account is deleted it shouldn't matter that the new one reuses the same port.  The only way there could be any impact in reusing a port number is if something is still running on that port.

If so, that would imply that either the server is not being shut down correctly before deletion, or that something is going wrong at the OS level that's causing the application to remain running but stop responding to POSIX signals.  That's quite simple to check, though -- delete an account, then run 'ps aux' and check to see if there is still an sc_serv/icecast/icescc process running for that account.