Upgrade from 16LTS to 18LTS breaks Apache2

[Poldi]

Just upgraded one of our servers from 16-LTS to 18-LTS, which broke Apache (the website that worked prior to the upgrade now displays
-----------
setStart($startTime, $startMem)->mark('afterLoad') : null; // Instantiate the application. $app = JFactory::getApplication('site'); // Execute the application. $app->execute();
-----------
Nothing really in any of the logs that sheds light on what may be wrong
After further investigation I found the Apache php7_module seems to have has disappeared during the upgrade . I fixed the issue on this one server by following the instructions from here https://www.vultr.com/docs/how-to-install-and-configure-php-70-or-php-71-on-ubuntu-16-04 which fixed the issue

I just upgraded another server, and and have found a similar issue. This time the php7_module is there (although the version of php is now 7.2) , but the website is down with now indication as to what is wrong

[Poldi (poldi)]

Something else I just noticed. The first server (the one I manually installed the php packages needed for Apache2) is on PHP 7.0.30.

The second server before the upgrade is also on PHP 7.0.30. When I do the upgrade on this server, no additional packages need to be installed, but the PHP version is 7.2. The 2 severs should be pretty much identical, so don't know why this is.

Sorry to be so vague, but the second server is the production server so I had to restore from backup and don't have much more info

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1787886/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Poldi (poldi)]

Before the upgrade I collected the following
-----------------------------------------------------------
llist@dc1:~$ sudo apache2ctl -M
[sudo] password for llist:
Loaded Modules:
 core_module (static)
 so_module (static)
 watchdog_module (static)
 http_module (static)
 log_config_module (static)
 logio_module (static)
 version_module (static)
 unixd_module (static)
 access_compat_module (shared)
 alias_module (shared)
 auth_basic_module (shared)
 authn_core_module (shared)
 authn_file_module (shared)
 authz_core_module (shared)
 authz_host_module (shared)
 authz_user_module (shared)
 autoindex_module (shared)
 deflate_module (shared)
 dir_module (shared)
 env_module (shared)
 filter_module (shared)
 headers_module (shared)
 mime_module (shared)
 mpm_prefork_module (shared)
 negotiation_module (shared)
 php7_module (shared)
 rewrite_module (shared)
 security2_module (shared)
 setenvif_module (shared)
 socache_shmcb_module (shared)
 ssl_module (shared)
 status_module (shared)
 unique_id_module (shared)
llist@dc1:~$ ls -lsa /etc/apache2/mods-enabled/
total 8
4 drwxr-xr-x 2 root root 4096 Jun 5 02:38 .
4 drwxr-xr-x 9 root root 4096 Jul 31 23:11 ..
0 lrwxrwxrwx 1 root root 36 Nov 17 2016 access_compat.load -> ../mods-available/access_compat.load
0 lrwxrwxrwx 1 root root 28 Nov 17 2016 alias.conf -> ../mods-available/alias.conf
0 lrwxrwxrwx 1 root root 28 Nov 17 2016 alias.load -> ../mods-available/alias.load
0 lrwxrwxrwx 1 root root 33 Nov 17 2016 auth_basic.load -> ../mods-available/auth_basic.load
0 lrwxrwxrwx 1 root root 33 Nov 17 2016 authn_core.load -> ../mods-available/authn_core.load
0 lrwxrwxrwx 1 root root 33 Nov 17 2016 authn_file.load -> ../mods-available/authn_file.load
0 lrwxrwxrwx 1 root root 33 Nov 17 2016 authz_core.load -> ../mods-available/authz_core.load
0 lrwxrwxrwx 1 root root 33 Nov 17 2016 authz_host.load -> ../mods-available/authz_host.load
0 lrwxrwxrwx 1 root root 33 Nov 17 2016 authz_user.load -> ../mods-available/authz_user.load
0 lrwxrwxrwx 1 root root 32 Nov 17 2016 autoindex.conf -> ../mods-available/autoindex.conf
0 lrwxrwxrwx 1 root root 32 Nov 17 2016 autoindex.load -> ../mods-available/autoindex.load
0 lrwxrwxrwx 1 root root 30 Nov 17 2016 deflate.conf -> ../mods-available/deflate.conf
0 lrwxrwxrwx 1 root root 30 Nov 17 2016 deflate.load -> ../mods-available/deflate.load
0 lrwxrwxrwx 1 root root 26 Nov 17 2016 dir.conf -> ../mods-available/dir.conf
0 lrwxrwxrwx 1 root root 26 Nov 17 2016 dir.load -> ../mods-available/dir.load
0 lrwxrwxrwx 1 root root 26 Nov 17 2016 env.load -> ../mods-available/env.load
0 lrwxrwxrwx 1 root root 29 Nov 17 2016 filter.load -> ../mods-available/filter.load
0 lrwxrwxrwx 1 root root 30 Jun 5 02:38 headers.load -> ../mods-available/headers.load
0 lrwxrwxrwx 1 root root 27 Nov 17 2016 mime.conf -> ../mods-available/mime.conf
0 lrwxrwxrwx 1 root root 27 Nov 17 2016 mime.load -> ../mods-available/mime.load
0 lrwxrwxrwx 1 root root 34 Nov 17 2016 mpm_prefork.conf -> ../mods-available/mpm_prefork.conf
0 lrwxrwxrwx 1 root root 34 Nov 17 2016 mpm_prefork.load -> ../mods-available/mpm_prefork.load
0 lrwxrwxrwx 1 root root 34...

[Poldi (poldi)]

php7.x-curl is also missing and needs to be manually installed after the upgrade

[Brian Murray (brian-murray)]

Are the log files from the upgrade available? If you used do-release-upgrade they'd be found in /var/log/dist-upgrade/.

[Poldi (poldi)]

Logs are attached

[Andreas Hasenack (ahasenack)]

Resseting to new as logs were provided.

[Andreas Hasenack (ahasenack)]

The php release upgrade is a bit odd indeed, or so I think. If you have the versioned packages installed only (like php7.0-curl without php-curl), then the release upgrade might not update those packages, and even remove some. One should always pay close attention to what the release upgrade tool is telling you when it gives a summary of the actions it is going to take.

I'm not familiar with php packaging, so I don't know if this is a known issue or not.