Troubleshooting

If your Airtime server is not working as expected, individual components of the system can be stopped, started or restarted using the service command:

$ sudo service airtime-playout        start|stop|restart|status
$ sudo service airtime-media-monitor  start|stop|restart|status
$ sudo service airtime-show-recorder  start|stop|restart|status

On Debian squeeze, use the command invoke-rc.d in place of service in the commands above.

The status option runs the airtime-check-system script to confirm that all of Airtime's dependencies are installed and running correctly.

Airtime stores log files under the directory path /var/log/airtime/ which can be useful for diagnosing the cause of any problems. The less command, when used with the +G option, enables reading the Airtime playout log file from the end:

$ less +G /var/log/airtime/pypo/pypo.log

If you want to watch a log file as it continues, such as the Liquidsoap log, you can use the tail command with the -f option:

$ sudo tail -f /var/log/airtime/pypo-liquidsoap/ls_script.log

You can interrupt tail by pressing Ctrl-C on your keyboard. The Airtime media monitor has its own log, in the file:

/var/log/airtime/media-monitor/media-monitor.log

and the Airtime show recorder has a log in the file: 

/var/log/airtime/show-recorder/show-recorder.log

Copies of these log files may be requested by Sourcefabric engineers while they are providing technical support for your Airtime deployment.