This article outlines useful information to review when having issues with airControl. In some cases this information might be requested from developers to track issues further.
Table of Contents
When having issues such as connecting or starting airControl server or client, please include the information below when posting in the community to help document the issue. This will allow us to diagnose and fix any issues faster. Much of this is information is included in the diagnostics page (see details in the following section).
- airControl version
- Server OS
- Client OS
- Java version (server and client side)
- Is this a fresh install or upgrade from older airControl version? From which version was it upgraded?
- Error message or screen-shot if available
For problems related to specific devices where: adding, reconnecting, monitoring or configuring devices is failing, please include the following information:
- Device model
- Device firmware version
- Topology description:
- Server behind router / firewall
- Firewall / port forward on device
- Routed network
- Attach files:
- Device configuration file
- Device properties screen shot (right-click on the device in airControl, click on More > Properties)
- Run commands when connected to device using ssh and attach output:
- mca-ctrl -t status
The diagnostics page can be retrieved by entering http://<ipofserver>:9081/diag into your web browser. Accessing this page is not only a good way to test communication with the server; it also shows useful data for developers such as version information, server uptime, memory usage, and Java thread dumps. Please save this information to a text file and include it when reporting a problem.
It is helpful to review automation rules when troubleshooting some issues. When a large number of devices is involved, many automation rules could have an impact on performance. To obtain a list of automation rules please take screenshots to document current automation rules found under Control Panel > Automation Rules.
Please send us complete logs (not excerpts) for the period the issue happened. If you do not want to post your data on forums, please send them to Ubiquiti staff at email@example.com.
Windows Client: C:\Users\<username>\.AirControl2\logs
Windows Server: C:\Program Files\Ubiquiti Networks\airControl2\logs
Linux Server/Client: /var/log/aircontrol/
Mac OS X: /Users/<username>/.AirControl2/logs/
Database Backup File
In some cases it is easier to replicate issues using and/or reviewing the database from airControl. Statistics do not need to be included for review. The database can be backed up using the the Client by going to Control Panel > Database Backup and clicking on Backup Now. More details can be found in the article airControl - How to Back-up and Restore a Database Manually.