Recently I have started working a lot more with various F5 hardware including BIG-IP LTM’s or BIG-IP Local Traffic Managers. F5 provides a VMware image so you can have a test environment running as a virtual machine. This is a great place to complete testing, example configurations, etc. Once you start the F5 BIG-IP LTM VE virtual machine you will need to login with the default username and password which is noted below along with screenshots so you can ensure you are logging in via the correct console prompt.
On one of my servers I run a couple sites via Django and recently when I upgraded the server it broke the Django sites that were running via FastCGI. After some investigation I was able to find the issue which happened to be a basic conflict between python2.4 which is the default python version on CentOS Linux and python2.6 which I installed to run via python26 instead of python. This way I can change the environment of any site that needs it to Python version 2.6 without much hassle. Below I describe the error in detail as well as what resolved the issue.
I recently was installing Django for a test project and needed to upgrade Python on a CentOS server to 2.6. The current revisions available via yum on CentOS are 2.4. The yum package manager requires Python 2.4 still to function properly so upgrading Python to 2.6 manually will break the CentOS yum package manager. After a little bit of research I found a yum repository that would allow you to install Python version 2.6 in parallel to Python version 2.4. Below I explain how to install the new Python version, not break the yum package manager, and modify a Django project that references Python to use the 2.6 version instead of the 2.4 version.
I have had a problem with a personal WordPress blog I installed a long time ago but never got the chance to look into until recently which is the fact that the logon part of the site was not auto logging me on. Not only was the blog not auto logging me on but it was not remembering my password though it would remember my username. This blog has been around since before WordPress 2.5 and I have upgraded from time to time. I remember the issue started somewhere around the time that I upgraded from WordPress 2.5 to WordPress 2.6 so that is where I started the troubleshooting process and sure enough I was able to find the answer pretty easily. I had been in a rush when upgrading the site and once I had time to go back and read the documentation I found some configuration file options located in wp-config.php that had been added with WordPress 2.6. There were 3 security key configuration options added in WordPress 2.6 and fourth security key added in WordPress 2.7.