You are here

Error message

Updating Windows Installer on XP 64-bit

Submitted by Druss on Sat, 2013-10-12 04:08

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.

Vim runs out of memory during a find and replace

Submitted by Druss on Sun, 2013-05-26 07:59

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.

PDOException: SQLSTATE[HY000]: General error: 144 Table 'cache_menu' is marked as crashed and last (automatic?) repair failed: DELETE FROM {cache_menu};

Submitted by Druss on Tue, 2013-04-23 10:38

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:

PDOException: SQLSTATE[HY000]: General error: 144 Table 'cache_menu' is marked as crashed and last (automatic?) repair failed: DELETE FROM {cache_menu};

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

Class 'MollomDrupal' not found

Submitted by Druss on Tue, 2013-04-23 10:15

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:

Class 'MollomDrupal' not found

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.

dpkg cannot install as there's no space left on the device even though there is

Submitted by Druss on Thu, 2012-11-22 23:46

I ran into this issue a couple of days ago and cannot recall the exact error message. However, the problem was effectively that aptitude could not install the new kernel update because my partition had apparently run out of space. An interrupted update to Klipper is one thing and the Linux kernel a whole 'nother kettle of fishies. Thinking that I simply needed to free up some space on my partition, I checked the current status via df.

Initializing new hard disk: The request could not be performed because of an I/O device error

Submitted by Druss on Fri, 2012-10-12 01:09

I got a new 3TB hard disk. While it's being detected in Windows 7, initializing it has proved to be impossible as I keep running into the following error:

The request could not be performed because of an I/O device error

After testing this one a couple of different systems and in Linux, I have arrived at the conclusion that the drive is screwed. Time to get it replaced.

cannot stat 'rageagainstthecage-arm5.bin': No such file or directory

Submitted by Druss on Sat, 2012-07-14 23:10

Today, I'm trying to root one of my Android phones in order to install Cyanogen Mod 7.2! First issue: while attempting to root the phone (a Motorola Defy running Android 2.2.2 Froyo), I ran into the following error message while following this guide:
C:\Users\foo>adb push rageagainstthecage-arm5.bin /data/local/tmp/
cannot stat 'rageagainstthecage-arm5.bin': No such file or directory

Cyrus sasld testsaslauthd connect() : No such file or directory 0

Submitted by Druss on Wed, 2012-07-11 01:22

While trying to debug a postfix authentication issue in Debian 6, I had to use testsaslauthd to test things out:
testsaslauthd -s smtp -u foo@example.com -p test

only to get the following error:
connect() : No such file or directory 0

This is apparently because a lot of people (and authors) follow the same guide for configuring postfix and saslauthd. One of the steps missing is to symlink and saslauthd directory to a location within postfix. To fix:

Pages

Subscribe to RSS - Error message