Stargate Logo

->  Stargate daily news 
Server upgrade Disks and OS release  
Posted by smurphy on Friday, 19 April 2019 - 19:42  GMT
spacer line
Stargate Icon

 The mail, web and DNS server has received new disks. The old 5400RPM 320Gbytes HDDs have been replaced by 1Tb SSD disks. This will allow to use larger quotas on the mail-server side, and will be specially faster for all requests that are ran on the server.

The day after the OS has been upgraded from Ubuntu 14.04 LTS to Ubuntu 18.04 LTS getting through Ubuntu LTS 16.04 LTS.
The main issues have been the passage from upstart to systemd, where some applications (mysql)_ could not be upgraded correctly as the upgraded needed to run mysql_upgrade, but the upgrader did shut down mysql for the process. Hence - stopping the upgrader just after he stopped the mysql-server, in another terminal, starting the mysqld, and then sending the CONT signal to the ugprader made the trick.
The second issue was apparmor and some applications not working correctly (bind9), had to be fixed by adding some special paths for bind9 to gather its data.
The mysql DB 5.7 is crap. Most application stopped working with it. Luckily I noticed that my dev environment using Mariadb 10.1 worked, so I tried upgrading the DB to mariadb 10.3 (10.2+ is required, as previous versions would not be compatible with mysql 5.7). That upgraded, all apps worked as before.
Luyckily dovecot, postfix, opendkim and the greylisting stuff were not impacted by the upgrade. Apparently admins of these installations don't like upgrades to mess with all this.
Lessons learned: Next developments will make sure the applications are running inside docker containers. This way - an OS Update will not impact any of the settings.  

Comments below
Database not dockerized by admin @ 2019-09-11 17:03:38
 Because some functions can't access the MySQL DB inside docker, and user ACL was becoming a nightmare. The strategy was changed to leave the DB running on the host system. So far the Web-Server including dynamic blacklisting is working as required. Scripts had to be adapted for the new locations etc.

Why the change? by smurphy @ 2019-09-11 17:04:26
 Why not connect all containers together to run it inside the docker environment alltogether?

Running system jobs by admin @ 2019-09-11 17:06:33
 Regular system jobs are running on the local host and require access to the DB. Interfacing with Docker call in front made some bail out. When using a local IP Address as host to connect mysql, most apps try to use the socket to connect to the DB and the communication fails.
When I figure this part out, I'll change it.


This page was issued from the Stargate Website:

The URL for this page is: