I have seen this error on three mostly identical Servers, which are maintained by me. They all run apticron via cron.daily at 6:25:00 +0200 (nearly unchange default-configuration). And apticron got stuck on September the 6th.
Perhaps, this additional information helps hunting the bug... -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
