This should not be performed on runners with the Shell executor, because it redefines the systemd service and runs all jobs as root. This poses security risks and changes to file ownership that makes it difficult to revert to a non privileged account. ... Debug logging can be enabled in the global section of the config.toml by setting the log_level setting to debug.

GitLab Runner is the open source project that is used to run your CI/CD jobs and send the results back to GitLab

Manually kill the process with kill -SIGQUIT <pid>. You have to find the pid of the main gitlab-runner process. You can find this by looking at logs, as it’s displayed on startup:

A logger emits a log message only if its log level is equal to or above the minimum log level.

And the question that will help me to investigate the answer for question above is: How to enable debug logs for gitlab runner services(especially for docker:dind)? EDITED. I figured out the solution. The answer is in my error code: 137. This Pod was killed by OOM. I just increased memory request\limit and it works fine now. log_level = "debug" in ~/.gitlab-runner/config.toml works fine.

July 8, 2021 - This is the error I’m getting intermittently. About 70% of the time. Retry the job (maybe a few times) and it works. The runner is in our Kube/openshift cluster. It is accessing the https://gitlab.com server. There is n…

April 17, 2024 - GitLab Runner is the open source project that is used to run your CI/CD jobs and send the results back to GitLab

May 24, 2023 - When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences, or your device, and is mostly used to make the site work as you expect. The information does not usually identify you directly, ...

July 29, 2020 - In case you want to set GitLab Runner’s log level to DEBUG, you can edit its configuration file (usually /etc/gitlab-runner/config.toml), and add log_level = "debug" to the global section. Don’t forget to restart the Runner, e.g. sudo gitlab-runner restart.

No log level, so messages cannot be filtered or routed.

June 4, 2026 - I’ve been writing a lot lately about Continuous Integration and using GitLab Runner. It’s really nice when it works and it works 90% of the time, but issues do pop up occasionally. They can be a pain to troubleshoot. I previously wrote about how to run GitLabRunner as a regular user. You should all do that. If you are not, go do that now, you’ll thank me later. But there is more to troubleshooting than just that, so I thought I’d add some more tips here. The first tip is to always turn on build logs and unit test reports.

January 7, 2021 - Public repo for testing purposes

May 30, 2022 - HI again, I have a rather new installation of latest gitlab CE. The installation seems to log in debug mode, and I can’t turn it off. I have changed the configuration to log “INFO”: registry['log_level'] = "info") gitl…