Hi friends, has anyone encountered this problem? My services are all normal, but a 502 error is displayed when opening the web. Does anyone know where to configure it?
Which Linux Distribution, and host resources/hardware are used? Anything in the logs that could explain the server error 5xx and the delayed boot time (maybe a lock or database migration).
GitLab 16.9.1 was released today, might be worth a try to update and test, too.
im using alma linux 8.7, I basically am trying to deploy an instance of gitlab in terraform. It stands up a bunch of containers (gitlab-workhorse, shell, gitaly, pages, runner, zoekt indexer/webserver, redis, postgres, etc). And im getting that same error that tonywgx got, im looking at the logs of workhorse and this is what its saying.
{“correlation_id”:“”,“duration_ms”:51,“error”:“badgateway: failed to receive response: dial tcp: lookup webservice on 192.168.223.2:53: no such host”,“level”:“error”,“method”:“GET”,“msg”:“”,“time”:“2024-02-22T15:37:35Z”,“uri”:“”}
Thanks for the details. When you mention containers in this context, is this a custom Terraform module? Or, more refined question: Which documentation or tutorial are you following?
When SELinux is enabled, it might prevent file descriptor access causing problems. The syslog should be able to provide more insights.
The docker-compose file in the Cloud Native container images project provides a development environment.. The images themselves are used in the Helm Chart and Kubernetes Operator to support cloud-native installation.
I would recommend following the official installation on Alma Linux, and use the Omnibus packages or container image instead of a custom setup. A custom setup is harder to support, introducing potential new problems and troubleshooting paths.