Don’t accuse me of sending you on a wild goose chase then, when I gave up my free time to attempt to help you. If it was a problem with Gitlab 14.2.x then everyone upgrading to 14.2.x would have this problem. They don’t. Just you do. So this is a problem with your installation. Otherwise, there would already be posts on this forum about it. Which as you found, there are none. Something has gone wrong during your upgrade process, which may or may not be related to the upgrade process. You cannot say for 100% that Gitlab is at fault just because you were running the upgrade process. I could restart a service and have problems and assume it was because of that. But it might not restart for a hundred reasons. You would be right however if the upgrade process failed, aborted or whatever during the upgrade. But if that was the case, you would have had this error output. So that if it is the case, will be in the Gitlab log files. If you say that this doesn’t exist, then that means the Gitlab upgrade process completed successfully, and the side-effects you are experiencing is because of something else, and I ask questions to try and find out where the problem is. Only you have access to your system, I do not.
So your logic is flawed, not mine. You checked the disk, fine, no errors. You checked syslog, fine. No errors. Did you check the gitlab log files inside the container? Did you connect to the container using docker exec? I don’t know if you did this or not. You checked the system logs, I don’t know what else you checked.
Nobody can know the answer to your problem, if no information from log files or debugging is provided. Check the Gitlab docs for gitlab rake commands maybe here: Maintenance Rake tasks | GitLab or maybe search the docs for other potential rake commands or debugging. Maybe through this you can find information that you said doesn’t appear in the log files.
Debugging problems requires asking questions, even if you don’t agree with me that this is the source of the problem. I ask the questions to rule out that disk errors or lack of disk space is not the cause of the problem. It is not a wild goose chase. Like I said, you have access to the system I do not.