First I tried without build, but same problem. --build just means that it will re-download all layers instead of using the ones already cached.

The only change I made in the .yml file was:
` ports:

• "8080:80" to ports:
• "8082:80" `
  I already had something running on 8080, but since it's the trains-apiserver and not the webserver, this shouldn't be an issue.

Is there anyway how I can figure out in the webinterface what version of Trains is actually running?

Ok it's that the user group also has to be root. I ran the following:
sudo chmod 775 -R /opt/trains/ sudo chown -R root:root /opt/trainsand it works.

It seems that it has to be 775 with both user and group as root. E.g. 771 does not work, because than the docker command has to be used with sudo (if I want to use my default sudo-user account)

That's useful to know! But actually in this case I want to just test if the code works (run 2 epochs and see if it works). I don't want this to be logged, so I don't Task.init in those cases.
I don't want the code to crash on Trains in those cases.

I see that Task.current_task() returns None if no task is running, so I can use that with an if statement 🙂

Thank you

As there are quite some hparams, which also change depending on the experiment, I was hoping there was some automatic way of doing it?

For example that it will try to find all dict entries that match "yet_another_property_name": "some value" , and ignore those that don't.
The value has to be converted to a string btw?

Port 8008 cannot be changed apparently:
https://allegroai-trains.slack.com/archives/CTK20V944/p1592478619463200?thread_ts=1592476990.463100&cid=CTK20V944

I see that Trains has been removed 2 days ago: https://github.com/PyTorchLightning/pytorch-lightning/commit/41f5df18a4b96ce753263fadd9c27f1d30e5d7a2

and instead has been moved to Bolts: https://github.com/PyTorchLightning/pytorch-lightning-bolts

However, I cannot find a reason why only Trains has been moved?

Aah, I couldn't find it under PLOTS, but indeed it's there under DEBUG SAMPLES.

Exactly, so that remapping of port 8080 should not be the reason for this issue

Would have been nice if they would have reached out to you guys/gals before removing Trains 😅

/opt/trains/ :

` $ ls -al
total 120
drwxrwsrwx 7 root miniconda 4096 Nov 2 18:15 .
drwxr-xr-x 15 root root 4096 Oct 5 15:12 ..
drwxrwxrwx 38 root miniconda 4096 Nov 2 18:15 agent
drwxrwxrwx 2 root miniconda 4096 Jun 19 14:43 config
drwxrwxrwx 8 root miniconda 4096 Nov 2 18:11 data
-rwxrwxrwx 1 root miniconda 4383 Jun 19 14:46 docker-compose_0.15.0.yml
-rwxrwxrwx 1 root miniconda 4375 Jun 26 15:06 docker-compose_0.15.1.yml
-rwxrwxrwx 1 root miniconda 4324 Nov 2 18:...

Ok, thanks for the info 🙂

AgitatedDove14 There is only a events.out.tfevents.1604567610.system.30991.0 file.
If I open this with a text editor, most is unreadable, but I do find a the letters "PNG" close to the name of the confusion matrix. So it looks like the image is encoded inside the TB log file?

AppetizingMouse58 If I:
sudo chmod 771 -R /opt/trains/(taking all permission away from other except execution)
The file permission error comes back, even though everything is under the root user.

So if I want it under plots, I would need to call e.g. report_confusion_matrix right?

Thank you 😉

trains ( 0.15.1-367 ) appears to be the version, same as you. Thank you. Appears Trains is up to date.

Apparently there should be 6 of them:

After a while I get the message:

New version available
Click the reload button below to reload the web page

I click the "RELOAD" button and the "newer version" message disappear. However, some plots still don't show up (fixed in 0.15.1). If I refresh the TRAINS webinterface, the "newer version" message appears again.

Ah I see, it's based on a naming scheme, thanks. Sorry I forgot to link the tutorial I was looking at: https://allegro.ai/docs/examples/frameworks/pytorch/pytorch_tensorboard/

Is it possible it's not just about the root user, but also the root group?

It's my colleague's experiment (with scikit-learn), so I'm not sure about the details.

TimelyPenguin76 The colleague is actually a her, but she replied that how it's looking now is correct? We're actually both already passed our work time (weekend :D), so we'll take a look at it after the weekend. If there is still something wrong, I'll get back to you. Thanks for offering help though :)

Ah my bad, it seems I had to run
docker-compose -f /opt/trains/docker-compose.yml pullonce. I quickly tried trains like half a year ago, so maybe it was using the old images? However, I thought --build would take care of that.

Now it's working 🙂

The relevant commit that deleted the trains logger from Bolts:
https://github.com/PyTorchLightning/pytorch-lightning-bolts/commit/91393eaa2751dc58c26cec6581aba19d63fa42f8

What's the abc issue ? Something Lightning team is responsible for?

It seems to be related to trains-apiserver , based on the log inside the Docker compose:

` trains-apiserver | [2020-11-10 04:40:14,133] [8] [ERROR] [trains.service_repo] Returned 500 for queues.get_next_task in 20ms, msg=General data error: err=('1 document(s) failed to index.', [{'index': {'_index': 'queue_metrics_d1bd92a3b039400cbafc60a7a5b1e52b_2020-11', '_type': '_doc', '_id': 'rkh0sHUBwyiZSyeZUAov', 'status': 403, 'error': {'type': 'cluster_block_exception', 'reason': 'index [queu...

Even when I do a "clean install" (renamed the /opt/trains ) folder and followed the instructions to setup TRAINS, the error appears.

SuccessfulKoala55 Thank you. I stared myself dead at trains-apiserver , but by coincidence I found this message:
` trains-elastic | {"type": "server", "timestamp": "2020-11-10T06:11:08,956Z", "level": "WARN", "component": "o.e.c.r.a.DiskThresholdMonitor", "cluster.name": "trains", "node.name": "trains", "message": "flood stage disk watermark [95%] exceeded on [QyZ2i1mxTG6yR7uhVWjV9Q][trains][/usr/share/elasticsearch/data/nodes/0] free: 43.3gb[4.7%], all indices on this node will be ...