new version of JATOS (3.7.2) doesn't transfer data

Uros

Hey everyone,

In the middle of February I've set up new JATOS server on a DigitalOcean droplet (8 GB Memory / 4 AMD vCPUs / 160 GB Disk / FRA1). I've followed the instructions from JatosDocumentation while setting up the server and everything seemed fine until I tried to test a few studies that I had imported.

The tasks are running fine until the end when the message "Transferring data, please wait a few moments" appears. The message stays there endlessly until I close the tab. When I check the results section I can see that a worker/participant had been counted but no data has been transferred, and the data size is 0b. The same thing happens when I close the task in the middle, the message "Aborting experiment, please wait a few moments" stays forever and no data has been saved after I close that tab.

This doesn't seem to be related to the memory size of the task, (as I was suspicious at the first hand) since it also happened with the small-sized OSWEB files which had a small number of variables. On the other hand, those tasks run pretty fine and the data is being saved if I import those studies on the other JATOS server, which is running on an older version (3.6.1).

So, I'm not sure should I edit some settings of my DigitalOcean docker, or JATOS itself in order to fix this issue with the data saving on the new server. I would appreciate any help, thank you very much in advance!

Kindest regards,

Uroš

kri

Hi Uroš,

If you try your study on cortex.jatos.org, does it work there, does it send result data? I try to figure out if your issue is some problem in JATOS or in your setup.

Best,

Kristian

Uros

Hey Kristian,

thank you for the fast response!

I've tried out my study on cortex.jatos.org and everything is ok with the data. So, I believe there was some mistake I've made while creating the droplet.

Something comes to my mind, the script I've added in the User data while creating the droplet was:

#!/bin/bash

# Run JATOS as docker container

docker run -d --restart=always -p 80:9000 jatos/jatos:latest

Now, I've noticed that the script on the screenshot at the JatosDocumentation is different:

#!/bin/bash

# Run JATOS as docker container

docker pull jatos/jatos:latest

docker run-d --restart=always -p 80:9000 jatos:/jatos:latest

Do you think that this could be the problem? Can I edit the user data after I've already created a droplet?

Thank you so much in advance,

Uroš

Uros

Hey Kristian,

just to let you know that I've updated my JATOS from 3.7.2 to 3.7.3 (I've just noticed that newest version) and the problem described above has been solved! :)

But, now I'm dealing with the same issue as described here, the results can't be exported.

I'll try the instructions you've given on that discussion.

Thanks for the help!

Uroš

kri

Hi Uros,

Great to here that an upgrade to 3.7.3 solved your issue. The underlying problem then was the bundling of jatos.js with webpack.

About the new issue: I'm on it. It's about streamsaver.js.

Best

Kristian