LinuxSysAdmin

Things I don't want to look for twice..

Monthly Archives: September 2013

unattended-upgrades not working on Debian Squeeze (6)

I had to debug a problem where unattended-upgrades didn’t work. All my log was full of:

2013-09-23 13:20:38,180 INFO Initial blacklisted packages: blacklisted-package
2013-09-23 13:20:38,180 INFO Starting unattended upgrades script
2013-09-23 13:20:38,180 INFO Allowed origins are: ["('Debian', 'stable')", "('Debian', 'squeeze-stable')", "('Debian', 'squeeze-security')", "('Debian', 'squeeze-updates')", "('packages.dotdeb.org', 'stable')"]
2013-09-23 13:20:39,507 INFO No packages found that can be upgraded unattended

I tried to run unattended-upgrades with “–dry-run” and “-d” but that didn’t help much. So, the issue here is that Wheezy is out. Wheezy being out, it will look for packages for Wheezy, instead of Squeeze. So this section:

Unattended-Upgrade::Allowed-Origins {
 "${distro_id} stable";
 "packages.dotdeb.org stable";
};

Will have to be replaced with:

Unattended-Upgrade::Allowed-Origins {
 "${distro_id} oldstable";
 "packages.dotdeb.org oldstable";
};

After that, dry-run worked perfectly, so probably the upgrades, too.

VMWare Workstation 10 “Failed to Lock the File”

I tried to copy all files from a VM running on VMWare Workstation 10 for Linux, to a Windows machine with the same software installed. When trying to power on the machine, I got an error that said “Failed to Lock the File” and something about not finding the vmdk file or one of the snapshots. I tried re-copying those files about 3 times with no success. After a short google search, you’ll have to remove the folders that have .lck at the end. After removing those, I powered on the machine, and up and running it is.

Cron: (*system*) WRONG INODE INFO (/etc/crontab)

So, I edited crontab because I wanted to reschedule cron.daily to a convenient time. After restarting cron, I noticed there’s an error in logs. ┬áNot a worry, the service was running fine, but I didn’t want to see that error. Problem is that is world-wide writable:

ls -la crontab
-rw-rw-rw- 1 root root 724 Sep 17 09:20 crontab

Don’t know how this changed, but it’s now 666, Devil’s number. So after:

chmod 644 /etc/crontab

..everything is back to normal again.

Still trying to figure out why logrotate doesn’t rotate some logs while running from cron.daily, but works just fine while running from command-line.