Again, my blog went down due to a power failure.

Yesterday, on the Island Of Montreal, we were experiencing some extreme weather. And, I host my blog on my own, private computer, acting as server. Due to the power failure which already took place last night, my blog went down then. And I wrote about this in this previous blog posting.

That event left many tree branches hanging in the power lines, which stayed there overnight. But alas, this morning, my power failed again around 6h45. And then, to aggravate my nerves, the power came on again for two seconds around 7h00, after which it promptly went off again. And the power came on for another two seconds, around 7h15, after which it went off again.

Naturally, in this situation I could not assume, that even if the power would have come on again at let us say 7h30, it would have stayed on. And so I did not restart my server this morning.

Presumably, the Hydro-Quebec crews have cleared the branches from the power lines by now, without electrocuting their workers.

But this blog would only have started to become visible again, around 12h00 or so today.

I apologize for any confusion this might have caused.



My blog was down tonight due to a power failure.

This blog is being hosted privately, on my own computer, acting as server. And for this reason, it is sensitive to such factors as power failures. I do not have a backup server, nor a UPS, the way hosting services would have.

In Montreal, we have been having difficult weather, with sleet turning into genuine freezing rain. As a result, a power failure did hit me at 22h40 this evening. The blog should have started to become accessible again after 23h40.

The actual power failure only lasted for 10 minutes, from 22h40 to 22h50. But I only restart my computers after I am convinced that consecutive p0ower failures are unlikely. And during the coming day, on February 25, additional power failures are possible, because while the freezing rain is officially over, wind gusts up to 60 km/H are forecast.

Thank you for understanding.



My Blog was down for an update briefly.

In order to protect myself from security vulnerability CVE-2015-7547, affecting a broad range of ‘glibc’ libraries and discovered by Google, I performed a security update on this server within hours of the vulnerability being known. And of course this required a reboot, since the old version of glibc was still loaded by nearly every program running. Therefore, this Blog was offline from 22h10 until about 22h30.



My Server was just down for an Upgrade.

From 14h30 until 15h30, I needed to do some upgrading to the hardware of the computer which I name ‘Phoenix’.

Link To Previous Posting

This old computer from 2008 may be running the most powerful Linux version at my disposal, in 64-bit mode, and its dual-core CPU may clock up to 2.6GHz, but until now, it had still only possessed 2GB of RAM! This box still uses DDR2 RAM modules, and I had upgraded it from 2x 512MB to 2x 1GB in the year 2008. But what I needed to do today, was to upgrade it to 2x 2GB, finally giving it its maximum of 4GB of RAM.

This time around, I no longer felt I’d have the dexterity to prevent static damage to the RAM modules, just by controlling the sequence with which I touched parts. And so this time, I also felt I needed to use an actual anti-static bracelet.

Further, the CPU heat sink was plugged full of dust, so that the CPU fan was no longer able to push any cooling air through it. I knew for a long time that this also needed to be remedied, but had procrastinated in doing so. While I had the tower open today, I also took care of the dust in the CPU heat sink, with a bottle of compressed gas.

One reason I was not so eager to do this much-needed work, was the knowledge that if I had botched this, I’d have lost my one and only server. But I was also reminded, that if the server was to fail, because the CPU was consistently running too hot, the outage would take longer than 1 hour to fix. And so I finally chose the 1 hour preventative action.

I am glad that now the CPU is being cooled properly again, and that I finally have 4GB of RAM on this 64-bit machine.

Also, this was one situation in which I could not post a Maintenance Mode Notice on my blog, because for 1 hour, there was no server to render the Maintenance message screen.