apt plugin from debians hobbit-plugins package
Hey all,
The apt plugin, which checks if apt-get update is run regularly, doesn't seem to work since I've upgraded to Debian Lenny. The file /var/lib/apt/lists/lock doesn't get updated anymore and that's one of the three files it checks for the timestamp. after 1.5 days, it turns yellow, no matter how often I run apt-get update. Anyone with that same experience? I have this on multiple machines.
Wouter
Yes, I see that on Ubuntu as well which is Debian derivative.
Sincerely, Jason
On Apr 30, 2009, at 9:20 AM, Wouter Schoot wrote:
Hey all,
The apt plugin, which checks if apt-get update is run regularly,
doesn't seem to work since I've upgraded to Debian Lenny. The file / var/lib/apt/lists/lock doesn't get updated anymore and that's one of
the three files it checks for the timestamp. after 1.5 days, it
turns yellow, no matter how often I run apt-get update. Anyone with
that same experience? I have this on multiple machines.Wouter
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
Yes, I see that on Ubuntu as well which is Debian derivative.
I'd suggest raising a bug report with the Debian package maintainer.
Malcolm
-- Technical copy-editor & proofreader
KDE Proofreading Team KDE British English Translation Team
http://l10n.kde.org/team-infos.php?teamcode=en_GB
Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01
An HTML attachment was scrubbed... URL: <http://lists.xymon.com/pipermail/xymon/attachments/20090430/52d662cd/attachment.html>
dOCtoR MADneSs wrote:
On my side I just changed my crontab : apt-get update && touch /var/lib/apt/lists/lock
Sounds good enough for now, I've changed that in the cron-apt file in cron.d and will see if it works.
Wouter
Re: dOCtoR MADneSs 2009-04-30 <49F9C9E9.1060406 at makelofine.org>
On my side I just changed my crontab :
apt-get update && touch /var/lib/apt/lists/lock
so if the update is succesfull, the mtime of /var/lib/apt/lists/lock is changed, and the apt plugin reports green.
Ah, looks like using a lock file doesn't update the mtime. I didn't notice until now as I'm using the "all-included" hack suggested in apt.pl:
44 */4 * * * root ! apt-get -qq update 2>&1 | grep -q . && date -u > /var/lib/apt/update_success
Unfortunately apt-get update even returns 0 in case of some errors (iirc unknown apt-keys etc.), so this command checks for an empty output of apt-get -qq update instead.
(http://bugs.debian.org/526894)
Christoph
cb at df7cb.de | http://www.df7cb.de/
i made a little change in /usr/lib/hobbit/client/ext/apt
in @stamp_files add "/var/lib/apticron/last_run" and remove "/var/lib/apt/lists/lock".
before: my @stamp_files = qw(/var/lib/apt/update_success /var/lib/apt/periodic/update-stamp /var/lib/apt/lists/lock); after: my @stamp_files = qw(/var/lib/apt/update_success /var/lib/apt/periodic/update-stamp /var/lib/apticron/last_run);
works fine in lenny
Rasmus
Christoph Berg schrieb:
Re: dOCtoR MADneSs 2009-04-30 <49F9C9E9.1060406 at makelofine.org>
On my side I just changed my crontab :
apt-get update && touch /var/lib/apt/lists/lock
so if the update is succesfull, the mtime of /var/lib/apt/lists/lock is changed, and the apt plugin reports green.
Ah, looks like using a lock file doesn't update the mtime. I didn't notice until now as I'm using the "all-included" hack suggested in apt.pl:
44 */4 * * * root ! apt-get -qq update 2>&1 | grep -q . && date -u > /var/lib/apt/update_success
Unfortunately apt-get update even returns 0 in case of some errors (iirc unknown apt-keys etc.), so this command checks for an empty output of apt-get -qq update instead.
(http://bugs.debian.org/526894)
Christoph
Rasmus Simon-Riegel wrote:
i made a little change in /usr/lib/hobbit/client/ext/apt
in @stamp_files add "/var/lib/apticron/last_run" and remove "/var/lib/apt/lists/lock".
before: my @stamp_files = qw(/var/lib/apt/update_success /var/lib/apt/periodic/update-stamp /var/lib/apt/lists/lock); after: my @stamp_files = qw(/var/lib/apt/update_success /var/lib/apt/periodic/update-stamp /var/lib/apticron/last_run);
ascent at tosca:~$ ls -l /var/lib/apticron/last_run ls: cannot access /var/lib/apticron/last_run: No such file or directory
That depends on another package I suppose?
The previous solutions work no matter what.
Wouter
with apticron it was simple to get a regularly updated lockfile. you never work with this tool, i have not thought about it.
Rasmus
Wouter Schoot schrieb:
Rasmus Simon-Riegel wrote:
i made a little change in /usr/lib/hobbit/client/ext/apt
in @stamp_files add "/var/lib/apticron/last_run" and remove "/var/lib/apt/lists/lock".
before: my @stamp_files = qw(/var/lib/apt/update_success /var/lib/apt/periodic/update-stamp /var/lib/apt/lists/lock); after: my @stamp_files = qw(/var/lib/apt/update_success /var/lib/apt/periodic/update-stamp /var/lib/apticron/last_run);
ascent at tosca:~$ ls -l /var/lib/apticron/last_run ls: cannot access /var/lib/apticron/last_run: No such file or directory
That depends on another package I suppose?
The previous solutions work no matter what.
Wouter
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
An HTML attachment was scrubbed... URL: <http://lists.xymon.com/pipermail/xymon/attachments/20090505/85187bf0/attachment.html>
participants (6)
-
cb＠df7cb.de
-
doctor＠makelofine.org
-
hv11623＠devk.de
-
jason＠hands4christ.org
-
malcolm.hunter＠gmx.co.uk
-
wouter＠schoot.org