FS#80077 - [gitlab] update from 16.4.1-1 to 16.5.0-1 went south

Attached to Project: Arch Linux
Opened by Mathias Rohnstock (mrohnstock) - Wednesday, 25 October 2023, 05:27 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 25 October 2023, 06:02 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After successfull installing the package, migrating the database and restarting all these gitlab services, gitlab won't startup

Additional info:
* package version(s)
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:
Update a already working gitlab 16.4.1 instance to 16.5.0.

in attached logfile you can find several issues.
Did I miss something to change (in config or something) between the update?

Thanks
   gitlab.log (32.9 KiB)
This task depends upon

Closed by  Toolybird (Toolybird)
Wednesday, 25 October 2023, 06:02 GMT
Reason for closing:  Not a bug
Additional comments about closing:  "path in puma.rb did changed - path was changed several updates ago to a none-standard path which introduced this issue."
Comment by Mathias Rohnstock (mrohnstock) - Wednesday, 25 October 2023, 06:00 GMT
... found my issue. In /usr/share/webapps/gitlab/config/puma.rb line 84 the defined path to error_handler did (somehow) change - used the correct path.

So.. it's a user fault - sorry for the noice!

Loading...