RSS
Username:
Password:

Menu

Home
Résumé
Personal
Board
Webcam
Links
Members

Powered by Apache Web Server

Powered by Slackware Linux

Valid XHTML5!

Valid CSS!

June 27th, 2015

Running new server: Intel i7 5500U, 16GB RAM, 64-bit Slackware 14.1

Posted at 06:28:07 AM by froems

The old server, which served us well for almost a decade, finally burned out. Literally, the CPU heatsink seems to have gone bad and its CPU was running temperatures of 200+ degrees and constantly shutting down. So it was time to upgrade.

The new server is running a 64 bit version of Slackware 14.1, Apache 2.2.29, PHP 5.4.42. I rolled back udev from 182 to 165 because I was having the same problem with the new server seeing the RAID array.

I've spent the last week copying over everything from the old server to the new, and it looks like everything is working again.

Also, I saw that mod_perl 2.0.9 is finally out with Apache 2.4 support. I'll have to look into moving to Apache 2.4 now, when I have time.

May 2nd, 2015

Now running PHP 5.4.40

Posted at 03:31:13 PM by froems

I've upgraded PHP again and everything appears to be working.

Still no mod_perl for Apache 2.4.

April 9th, 2015

Now running PHP 5.4.39

Posted at 06:45:50 PM by froems

Upgraded PHP again. Everything seems to be working after the upgrade.

Still no mod_perl for Apache 2.4.

February 11th, 2015

Now running PHP 5.4.37

Posted at 10:01:20 PM by froems

Upgraded PHP once again. Everything seems to be running fine.

There's still no release version of mod_perl for Apache 2.4 yet. I'm starting to wonder if it will ever be released.

October 17th, 2014

Now running PHP 5.4.34

Posted at 04:54:24 PM by froems

New PHP version, patched some security holes, installed without any issues, blah blah blah.

October 7th, 2014

Now running Apache 2.2.29 and PHP 5.4.33

Posted at 05:45:49 AM by froems

I've upgraded the software to the newest versions yet again.

I still can't move to Apache 2.4, because mod_perl for Apache 2.4 still isn't a thing yet. I hear it should be ready Real Soon Now, though.

I also upgraded Bash to patch the Shellshock security hole, although none of my CGI scripts use Bash anyway. Why would anyone ever use Bash for CGI when there's Perl?

July 11th, 2014

PHP/MySQL framework converted from mysql to mysqli functions

Posted at 01:13:12 PM by froems

It turned out that there were only four scripts in the main site framework that needed to be converted, so the amount of work involved to convert everything to mysqli wasn't all that much after all. While doing the conversion, I also took the opportunity to clean up some old code in a few spots.

I've tested everything after the conversion, and it all seems to be working properly, so hopefully the framework should be good to go for the next decade or so now.

July 11th, 2014

Now running Apache 2.2.27 and PHP 5.4.30

Posted at 03:39:58 AM by froems

I compiled and installed updated versions of Apache HTTP server and PHP tonight. I still can't go to Apache 2.4, because mod_perl still doesn't work with it.

This time I compiled PHP with mysqli support, because the old mysql libraries are supposedly going away eventually. I guess I'll be changing the supporting code over to mysqli when I have the time.

April 23rd, 2014

Finally re-connected

Posted at 09:38:38 PM by froems

Internet access at the new location was finally connected about a week ago, but it was not AT&T, which is still having "facility issues".

Once the internet was connected, DNS was not updating for the new location; it turned out this was due to ddclient being dependent on the Perl module IO::Socket::SSL, which had not been reinstalled since upgrading to Slackware 14.0. So I reinstalled the module from CPAN.

Also, while installing IO::Socket::SSL, I noticed that the local version of OpenSSL was 1.0.1c, which was vulnerable to the new Heartbleed exploit, so I downloaded the latest Slackware package and upgraded that too.

Once all that was done, I noticed that the software I wrote to check blog entries does not properly escape ampersands. So I'll have to go back and fix that.

And that's about it for now.

April 3rd, 2014

New server location!

Posted at 07:41:10 AM by froems

I've moved the server to a new location, but the new location doesn't have internet access yet! Which, of course, means that nobody out there can see this blog post at the moment.

AT&T says that they can get internet access to this particular location around April 8th 2014. So if you're reading this before then, that means that internet access was connected faster than anticipated, I guess.