• Introduction
• What is Airtime?
• Rights and royalties
• Using Airtime
• Getting started
• Manage users
• Preferences
• Manage media folders
• Stream settings
• Support settings
• Status
• Now playing
• Add media
• Playlist builder
• Calendar
• Listen
• Recording
• Help
• Installation
• Preparing the server
• Easy setup
• Manual installation
• Automated installation
• Configuration
• Setting the server time
• Administration
• Using the airtime-import script
• The airtime-log command
• Backing up the server
• Upgrading
• Troubleshooting
• Advanced configuration
• Icecast and SHOUTcast
• Stream player for your website
• Using Monit
• Automated file import
• Exporting the schedule
• Interface customization
• Integration with Mixxx
• Stream handover
• Appendix
• Expert install
• HD Audio Models
• About this manual

[view all chapters]

Troubleshooting

If your Airtime server is not working as expected, individual components of the system can be stopped, started, restarted or checked in the server console using the invoke-rc.d command:

sudo invoke-rc.d airtime-playout        start|stop|restart|status
sudo invoke-rc.d airtime-media-monitor  start|stop|restart|status
sudo invoke-rc.d apache2                start|stop|restart|status
sudo invoke-rc.d rabbitmq-server        start|stop|restart|status

For example, to restart the Airtime playout engine, you could enter the command:

sudo invoke-rc.d airtime-playout restart

The server should respond:

Restarting Airtime Playout: Done.

The status option for airtime-playout and airtime-media-monitor 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. Copies of these log files may be requested by Sourcefabric engineers while they are providing technical support for your Airtime deployment. See the chapter The airtime-log command for more details.