Bug#1028142: dlocate: cannot find recent files - obsolete database?
On 2023-01-07 19:48 +0100, Vincent Lefevre wrote:
> On 2023-01-07 19:20:56 +0100, Sven Joachim wrote:
>> On 2023-01-07 18:53 +0100, Vincent Lefevre wrote:
>> > zira:~> ll /var/lib/dlocate
>> > total 109172
>> > -rw-r--r-- 1 root root 55750318 2022-11-25 00:27:44 dlocatedb
>> > -rw-r--r-- 1 root root 55623054 2022-11-14 09:47:51 dlocatedb.old
>> > -rw-r--r-- 1 root root 105318 2022-11-25 00:27:44 dlocatedb.stamps
>> > -rw-r--r-- 1 root root 299199 2022-11-25 00:27:44 dpkg-list
>
> Same issue my other machine.
>
>> That could have been the case for much longer actually. At installation
>> time, the postinst script runs "update-dlocatedb -b" which seems to have
>> been successful.
>
> I suppose that explains the
>
>> > -rw-r--r-- 1 root root 55623054 2022-11-14 09:47:51 dlocatedb.old
>
>> > The cron file /etc/cron.daily/dlocate is there, though:
>> >
>> > #!/bin/sh
>> >
>> > # update databases for both files and packages.
>> > if [ -x /usr/sbin/update-dlocatedb ] ; then
>> > /usr/sbin/update-dlocatedb -b
>> > fi
>>
>> But apparently it is never executed. Are any other cron jobs being run
>> on your system?
>
> In the logs I can see for today:
>
> Jan 07 06:25:01 zira CRON[1843444]: (root) CMD (test -x
> /usr/sbin/anacron || { cd / && run-parts --report /etc/cron.daily; })
>
> and
>
> Jan 07 14:38:01 zira CRON[1857920]: (root) CMD ( test -x
> /etc/cron.daily/popularity-contest &&
> /etc/cron.daily/popularity-contest --crond)
>
> So it seems to be OK, though I don't know what leads to the logging
> of popularity-contest only.
Most likely the script /etc/cron.d/popularity-contest, I get the same
messages.
>> If not, you may have been bitten by bug #1019554 in
>> anacron which needs manual restore as mentioned in
>> https://lists.debian.org/debian-devel-announce/2022/11/msg00001.html.
>
> 2022-07-14 20:57:59 upgrade anacron:amd64 2.3-32 2.3-33
> 2022-07-14 20:57:59 status half-configured anacron:amd64 2.3-32
> 2022-07-14 20:57:59 status unpacked anacron:amd64 2.3-32
> 2022-07-14 20:57:59 status half-installed anacron:amd64 2.3-32
> 2022-07-14 20:57:59 status unpacked anacron:amd64 2.3-33
Note that the anacron bug only makes itself apparent after the upgrade
to a later version, since that would run the faulty postrm from 2.3-33.
> but I get mail from failing cron scripts.
What does "systemctl status anacron.service" print?
Cheers,
Sven
Reply to: