FreeBSD 12.0 -> 12.1 upgrade breaks passenger-install-apache2-module #2240
Comments
|
This will be fixed by this commit: d0d660b which will be included in the next release. |
|
So cool. Thanks |
|
Temporary fix: |
|
Just wondering: Will this also be fixed for the nginx module? I get the same error when trying to build nginx on FreeBSD 12.1. with the passenger module option enabled. |
|
The temporal fix with GCC can be a pain as soon as you have ports installed (it means source compilation instead of binary packages). Most of the time, I don’t have anything from ports. Right now the pkg (binary package) version of PostgreSQL 12 is still 12rc while the ports/stable version is 12.1. It made no sense to install RC version of PostgreSQL on new production servers. So, I did it with ports. But the binary version of GCC downgrades ICU which breaks both Node and PostgreSQL. I had to compile (install from ports) all of these together that took me several hours mostly due to the compilation of GCC itself. Without PostgreSQL 12 it wouldn’t be an issue, I guess. It’s just bad timing and unlucky combination. However, Rails + PostgreSQL + Node + Passenger is a reasonable setup on a webserver. And FreeBSD 12.0 is already complaining about "end of life" (no security upgrades) as the supported stable version is 12.1. I hope the fix will be released as a gem soon. |
I'm installing on a new server (AWS running FreeBSD 12.1) and having problems even after doing the above. I originally got the ambiguous thread failure and then applied the above instructions and now get the following (with both Ruby 2.6.5 and 2.7, installed with rvm): |
|
@lindensmith I find it strange because I have been running it on three production servers for a while already. Since our setups seem similar (RVM, Ruby 2.6.5, Apache), my first guess is it might be a difference between the modules we compile. What checkboxes did you have on? On my servers, by default Ruby and Node are checked, and the two others aren’t. I always turn off the Node since I’m not using it. It’s installed only for the Rails asset generation. If you had both checked, and you don’t need Passenger for Node, try turning it off, and be sure only Ruby is checked. |
|
I only had Ruby checked - I don't have Node installed, and I'm only just getting the virtual machine set up. there may be other things that got installed in the course of your setup that are slightly different - I hadn't installed much at all on the server yet. I hadn't even installed any other gems. I've installed a few more things, and just retried with 2.6.5 and 2.7 and it dies slightly differently in the two. I might just roll back to FreeBSD 11 for this setup, since I don't have anything on it yet. from 2.6.5: from 2.7: |
|
@lindensmith I don’t code in either C or C++ so my hint might be ridiculous. I can’t see any error message in your log except for "error: Killed signal terminated program cc1plus" My log was full of error messages like "error: reference to 'this_thread' is ambiguous At first glance, it looks like your machine ran out of memory, and the OS killed the compiler process. |
|
@PeterMozesMerl @lindensmith yup the compiler was killed by an external actor, whether that was the kernel or something else isn't specified but it's not a passenger problem per se. |
|
@PeterMozesMerl @CamJN |
|
It's fixed already. |
PeterMozesMerl commentedDec 22, 2019
Issue
I can’t reinstall Passenger 6.0.4 after FreeBSD upgrade
Steps
I upgraded my test servers from FreeBSD 12.0 to 12.1. I followed the official handbook as usual.
I installed Ruby 2.6.5 using RVM. The same version has been running before the upgrade. It’s the latest public version.
All my Rails gems were installed, and 1,000+ Rails tests passed.
When I try to install Passenger, the following happens. Note that my systems are as close to the default FreeBSD install as possible (I’m using the default compilers, etc).
The text was updated successfully, but these errors were encountered: