gitlab 15.1.3
os：Ubuntu 20.04
The actions performed are as follows:
rm -rf /var/log/gitlab/*
gitlab-ctl restart
The gitlab url cannot be accessed, and all requests to view the log nginx are 499。
I tried restarting gitlab and reconfigure again
Related
Gitlab:14.4.0
Gitlab-Runner:14.4.0 & 13.0.1
After I upgrade Gitlab from 13.6.3 to 14.4.0, all Runner could not pick up jobs
I thought it was Runner version too old，but Gitlab-Runner:14.4.0 on other Linux vm show the same problem
gitlab-runner status looks normal
But when I use gitlab-runner --debug run on each vm, Runner work for few minutes, the runner on that vm could pick up jobs, now I run this command manual every 5 minute to keep other developer working
the problem is we deploy gitlab use docker version image on hand wirte Deployment deploy on Kubernetes, the background jobs fail and stuck many times, after we transfer data to new Gitlb which deploy by helm problem solved
I had the same problem. But I figured it came from the GitLab instance iteself.
The problem was thensolved by upgrading to 14.4.2. I don't think it's the update itself, but the restart of the GitLab instance after the upgrade proved useful.
Ran into a similar issue (GitLab EE v14.2.3-ee) whereby all 3 runners where in a wait state for minutes at a time, before any pending jobs were eventually picked up. Resolved the issue by...
removing all runners,
resetting the config.toml file (which was cluttered with [[runner]] entries from former runners),
restarting GitLab, and
then creating new runners.
Specifically, I performed the following steps...
Delete all runners via "GitLab console > Admin > Overview > Runners".
Log into runner host(s), find config.toml, and clean out the entire file except for...
concurrent=5
check_interval=0
[session_server]
session_timeout = 1800
Log into GitLab EE host and restart GitLab EE.
sudo gitlab-ctl restart
Log into the runner host(s), and create new runners (follow directions from "GitLab console > Admin > Overview > Runners" )
After the above corrective action, the runners now immediately pick up pending jobs.
I'm running the Openshift origin all in one, and the various project templates seem to work fine, except for gitlab. When restarting the machine, or trying to restart the gitlab-ce pod, it seems to either take a really long time (just under 10m) or it fails due to timeout. It always seems to get stuck at the same place.
How can i troubleshoot this deployment?
Thank you for using GitLab Docker Image!
Current version: gitlab-ce=8.14.1-ce.1
Configure GitLab for your system by editing /etc/gitlab/gitlab.rb file
And restart this container to reload settings.
To do it use docker exec:
docker exec -it gitlab vim /etc/gitlab/gitlab.rb
docker restart gitlab
For a comprehensive list of configuration options please see the Omnibus GitLab readme
https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/README.md
If this container fails to start due to permission problems try to fix it by executing:
docker exec -it gitlab update-permissions
docker restart gitlab
Preparing services...
Starting services...
Configuring GitLab package...
/opt/gitlab/embedded/bin/runsvdir-start: line 24: ulimit: pending signals: cannot modify limit: Operation not permitted
/opt/gitlab/embedded/bin/runsvdir-start: line 34: ulimit: max user processes: cannot modify limit: Operation not permitted
/opt/gitlab/embedded/bin/runsvdir-start: line 37: /proc/sys/fs/file-max: Read-only file system
Configuring GitLab...
* Moving existing certificates found in /opt/gitlab/embedded/ssl/certs
* Symlinking existing certificates found in /etc/gitlab/trusted-certs
Your process hangs on https://hub.docker.com/r/gitlab/gitlab-ce/~/dockerfile/
wrapper
line
you can run it manually by executing
docker run -it gitlab/gitlab-ce 'bash'
and entering there wrapper
If you manage to see
Starting Chef...
then everything after that should be OK.
The root cause of this for me, turned out to be lack of memory. I was running AWS EC2 t1.micro - 1GB. To fix, I stopped the EC2 instance and upgraded to t2.small (2GB). I started the EC2 again, ran free to check the memory was available, and then ran the docker run -ti gitlab/gitlab-ce command again.
Also, this saved me a couple of times, to clear up a corrupted docker state:
service docker stop
sudo rm -rf /var/run/docker
sudo rm /var/run/docker.*
service docker start
I am using Gitlab-CI-Multi-Runner on Windows (64 bit), and have configured it to run with the default shell. The connectivity with the Gitlab server is fine, but when it tries to run a build, it is cloning the repository using HTTP endpoint. My repo is quite big, and the Gitlab NGINX fails with an error. SSH endpoint works perfectly.
How do I make my GitLab-CI-Multi-Runner use the SSH endpoint when cloning the repo for executing a build?
Note: The same problem existed with the older Gitlab-CI-Runner for Windows which was written using C#.
The problem is related to the timeout of the unicorn engine workers, that is too short to allow big repositories to be cloned/pushed.
in /etc/gitlab/gitlab.rb uncomment and set
unicorn['worker_timeout'] = 1200
(hopefully enough).
then issue
# gitlab-ctl reconfigure
# gitlab-ctl restart
that works for me.
I have installed GitLab following the instructions here on the gitlab website for centos. I have ruby version 2.1.2 installed and mysql. And a bunch of other programs. I set the external url to git.mywebsite.com, but when i go to the url nothing is there. I have tried uninstalling it and reinstall it many time. Am I missing a key piece to make this work? How can I get gitlab working?
Update config/gitlab.yml production configuration:
production: &base
#
# 1. GitLab app settings
# ==========================
## GitLab settings
gitlab:
## Web server settings (note: host is the FQDN, do not include http://)
host: domain.tld
port: 8888
https: false
Then restart gitlab.
As I am running other web services, I am using Nginx to proxy my GitLab instance. My installation followed the Ubuntu manual install instructions available from GitHub.
Your install may feature a Ruby configuration at: /etc/gitlab/gitlab.rb
After editing your gitlab.rb configuration, execute the following to reconfigure:
sudo gitlab-ctl reconfigure
Then restart GitLab:
sudo gitlab-ctl stop
sudo gitlab-ctl start
After sudden restart of server, gitlab is inaccessible. I don't know whats happen. I have posted another question as well check this here. Gitlab is up and running when I start/restart from server but it is inaccessible from browser(This is way I used to access GtiLab).
When I start GitLab
The GitLab Unicorn web server with pid 2020 is running
The GitLab SideKiq job dispatcher with pid 2028 is running
GitLab and all its components are up and running.
but I can't access the web interface of gitlab by using IP of Git container: 192.168.2.9. I can able to ping 192.168.2.9 from my system.
That you can ping 192.168.2.9 does nothing to do with GitLab page not showing up. First of all, it would we helpful if you could paste the output of this commands:
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
sudo -u git -H /home/git/gitlab-shell/bin/check
You can also check GitLab's & nginx's logs for errors and that you configured well GitLab's page on nginx.
If you keep finding troubles I recommend you to Install the lates Omnibus version at: https://www.gitlab.com/downloads/ which will install you the latest GitLab stable version and all it's dependencies, so you don't have to do a manual installation.
I had this problem after the restart of the machine. It turned out that I had installed a firewall that was re-enabled at startup, so the connection would be refused. I disabled it and all worked fine afterwards.