Closed (fixed)
Project:
Barracuda
Component:
PHP-FPM Server
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
6 May 2013 at 10:25 UTC
Updated:
22 May 2013 at 21:20 UTC
The meta installer seems to override my custom .barracuda.cnf settings since BOA 2.0.8 (?).
_PHP_MODERN_ONLY=YES
_PHP_FPM_VERSION=5.3
_PHP_CLI_VERSION=5.3
I set these to:
_PHP_MODERN_ONLY=NO
_PHP_FPM_VERSION=5.2
_PHP_CLI_VERSION=5.2
How do I install php 5.2x for legacy D5 sites and D6 modules with the latest BOA 2.0.8 on a newly provisioned server? Do I need to use BOA 2.0.5 and what's the best way to install an older version of BOA, if yes.
The custom config worked fine in previous versions of BOA where I have D5 sites running on php 5.2x and I've read each of the following:
http://omega8.cc/boa-208-edition-255
http://omega8.cc/boa-207-edition-254
http://omega8.cc/boa-206-edition-253
Comments
Comment #1
Mojah commentedI edited o1.octopus.cnf after running the installer and set the php variables to 5.2 then ran
octopus up-stable o1which appeared to work, but I'm still unable to verify the D5P platform due to php syntax errors. Then I checked the o1.octopus.cnf file after the upgrade and _PHP_FPM_VERSION and _PHP_CLI_VERSION was back to 5.3.Can you point me out to a doc/commit comment which hints on how to resolve php 5.2 installation with the latest BOA?
cat /var/aegir/config/includes/barracuda_log.txt
cat /var/aegir/install.log
cat /root/.barracuda.cnf
cat /root/.o1.octopus.cnf
Comment #2
snlnz commentedBe much nicer if you use pastebin to post your logs in future. :)
In any event, php 5.2 is no longer supported in BOA 208 so yes you will need to use an older version of BOA as you suggested in order to get it installed.
On a side note, the only unsupported behaviour is the excessive error reporting that php produces no functionality is diminished that I'm aware of.
Correct me if I'm wrong?
Another note would be, why are you still using D5? shouldn't you be looking to update those sites over forcing older technology into place? Just a thought.
Comment #3
omega8cc commentedIt is not possible to install and use PHP 5.2 with BOA stable and also it is not possible to install older BOA version (at least not yet - there is a feature request).
I think that we shouldn't overwrite these settings to force PHP 5.3 only, if these options are still present and *could* be used, if not overwritten.
While running PHP 5.2, not to mention Drupal 5 is really bad idea, we should still allow to override BOA new defaults with old settings to get PHP 5.2 installed and available to use both in D5 and D6 sites - if you know what are you doing, of course, because we can't guarantee that PHP 5.2 will still work, once we stopped re-building it on upgrades.
Comment #4
Mojah commented@snlzn thank you. I'll be sure to use paste bin next time. From what I can tell, the D5 platform won't verify on Aegir. Agreed, it's much better to upgrade, but some of the non-profits and NGOs we sponsor/support don't have the budget for that right now. Most of them are content with their D5 sites because they use it for basic purposes, so they don't have a good enough reason to upgrade.
@omega8cc thank you. Yup, the overrides allowed in previous versions of BOA would help, but better yet some way to run older versions of BOA so we would not have to be concerned about breaking the php-fpm server with upgrades. Do you guys still support clients with legacy sites?
Comment #5
omega8cc commented@Mojah - we do support legacy systems, because removing previously available service is not an option, but we have prepared our clients during the last year that we will progressively switch everything to modern PHP, so they should upgrade as soon as possible. I feel it is OK to give at least few months for this, but these months already passed, and we will notify clients that their legacy sites will stop working after a deadline, once announced, because we can't keep outdated and insecure service running forever.
Comment #6
Mojah commentedSorry for taking this off topic, but this may be of use for people in a the same situation as me.
We have D5 running under BOA 2.0.8 using this patch. See: http://drupal.org/node/1016008#comment-7137910
Make sure to use the dev version of D5
And then we need to run...
for i in `find . -name *.info`; do echo "$i";grep -v "Information added by drupal.org packaging script" $i>$i;echo "-----------------------";done...inside the sites/all/modules folder and in the case of multi-sites, within each of the sites modules folder. The syntax/formatting in Drupal 5 .info results in php 5.3 errors and Aegir won't verify the site unless the above code is run.
@snlzn - once the patch and info files are fixed, yes D5 runs fine with php 5.3x.
@omega8cc - I appreciate so much the work you guys have done with BOA. It would take me hours to manually provision a server and now I get it done in a matter of 20mins. Besides all the cost savings, we also use less hardware and thereby have a smaller carbon footprint. Thank you.
Feedback about legacy support.
If I were a client and I loved the service you guys provided, I would be hurt if you "forced" me to upgrade by not supporting my outdated website. I'm running a wildlife rehabilitation center and our sponsored website does everything we need, as it is. I see no reason to upgrade. (I'm using one of the NPOs we support as an example)
This may not be the case with your clients and maybe they have already all upgraded, but if there is even one client who cannot upgrade for whatever reason, please go out of your way to keep her.
Comment #7
Mojah commentedSorry, bash code above does not work as expected. All module .info files needs to be edited for two things.
- Remove all occurrences of lines like "; Information added by drupal.org packaging script...."
- add quotes "" around the description string which sometimes contains the word "on" regarded as a boolean in php 5.3x
Comment #8
omega8cc commentedFixed in commits:
http://drupalcode.org/project/barracuda.git/commit/c27fdfc
http://drupalcode.org/project/barracuda.git/commit/c14988c
http://drupalcode.org/project/barracuda.git/commit/a8a28b0