Content
Upgrade 4.0.9->4.2. - nothing works anymore!
Added by Michael Heseltine about 9 years ago
I just tried an upgrade of our OP installation from 4.0.9 to the latest 4.2 using [[https://www.openproject.org/open-source/manual-installation/latest-upgrade-guide/]]
. Everything worked without any errors (I had to manually install passenger in the new ruby because gem update passenger did nothing, but apart from that, everything was fine), but now, the website won’t start anymore.
At first, I got a passenger error saying “somethin is wrong” without being more specific. After a restart of the apache (I wanted to enable PassengerFriendyErrorPages), now i get nothing (error during loading). In the apache log, I now get a segmentation fault:
[Thu Sep 17 20:11:42.413581 2015] [core:notice] [pid 3938] AH00051: child pid 19784 exit signal Segmentation fault (11), possible coredump in /etc/apache2
This is a Ubuntu 14.04 installation. The apache starts with the following version information:
[Thu Sep 17 19:57:34.483304 2015] [mpm_prefork:notice] [pid 3938] AH00163: Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.11 OpenSSL/1.0.1f Phusion_Passenger/5.0.18 configured -- resuming normal operations
Can anybody tell me what to do to recover the site without losing all the data? I can provide additional information if you tell me what to send. I’m not familiar at all with ruby or passenger, so don’t know where to look for the root of my problem.
Thanks in advance, Mike.
Replies (1)
Okay, the segmentation fault is gone (another restart of the apache helped).
But OP won’t start, I get the passenger error again. I now enabled the friendly error pages and get this output:
execjs is installed, though, I can find both a version 2.4.0 and one 2.6.0 in the /home/op/.rvm/gems/ruby-2.1.5/gems/ directory.
What have I done wrong, and how can I get OP working again?
Cheers, Mike