Issues after upgrading to 16.04

[Tom]

So I followed the steps 1-6, when running the installer, apache is failed to install.

[Tom]

When trying to install apache2 , I get broken package.

Frustrating!!

[EAHarvey]

@Tom Did you try the commands I talked about earlier.

sudo apt purge php*
sudo apt purge apache*
sudo rm -rf ‘/etc/apache*’ ‘/etc/php*’
sudo apt-get autoremove

Along with the #COMMENT out the entire PACKAGES LINE in fogsettings. So in front of the entire line. (#PACKAGES)

I know you have probably done this too but make sure all is updated.

sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade

I would also make sure you have all the updates release info.

sudo do-release-upgrade.

Once this has all been done then reboot (sudo shutdown -r now) and rerun the ./installfog.sh and see what happens.

[Tom]

@EAHarvey I’ve done it all, once apache2 got broken, I could not fix it.
Thanks!

[Quazz]

@Tom Please put the output of

dpkg --get-selections | grep hold

here

[Wayne Workman]

So - I just spun up a brand-new Ubuntu 16 Server VM, updated it, and installed RC-10 on the first try with zero problems.

We typically warn people against upgrading Linux Distributions to another newer major version for use with FOG. It never goes well, this is a good example of why we recommend against it.

I’m going to guarantee that your problems are either being caused by imperfections in the upgrade process from 14 to 16, or by grandfathered-in settings, or by PHP 5.x being mixed with PHP 7.x

All the below instructions assume you are root - proper. Become root properly first with:
sudo -i

Along the lines of what @EAHarvey said about updating, I’d recommend running this line to do that, it’s a more aggressive version that will also clean out things that aren’t needed too.
apt-get update -fy;apt-get upgrade -fy;apt-get dist-upgrade -fy;apt-get autoremove

The next thing to try is simply running the commands the installer would run, but manually. These are them, just copy/paste and give us the results:

a2enmod php
a2enmod rewrite
a2enmod ssl
a2ensite "001-fog"

The next thing to try is deleting the .fogsettings file and then forcing the installer to use PHP7 as we used to do when we had issues with Ubuntu 16, Do that with these commands:

#Go to your fogproject repo's bin directory first#
rm -f /opt/fog/.fogsettings
apt-get purge php*
apt-get purge apache*
rm -rf ‘/etc/apache*’ ‘/etc/php*’
apt-get autoremove
php_ver='7.0' php_verAdds='-7.0' ./installfog.sh -y

Here’s some of my configuration files from Ubuntu 16, does yours look like this? If you run each of the commands in red, it’ll output the file.

cat /etc/apache2/sites-enabled/001-fog.conf

<VirtualHost *:80>
	KeepAlive Off
	ServerName 10.0.0.12
	DocumentRoot /var/www/
	#RewriteEngine On
	#RewriteRule /management/other/ca.cert.der$ - [L]
	#RewriteRule /management/ https://%{HTTP_HOST}%{REQUEST_URI}%{QUERY_STRING} [R,L]
</VirtualHost>

cat /etc/apache2/sites-available/001-fog.conf

<VirtualHost *:80>
	KeepAlive Off
	ServerName 10.0.0.12
	DocumentRoot /var/www/
	#RewriteEngine On
	#RewriteRule /management/other/ca.cert.der$ - [L]
	#RewriteRule /management/ https://%{HTTP_HOST}%{REQUEST_URI}%{QUERY_STRING} [R,L]
</VirtualHost>

cat /etc/apache2/apache2.conf

# This is the main Apache server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.4/ for detailed information about
# the directives and /usr/share/doc/apache2/README.Debian about Debian specific
# hints.
#
#
# Summary of how the Apache 2 configuration works in Debian:
# The Apache 2 web server configuration in Debian is quite different to
# upstream's suggested way to configure the web server. This is because Debian's
# default Apache2 installation attempts to make adding and removing modules,
# virtual hosts, and extra configuration directives as flexible as possible, in
# order to make automating the changes and administering the server as easy as
# possible.

# It is split into several files forming the configuration hierarchy outlined
# below, all located in the /etc/apache2/ directory:
#
#	/etc/apache2/
#	|-- apache2.conf
#	|	`--  ports.conf
#	|-- mods-enabled
#	|	|-- *.load
#	|	`-- *.conf
#	|-- conf-enabled
#	|	`-- *.conf
# 	`-- sites-enabled
#	 	`-- *.conf
#
#
# * apache2.conf is the main configuration file (this file). It puts the pieces
#   together by including all remaining configuration files when starting up the
#   web server.
#
# * ports.conf is always included from the main configuration file. It is
#   supposed to determine listening ports for incoming connections which can be
#   customized anytime.
#
# * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/
#   directories contain particular configuration snippets which manage modules,
#   global configuration fragments, or virtual host configurations,
#   respectively.
#
#   They are activated by symlinking available configuration files from their
#   respective *-available/ counterparts. These should be managed by using our
#   helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See
#   their respective man pages for detailed information.
#
# * The binary is called apache2. Due to the use of environment variables, in
#   the default configuration, apache2 needs to be started/stopped with
#   /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not
#   work with the default configuration.


# Global configuration
#

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE!  If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the Mutex documentation (available
# at <URL:http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
#ServerRoot "/etc/apache2"

#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
Mutex file:${APACHE_LOCK_DIR} default

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 5


# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off

# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog ${APACHE_LOG_DIR}/error.log

#
# LogLevel: Control the severity of messages logged to the error_log.
# Available values: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the log level for particular modules, e.g.
# "LogLevel info ssl:warn"
#
LogLevel warn

# Include module configuration:
IncludeOptional mods-enabled/*.load
IncludeOptional mods-enabled/*.conf

# Include list of ports to listen on
Include ports.conf


# Sets the default security model of the Apache2 HTTPD server. It does
# not allow access to the root filesystem outside of /usr/share and /var/www.
# The former is used by web applications packaged in Debian,
# the latter may be used for local directories served by the web server. If
# your system is serving content from a sub-directory in /srv you must allow
# access here, or in any related virtual host.
<Directory />
	Options FollowSymLinks
	AllowOverride None
	Require all denied
</Directory>

<Directory /usr/share>
	AllowOverride None
	Require all granted
</Directory>

<Directory /var/www/>
	Options Indexes FollowSymLinks
	AllowOverride None
	Require all granted
</Directory>

#<Directory /srv/>
#	Options Indexes FollowSymLinks
#	AllowOverride None
#	Require all granted
#</Directory>




# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives.  See also the AllowOverride
# directive.
#
AccessFileName .htaccess

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<FilesMatch "^\.ht">
	Require all denied
</FilesMatch>


#
# The following directives define some format nicknames for use with
# a CustomLog directive.
#
# These deviate from the Common Log Format definitions in that they use %O
# (the actual bytes sent including headers) instead of %b (the size of the
# requested file), because the latter makes it impossible to detect partial
# requests.
#
# Note that the use of %{X-Forwarded-For}i instead of %h is not recommended.
# Use mod_remoteip instead.
#
LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %O" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

# Include of directories ignores editors' and dpkg's backup files,
# see README.Debian for details.

# Include generic snippets of statements
IncludeOptional conf-enabled/*.conf

# Include the virtual host configurations:
IncludeOptional sites-enabled/*.conf

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet

[Tom]

@Wayne-Workman Thank you so much. I had to revert back to 14.04 since I could not leave it non functional - we use it on a daily basis.
I would really appreciate if it can be summarized into one simplified (as possible) list of steps that will result in successful upgrade. It feels like the more I try to fix it, it gets further away from success.

Would it be easier to backup all fog settings and images, build new 16 server, install fog and restore?

If none of this is possible, I will try again using your recent instructions.

Again, thank you all for being out there supporting…

Tom

[Wayne Workman]

@Tom I’d suggest staying on 14.04 - and moving to FOG Trunk.

[Tom]

@Wayne-Workman I think I’m on FOG trunk 1.3 RC10.
Thanks!

[Wayne Workman]

@Tom Then you’re good to go.

[Tom]

@Wayne-Workman The question is what should I do when I will need to upgrade to new OS. I’m not looking to stay on 14.04 forever
Is there a way to export\import fog settings and images?

[Wayne Workman]

@Tom Build a new server (use the same IP), install the latest FOG RC or release on it, and port over images and hosts. Copying over images is a simple six-command pow-wow. Getting image definitions and hosts is through the web interface. Host Management -> export, Image Management -> Export, and import on the new server. Then just moving over the certificates and all done.

Just change the old fog server’s IP address at CLI, imaging won’t work on it after this, but it’s fine. The new server shoud be given the old one’s IP address.

From the newly built server with FOG installed, just mount the old server’s images directory to a local directory and then copy them over.

mkdir /tempMount
mount x.x.x.x:/images /tempMount
cp -r /tempMount /images
umount /tempMount
chown -R fog:root /images
chmod -R 777 /images

Follow instructions here for moving your ssl stuff over to the new server - this is very important if you use the new FOG Client.
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#Maintain_Control_Of_Hosts_When_Building_New_Server

[Tom]

@Wayne-Workman Thank you so much!