sameersbn / sameersbn/docker-gitlab
Gitlab stops working when using Logstash-Forwarder
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Hello there. Apparently there is an issue with Docker Gitlab and Docker Logstash-Forwarder. Logstash-Forwarder is a tool to read out Logs and send them to a Logstash-Server. Now, my problem consists out of the following:
I haev mounted the log-Directory of Gitlab to a directory on my Host-System. Now I have pointed Logstash-Forwarder to those logs, and upon starting of the forwarder, gitlab stops working (I can't access it onto it's web interface anymore, as well as it stops writing logs). Apparently there is an issue with GitLab permanently using the Logs and Logstash-Forwarder somehow forcing itself upon the logs, taking away the possibility for GitLab to read the logs.
Is there any way to bypass this?
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 by reproducing the failure with GitLab's mounted log directory and Logstash-Forwarder pointed at those logs. Investigate why GitLab's web interface and log writing stop, then verify that GitLab remains accessible and continues writing logs while the logs are forwarded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, gitlab
- Domain
- devops, observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100