Rackspace Backup stuck in Queueing state

If your backup is stuck in a queueing state and being skipped the next day because of an already running instance, the problem may be due to a crash or unexpected reboot.

Make sure you do not have a state lockfile located at:

/var/cache/driveclient/backup-running.lock

after shutting down the daemon, this shouldn't exist.

Thanks to Evan B @ Rackspace for the quick pointer!

Rackspace driveclient on RHEL/CentOS segfault

The issue in
http://www.transdimensia.ravenhurst.com/2012/12/libstdc-dies-running-driveclient.html
is alive and well, although with a slightly different signature:

This is the line from /var/log/messages:

Oct  9 16:29:09 <hostname> kernel: driveclient[28672] general protection ip:7f06ec55e867 sp:7fff0a73adb0 error:0 in libgcc_s-4.4.7-20120601.so.1[7f06ec54f000+16000]

You might receive the following in strace:

stat("/etc/issue", {st_mode=S_IFREG|0644, st_size=1882, ...}) = 0 stat("/etc/issue", {st_mode=S_IFREG|0644, st_size=1882, ...}) = 0 open("/etc/issue", O_RDONLY) = 3 read(3, " _ ____ ___"..., 8191) = 1882 --- SIGSEGV (Segmentation fault) @ 0 (0) ---

libstdc++ dies running driveclient

Received this error trying to start up driveclient for a rackspace cloud backup.

Dec  4 15:57:07 system kernel: driveclient[12763] general protection ip:7fa8bd8b5590 sp:7fff41ec2450 error:0 in libstdc++.so.6.0.13[7fa8bd849000+e8000]

Installed were: libstdc++.x86_64 4.4.6-4.el6 @anaconda-CentOS-201207061011.x86_64/6.3 driveclient.x86_64 1.04.005581-0 @drivesrvr

stat("/etc/issue", {st_mode=S_IFREG|0644, st_size=1882, ...}) = 0
stat("/etc/issue", {st_mode=S_IFREG|0644, st_size=1882, ...}) = 0
open("/etc/issue", O_RDONLY)            = 3
read(3, " _  ____                     ___"..., 8191) = 1882
--- SIGSEGV (Segmentation fault) @ 0 (0) ---

I am not sure if my /etc/issue was too large or there bad characters or something else wrong with this file, but removing it fixes the problem.