On Sonntag 17 Januar 2010, Patrick Matthäi wrote: > Sorry, here it is working well. I have installed exactly the same > version to our productive machine, where debian 4.0, 5.0, 6.0, centos, > redhat and some other distrubtions are managed, everything is working well. > > I think there might be another problem. > > What happens, if you connect to the host with the problem and execute: > /usr/bin/apt-dater-host status
ADPROTO: 0.5 LSBREL: Debian|testing|squeeze VIRT: Unknown UNAME: Linux|i686 FORBID: 0 STATUS: sp|1.3.4-1.2.1-47|i STATUS: notification-daemon|0.4.0-2|i STATUS: groff-base|1.20.1-6|i ... STATUS: autoconf|2.65-3|i STATUS: libcdio7|0.78.2+dfsg1-3|d KERNELINFO: 0 2.6.32-trunk-686 > Also what is the content of this file: > cat ~/.cache/apt-dater/stats/<hostname>\:0.stat ------------------------------------------------------------------------------- ADPROTO: 0.5 ADPERR: Failed to execute 'sudo aptitude update' (256). ------------------------------------------------------------------------------- (But if I try 'sudo aptitude update' by hand, it works just fine, although it does leave an exit status of 255.) Andreas
signature.asc
Description: This is a digitally signed message part.
