Hi to all !
I’m currently using the “self-managed GitLab” version on Debian for several years now.
I tried yesterday to update, and the update process stuck all the night on:
ruby_block[wait for puma service socket] action run
I stoppped the process, restarted it, looked for the logs to no avail.
When I stop/start Gitlab, the only service that doesn’t start is puma, and when I try to start it manually, I get:
warning: puma: unable to open supervise/ok: file does not exist
I’m at my wit’s end (I don’t know the ruby ecosystem), and my Gitlab instance is down at this time.
Do someone have an idea ?
- current Gitlab version: 13.0.3-ce.0
- current target version: 13.0.4-ce.0
- I assume that the version I had before the update process was the 13.0.3 as it was release the may 29, the target the june 3, and I did my update yesterday (https://about.gitlab.com/releases/categories/releases/)
- I discovered that unicorn is now superseded by puma, but I did nothing on this point: I didn’t change anything in gitlab.rb lately