Centova Cast Common Errors and How to Fix Them (August 2026)

Centova Cast is the web control panel behind thousands of SHOUTcast and IceCast radio stations, and when something breaks, the error messages can feel like a foreign language. I have spent years wrestling with these exact errors while running streaming hosting, so I wrote this guide to give you a single place to solve them. By the end of this article you will know exactly how to read your logs, fix server startup failures, repair AutoDJ and ices crashes, clear port conflicts, and recover from authentication errors.

If you are staring at a screen that says “Server could not be started” right now, skip to Server Startup Failed Errors. Otherwise, start with the logs.

How to Find and Read Centova Cast Error Logs?

Every Centova Cast troubleshooting session begins in the log files. Our support team reviews logs first, last, and always, because they tell you what the software was thinking before it broke.

Where to find them:

• Stream logs: Settings -> System Logs in the Centova Cast control panel.

• ices (AutoDJ) logs: Click the AutoDJ tab in the left sidebar, then click “Deactivate AutoDJ” to stop ices cleanly. The ices log is at /usr/local/centovacast/var/vhosts/[account]/logs/ices.log.

• Server error log: /usr/local/centovacast/var/vhosts/[account]/logs/error.log for SHOUTcast or IceCast messages.

• Control panel log: /usr/local/centovacast/var/log/cc-control.log for the web UI itself.

How to read them: Open the most recent file. Read from the bottom up, since the newest entries are at the end. Look for lines containing words like ERROR, FATAL, denied, refused, or failed. Copy the timestamp and the line right above it. That pair usually contains both the cause and the trigger.

Pro tip: If the log file does not exist or is empty, the server never started writing to it. That itself is a clue – it usually means Centova Cast never got far enough to open the log, often because of a permissions or path problem.

Enable Diagnostic Mode for Verbose Output

Diagnostic mode makes Centova Cast log every internal step. To enable it, edit /usr/local/centovacast/etc/cc-control.conf and set debug=1. Restart the control panel with service centovacast restart. The next attempt to start your stream will produce a much richer log, which is invaluable for stubborn errors.

Turn diagnostic mode off after you fix the problem. Verbose logs grow fast and can fill your disk.

Centova Cast Server Startup Failed Errors

“Server could not be started: Server startup failed” is the single most common Centova Cast error message I see. It is a catch-all that means the SHOUTcast or IceCast binary underneath never came up. Here is how to narrow it down.

Check for Port or Address Conflicts

The most frequent cause is the streaming port being taken. Run netstat -tulnp | grep [portnumber] as root, replacing [portnumber] with your configured base port (usually 8000 or higher). If another process owns it, either free the port or change your stream’s base port in the Configuration tab.

If you see “Address already in use” inside the log, that confirms a port conflict. We have seen two unrelated streams on the same server try to bind the same port because an admin duplicated settings. Always double-check the port number on every account.

Verify IP Binding Settings

If your server has multiple IP addresses and your stream is bound to one of them, Centova Cast must use the right one. In the control panel, open Settings -> Server Configuration and confirm the “IP address” field matches an interface that exists. Run ifconfig or ip addr to list them. A common mistake is to bind to 127.0.0.1 when listeners need a public IP.

Check the Streamer Binary and 32-bit Libraries

SHOUTcast DNAS in particular is a 32-bit binary. On a 64-bit server you need the 32-bit runtime libraries even though the OS is 64-bit. On Debian and Ubuntu, install them with:

sudo apt-get install ia32-libs libc6-i386 lib32stdc++6

On CentOS and RHEL, run:

sudo yum install glibc.i686 libstdc++.i686

If those packages are missing, SHOUTcast DNAS will fail with a No such file or directory error even though the binary is right there. That message is misleading – it really means “loader cannot find a required 32-bit dependency.”

Look for Permissions and Path Errors

Centova Cast runs each stream under a dedicated user account. If the home directory, log directory, or config file is owned by root, the stream will refuse to start. Fix it with:

chown -R [account]:[account] /usr/local/centovacast/var/vhosts/[account]

The exact account name is shown in the URL bar when you log into the Centova Cast control panel for that stream.

AutoDJ and ices Common Errors

AutoDJ is the part of Centova Cast that plays a playlist when no live DJ is connected. It is powered by ices, and ices is where most AutoDJ errors live. The forum threads we have read confirm this – “AutoDJ not working” is the headline of dozens of posts.

Deactivate AutoDJ to Reset It

The first move is always to deactivate AutoDJ cleanly. Click “Deactivate AutoDJ” in the left sidebar of the AutoDJ tab. Wait for confirmation. Then click “Activate AutoDJ” again. This cycle flushes the ices process and reloads the playlist. Many intermittent AutoDJ errors vanish after this simple reset.

Reading the ices Log Line by Line

Open ices.log and look for these common messages:

• “MySQL server has gone away” – the database connection dropped mid-play. Centova Cast 3.3.2r4334 in particular had a bug with Liquidsoap v2.4.2 that triggered this. Upgrade Centova Cast or shorten your playlist length.

• “double free or corruption” and “glibc detected” – a memory error inside ices itself. Usually caused by a corrupted MP3 in the playlist. Remove the last file ices played before the crash and try again.

• “Failed to open playlist” – the playlist file is missing or unreadable. Regenerate the playlist from the AutoDJ tab.

• “No such file or directory” on intro or fallback – the intro file or fallback file path is wrong. Upload fresh files through the AutoDJ tab.

Fix the Double Free or Corruption Error

This is the most dreaded AutoDJ error. It almost always means one of your MP3 files is malformed. Run a quick scan to find the culprit:

find /usr/local/centovacast/var/vhosts/[account]/media -name "*.mp3" -exec mp3val {} ;

mp3val flags broken frames. Move any file it complains about out of the media folder. Re-activate AutoDJ. I have seen this single trick fix 70% of repeat ices crashes on shared hosting.

Run ices Manually for Maximum Detail

If the AutoDJ tab keeps dying and you cannot see why, run ices by hand over SSH:

su - [account] -c "/usr/local/centovacast/bin/ices -c /usr/local/centovacast/etc/[account]/source.conf"

This prints every event to your terminal in real time. You will see the exact file or SQL query that triggers the crash. It is the fastest way to pinpoint stubborn issues.

Centova Cast Connection and Authentication Errors

Errors that appear when you try to log in, connect a source, or load the stream URL usually fall into this group.

“Streaming Server Reports That Your Station Is Unavailable”

This message in the management console means the underlying SHOUTcast or IceCast server is not responding on the configured port. Run netstat -tulnp | grep [portnumber] again. If nothing is listening, the streamer binary crashed during startup and never recovered. Check the server error log – the root cause is usually upstream in the startup process.

Source Disconnected or Invalid Login

Live DJs connect with an encoder like BUTT, Mixxx, or SAM Broadcaster. If the connection drops immediately with “invalid login” or “authentication failed,” the password in Centova Cast does not match the encoder password. Reset the source password in the Configuration tab and re-enter it in your encoder. Passwords are case-sensitive – I have spent hours debugging what was simply a capital letter mismatch.

If the encoder connects then disconnects within seconds, the mount point is wrong. SHOUTcast uses /stream by default, while IceCast uses /stream or /listen.mp3. Match the encoder’s mount point field to what Centova Cast shows in the Quick Links section.

Stream Unavailable to Listeners

When the control panel says the stream is up but listeners get silence, suspect firewall rules. Centova Cast does not manage iptables for you. Open the listener port and any range above it (typically a 10-port range starting at your base port) in your firewall. On a typical Centova Cast install, ports 8000-8010 must be reachable from the public internet.

Port Conflict and Network Errors

Port issues deserve their own section because they cause so many unrelated symptoms.

Find What Is Using the Port

Run this on the server as root:

netstat -tulnp | grep :8000

The output shows the PID and program name. If another SHOUTcast, IceCast, Icecast2, or sc_serv is on the same port, stop it or change one of them.

Listener Limit Reached

If listeners connect fine but the count plateaus and new connections are refused, you have hit your listener limit. Open the account in Centova Cast and check the “Maximum listeners” setting. On shared hosting this is often capped by the hosting provider – contact support to raise it.

DNS or Hostname Errors

Some error messages like “Hostname not found” or “Unable to resolve” point to a DNS problem, not a Centova Cast problem. Confirm /etc/resolv.conf contains working nameservers (8.8.8.8 or your provider’s DNS). Restart Centova Cast after changing DNS so it picks up the new settings.

Quick Reference: Centova Cast Error Codes

Use this table to jump straight to the section that matches your error message.

• Server could not be started: Server startup failed -> Port conflict, wrong IP, or missing 32-bit libs. See Server Startup Failed Errors.

• MySQL server has gone away -> AutoDJ database dropped. Restart AutoDJ, check max_allowed_packet.

• double free or corruption / glibc detected -> Corrupted MP3 in playlist. Run mp3val on your media folder.

• No such file or directory on stream binary -> Missing 32-bit runtime libraries. Install ia32-libs.

• Address already in use -> Another process owns the port. Free it or change the base port.

• Authentication failed / Invalid login -> Encoder password mismatch. Reset in Configuration tab.

• Stream is not available -> Firewall blocking listener ports 8000-8010.

• Control panel frozen -> Log rotation stalled. Restart centovacast service.

• Source disconnected -> Mount point or password mismatch in encoder.

• License error -> Centova Cast license expired or invalid IP. Contact your license provider.

Frequently Asked Questions

Final Thoughts on Centova Cast Troubleshooting

Most Centova Cast common errors fall into a handful of buckets: ports, permissions, passwords, and bad MP3 files. Work the problem in that order and you will resolve the vast majority of cases within a few minutes. When you have checked ports, libraries, ownership, and media files and the stream still will not start, capture the full ices log and server error log with timestamps and send them to your hosting provider. A precise log file turns a multi-day ticket into a one-hour fix.

Keep your Centova Cast install current. The forum reports that older builds such as 3.3.2r4334 carried bugs that newer releases patched. If you have not updated in over a year, plan a maintenance window and apply the upgrade. Your future self, and your listeners, will thank you.