Starting deferred execution scheduler: atd failed!

JedMeister

New Member
Aug 13, 2009
17
1
1
Austalia
Code:
Starting deferred execution scheduler: atd [failed!]
appears during boot (quite late).

If I try to start it manually it gives basically the same message:
Code:
Starting deferred execution scheduler: atd failed!

If I try to run atd in debug mode:
Code:
atd -d
Cannot change to /var/spool/cron/atjobs: Permission denied

But I checked the permissions of /var/spool/cron/atjobs:
Code:
ls -l /var/spool/cron/|grep atjobs
drw------- 2 daemon daemon  4096 Apr  9 13:17 atjobs

According to 'man atd' permissions should be 700 so I changed it:
Code:
chmod -R 700 /var/spool/crom/atjobs
ls -l /var/spool/cron/|grep atjobs
drwx------ 2 daemon daemon  4096 Apr  9 13:17 atjobs
But the same error persists...


I have searched google and found nothing very helpful...
Any ideas anyone?

This is on a standalone PVE v2.1 (originally installed as v1.8 and upgraded). It has a few non-PVE packages installed but nothing recently, and nothing that I would've thought would cause this. As part of my troubleshooting I did:
Code:
apt-get update
apt-get upgrade
apt-get dist-upgrade
and rebooted

Info for at:
Code:
apt-cache policy at
  Installed: 3.1.12-1+squeeze1
  Candidate: 3.1.12-1+squeeze1
  Version table:
 *** 3.1.12-1+squeeze1 0
        500 http://mirror.internode.on.net/pub/debian/ squeeze/main amd64 Packages
        500 ftp://ftp.au.debian.org/debian/ squeeze/main amd64 Packages
        100 /var/lib/dpkg/status

Info for PVE:
Code:
pveversion -v
pve-manager: 2.1-14 (pve-manager/2.1/f32f3f46)
running kernel: 2.6.32-14-pve
proxmox-ve-2.6.32: 2.1-74
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-12-pve: 2.6.32-68
pve-kernel-2.6.32-14-pve: 2.6.32-74
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.92-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.8-1
pve-cluster: 1.0-27
qemu-server: 2.0-49
pve-firmware: 1.0-18
libpve-common-perl: 1.0-30
libpve-access-control: 1.0-24
libpve-storage-perl: 2.0-31
vncterm: 1.0-3
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.1-8
ksm-control-daemon: 1.1-1
 
Around this time, or soon after I also started having issues with the WebUI not loading. It would come good after a reboot but would again start playing up soon after. As it turns out, this seems to have been the early signs of a HDD failure. The drive finally failed yesterday but after a recovery all is well again...