Skip to content
This repository has been archived by the owner on Dec 24, 2019. It is now read-only.

Additional workers won't show up #95

Open
borisbaldassari opened this issue Aug 29, 2019 · 8 comments
Open

Additional workers won't show up #95

borisbaldassari opened this issue Aug 29, 2019 · 8 comments
Labels
bug Something isn't working

Comments

@borisbaldassari
Copy link
Member

As mentioned in the documentation and docker-compose file, I've setup multiple oss-slaves containers to parallelize computations. The docker-compose file is attached to this issue.

In the Admin / Workers page only 3 workers are displayed, one of them useless (worker1). Only two of them seem to be working (w1 and w5). Note that I don't know if the others (w2 > w4) are actually active or not, but they are not displayed.

@borisbaldassari
Copy link
Member Author

borisbaldassari commented Aug 29, 2019

Here is the list of workers as seen in the web ui:
Capture du 2019-08-29 17-50-16

And here is the docker-compose file used:
docker-compose-build.txt

@borisbaldassari borisbaldassari added the bug Something isn't working label Aug 29, 2019
@borisbaldassari
Copy link
Member Author

After a down/up the workers all come back in the UI.. If I don't get it again in the upcoming days i'll close the issue as not reproducible..

@borisbaldassari
Copy link
Member Author

As mentioned, still an issue.

@borisbaldassari
Copy link
Member Author

borisbaldassari commented Sep 26, 2019

docker stop / start did the trick.
Almost all projects are now in error. I'll update the instance and restart everything from scratch to get the latest fixes.

@MarcioMateus
Copy link
Contributor

Hi @borisbaldassari . Can you connect to the oss-db and check the number of workers in the collection workers on the scava-analysis database?

On that collection you can check the number workers, their heartbeat and if they are executing any task.

@borisbaldassari
Copy link
Member Author

Hi @MarcioMateus
Thank you for your interest. Do you have the required commands to do that at reach? I'm not a mongo guy, that would help. Otherwise I'm going to google that before re-initialising the instance..

@MarcioMateus
Copy link
Contributor

No problem @borisbaldassari .

I use the client Robo 3T to connect to the DB. Just create a connection to the running the docker deployment and to the exposed by oss-db and you should see the databases on the mongodb instance.

@borisbaldassari
Copy link
Member Author

borisbaldassari commented Sep 26, 2019

thanks @MarcioMateus . Here is the screenshot.

Capture du 2019-09-26 17-12-32

Note however that I've already done a stop/start before you posted your comment.. If that happens again I'll do the screenshot before anything else. :-)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants