Redmine

It looks like this error is being displayed by Phusion Passenger.
Could you check if any Phusion Passenger errors are recorded in the log?

Also, Redmine 5.0.x is outdated, so I recommend using 6.0.x instead.
I wrote an article on the installation process, so please refer to it:
Install Redmine 6.0 on Ubuntu 24.04 LTS | Redmine Advisor
https://www.redmineadvisor.com/articles/6_0/install/ubuntu24/

Thanks for Answer, thanks for the Install Tutorial Link.
I want to have an worked "copy" from the redmine at work, and this is actually an 5.0.5.

can u tell me where to find the logs of passenger?
or are they the apache error log at /var/log/apache2/error.log?

this is after start of both VMs and connect to the ip from redmine:

[ N 2025-02-04 06:59:11.9540 772/T1 age/Wat/WatchdogMain.cpp:1373 ]: Starting Passenger watchdog...
[ N 2025-02-04 06:59:11.9800 783/T1 age/Cor/CoreMain.cpp:1340 ]: Starting Passenger core...
[ N 2025-02-04 06:59:11.9800 783/T1 age/Cor/CoreMain.cpp:256 ]: Passenger core running in multi-application mode.
[ N 2025-02-04 06:59:12.0080 783/T1 age/Cor/CoreMain.cpp:1015 ]: Passenger core online, PID 783

[ N 2025-02-04 06:59:12.0212 783/T7 age/Cor/CoreMain.cpp:670 ]: Signal received. Gracefully shutting down... (send signal 2 more time(s) to force shutdown)
[ N 2025-02-04 06:59:12.0212 783/T1 age/Cor/CoreMain.cpp:1245 ]: Received command to shutdown gracefully. Waiting until all clients have disconnected...
[ N 2025-02-04 06:59:12.0213 783/T7 Ser/Server.h:901 ]: [ServerThr.1] Freed 0 spare client objects
[ N 2025-02-04 06:59:12.0213 783/T7 Ser/Server.h:558 ]: [ServerThr.1] Shutdown finished
[ N 2025-02-04 06:59:12.0220 783/Tb Ser/Server.h:901 ]: [ServerThr.2] Freed 0 spare client objects
[ N 2025-02-04 06:59:12.0220 783/Tb Ser/Server.h:558 ]: [ServerThr.2] Shutdown finished
[ N 2025-02-04 06:59:12.0229 783/Td Ser/Server.h:901 ]: [ApiServer] Freed 0 spare client objects
[ N 2025-02-04 06:59:12.0229 783/Td Ser/Server.h:558 ]: [ApiServer] Shutdown finished
[ N 2025-02-04 06:59:12.0435 804/T1 age/Wat/WatchdogMain.cpp:1373 ]: Starting Passenger watchdog...
[ N 2025-02-04 06:59:12.0667 807/T1 age/Cor/CoreMain.cpp:1340 ]: Starting Passenger core...
[ N 2025-02-04 06:59:12.0667 807/T1 age/Cor/CoreMain.cpp:256 ]: Passenger core running in multi-application mode.
[ N 2025-02-04 06:59:12.0770 807/T1 age/Cor/CoreMain.cpp:1015 ]: Passenger core online, PID 807
[Tue Feb 04 06:59:12.078883 2025] [mpm_event:notice] [pid 802:tid 139972082534272] AH00489: Apache/2.4.52 (Ubuntu) Phusion_Passenger/6.0.10 configured -- resuming normal operations
[Tue Feb 04 06:59:12.079055 2025] [core:notice] [pid 802:tid 139972082534272] AH00094: Command line: '/usr/sbin/apache2'
[ N 2025-02-04 06:59:12.3187 783/T1 age/Cor/TelemetryCollector.h:531 ]: Message from Phusion: End time can not be before or equal to begin time
[ N 2025-02-04 06:59:12.3554 783/T1 age/Cor/CoreMain.cpp:1325 ]: Passenger core shutdown finished
[ E 2025-02-04 06:59:14.2882 807/T6 age/Cor/SecurityUpdateChecker.h:521 ]: A security update is available for your version (6.0.10) of Phusion Passenger(R). We strongly recommend upgrading to version 6.0.24.
[ E 2025-02-04 06:59:14.2883 807/T6 age/Cor/SecurityUpdateChecker.h:526 ]: Additional security update check information: 
- [Fixed in 6.0.14] [CVE-2018-25032] zlib before 1.2.12 allows memory corruption when deflating (i.e., when compressing) if the input has many distant matches.
- [Fixed in 6.0.14] A use after free memory safety issue was introduced in 6.0.12, and fixed in 6.0.14.
- [Fixed in 6.0.19] [CVE-2023-38545] A vulnerability existed in libcurl before 8.4.0 which was the library used for Passenger proxy functionality. Exploiting this vulnerability would require two preconditions. First a SOCKS5 proxy to be configured for Passenger licensing, anonymous telemetry, or security update check which is not the default but is possible. Second the attacker would need to cause Passenger to use an attacker-controlled URL when performing these requests. Causing Passenger to use non-standard urls requires that the attacker already have code execution on the Passenger host, or control of the Passenger config. If exploited this vulnerability could lead to code execution, due to buffer overflow.
App 1285 output: Error: The application encountered the following error: uninitialized constant ActiveSupport::LoggerThreadSafeLevel::Logger (NameError)
App 1285 output:     /var/lib/gems/3.0.0/gems/activesupport-6.1.7.2/lib/active_support/logger_thread_safe_level.rb:16:in `<module:LoggerThreadSafeLevel>'
App 1285 output:     /var/lib/gems/3.0.0/gems/activesupport-6.1.7.2/lib/active_support/logger_thread_safe_level.rb:9:in `<module:ActiveSupport>'
App 1285 output:     /var/lib/gems/3.0.0/gems/activesupport-6.1.7.2/lib/active_support/logger_thread_safe_level.rb:8:in `<top (required)>'
App 1285 output:     /var/lib/gems/3.0.0/gems/activesupport-6.1.7.2/lib/active_support/logger_silence.rb:5:in `require'
App 1285 output:     /var/lib/gems/3.0.0/gems/activesupport-6.1.7.2/lib/active_support/logger_silence.rb:5:in `<top (required)>'
App 1285 output:     /var/lib/gems/3.0.0/gems/activesupport-6.1.7.2/lib/active_support/logger.rb:3:in `require'
App 1285 output:     /var/lib/gems/3.0.0/gems/activesupport-6.1.7.2/lib/active_support/logger.rb:3:in `<top (required)>'
App 1285 output:     /var/lib/gems/3.0.0/gems/activesupport-6.1.7.2/lib/active_support.rb:29:in `require'
App 1285 output:     /var/lib/gems/3.0.0/gems/activesupport-6.1.7.2/lib/active_support.rb:29:in `<top (required)>'
App 1285 output:     /var/lib/gems/3.0.0/gems/railties-6.1.7.2/lib/rails.rb:7:in `require'
App 1285 output:     /var/lib/gems/3.0.0/gems/railties-6.1.7.2/lib/rails.rb:7:in `<top (required)>'
App 1285 output:     /opt/redmine-5.0.5/config/application.rb:5:in `require'
App 1285 output:     /opt/redmine-5.0.5/config/application.rb:5:in `<top (required)>'
App 1285 output:     /opt/redmine-5.0.5/config/environment.rb:4:in `require'
App 1285 output:     /opt/redmine-5.0.5/config/environment.rb:4:in `<top (required)>'
App 1285 output:     config.ru:3:in `require'
App 1285 output:     config.ru:3:in `block in <main>'
App 1285 output:     /var/lib/gems/3.0.0/gems/rack-2.2.10/lib/rack/builder.rb:125:in `instance_eval'
App 1285 output:     /var/lib/gems/3.0.0/gems/rack-2.2.10/lib/rack/builder.rb:125:in `initialize'
App 1285 output:     config.ru:1:in `new'
App 1285 output:     config.ru:1:in `<main>'
App 1285 output:     /usr/share/passenger/helper-scripts/rack-preloader.rb:101:in `eval'
App 1285 output:     /usr/share/passenger/helper-scripts/rack-preloader.rb:101:in `preload_app'
App 1285 output:     /usr/share/passenger/helper-scripts/rack-preloader.rb:189:in `block in <module:App>'
App 1285 output:     /usr/lib/ruby/vendor_ruby/phusion_passenger/loader_shared_helpers.rb:390:in `run_block_and_record_step_progress'
App 1285 output:     /usr/share/passenger/helper-scripts/rack-preloader.rb:188:in `<module:App>'
App 1285 output:     /usr/share/passenger/helper-scripts/rack-preloader.rb:30:in `<module:PhusionPassenger>'
App 1285 output:     /usr/share/passenger/helper-scripts/rack-preloader.rb:29:in `<main>'
[ E 2025-02-04 07:02:42.0282 807/Tf age/Cor/App/Implementation.cpp:221 ]: Could not spawn process for application /opt/redmine: The application encountered the following error: uninitialized constant ActiveSupport::LoggerThreadSafeLevel::Logger (NameError)
  Error ID: dc023ac5
  Error details saved to: /tmp/passenger-error-erTEBI.html

[ E 2025-02-04 07:02:42.0299 807/T8 age/Cor/Con/CheckoutSession.cpp:274 ]: [Client 1-1] Cannot checkout session because a spawning error occurred. The identifier of the error is dc023ac5. Please see earlier logs for details about the error.

The following might be the cause.
https://www.redmine.org/issues/42113
It has been resolved in version 5.0.11.
Would it be possible for you to use 5.0.11?

At Work we use the same Server and Redmine Version, only not into a VirtualBox, but into an Hyper-V Cluster. And the Redmine at work ist working fine since some time.

I want to play around with redmine in a virtualbox to test the right system and to test the update process to version 6.x. Because the redmine at work is in productive use and we have actually no test enviroment

This issue is tracked in #42113.

All supported Redmine versions have now been updated with fixes for this issue, namely

• 5.0.11
• 5.1.6
• 6.0.3

Please update your Redmine to one of these versions.