Error message

I ran into a WSOD on a Drupal site and checking the Drupal 7 log showed me the following:

I ran into the following error (or something like it) while setting up Drupal's xmlsitemap module:

This is as expected some kind of permissions issue. Why the module can't sort this on its own, I do not know. As with everything Drupal, clear the cache first to see if that fixes things. It sometimes does. If not, you will need to get your hands dirty on the commandline (if linux):

I tried installing the Twitter module for a client and ran into the following error during authentication (oauth):

Installing Aegir 2 on a fresh install of Ubuntu Saucy in a Virtualbox, I ran into the following message:

To fix this run, sudo mysql_secure_installation and ensure that you remove anonymous users. This should do the trick.

Using Virtualbox (4.3.6) on an XP64 machine, I ran into the following error while trying to install a 64-bit version of Ubuntu:

This happens even if the host machine is a 64-bit machine. To fix this, reboot the box and enter the BIOS. Look around for a virtualisation setting and enable it. Save and exit the BIOS configuration screen.

I recently had trouble with a MySQL installation in Ubuntu. For some reason or the other, during an upgrade to a newer version of mysql-server, the upgrade script had issues stopping the server and the script failed. This meant that apt could no longer function as it kept raising a red flag over the broken upgrade with the following instructions:

I ran into a hitch while trying to install the latest version of TortoiseSVN on my XP 64-bit Windows installation. Apparently, the entire world has forgotten about the existence of this variety of Windows. There's absolutely no mention of it anywhere on TortoiseSVN's installer page. The MSI installer failed stating that the version of Windows Installer that I was using was dated and that I needed to update my version of XP (x86) to SP3 or some other drivel like that. TortoiseSVN has no manual install option either. I did the whole Windows Update thing as well, to no avail.

Earlier today, I had to perform a substitution in Gvim within a 2GB file. Unfortunately, after a few thousand operations, Vim ran out of memory with the following error:

  Out of memory!
Out of memory!  (allocating XXX bytes)

Windows too complained about running out of virtual memory and my system slowed down to treacle-like response times.

While trying to edit a menu on a Drupal site, I found that none of my changes were being saved. Looking at the logs led me to the following error message:

Simply restarting MySQL did not fix things and it looked like I had to get my hands a li'l dirty.

I upgraded the Mollom module on this site from the 7.1.x version to the newer branch of 7.2.x and ran into a White Screen of Death (WSOD). Checking the logs pointed me to the Mollom error:

It's tough to fix this as you might not be able to even log into the site to get to the admin page. Therefore, you will need to disable the module from the database.