JATOS failed to update the GUI automatically?
Try reloading the browser.
Downloading a study / exporting a study fails (e.g. in Safari browsers)
JATOS fails to start?
(Or, if you are running Windows, do you get the message ‘JATOS is already running. Press any key to continue’…)
This will happen if your computer crashed before you had the chance to close JATOS.
This is what you might see on a Mac Terminal if JATOS doesn’t start:
Close any open command prompt windows. Then look into your JATOS folder, and check if there’s a file called ‘RUNNING_PID’. Delete this file and try to start JATOS again.
Here is how it should look if JATOS started successfully:
Read log file in the browser
In a perfect world, JATOS always works smoothly and, when it doesn’t, it describes the problem in an error message. Unfortunately we aren’t in a perfect world: every now and then something will go wrong and you might not get any clear error messages, or no message at all. In these (rare) cases, you can look into JATOS’ log file to try to find what the problem might be.
The standard way to read the log file is directly on the server. You’ll find your complete log file in
jatos_directory/logs/application.log. Because JATOS is designed to avoid the command line interface, we offer a way to view your log file directly in your browser.
Just open the URL
http://your-jatos-server/jatos/admin/log. For privacy and security reasons, you must be logged in as Admin. For example, if you’re running JATOS locally with the standard settings, you’d have to go to
http://localhost:9000/jatos/admin/log to view your log file.
By default, JATOS will display the last 1000 lines of the application.log file. If you want to see more than the last 1000 lines, add the query parameter
limit. E.g. to display the last 10000 lines on a local JATOS instance, you’d have to go to http://localhost:9000/jatos/admin/log?limit=100000.
A file (library, image, …) included in the HTML fails to load?
There is a common mistake Windows users make that might prevent files in the HTML from loading: Any URL or file path in a HTML file should only use ‘/’ as a file path separator - even on Windows systems. So it should always be e.g.
<script src="/study_assets/mystudy/jsPsych-5.0.3/jspsych.js"></script> and not