Hi All ,
We are new install Giblab .But Login error message ;
Deploy in progress
Please try again in a few minutes.
Please contact your GitLab administrator if this problem persists.
what could be the reason.?
I can see error log ;
— gitlab-workhorse
2018-04-05_18:39:03.47769 time=“2018-04-05T21:39:03+03:00” level=info msg=Starting version=“gitlab-workhorse v4.0.0-20180403.161906”
2018-04-05_18:39:03.47775 time=“2018-04-05T21:39:03+03:00” level=info msg=“keywatcher: starting process loop”
2018-04-05_18:39:03.47777 time=“2018-04-05T21:39:03+03:00” level=info msg=“redis: dialing” address=/var/opt/gitlab/redis/redis.socket network=unix
2018-04-05_18:39:06.50549 time=“2018-04-05T21:39:06+03:00” level=error msg=“unknown error” error=“keywatcher: pubsub receive: EOF”
2018-04-05_18:39:06.50554 time=“2018-04-05T21:39:06+03:00” level=info msg=“redis: dialing” address=/var/opt/gitlab/redis/redis.socket network=unix
2018-04-05_18:39:06.50557 time=“2018-04-05T21:39:06+03:00” level=error msg=“unknown error” error=“keywatcher: dial unix /var/opt/gitlab/redis/redis.socket: connect: no such file or directory”
2018-04-05_18:39:06.59839 time=“2018-04-05T21:39:06+03:00” level=info msg=“redis: dialing” address=/var/opt/gitlab/redis/redis.socket network=unix
---- prometheus
2018-04-05_18:39:07.46453 time=“2018-04-05T21:39:07+03:00” level=error msg=“Error creating HTTP client for job “kubernetes-cadvisor”: unable to use specified CA cert /var/run/secrets/kubernetes.io/serviceaccount/ca.crt: open /var/run/secrets/kubernetes.io/serviceaccount/ca.crt: no such file or directory” source=“scrape.go:121”
2018-04-05_18:39:07.46454 time=“2018-04-05T21:39:07+03:00” level=error msg=“Cannot create Kubernetes discovery: open /var/run/secrets/kubernetes.io/serviceaccount/token: no such file or directory” source=“discovery.go:86”
2018-04-05_18:39:07.46456 time=“2018-04-05T21:39:07+03:00” level=error msg=“Error creating HTTP client for job “kubernetes-nodes”: unable to use specified CA cert /var/run/secrets/kubernetes.io/serviceaccount/ca.crt: open /var/run/secrets/kubernetes.io/serviceaccount/ca.crt: no such file or directory” source=“scrape.go:121”
2018-04-05_18:39:07.46459 time=“2018-04-05T21:39:07+03:00” level=error msg=“Cannot create Kubernetes discovery: open /var/run/secrets/kubernetes.io/serviceaccount/token: no such file or directory” source=“discovery.go:86”
2018-04-05_18:39:07.46461 time=“2018-04-05T21:39:07+03:00” level=error msg=“Error creating HTTP client for job “kubernetes-pods”: unable to use specified CA cert /var/run/secrets/kubernetes.io/serviceaccount/ca.crt: open /var/run/secrets/kubernetes.io/serviceaccount/ca.crt: no such file or directory” source=“scrape.go:121”
2018-04-05_18:39:07.46462 time=“2018-04-05T21:39:07+03:00” level=error msg=“Cannot create Kubernetes discovery: open /var/run/secrets/kubernetes.io/serviceaccount/token: no such file or directory” source=“discovery.go:86”
---- unicorn
W, [2018-04-05T21:52:58.126500 #37718] WARN – : #Unicorn::HttpServer:0x00007f85084a51c0: worker (pid: 37718) exceeds memory limit (533574144.0 bytes > 471193609 bytes)
W, [2018-04-05T21:52:58.126816 #37718] WARN – : Unicorn::WorkerKiller send SIGQUIT (pid: 37718) alive: 750 sec (trial 1)
---- redis
2018-04-05_18:39:06.52916 37222:M 05 Apr 21:39:06.528 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
2018-04-05_18:39:06.52917 37222:M 05 Apr 21:39:06.528 # Server started, Redis version 3.2.11
2018-04-05_18:39:06.52918 37222:M 05 Apr 21:39:06.528 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add ‘vm.overcommit_memory = 1’ to /etc/sysctl.conf and then reboot or run the command ‘sysctl vm.overcommit_memory=1’ for this to take effect.
2018-04-05_18:39:06.54143 37222:M 05 Apr 21:39:06.540 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command ‘echo never > /sys/kernel/mm/transparent_hugepage/enabled’ as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
2018-04-05_18:39:06.54228 37222:M 05 Apr 21:39:06.541 * DB loaded from disk: 0.001 seconds
2018-04-05_18:39:06.54229 37222:M 05 Apr 21:39:06.541 * The server is now ready to accept connections at /var/opt/gitlab/redis/redis.socket
I don’t know if you’re still struggling with this issue but I recently did and here is the solution.