How use GITLAB_RAILS_RACK_TIMEOUT_ENABLE (contanier env var or new (?) configuration parameter) about docker-gitlab HOT 5 CLOSED

@fidoedidoe
Your problem may be temporaly resolved by setting GITLAB_RAILS_RACK_TIMEOUT to a value higher than the default value of "60" (seconds). But it's just a temporal workaround. As far as I researched, we have no method to completely disable request timeout.

from docker-gitlab.

@kkimurak - thank you so much for the feedback/insight/understanding of my problem - very much appreciated!! Let me look into this and I'll update (edit here) once I know more.

EDIT: @kkimurak - I can't thank you enough, your suggestion worked perfectly. We can now see the details of our MR!! Than you sooo much!!!

from docker-gitlab.

Looking into the code, gitlab itself loads the environment variable GITLAB_RAILS_RACK_TIMEOUT_ENABLE. It works for both official gitlab-ce (gitlab-ee) and unofficialsameersbn/gitlab. So we have nothing to do here for sameersbn/gitlab image. Just set container environment variable.

I don't know how you are running the container, but here is a part of docker-compose.yml example:

services:
  gitlab:
    image: sameersbn/gitlab:16.5.1
   environment:
    - GITLAB_RAILS_RACK_TIMEOUT_ENABLE=false

from docker-gitlab.

Hey @kkimurak

Thanks for your reply (and apologies for the delay in replying). I implemented the Docker Env Var (GITLAB_RAILS_RACK_TIMEOUT_ENABLE=false) but unfortunately it doesn't alleviate the issue I'm experiencing.

In the logs (/var/log/gitlab/gitlab/production.log) I see (basically a MR has many many comments and times out rendering these to web UI):

Rack::Timeout::RequestTimeoutException (Request ran for longer than 60000ms ):

Perhaps I'm misunderstanding the influence this env var has in respect to the above? Any further suggestions/further insight would be very welcomed.

Kind regards

from docker-gitlab.

Hi @fidoedidoe , sorry for late.

I have noticed that the code introduced by !90958 have been removed by !92200. The environment variable GITLAB_RAILS_RACK_TIMEOUT_ENABLE have no effect.

Alternatively GITLAB_RAILS_RACK_TIMEOUT_ENABLE_LOGGING is introduced but it may not solve your problem (it just control wheather enable / disable logging, not timeout itself)..

from docker-gitlab.