Missing nginx-upload-progress-module can break install and upgrade

Yes, it is running. I should have mentioned that the sites of my octopus user are accessible normally. It is just the admin panel for octopus (and the master instance) not available.

settings.php from the aegir master instance look correct also. I can connect with the db user, and inside the variable table everything looks fine.

Unfortunately i did not enable debug, and just found the option. However, i have made a snapshot before the upgrade, and will now revert back, and do the barracuda + octopus upgrade with debug enabled again.

Where will i find the log's?

Thanks for the info!

This is weird. After i rolled back to an earlier snapshot, changed the configs to reflect DEBUG = TRUE, it went through without errors. Just like before. However, the web panel was accessible this time. I did not change anything else.

The only thing that came up (before aswell), is that nginx could initially not be startet. It said there were unknown configuration directives.

I had to comment the following lines:

line 79 /var/aegir/config/includes/nginx_advanced_include.conf

location ^~ /progress {
  access_log off;
#  report_uploads uploads;
}

line 503 /var/aegir/config/includes/nginx_advanced_include.conf

location ~* ^/index\.php$ {
  add_header    X-Header "Barracuda Engine 1.0 Turbo";
  add_header    X-Device "$device";
  try_files     $uri =404;      ### check for existence of php file first
  fastcgi_pass  127.0.0.1:9000; ### php-fpm listening on port 9000
#  track_uploads uploads 60s;    ### required for upload progress

and the same for /data/disk/myuser/config/includes/nginx_advanced_include.conf

Is there a module/plugin missing for nginx?

Please find attached the two log files. If you need more info please let me know.

This makes perfect sense and explains that it was working the second time around. Are there any plans to download the packages earlier in the installation/upgrade state, so that it cancels the install in a 404 case?

Here is my nginx -V

nginx: nginx version: Barracuda/1.0.8
nginx: built by gcc 4.4.5 (Debian 4.4.5-8) 
nginx: TLS SNI support enabled
nginx: configure arguments: --prefix=/usr --sbin-path=/usr/sbin/nginx --conf-path=/etc/nginx/nginx.conf --error-log-path=/var/log/nginx/error.log --http-log-path=/var/log/nginx/access.log --pid-path=/var/run/nginx.pid --lock-path=/var/lock/nginx.lock --user=www-data --group=www-data --with-http_realip_module --with-http_gzip_static_module --with-http_stub_status_module --with-http_ssl_module --without-mail_pop3_module --without-mail_imap_module --without-mail_smtp_module --without-http_ssi_module --without-http_scgi_module --without-http_uwsgi_module --with-debug --with-ipv6

Attached you will find the two log files.

Thanks for the explanation. I dont have a solution to the problem you stated, thats indeed something out of our hands. Maybe it is time to run a (cloned) repository network (with a dns like aegir.cc) with some mirrors to try to keep packages needed for BOA available? I would be happy to donate and maintain a fast mirror in europe for BOA.

In my case, can i simply rerun the parts of the BARRACUDA installer ( 2664 if [ $_NGINX_INSTALL_REQUIRED = "YES" ] ; then .... ) and rebuild nginx manually? Will it kill my config files?

Great, thanks for the info! :)