Troubleshooting

If you encounter issues, try checking the [log files](Log Files), and connecting to the affected node(s) via VNC to see if there's anything suspicious. Check the environments for details of where to find these. If you need more help you can contact us (see the footer for support channels).

Common Issues

Dashboard is not responding

It may be that the dashboard is not responding. This can happen if a large number of builds are getting processed, e.g. during a Firefox release. In those cases wait a couple of minutes for the dashboard to be loaded. If there is still no response it could be that the Jenkins process has been crashed. You can use SSH to log into the appropriate Jenkins machine (see environment). Use screen -x (see screen) to reconnect to the existent session. Select the 'jenkins' window, and check for the Jenkins process. If it has been crashed, you can start Jenkins again with ./start.sh. The dashboard should be available when Jenkin's startup has been completed.

Please note that you should disconnect from screen first before closing the SSH session!

Jenkins doesn't start

If Jenkins fails to start it may be due to the default memory requirements. If your machine has less than 2GB of available memory you may need to reduce the values for Xms and Xmx in start.py.

Failure when downloading Firefox

If the is a failure when downloading a Firefox build it may be because the binary is not yet available at the time the build is triggered. If so, a rebuild is usually enough to get it running again. If the build still cannot be found please observe the console output, and check the listed download location manually. If the build exists, you might face a networking problem. As best you get in contact with us.

OS or application popups

These can sometimes disrupt the tests. If you connect to a slave node and see any dialogs present please file an infrastructure bug with a screenshot. After this, you can try dismissing the popup and running the tests again.