To me, the following solved the problem:
gitlab-runner restart
Where gitlab-runner is a symlink to gitlab-ci-multi-runner:
Answer from fedorqui on Stack OverflowGitLab Runner is the open source project that is used to run your jobs and send the results back to GitLab. It is used in conjunction with GitLab CI, the open-source continuous integration service included with GitLab that coordinates the jobs.
gitlab: Runner is offline, last contact was about some hours ago - Stack Overflow
Gitlab runner offline status - GitLab CI/CD - GitLab Forum
How to know if a job is running in a gitlab.com runner
Gitlab runner status show "the service is not installed" but it was installed and run successfully - Stack Overflow
To me, the following solved the problem:
gitlab-runner restart
Where gitlab-runner is a symlink to gitlab-ci-multi-runner:
GitLab Runner is the open source project that is used to run your jobs and send the results back to GitLab. It is used in conjunction with GitLab CI, the open-source continuous integration service included with GitLab that coordinates the jobs.
This worked for me:
sudo gitlab-runner verify
since gitlab-runner restart didn't actually restarted runners
TLDR: I want to know, given any random (not owned by me) repository (for example its .gitlab-ci.yml file) and, if needed, the corresponding pipeline result, a method to know for certain whether gitlab.com runners were used, or self-hosted ones, or both.
I will add some details here.
Keep in mind that my problem refers to a repository from gitlab.com and not "exotic" solutions such as a repository from gitlab.custom.com which attempts to use gitlab.com runners.
Normally, if a job does not specify a tag, then it will run in the default gitlab.com runner.
If a job specifies a tag from gitlab.com (for examplesaas-linux-small-amd64) then it will run with gitlab.com runners.
Nevertheless, if a job specifies a custom tag, such as docker, it's not clear to me whether this is certainly a self-hosted runner or could still be a gitlab.com one.
Let's also talk about the Gitlab pipeline UI, since some clues to answer this question can be there:
- the UI specifies the runner for this job. From the runner description we can clearly see it's a gitlab runner.
- the UI specifies the runner for this job. From the runner description it's not clear whether it's a gitlab runner or not.
- the UI doesn't specify the runner for this job (also included in the picture). Why isn't is specified, if in example 2 it was? How can I know if it's gitlab runner or not?
Thanks for your help in advance!
Run "service gitlab-runner status" for more information.
When I got the message "gitlab-runner: the service is not installed" I realized that the file /usr/lib/gitlab-runner/gitlab-runner had incorrect permissions.
for Ubuntu
Change your /etc/init.d/gitlab-runner
...
DAEMON="/usr/bin/gitlab-runner"
DESC="GitLab Runner"
USER="gitlab-runner"
...
--exec "$DAEMON" -- "run" "--working-directory" "/var/lib/gitlab-runner" "--config" "/etc/gitlab-runner/config.toml" "--service" "gitlab-runner" "--syslog" "--user" "$USER"
...
Variable $DAEMON not defined and is used
status)
status_of_proc -p "$PIDFILE" "$DAEMON" "$DESC"
;;
*)
I know where I can find running jobs in pipelines. But is there a CLI Option where I could pull what jobs are currently running on an Ubuntu Self Hosted Runner?