upgrading from 1.5.0 to 1.5.1 fails at backup

[falko]

Hi,

when I try to upgrade to 1.5.1 it fails at the database backup
(running Debian 8.10 & FOG 1.5.0)

• Setting up Apache virtual host (no SSL)…OK
  sed: can’t read /etc/php/5/fpm/pool.d/www.conf: No such file or directory
• Starting and checking status of web services…OK
• Changing permissions on apache log files…OK
• Backing up database…Failed!,

---

[davido38]

Debian 8
Fog 1.5.0

Same error for me when i try to update to 1.5.1

[Tom Elliott]

I’ll see if I can come up with a hack-patch solution. With php-fpm becoming a normal use case requirement, I coded php-fpm to be able to be used. However, I forgot to take account of php5 based setups such as debian 8. (As far as I know this should only impact debian based installations which use the php5 vs, php7.x formats and where php-fpm would be under /etc/php5/fpm.

[falko]

@tom-elliott thanks

[Tom Elliott]

@falko Mind trying:
git checkout working; cd bin; ./installfog.sh -y

I don’t have a debian 8 based system handy quite yet so this would be useful.

[falko]

@tom-elliott that was quick! Upgrade seemed to go through fine.

[Tom Elliott]

@falko Don’t let my wife tell you…I’m always quick when I can lol.

[davido38]

ok for me ! Thanks a lot !!!

just have this message

You are not running the most current version of FOG!
You are currently running version: 1.5.1

[Tom Elliott]

Updated working, dev-branch, and master with this change and updated the tag to point accordingly, thanks letting me know.

[Tom Elliott]

@davido38 Version should be correct now as well. That’s just an update on the main fogproject.org site.

[falko]

@tom-elliott strangley my fog clients all reported Middleware::Response ERROR: so I reset encryption on my ‘all hosts’ group. Not sure if there was something else I needed/should have done but that sorted it.

[Hanz]

@tom-elliott Using Fedora 26 still failing with working branch and master…was working with 1.5.0 though. I’ll also add that I can create a backup via GUI just fine and this only occurs during installation.

**Extra information. I tried running the installer with the -X option to continue on fail. After finishing with backup db…failed being the only error, I try going to GUI and get

Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

Error differs slightly

* Setting up Apache virtual host (no SSL).....................OK
 * Starting and checking status of web services................OK
 * Changing permissions on apache log files....................OK
 * Backing up database.........................................Failed!
[root@fog-server bin]#

Running MariaDB 10.1.32

[Wayne Workman]

@Tom-Elliott concerning Hanz issue, I am unsure if it’s related or not but all of my Fedora tests failed last night: http://theworkmans.us:20080/fog_distro_check/installer_dashboard.html

[Wayne Workman]

@hanz Check the status of the mysql / mariadb service. See what it says. Try to access it with the -h option. Specify both localhost and 127.0.0.1 Try both:
mysql -h 127.0.0.1 -D fog
mysql -h localhost -D fog

[Hanz]

@wayne-workman Both are working from server with additional -u root -p options (since I have password)

[Wayne Workman]

@hanz Can you figure out your PHP version please?

[Hanz]

@wayne-workman

PHP 7.1.16 (cli) (built: Mar 28 2018 07:11:55) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.1.0, Copyright (c) 1998-2018 Zend Technologies
    with Zend OPcache v7.1.16, Copyright (c) 1999-2018, by Zend Technologies

[Wayne Workman]

@hanz Any errors in the apache error log when you try to run the upgrade?

[Hanz]

@wayne-workman

none other than my 3000 hosts complaining about not being able to connect to backend at 127.0.0.1

[Wayne Workman]

@Tom-Elliott that’s the same error I have in my test VMs:

[Tue Apr 10 02:04:17.644043 2018] [proxy_fcgi:error] [pid 17902] [client 10.0.0.22:51312] AH01079: failed to make connection to backend: 127.0.0.1

Considering that Fedora VMs on working, dev-branch, and master all failed the exact same way on the same day and that @Hanz is having the same issue, this must be a Fedora problem.