I installed airtime in a virtual machine to do some testing and after installing it with no errors, I noticed I wasn't getting any audio when I tried to 'tune in' or just play some files in the playlist builder. I am not getting audio from the demo site either, but I am getting audio when I just play the files in the playlist builder.
Can anyone point towards the right direction? I can't seem to troubleshoot this problem, especially since it's confusing that the demo site isn't working properly either.
Here's my airtime-check-system output (everything seems fine):
When I checked the stream settings I saw an error I had seen in the logs but wasn't reported as an error in the logs.
2012/04/24 10:26:03 [lang:3] /usr/lib/airtime/pypo/bin/liquidsoap_scripts/notify.sh --error='could not write data to host: Connection refused in write()' --stream-id=1 --time=1335282315.22 2012/04/24 10:26:03 [airtime_128:3] Will try again in 5.00 sec. 2012/04/24 10:26:09 [airtime_128:3] Connecting mount airtime_128 for source@127.0.0.1... 2012/04/24 10:26:09 [airtime_128:2] Connection failed: could not write data to host: Connection refused in write()
Anyway, my stream settings are:
Stream type: OGG/VORBIS Bit rate: 128Kbits/s Server: 127.0.0.1 Port: 8000 Service Type: lcecast
Mount type: airtime_128
EDIT: Also, I'm still clueless as to why the demo site isn't working properly for me (and other people I've asked to test it).
The credentials under 'Additional Options' should be matched to Icecast username and password settings. As for the demo site, we are investigating the cause of the issue you mentioned.
You problem is not the same as the one on demo site. We can see that the hose is refusing the connection as the log file shows:
2012/04/24 10:26:03 [lang:3] /usr/lib/airtime/pypo/bin/liquidsoap_scripts/notify.sh --error='could not write data to host: Connection refused in write()' --stream-id=1 --time=1335282315.22
So I'm suspecting you have something configured wrong on Icecast side, or on airtime relating to connecting to Icecast.
I'm slightly embarrassed. The ENABLE line in /etc/default/icecast2 was set to false. Needless to say, the service never started. It's working properly now.