## System Maintenance Today

As a follow-up to this test yesterday, I just performed a reboot of the home-computer that acts as my Web-server, and that I name ‘Phoenix’ on my LAN. Unlike how it was yesterday, the reboot took place effortlessly tonight, requiring less than 5 minutes to complete, and undertaken around 21h20.

Again, my purpose was just to determine, whether a reboot would work, and again, there was a plausible reason why it might not have. Luckily, this one worked on the first try.

## System Maintenance Today, Downtime

I take the somewhat unusual approach, Of hosting this Web-site, and therefore also my blog, on my personal computer at home. Therefore, any downtime of my home computer, also affects the visibility of the blog. And, as long as the actual Web-server is not online, I also cannot make it display a maintenance-mode page.

Just in recent days, I took the more-unusual step, of running the command:


root@Phoenix:/home/dirk# update-initramfs -u -k 3.18.0-14-generic




root@Phoenix:/home/dirk# update-initramfs -u -k 3.16.0-4-amd64



While it seemed nice for some time, to be running a kernel-version named ‘3.18.0-14-generic’, the mainstream version which a Debian / Jessie system is supposed to be running, is ‘3.16.0-4-amd64′. So, while the mainstream kernel had been receiving regular updates, I was running a kernel, which had not been receiving any updates, for years now. This helped reduce the number of reboots which I needed to carry out, due to frequent updates on the ‘3.16.0’ kernel.

But just because this was the first time in ages, that I had run the ‘update-initramfs’ command on the running kernel, I next needed to attempt a reboot, just to see whether the computer could still boot.

Therefore, readers would have experienced problems accessing my blog or site, from about 16h40 until about 17h10 today.

And No, My system Failed to Reboot.

## Routine Kernel Update Today, Downtime

I host this site on a Debian / Jessie (Linux) computer, which I name ‘Phoenix’. Through the package manager, it receives routine kernel updates, and today was a day on which it received one.

Even on a Linux computer, a kernel update generally requires a reboot, which I carried out.

But, because This computer is also my Web-server, and the host to my blog, that means that for a few minutes my site and blog were offline – i.e., unavailable to readers. This was happening from approximately 19h45 until 19h55.

I apologize for any inconvenience.

For what it’s worth, I consider this to have been one of the least-troublesome reboots, that I’ve had to carry out over the years.

Dirk

This computer is a Debian / Jessie (Linux) system. Just today, it mainly received an update to its ‘libc‘ libraries, that comprised 16 packages. These libraries are essential to the core of how every program works. Therefore, even though it is a Linux system, it needed a reboot.

The update seems to have gone smoothly, but because this computer is also my Web-server, my site and blog would have been offline from about 20h30 until 20h45.

It is also not feasible for me to display a Maintenance Mode page during such a time, because a Web-server would need to be running, in order actually to display a Maintenance Mode page.

I apologize for any inconvenience this 15-minute interval may have caused to my readers, but it was essential.

Also, because this was a full reboot of my host-machine, my ‘memcached‘ (server-side) caching daemon was restarted, for which reason the most-favorite postings retrieved by my readers will be a bit slow to fetch for some time.

Sorry again,

Dirk