Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#80147 - Directory for puma pid files and logs missing
Attached to Project:
Arch Linux
Opened by Malte (Chrysaor) - Friday, 03 November 2023, 11:41 GMT
Last edited by Toolybird (Toolybird) - Friday, 03 November 2023, 19:00 GMT
Opened by Malte (Chrysaor) - Friday, 03 November 2023, 11:41 GMT
Last edited by Toolybird (Toolybird) - Friday, 03 November 2023, 19:00 GMT
|
DetailsDescription: Directory for puma pid files and logs missing
Additional info: * package version(s) 16.5.0-2 * config and/or log files etc. puma.rb * link to upstream bug report, if any / Steps to reproduce: After the upgrade to gitlab 16.5.0-2 my gitlab instance was giving me badgateway errors because gitlab-workhorse couldn't connect to puma. As I took a clother look into the changes in the puma.rb file I saw a change in the directories where the pids and logs are stored in this version. These directories are not present in my filesystem nor in the package: '/var/lib/gitlab/tmp/pids/' and '/var/lib/gitlab/log/'. As I created the directories as gitlab user the error went away. |
This task depends upon
Closed by Toolybird (Toolybird)
Friday, 03 November 2023, 19:00 GMT
Reason for closing: None
Additional comments about closing: @reporter requested closure but gave no reason
Friday, 03 November 2023, 19:00 GMT
Reason for closing: None
Additional comments about closing: @reporter requested closure but gave no reason