Hi, I just tried to upgrade my company docker container from GitLab community edition version 13.x to the latest 14.x.
I got this error, which made it no more working:
2021-07-05T09:02:46.233972165Z
2021-07-05T09:02:46.234066302Z System Info:
2021-07-05T09:02:46.234079799Z ------------
2021-07-05T09:02:46.234084187Z chef_version=15.14.0
2021-07-05T09:02:46.234088946Z platform=ubuntu
2021-07-05T09:02:46.234096541Z platform_version=20.04
2021-07-05T09:02:46.234101289Z ruby=ruby 2.7.2p137 (2020-10-01 revision 5445e04352) [x86_64-linux]
2021-07-05T09:02:46.234108182Z program_name=/opt/gitlab/embedded/bin/chef-client
2021-07-05T09:02:46.234112811Z executable=/opt/gitlab/embedded/bin/chef-client
2021-07-05T09:02:46.234181942Z
2021-07-05T09:02:46.234350521Z
2021-07-05T09:02:46.234361362Z Running handlers:
2021-07-05T09:02:46.234486508Z
2021-07-05T09:02:46.234498823Z Removals:
2021-07-05T09:02:46.234504042Z * unicorn[âworker_processesâ] has been deprecated since 13.10 and was removed in 14.0. Starting with GitLab 14.0, Unicorn is no longer supported and users must switch to Puma, following Configure the bundled Puma instance of the GitLab package | GitLab.
2021-07-05T09:02:46.234514492Z
2021-07-05T09:02:46.234518569Z Running handlers complete
2021-07-05T09:02:46.234680607Z There was an error running gitlab-ctl reconfigure:
2021-07-05T09:02:46.234693781Z
2021-07-05T09:02:46.234698450Z Removed configurations found in gitlab.rb. Aborting reconfigure.
How can I solve it?
Regards,
Antonio
Hi,
Check your gitlab.rb and make sure that any lines with unicorn are removed, since puma should be used now. After removing, you need to run reconfigure so that it will start using puma. Then after this do the upgrade.
Alternatively, if you have a situation where there are no unicorn lines, this means that you are redirecting logs somewhere and this process is using unicorn. So remove the log redirect in gitlab.rb reconfigure and then do the upgrade.
Search the forum for more info on this, since people have already posted about it. Good luck!
1 Like
Hi, thank you for answering me.
The gitlab.rb file is accessibile by an external docker volume, and I confirm that all the unicorn settings are commented out.
The only action I can take is to restart the container by docker start gitlab, but it always ends (as seen by docker logs -f -t gitlab) in:
2021-07-05T10:12:05.024965631Z Removals:
2021-07-05T10:12:05.024980269Z * unicorn[âworker_processesâ] has been deprecated since 13.10 and was removed in 14.0. Starting with GitLab 14.0, Unicorn is no longer supported and users must switch to Puma, following Configure the bundled Puma instance of the GitLab package | GitLab.
2021-07-05T10:12:05.024988936Z
2021-07-05T10:12:05.024992161Z Running handlers complete
2021-07-05T10:12:05.024995017Z Chef Infra Client failed.
Any other suggestion please! 
Issue solved by updating the GITLAB_OMNIBUS settings, I forgotten that there it was a setting for Unicorn!
2 Likes
@antonio-petricca Hey I am having the same issue, I do not see unicorn in any of my stuff. How did you fix this? I just updated to 14.0.X and not my site will not come up to save my life but if I downgrade to 13.12.12(? I think it was) everything comes back up.
I am using the OMNIBUS docker image, so I set the puma in place of unicorn by the enviroment configuration variable.
Mind giving me some more information. I checked my environment variables for both the Docker image docker exec -it gitlab env and I checked my docker-compose.yml and do not see any reference to unicorn. My gitlab.rb file does not have anything for unicorn also. I am lost as what to do to fix this or just revert back to 13.12.12. I have reverted and it works but as soon as I upgrade the image to 14.0.X I just get a 502 error from cloudflare.