Some Frequently Asked Questions about GitLab Runner.
## 1. Where are logs stored when run as a service?
## What does `coordinator` mean?
The `coordinator` is the GitLab installation from which a job is requested.
In other words, runners are isolated (virtual) machines that pick up jobs
requested by their `coordinator`.
## Where are logs stored when run as a service?
+ If the GitLab Runner is run as service on Linux/OSX the daemon logs to syslog.
+ If the GitLab Runner is run as service on Windows it logs to System's Event Log.
## 2. Run in `--debug` mode
## Run in `--debug` mode
Is it possible to run GitLab Runner in debug/verbose mode. From a terminal, do:
...
...
@@ -15,7 +22,7 @@ Is it possible to run GitLab Runner in debug/verbose mode. From a terminal, do:
gitlab-runner --debug run
```
## 3. I get a PathTooLongException during my builds on Windows
## I get a PathTooLongException during my builds on Windows
This is caused by tools like `npm` which will sometimes generate directory structures
with paths more than 260 characters in length. There are two possible fixes you can
...
...
@@ -33,11 +40,11 @@ The [NTFSSecurity](https://ntfssecurity.codeplex.com/) PowerShell module provide
a *Remove-Item2* method which supports long paths. The Gitlab CI Multi Runner will
detect it if it is available and automatically make use of it.
## 4. I'm seeing `x509: certificate signed by unknown authority`
## I'm seeing `x509: certificate signed by unknown authority`
Please [See the self-signed certificates](../configuration/tls-self-signed.md)
## 5. I get `Permission Denied` when accessing the `/var/run/docker.sock`
## I get `Permission Denied` when accessing the `/var/run/docker.sock`
If you want to use Docker executor,
and you are connecting to Docker Engine installed on server.
...
...
@@ -45,7 +52,7 @@ You can see the `Permission Denied` error.
The most likely cause is that your system uses SELinux (enabled by default on CentOS, Fedora and RHEL).
Check your SELinux policy on your system for possible denials.
## 6. The Docker executor gets timeout when building Java project.
## The Docker executor gets timeout when building Java project.
This most likely happens, because of the broken AUFS storage driver:
[Java process hangs on inside container](https://github.com/docker/docker/issues/18502).
...
...
@@ -55,13 +62,13 @@ to either OverlayFS (faster) or DeviceMapper (slower).
Check this article about [configuring and running Docker](https://docs.docker.com/engine/articles/configuring/)
or this article about [control and configure with systemd](https://docs.docker.com/engine/articles/systemd/).
## 7. I get 411 when uploading artifacts.
## I get 411 when uploading artifacts.
This happens due to fact that runner uses `Transfer-Encoding: chunked` which is broken on early version of Nginx (http://serverfault.com/questions/164220/is-there-a-way-to-avoid-nginx-411-content-length-required-errors).
Upgrade your Nginx to newer version. For more information see this issue: https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/issues/1031
## 8. I can't run Windows BASH scripts; I'm getting `The system cannot find the batch label specified - buildscript`.
## I can't run Windows BASH scripts; I'm getting `The system cannot find the batch label specified - buildscript`.
You need to prepend `call` to your batch file line in .gitlab-ci.yml so that it looks like `call C:\path\to\test.bat`. Here
is a more complete example:
...
...
@@ -73,7 +80,7 @@ before_script:
Additional info can be found under issue [#1025](https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/issues/1025).
## 9. My gitlab runner is on Windows. How can I get colored output on the web terminal?
## My gitlab runner is on Windows. How can I get colored output on the web terminal?
**Short answer:**
...
...
@@ -94,7 +101,7 @@ If your program is doing the above, then you need to disable that conversion for
See issue [#332](https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/issues/332) for more information.
## 10. "warning: You appear to have cloned an empty repository."
## "warning: You appear to have cloned an empty repository."
When running `git clone` using HTTP(s) (with GitLab Runner or manually for
tests) and you see the following output:
...
...
@@ -130,13 +137,13 @@ See [an example of a user issue][1105].