I've got Airtime 2.2 on Debian Squeeze running, installation went smoothly. But I cannot stream to a Shoutcast server. The status panel suggest that airtime-playout is OK, but it looks like that it cannot connect to the given Shoutcast server. It permanently says: Getting information from the server (in orange box) and it does not become green.
I've tried to manually connect with a client software (Nicecast on OSX) and it works just fine. So I've tried to connect with the airtime-test-stream utility
Just realized there is the same problem with Icecast :(
Looked at the logs:
2012/11/04 17:22:24 [airtime_128:3] Connecting mount airtime_128 for source@127.0.0.1... 2012/11/04 17:22:24 [airtime_128:2] Connection failed: bad answer: scanf: bad input at char number 0: looking for 'H', found 'i' 2012/11/04 17:22:24 [lang:3] /usr/lib/airtime/pypo/bin/liquidsoap_scripts/notify.sh --error='bad answer: scanf: bad input at char number 0: looking for 'H', found 'i'' --stream-id=1 --time=1352027880.83 & 2012/11/04 17:22:24 [airtime_128:3] Will try again in 5.00 sec.
It is empty actually, but it seems that Liquidsoap is not using an updated configuration. It is still using some old Icecast configuration?!
It should not even matter if the mountpoint is empty if you are using ShoutCast, because the Liquidsoap script should ignore it: In /usr/lib/airtime/pypo/bin/liquidsoap_scripts/ls_script.liq
if s1_output == 'shoutcast' then s1_namespace := "shoutcast_stream_1" else s1_namespace := s1_mount end
Outputting to icecast streaming server. You should be able to hear a monotonous tone on 'http://localhost:8000/livestream'. Press ctrl-c to quit. 2012/11/04 19:32:01 [livestream:2] Connection failed: bad answer: scanf: bad input at char number 0: looking for 'H', found 'i' 2012/11/04 19:32:05 [livestream:2] Connection failed: bad answer: scanf: bad input at char number 0: looking for 'H', found 'i'
So how can I make sure that Airtime is using the configuration I set in System > Streams?
After spending a day on this issue I could resolve it :)
The problem was that the airtime-liquidsoap failed to restart, but there were no errors in the logs nor any other indication (not even in the system status in the web interface).
In /etc/init.d/airtime-liquidsoap I removed --nicelevel -15 from the parameters and restarted the service with $ sudo invoke-rc.d airtime-liquidsoap restart
The service restarted, the settings updated and liquidsoap could connect to Shoutcast!