I just used the standard highly automated upgrade script on an existing B2.0.1 install to upgrade it to B2.0.2. The install was originally on BOA-1.4S. I'm hosting my sites on platforms on the main Barracuda install rather than using Octopus, as the setting up of multiple FQDNs was distinctly unfun when I was trying to get everything working in the first place.
Anyhoo, edited my FQDN info and email address into the install script, ran it, everything reports back fine. It completes, and the Aegir server page returns a 102 connection refused error while the various hosted websites don't return anything at all. Checking nginx logs shows a repeated error similar to the following:
2012/02/11 14:26:01 [emerg] 30419#0: unknown directive "upload_progress" in /etc/nginx/conf.d/aegir.conf:105
No evident errors in the other log files. It's worth noting that despite the current and former scripts being set to PHP-FPM 5.2, PHP 5.3 is definitely also present on the system. I've also run aptitude full-upgrade at least once in the past owing to receiving repeated, daily emails from the system telling me to do this.
I can't see how to recover this - running the script again didn't help, and nor did rebooting the server. Would you recommend any other steps, or should I reinstall from scratch? I backed up all my sites before upgrading, so it's not the end of the world if necessary.
Comments
Comment #1
omega8cc commentedPlease follow the bug submission guidelines: http://drupal.org/node/add/project-issue/barracuda
Also, what is the output when you type
nginx -V?Finally, please read: http://groups.drupal.org/node/175804#comment-646423
Comment #2
omega8cc commentedAlso: http://drupal.org/node/1320206#comment-5161680
Comment #3
DanielJohnston commentedThanks for the response! The suggestion to mv /usr/sbin/nginx /usr/sbin/nginx-old and run Barracuda again did the trick. I've included the rest of the requested output anyway (from before I moved nginx and reran), but I'm marking this as fixed since it's all working again.
nginx -V output:
barracuda_log.txt contents:
install.log contents:
.barracuda.cnf contents:
VPS provider is Bytemark, root access VM with a moderate amount of memory and storage, using a Debian Squeeze install.
Comment #4
DanielJohnston commentedSigh. The install.log paste contained characters that zapped display on this site. I've created a paste of the above post at http://pastebin.com/AP4GYB0N but obviously your suggestion worked anyway, so it's only there if there's anything you want to explore further for your own interest. Thanks again for your help.
Comment #5
omega8cc commentedThank you.
To explain why it failed: the
nginx -Voutput didn't include expected--add-module=/var/opt/nginx-upload-progress-module/line. It was probably some edge case, since it looks like it failed to download this module from GitHub, while other modules have been downloaded without issues.However, Barracuda should then use Nginx config without
upload_progressdirective to avoid the error you reported. But even this would not help when it is an upgrade, since Octopus config may include upload_progress related location, so it would fail anyway, until the Nginx server is rebuild with this module again. This is also why it is always better to use Barracuda script to fix issues than trying to fix them manually.Anyway, I'm glad it worked this time.