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

 

What was unusual about this, was the fact that this was not the command:

 


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.

Continue reading System Maintenance Today, Downtime

Extreme Thunderstorm, Power Failure, Downtime

I take the unusual measure, of Hosting My Own Site and Blog, on my personal computer at home. This means that the availability of this blog, is only as good as the functionality of my PC.

Yesterday, August 22, 2017, we had an extremely powerful thunderstorm in the afternoon, which caused a power-failure to my home from 16h00 that afternoon, until 5h50 the next morning (August 23). Therefore, my site and blog were also offline until about 11h00, this morning, August 23.

I apologize for any inconvenience to my readers.

Dirk

 

Routine Power-Cut Since Yesterday

One development which this earlier posting foretold, was that my power-utility needed to do work on their power-lines, and they had informed me via an automated message, that my power would be cut between 12h30 and 15h30 today.

One of the details which I would not trust 100%, is the exact timing of such a power-cut. Furthermore, yesterday, before I went to bed, I felt like this morning, I might sleep in. Which I did.

This implied, according to my thinking last night, that I could get woken at 10h00 this morning, by a power-cut, which was intended to take place only as of 12h30. And so around 22h00 last night, I shut down my computers, and battened down the hatches otherwise, so that my home would be ready for a power-cut by then.

As far as I can tell, the power-cut did take place within the intended time-interval. So maybe, I could have left the computer running overnight after all, and just shut everything down this morning after getting out of bed. But I was not sure of this fortunate turn of events, last night.

And as it goes, I also saw no point ins staying home, if for some part of my afternoon I’d have no computers to play with. I left this morning to follow activities outside, and came back home after my power had already been restored.

So my site and blog were offline as of 22h00 last night, until about 16h50 this afternoon.

Greetings again,

Dirk

 

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