A number of people run centovacast to control icecast servers, some of those run the icecast KH server with it and have experienced odd messages which do not occur with the official 2.3.x set.

While the centovacast people have refused to look into their issue, it is looking like the issue is down to possible messages that my version is reporting when parsing the xml provided. The server works but the messages on standard error are warnings of xml issues eg unrecognized tag like <burst-on-connect>, which is something 2.3.2 does not do.

This can lead to centovacast reporting messages unrelated to icecast like "mysql went away", may be the "error on line 0"

While they should fix centovacast to either background icecast or treat standard error properly, the easiest workaround is to have a simple script to bypass any startup messages eg

in /usr/local/bin/icecast.centova

#!/bin/sh
exec /usr/local/bin/icecast $* 2> /dev/null

then edit the server software icecast entry in centova to call the above script eg /usr/local/bin/icecast.centova

This advice is in addition to increasing the imposed queue size value of 100k, the icecast default is 512k