• Introduction
• What is Airtime? (Russian)
• Rights and royalties (Russian)
• Using Airtime
• Getting started
• Manage users
• Preferences
• Manage media folders
• Stream settings
• Support settings
• Status
• Now playing
• Add media
• Playlist builder
• Calendar
• Listen
• Help
• Installation
• Preparing the server
• Easy install
• Manual installation
• Automated installation
• Configuration
• Setting the server time
• Administration
• Using the airtime-import script
• The airtime-user command
• 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

Troubleshooting

If your Airtime server is not working as expected, individual components of the system can be stopped, started or restarted in the server console 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. 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.