Well, I decided to figure out if I can help you or not, so I used my test server to check/verify what I’m about to suggest. That way if it breaks, it’s not important for me. However my system didn’t break and still works. My Gitlab version is 15.3.2 on my test server, and there is an upgrade available to 15.3.3, so I will then do the upgrade afterwards.
Since you mentioned it says the file is in some way corrupted, I decided to do this:
mv /opt/gitlab/embedded/nodes/gitlab.mydomain.com.json /root/
/opt/gitlab/embedded/nodes is empty, so we now reconfigure gitlab:
after reconfigure, I find that
/opt/gitlab/embedded/nodes/gitlab.mydomain.com.json has been recreated. So the reconfigure did what I was hoping it would do. At this point I stopped and started Gitlab, and then went to my web browser to make sure everything was working. Yes it was working fine.
So, now I update Gitlab on my install. In my instance I’m using Debian, so apt instead of yum, but the end result should be the same.
I then checked/verified again from the web browser, to make sure I had 15.3.3, and all seems to be working perfectly fine.
So for you, you move the
hostgitlab.domain.com.json somewhere else so that
/opt/gitlab/embedded/nodes is empty, reconfigure Gitlab, and then restart/verify all is OK, and then upgrade Gitlab, and hopefully you will be sorted out.
I’m not sure what your current Gitlab version is, but if you don’t upgrade regularly, I suggest you find out what Gitlab version is installed, and then check the Gitlab documentation to make sure you follow the upgrade path. Doing a yum update or dnf update might end up with it installing the latest Gitlab over your install, not following the upgrade path and potentially breaking your Gitlab install. You can find more on that here: Upgrading GitLab | GitLab