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

Workers failing #390

Open
borisbaldassari opened this issue Sep 30, 2019 · 3 comments
Open

Workers failing #390

borisbaldassari opened this issue Sep 30, 2019 · 3 comments

Comments

@borisbaldassari
Copy link
Member

Two of the 4 slaves have stopped last night. The UI doesn't show any worker or tasks or projects.

Firefox_Screenshot_2019-09-30T09-51-44 567Z
Firefox_Screenshot_2019-09-30T09-52-05 088Z

Log of the 2 stopped docker containers (oss-app slaves):

@borisbaldassari
Copy link
Member Author

The ci4 host (and portainer instance) can be freely investigated if needed. As a reminder, all URLs are provided in the main page:

http://ci4.castalia.camp

@tdegueul
Copy link

The logs show that both JVMs have crashed due to SIGBUS (0x7), which is most likely a consequence of running out of disk space. Indeed, here's the situation in the container:

root@4b82ecdd65a0:/ossmeter# df -h
Filesystem                                                                                          Size  Used Avail Use% Mounted on
/dev/mapper/docker-9:3-1075930394-48078256fd82f44cc110c99d207c086804c397b71b0a11cafeb00dc1bd95aca3   10G   10G  904K 100% /
[...]

I am not familiar with Docker's volume management. Maybe there is a way to allocate more space to the metric-plaform containers (master and slave)?

@MarcioMateus
Copy link
Contributor

Humm, it really seems to be the case that the Docker container ran out of storage space. I will look into it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants