This indicates that Centova Cast could not start your streaming server (ShoutCast or IceCast).  You should be prompted to try starting the server in diagnostic mode; please do so and see if any relevant information is displayed.

If diagnostic mode does not explain the problem, you will need to review the server logs.  To do so:

1. Login to the affected account and click the View Logs link under the Management heading.
2. Scroll to the bottom of the log page and select click the Error Log link.
3. Review the error log to determine the cause of the startup failure.  Note that the error log is displayed from OLDEST to NEWEST so you need to select the very last page of log data to see the recent entries.
   

While this problem can have a number of potential causes, the most common is a port conflict, indicated by the presence of the following message in the log (under ShoutCast):

This indicates that another application is using the same port number that you assigned to your stream.  To correct this error, you need to either stop the other application from using this port number, or change your stream settings to use an alternate port.


My error log is empty

If the error log is empty, this usually indicates either a permissions/ownership problem, or that the path to your ShoutCast or IceCast server is incorrect. 

To check your path to ShoutCast/IceCast, login to Centova Cast as "admin", click on ShoutCast (or IceCast) and review/modify the path as needed.

If the path is correct, please check that your /home/centovacast/vhosts/ directory, the subdirectory for the stream you are trying to start, and all of the files and directories within that subdirectory are owned by the "centovacast" UNIX user account and have "sane" permissions (i.e., NOT chmod 0777).  If you need to correct your account permissions/ownerships, please refer to the "Manual Recovery" section of our Disaster Recovery article.


I'm seeing a "No such file or directory" error

If you are seeing a message stating "No such file or directory" below the "Server startup failed" error, you are likely using a 64-bit Linux distribution without 32-bit runtime libraries installed.

This is not related to Centova Cast; all 64-bit Linux distributions require 32-bit runtime libraries in order to run 32-bit software.  ShoutCast is a 32-bit application, so it will fail to run without those libraries installed.

Please ask your systems administrator to check this for you.  On Debian-based servers, installing the 32-bit runtime libraries is as simple as running "apt-get install ia32-libs".


My error log says the port is in use, but it's not

If you see the "FATAL ERROR! Some other process is using this port!" error, but you know the port is not in use, this usually indicates that you've configured the stream to listen on an IP address that has not been configured on your server.

Please check the IP address configured for the stream and ensure that it matches one of the IP addresses configured on your server.

If that does not resolve the problem, login to your server via SSH as root and run "netstat -tlnp" to see which process is using the selected port.


I still can't get it to work

If you still experience problems after checking all of the above items, please open a ticket with the helpdesk and provide the following information.  Note that we will only be able to diagnose the problem if all of the following items are provided:

Please include in your ticket:

• The complete error messages and diagnostic mode output from when you try to start the server.
• The last page of log text from your error log.
  
• The URL and admin password for your Centova Cast installation

Add to Favourites
Print this Article