There are several possible reasons why Centova Cast could not start your streaming server. Some of the common ones are:

• Another application is using the same port number that you assigned to your stream. This can happen if you have multiple streams on the same server, or if you have configured the stream for an IP address that does not exist on your server.
• You have set your listener limit to an unrealistic value (such as 99999). This can cause memory allocation problems for your streaming server.
• The pathname to your SHOUTcast or IceCast server binary is incorrect. This can happen if you have installed or updated your streaming server software manually, or if you have moved or renamed the files.
• There is a permissions or ownership problem on your files or directories. This can happen if you have changed the permissions or ownership of your Centova Cast files or directories manually, or if you have restored them from a backup.

How to Fix the Error

To fix this error, you need to diagnose the problem by reviewing the server logs. To do so:

• Login to the affected account and click the View Logs link under the Management heading.
• Scroll to the bottom of the log page and select click the Error Log link.
• 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.

Depending on the cause of the error, you may need to take different actions to resolve it. Some of the possible solutions are:

• If another application is using the same port number, you need to either stop the other application from using this port number, or change your stream settings to use an alternate port. To change your stream settings, login to Centova Cast as admin, click on Streams, select your stream, and click on Edit. Then go to the Server tab and change the port number in the Port field. Save your changes and try starting your stream again.
• If you have set your listener limit too high, you need to lower it to a reasonable value. To do so, follow the same steps as above, but go to the Limits tab and change the value in the Max Listeners field. Save your changes and try starting your stream again.
• If the pathname to your SHOUTcast or IceCast server binary is incorrect, you need to correct it. To do so, login to Centova Cast as admin, click on Server Software, then select SHOUTcast (or IceCast) and look in the Pathname field. Make sure that this matches the location of your streaming server binary on your server. You can verify that by logging in to your server via SSH and typing the pathname followed by enter. If you see a message like “SHOUTcast Distributed Network Audio Server” or “IceCast v2.x.x”, then the path is correct. If you see any errors, then you need to fix them.
• If there is a permissions or ownership problem on your files or directories, you need to restore them to their original state. To do so, login to your server via SSH as root and run these commands:

chown -R centovacast:centovacast /home/centovacast/vhosts/ chmod -R 0755 /home/centovacast/vhosts/

This will ensure that all your files and directories are owned by the “centovacast” user and group, and have “sane” permissions.

After applying any of these solutions, try starting your stream again and see if it works.

In this article, we have explained how to fix problems starting server: server startup failed error in Centova Cast. We have covered some of the possible causes of this error and how to diagnose them by reviewing the server logs. We have also provided some possible solutions for each cause and how to apply them.

We hope that this article has helped you resolve this error and start your stream successfully. If you have any questions or feedback, please feel free to contact us at tutosquad.com/contact-us