You are here
Veronica Charlton - Thu, 2021/06/03 - 22:21
Initially when I install the appliance it boots and runs.
I use turnkey-init to setup the information needed for gitlab.
Gitlab runs but when I try to login on the web interface I get a 500 error.
If I reboot gitlab is not started in the bootup provess.
help!!
Forum:
Tags:
You're right, I've confirmed the bug (Geez I hate GitLab!)
Argh! Bloody GitLab! One of the most painful appliances to maintain...!
Ok, sorry for my rant. I'll take a few deep breaths...
I don't yet have a fix, but I can confirm the bug. FWIW, on face value, it appears that between my final test of the new appliance and the final build (~1-2 hours) they released a new version which was either buggy or at least not compatible with our setup. Argh!
I want to blame GitLab (because I really do hate it) but really it's my fault. I should have done a final test (after doing the final build, destined for publishing). But I'd spent so long working on it, it was so late on Friday when I finally got it working and so resource intensive and so slow to build/start and therefore test (plus, I'd tested my local build so intensively), that I skipped that step. I can only assume that within that 1-2 hour window, they released a new version that broke things for us... Following my previous experience with GitLab, I should have known that would bite me...
I can't yet confirm, but I suspect that installing (i.e. updating to) the latest GitLab version should fix it. I had hoped to be able to post back to confirm (or not as the case maybe) by now, but after 20 minutes, it's still only 60%. In the meantime, here's the command to update GitLab CE (run as root user, or prefix with 'sudo'):
Updating doesn't work... :(
Sorry, I can now confirm that even updating GitLab-CE doesn't work. I'm still not clear what the issue is, but it appears to run deeper than I suspected...
In the meantime, I've reverted the GitLab appliance page back to the previous v16.0.
Attempting to use the older one
I understand how things go sometimes. Been around the block a few times.
My environment is on a closed network. I will grab the current one linked and bring it up. Theen move it over and check it out.
Thanks!
Still not right
I installed the 1.60 version and it appears to go through the initializatino process properly. When I check using gitlab-ctl status I see everything I would expect running.
When I attemtp to access it through the web interface it does not connect. I can ping the VM so I know that part is working.
When I do a netstat I do not see any connections to port 80. Gitlab seems to be only connection is the localhost address (127.0.0.1). I have an external DNS that is resolving the IP correctly.
I am also able to access the webadmin interface for the server itself.
That is where things stand at the moment.
Can you show the error you
Can you show the error you get when you try to access the webUI? (screenshot would be good)
Sorry for not responding
I appologize for not getting back to you.
In all honesty I installed Centos in a new appliance and then gitlab onto that.
That is working and I have not gone back to try and figure out why the turnkey one isn't.
Alternatively you could use
Alternatively you could use TKLCore LXC and install gitlab into that, then you get webmin and other features.
I have the same problem like
I have the same problem like the first comment. I can give a small Workaround for one part of the problem:
For restart GitLab after reboot you can do following on console:
But for the 500-Error i have no solution yet.
Error 500
I'm trying to understand the gitlab 500 error but it's not easy.
The command `gitlab-rake gitlab:check --trace` report no issue:
The command `gitlab-ctl tail` report the error:
I also find an error in the postgresql which was not present in the previous package:
But the config line seems identical to the preivous package.
I will continue to investigate a bit.
ok this explains why I couldn
ok this explains why I couldn't get it to work the last couple of days. Thanks in advance for not giving up on this hard to maintain appliance.
just to confirm, even the `apt install gitlab-ce` is now broken:
Gitlab is way over my head, as it's a beast to maintain, so unfortunately I will be no help to you on this one :(
Try having a read as per the link in the error message
If you look closely at the output you posted and you can see this line:
Between the error message and looking at that doc page, it appears that you need to do some incremental updates before upgrading to latest v14.x. I.e. So try this:
Please note that I have guessed the version number format. Hopefully I've got it right, but it may be formatted slightly differently. If that command fails, please check the specific version number format like this:
(If feeling unsure, please post the output and I'll help you interpret it).
Then next up, upgrade to v14.0.x, then v14.1.x (adjust version numbers as need be as per above) and finally the latest:
Plans on new container?
Are there any plans on releasing a new LXC with these fixes implemented, and the upgrades done? I have to admit, I am mad at myself for not googling for the answer quicker. I had just built a Ubuntu VM and installed GitLab, but for other reasons wanted to run it as a container on Proxmox so installed again. After doing the upgrade dance hoping to fix the problem, turned out a simple update query was all that was needed. Would be nice if a new container was released.
I need to circle back to this...
The current build code has issues so building a new container won't fix it (the new container will be broken). I put some time aside to work on it but was unable to resolve the latest issues with certificates in the time allocated so had to move to other things.
Once we have the base of our upcoming v17.0 release underway, I will circle back to GitLab and try again. I'm confident that I'll be able to work it out, but I need to get these other higher priority items resolved first.
Issues resolved
Everything works (for me) now... Thanks everyone for the advice
How to fix the errors in TurnKey v17.1 (GitLab v15.10.0-ce)
Add new comment