It seems like there are never-ending layers to the Redmine problems with this upgrade.
Currently, the package build and installs. However, when it runs, it produces a 500 Internal Server Error.
https://salsa.debian.org/ruby-team/redmine/-/jobs/7232783/viewer#L3068
Pulling the Apache log from one of my test instances shows the following:
[ N 2025-03-11 03:40:57.2749 73604/T1 age/Wat/WatchdogMain.cpp:1367 ]: Starting Passenger watchdog...
[ N 2025-03-11 03:40:57.3016 73608/T1 age/Cor/CoreMain.cpp:1337 ]: Starting Passenger core...
[ N 2025-03-11 03:40:57.3017 73608/T1 age/Cor/CoreMain.cpp:255 ]: Passenger core running in multi-application mode.
[ N 2025-03-11 03:40:57.3140 73608/T1 age/Cor/CoreMain.cpp:1012 ]: Passenger core online, PID 73608
[ N 2025-03-11 03:40:57.3327 73608/T9 age/Cor/CoreMain.cpp:669 ]: Signal received. Gracefully shutting down... (send signal 2 more time(s) to force shutdown)
[ N 2025-03-11 03:40:57.3327 73608/T1 age/Cor/CoreMain.cpp:1242 ]: Received command to shutdown gracefully. Waiting until all clients have disconnected...
[ N 2025-03-11 03:40:57.3328 73608/Tf Ser/Server.h:895 ]: [ServerThr.4] Freed 0 spare client objects
[ N 2025-03-11 03:40:57.3328 73608/Tf Ser/Server.h:552 ]: [ServerThr.4] Shutdown finished
[ N 2025-03-11 03:40:57.3346 73608/T9 Ser/Server.h:895 ]: [ServerThr.1] Freed 0 spare client objects
[ N 2025-03-11 03:40:57.3346 73608/Tb Ser/Server.h:895 ]: [ServerThr.2] Freed 0 spare client objects
[ N 2025-03-11 03:40:57.3347 73608/T9 Ser/Server.h:552 ]: [ServerThr.1] Shutdown finished
[ N 2025-03-11 03:40:57.3347 73608/Tb Ser/Server.h:552 ]: [ServerThr.2] Shutdown finished
[ N 2025-03-11 03:40:57.3347 73608/Td Ser/Server.h:895 ]: [ServerThr.3] Freed 0 spare client objects
[ N 2025-03-11 03:40:57.3347 73608/Td Ser/Server.h:552 ]: [ServerThr.3] Shutdown finished
[ N 2025-03-11 03:40:57.3348 73608/Th Ser/Server.h:895 ]: [ApiServer] Freed 0 spare client objects
[ N 2025-03-11 03:40:57.3348 73608/Th Ser/Server.h:552 ]: [ApiServer] Shutdown finished
[ N 2025-03-11 03:40:57.3727 73636/T1 age/Wat/WatchdogMain.cpp:1367 ]: Starting Passenger watchdog...
[ N 2025-03-11 03:40:57.4012 73640/T1 age/Cor/CoreMain.cpp:1337 ]: Starting Passenger core...
[ N 2025-03-11 03:40:57.4013 73640/T1 age/Cor/CoreMain.cpp:255 ]: Passenger core running in multi-application mode.
[ N 2025-03-11 03:40:57.4136 73640/T1 age/Cor/CoreMain.cpp:1012 ]: Passenger core online, PID 73640
[Tue Mar 11 03:40:57.415820 2025] [mpm_event:notice] [pid 73633:tid 73633] AH00489: Apache/2.4.63 (Debian) Phusion_Passenger/6.0.24 configured -- resuming normal operations
[Tue Mar 11 03:40:57.416444 2025] [core:notice] [pid 73633:tid 73633] AH00094: Command line: '/usr/sbin/apache2'
[ N 2025-03-11 03:40:58.0173 73608/T1 age/Cor/TelemetryCollector.h:531 ]: Message from Phusion: End time can not be before or equal to begin time
[ N 2025-03-11 03:40:58.0703 73608/T1 age/Cor/CoreMain.cpp:1322 ]: Passenger core shutdown finished
[ E 2025-03-11 03:41:00.1233 73640/T6 age/Cor/SecurityUpdateChecker.h:521 ]: A security update is available for your version (6.0.24) of Phusion Passenger(R). We strongly recommend upgrading to version 6.0.26.
[ E 2025-03-11 03:41:00.1234 73640/T6 age/Cor/SecurityUpdateChecker.h:526 ]: Additional security update check information:
- [Fixed in 6.0.26] [CVE-2025-26803] The http parser (from Passenger 6.0.21-6.0.25) was susceptible to a denial of service attack when parsing a request with an invalid HTTP method.
So, Passenger starts and then immediately stops. Nothing in this log indicates to me what the core problem is. Any ideas?
--
Soren Stoutner
soren@debian.org
Attachment:
signature.asc
Description: This is a digitally signed message part.