sameersbn / sameersbn/docker-gitlab
Lots of "INFO reaped unknown pid " in log
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
I just upgraded my docker-gitlab to version 12.5.2. And I found a lot of INFO reaped unknown pid <pid-number> messages in the log of gitlab.
2019-12-25 03:18:24,637 INFO reaped unknown pid 44831
2019-12-25 03:18:27,127 INFO reaped unknown pid 44863
2019-12-25 03:18:29,721 INFO reaped unknown pid 44876
2019-12-25 03:18:30,251 INFO reaped unknown pid 44889
2019-12-25 03:18:32,941 INFO reaped unknown pid 44902
...
The messages are found by running docker logs -f <docker-gitlab-container-id>.
Does anyone know if this is a normal phenomenon or not?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with docker-gitlab version 12.5.2 and the output from docker logs -f <docker-gitlab-container-id>. Investigate what produces the repeated INFO reaped unknown pid messages and whether they indicate a problem. Done means establishing whether this behavior is normal and documenting the explanation or identifying a specific fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, gitlab, shell
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100