Yup, Same here. Restored and currently working with 16.11 version. Have to plan for next upgrade either with fresh installation and import the data.
You are right, After removing noexec for /var, it works fine now. My bad ignored your step. Not sure why they implemented in 17.x versions.
1 Like
Ah for gods sake, yep… Same here, completely forgot we mount the /var folder with noexec.
This make it non-compliant with a standard minimum security baseline for almost any Linux flavor. Why are we executing from /var?
We’re not big enough to have an enterprise license but if anyone reading this does, please raise it with GitLabs 
Searching open issues here: Issues · GitLab.org / GitLab · GitLab shows 2 of them but seems nothing has been done about it.
Someone noticed it with Gitlab 15.2. You could vote on the issues so that Gitlab can see more people are affected by it, and add comments as well to say it’s still an issue in later versions. That way, they can see more people are using noexec and therefore they need to fix the way they implement Gitlab accordingly to take this into account.