Claas Z

For anyone wondering how to install 2.2.0 in the meantime: As a workaround you can use `$ ansible-galaxy install https://github.com/rvm/rvm1-ansible/archive/refs/tags/v2.2.0.tar.gz`

> ``` > [ E 2020-03-04 06:25:21.0225 32376/T0 apa/Hooks.cpp:751 ]: Unexpected error in mod_passenger: Cannot connect to the Passenger core at unix:/var/passenger/passenger.0Oh8G1l/agents.s/core > Backtrace: > in 'Passenger::FileDescriptor Passenger::Apache2Module::Hooks::connectToCore()' (Hooks.cpp:343) >...

> @claasz are you using 6.0.8 or later? Are you using systemd's `PRIVATE_TMP`? @CamJN We are using 6.0.7. I have no idea what systemd's `PRIVATE_TMP` is. How would I check...

> @claasz This might help you determine if you are using systemd private tmp: https://access.redhat.com/discussions/3027351 @CamJN I see. So yes, we are using systemd private tmp.

@CamJN Thanks. However, we've already applied @patrickdavey 's `copytruncate` workaround. It's a production system which showed the problem quite infrequently, so it's not possible for us to test the fix.

We've experienced similar problems when installing an a server with 0.5GB RAM only. Looks like installation requires at least 1GB of RAM. ` g++: internal compiler error: Killed (program cc1plus)`...

It would be nice if docs would not confuse 50% of Rails users who are running on MySQL.

Regardless whether your CDN supports a perma cache or not (or maybe you don't use a CDN at all), you could always put your app behind a standard HTTP caching...