This is not a duplicate post. Omega8cc asked me to split my original support request issue in to separate issue posts (http://drupal.org/node/1551136#comment-5932720), one for each issue I was dealing with. If you want the whole story, you can find it in http://drupal.org/node/1551136.
My Setup and Background
I'm working on an Ubuntu 10.04 LTS 64bit Linode VPS with 80GB total storage (67 GB used, 13 GB Available, most space used is from site backups), 2 GB RAM.
Here is a link to the
This is not exactly a duplicate post. Omega8cc asked me to split my original support request issue in to separate issue posts (http://drupal.org/node/1551136#comment-5932720), one for each issue I was dealing with. If you want the whole story, you can find it in http://drupal.org/node/1551136.
My Setup and Background
I'm working on an Ubuntu 10.04 LTS 64bit Linode VPS with 80GB total storage (67 GB used, 13 GB Available, most space used is from site backups), 2 GB RAM.
Here is a gist.github.com link to the
BOA files for before upgrading to BOA HEAD as of 3/31/2012
and a gist.github.com link to
BOA files after upgrading to latest version of BOA HEAD as of 4/27/2012
for the following files:
/var/aegir/config/includes/barracuda_log.txt
/data/disk/user/log/octopus_log.txt
/var/aegir/install.log (password removed)
/root/.barracuda.cnf
/root/.USER.octopus.cnf
Also here are links to:
Barracuda and Octopus Script Output
Problem: Config Files Get Overridden upon Upgrade
When I run the latest version of BOA HEAD my custom settings in the following files
- /etc/mysql/my.cnf
- /opt/etc/php.ini
- /usr/local/lib/php.ini
- /opt/local/etc/php53.ini
are being overridden by Barracuda even though I have touched the following files to prevent my custom settings from being overridden.
- /etc/mysql/custom.my.cnf
- /opt/etc/custom.php.ini
- /usr/local/lib/custom.php.ini
- /opt/local/etc/custom.php53.ini
- /opt/etc/custom.php53.ini
The Baracuda Changelog.txt file says the following:
* You can avoid overwriting /etc/mysql/my.cnf with empty
control file: $ touch /etc/mysql/custom.my.cnf
* You can avoid overwriting /opt/etc/php.ini on upgrade
with empty control file: $ touch /opt/etc/custom.php.ini
* You can avoid overwriting /usr/local/lib/php.ini on upgrade
with empty control file: $ touch /opt/etc/custom.php.ini
* You can avoid overwriting /opt/local/etc/php53.ini on upgrade
with empty control file: $ touch /opt/etc/custom.php53.ini
And this is exactly what I've done. In fact, I added extra touch files in the locations of the actual config files for the php.ini files because just putting them in /opt/etc directory was not working.
Thanks for any and all help in advance. I truly appreciate it!
Steve
Comments
Comment #1
omega8cc commentedYou are reading changelog for BOA-2.0.2 which doesn't apply to BOA HEAD. Please read and use the options explained in the config section: http://drupalcode.org/project/barracuda.git/blob/HEAD:/BARRACUDA.sh.txt#...
Note, if those options are already present in your
/root/.barracuda.cnffile, you must edit them there before running another upgrade. All of them - _CUSTOM_CONFIG_SQL, _CUSTOM_CONFIG_PHP_5_2 and _CUSTOM_CONFIG_PHP_5_3 are set to NO, so you must change them to YES to avoid overwriting your PHP and/or SQL config.Comment #2
omega8cc commentedHowever, it doesn't work as expected. We check if the control files exists on upgrade to convert them into config options, but only when those new config options are already present, so it would work only on the next upgrade, which doesn't make any sense, so it is a bug.
Comment #3
omega8cc commentedFix committed: http://drupalcode.org/project/barracuda.git/commit/9649d64
Thanks!
Comment #4
wickwood commentedOk, now I get it. And of course it now works as expected.
Based on the answer you gave me on a previous issue, I assume that there is currently no way to prevent the override of /var/aegir/config/server_master/nginx.conf when Nginx gets upgraded. Correct?
I went through all the configuration options in the lastest version of Barracuda and I didn't see anything related to nginx.conf file (although you and I both know I'm not the most observant guy in the world!)
Thanks again for all your help!
Steve
Comment #5
omega8cc commentedIt is not possible to avoid overwriting
nginx.confand we can't allow this, because it could introduce fatal issues. You can still override it manually after upgrade, if you need for some reason, but it should be re-created on every upgrade to keep the main config in sync with all new options.Comment #6
wickwood commentedThe only reason I need to change the
nginx.conffile is so thatclient_max_body_sizematches thepost_max_sizeandupload_max_filesizein thephp.inifiles.This was discussed in the issue Nginx / PHP Upload file limitation.
Thanks for explaining why it can't be done. I'll just make sure to keep that on my to-do list when I do any upgrades. At least now I only have 1 file to edit!
Thanks again for your help!
Steve
Comment #7.0
(not verified) commentedChanged some formatting to help readablity