Today, the computers I name ‘Phoenix’ and ‘Klystron’ received major updates to their core ‘libgcc’ and ‘libstdc++’ libraries, as part of a combination of 25 actually-updated packages. Even though this did not upgrade the (Linux) Debian version of either O/S, which is still ‘8.10’ , This type of an upgrade requires a reboot. So I rebooted.

But, The PC which I name ‘Phoenix’ is also my Web-server. Therefore, there is no way for my blog or site to be visible to the Internet, during a reboot. My blog was offline from 20h15 until 20h25.

I apologize for any inconvenience this might have been to my readers.

Dirk

## System Update Today, Downtime

I take the unusual measure, of hosting my Web-site, and therefore also this blog, on a PC running at home. The PC I use is the Debian / Jessie (Linux) computer I name ‘Phoenix’.

This morning, I installed a major set of updates on this computer, which included 137 packages, and doing so, brought it from Debian version 8.9 to version 8.10 .

But, because this PC is also my Web-server, the required reboot also meant, that the site was offline from about 10h20 until about 10h30.

I apologize for any inconvenience.

BTW, ‘Phoenix’ had been Up, for 62 straight days.

It’s too early really to tell, whether this large an update has affected reliability adversely, but they usually do not. So for now, I’m counting this as a successful update.

Dirk

## Routine Desktop Session Restart

According to This Earlier Posting, the ‘unattended-upgrades‘ package updated a whole slew of MySQL packages this morning, that of course form the most important database engine on this machine (‘Phoenix’). As an automated part of the process, the update restarted the MySQL Server process, which runs as a system service.

However, the way KDE works, it has an Akonadi Server for ‘PIM’ (Personal Information Management), which runs its own, local MySQL database engine, as part of the user session, which is of course not restarted automatically, because to do so would also interfere strongly with a running session.

And yet, this latter process can also be brought up-to-date, by just logging out the (graphical) desktop session, and logging back in again. Doing so should not affect any of the system processes, which either run as ‘root‘, or which run as a vestigial, system user-name. Likewise, doing so should not affect the Web-server.

Hence, to bring my session up-to-speed, I performed this logout / login successfully and without ado, which actually took from 15h15 until 15h25.

Yet, there was An Earlier Situation, in which an attempt to do the same thing went wrong.