Braving the Bionic Beaver

closeHey, just so you know ... this post is now about 2 years old. Please keep that in mind as it very well may contain broken links and/or outdated information.

The NFL Draft is done (will the Browns overall #1 pick, Baker Mayfield, help them win at least one game this year?), the Lightning are in the second round of the Stanley Cup Playoffs (facing off against the Boston Bruins), the Cavs survived a seven game first round series against the Pacers, and one month of baseball is in the books (the Rays have won eight straight but are still close to last in the East, and the Indians are in first place in the Central). Yeah, it’s Spring in late April, which means it’s time for the latest Ubuntu LTS release, 18.04 Bionic Beaver.

Just like last time in October, the upgrade process itself was smooth: I issued the do-release-upgrade command and the whole process took just under 15 minutes to download the new packages and execute the reconfiguration. I then re-applied my customizations to a few configuration files, rebooted the server, and was back in business:

$ lsb_release -a
Distributor ID: Ubuntu
Description: Ubuntu 18.04 LTS
Release: 18.04
Codename: bionic

$ uname -a
Linux nucleus 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

But also like last time, I had a handful of post-upgrade, early adopter issues:

  • I had to enable the PHP 7.2 for Apache (a2enmod php7.2) so it wouldn’t serve up PHP files as plain text (I had this same issue last time)
  • I had to manually install the php7.2-xml package for (Piwigo and phpSysInfo)
  • I had to manually re-install the smbclient package (for Nagios)
  • Pulseway won’t start due to a “undefined symbol: CRYPTO_num_locks” error (forum post)
  • I had some errors in phpMyAdmin (due to the PHP 7.2 update) that I fixed with this manual patch (it’s also fixed in the latest release,
  • the Unifi controller wouldn’t start which turned out to be a problem with MongoDB being upgraded from 3.4 to 3.6. I had to downgrade back to 3.4 to get the controller running again, issue a db.adminCommand( { setFeatureCompatibilityVersion: "3.4" } ) command to get my database upgraded (it was actually still in a 3.2 structure), and then re-upgrade to 3.6. I also had to copy /usr/bin/mongod to /usr/bin/mongod.bin and create a workaround script named /usr/bin/mongod to get the controller to start (forum post)

Check back here in October for 18.10!

One Comment

Leave a Reply

Your email address will not be published. Required fields are marked *