Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1009827: plocate updatedb is not being run
124 views
Skip to first unread message
Ron Murray
Apr 18, 2022, 2:50:04 PM4/18/22
to
Package: plocate
Version: 1.1.15-2
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Dear Maintainer,
The daily update.db job for plocate is not being run. Last time it
ran on my system was December 30, 2021. Manual updates work fine.
This job should be run by systemd's timer system, but that doesn't
seem to be working for some reason, although other jobs (logrotate for
example) have been run successfully. systemd's timer system leaves its
timestamps in /var/lib/systemd/timers; the timestamp for
plocate-updatedb (indicating the last time that systemd ran it) is
dated December 30, 2021, same as the date of the last automatic run.
The .service and .timer files for plocate-updatedb look ok to my
(admittedly untrained) eye. Permissions on them are identical to other
files in /lib/systemd/system, and I don't see any mention of plocate
(error or otherwise) in journalctl.
It seems, then, that systemctl isn't running this job for some
reason, but not logging any errors.
.....Ron
- -- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.17.3.khufu (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages plocate depends on:
ii libc6 2.33-7
ii libgcc-s1 12-20220319-1
ii libstdc++6 12-20220319-1
ii liburing2 2.1-2
ii libzstd1 1.5.2+dfsg-1
plocate recommends no packages.
Versions of packages plocate suggests:
ii powermgmt-base 1.36
ii systemd-sysv 250.4-1
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
iQJCBAEBCgAsFiEETZlw4yMXM0sUHntjEvfoZbXi52EFAmJdrxsOHHJqbXhAcmpt
eC5uZXQACgkQEvfoZbXi52EW5Q//YSH544LLZs4Br2TqVQQbbphi+v4OFOjKoBSr
H5B9zH+mVYQgKZPP3AEwwbsiaswDM4m+JiOMAiDR0n3+RTF+5KY3l6uy2uzA2dbx
XkRowTvD/XzfSCuBR5CZEnLTAZoQW42uiQ6hH/fdmqVmw7MDr5twMgHrfjpeGws+
sbQMWlu52nMAfcu1Dnfi7DtST2jX9Bs+2ItPmzKnvodldMItFRqzjPEKqzTnICa0
/OrWNeX1JKfvcAqmFqNp0WUh3htpY7GhCqUY/92mupr4dCibZMzvBl9A8PPEN8Eu
l/PkBKQDbT3OUQ48T1F8vtQP8wH0hSNuLCgkzfB77bedVzbpX4+t/OBMWkSIWfYF
9TxJZwTBKIcLuRHd+HO8UwkPjbX2Mo6i6c8BdlTWlkF18lktSYRoezSskjbQ1uyq
Hz6LBW66lfYCENNbXB/hoipYLKGgB3jsctr6w5XmTPcEseUjg69TXcdIkF6WSdaT
lDtT0Bt+r4BVtska2zJKEm4zJE7bzZIdmdD23EGzY/zn1cTYuYF+hIsRMlmI+2te
Z6WfyMbconPNIQ3yn2hsb/TNIwSvato8hcqAQ2vVzMISodekPxxHgU9er2Isj2Ps
haZXJoXuOF4QVriUcWxcoNG4WjCotti4IW5ZbCVdJHSviuOfLwQt+4OAa5cBHt8d
5rg1Vp0=
=l+qe
-----END PGP SIGNATURE-----
Version: 1.1.15-2
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Dear Maintainer,
The daily update.db job for plocate is not being run. Last time it
ran on my system was December 30, 2021. Manual updates work fine.
This job should be run by systemd's timer system, but that doesn't
seem to be working for some reason, although other jobs (logrotate for
example) have been run successfully. systemd's timer system leaves its
timestamps in /var/lib/systemd/timers; the timestamp for
plocate-updatedb (indicating the last time that systemd ran it) is
dated December 30, 2021, same as the date of the last automatic run.
The .service and .timer files for plocate-updatedb look ok to my
(admittedly untrained) eye. Permissions on them are identical to other
files in /lib/systemd/system, and I don't see any mention of plocate
(error or otherwise) in journalctl.
It seems, then, that systemctl isn't running this job for some
reason, but not logging any errors.
.....Ron
- -- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.17.3.khufu (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages plocate depends on:
ii libc6 2.33-7
ii libgcc-s1 12-20220319-1
ii libstdc++6 12-20220319-1
ii liburing2 2.1-2
ii libzstd1 1.5.2+dfsg-1
plocate recommends no packages.
Versions of packages plocate suggests:
ii powermgmt-base 1.36
ii systemd-sysv 250.4-1
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
iQJCBAEBCgAsFiEETZlw4yMXM0sUHntjEvfoZbXi52EFAmJdrxsOHHJqbXhAcmpt
eC5uZXQACgkQEvfoZbXi52EW5Q//YSH544LLZs4Br2TqVQQbbphi+v4OFOjKoBSr
H5B9zH+mVYQgKZPP3AEwwbsiaswDM4m+JiOMAiDR0n3+RTF+5KY3l6uy2uzA2dbx
XkRowTvD/XzfSCuBR5CZEnLTAZoQW42uiQ6hH/fdmqVmw7MDr5twMgHrfjpeGws+
sbQMWlu52nMAfcu1Dnfi7DtST2jX9Bs+2ItPmzKnvodldMItFRqzjPEKqzTnICa0
/OrWNeX1JKfvcAqmFqNp0WUh3htpY7GhCqUY/92mupr4dCibZMzvBl9A8PPEN8Eu
l/PkBKQDbT3OUQ48T1F8vtQP8wH0hSNuLCgkzfB77bedVzbpX4+t/OBMWkSIWfYF
9TxJZwTBKIcLuRHd+HO8UwkPjbX2Mo6i6c8BdlTWlkF18lktSYRoezSskjbQ1uyq
Hz6LBW66lfYCENNbXB/hoipYLKGgB3jsctr6w5XmTPcEseUjg69TXcdIkF6WSdaT
lDtT0Bt+r4BVtska2zJKEm4zJE7bzZIdmdD23EGzY/zn1cTYuYF+hIsRMlmI+2te
Z6WfyMbconPNIQ3yn2hsb/TNIwSvato8hcqAQ2vVzMISodekPxxHgU9er2Isj2Ps
haZXJoXuOF4QVriUcWxcoNG4WjCotti4IW5ZbCVdJHSviuOfLwQt+4OAa5cBHt8d
5rg1Vp0=
=l+qe
-----END PGP SIGNATURE-----
Steinar H. Gunderson
Apr 18, 2022, 3:20:03 PM4/18/22
to
On Mon, Apr 18, 2022 at 02:34:22PM -0400, Ron Murray wrote:
> The daily update.db job for plocate is not being run. Last time it
> ran on my system was December 30, 2021. Manual updates work fine.
What does systemd say about the timer? (E.g., sudo systemctl status
> The daily update.db job for plocate is not being run. Last time it
> ran on my system was December 30, 2021. Manual updates work fine.
plocate-updatedb.timer.)
/* Steinar */
--
Homepage: https://www.sesse.net/
Steinar H. Gunderson
Apr 18, 2022, 4:00:03 PM4/18/22
to
On Mon, Apr 18, 2022 at 03:46:21PM -0400, Ron Murray wrote:
> root@khufu:~# systemctl status plocate-updatedb.timer
> ○ plocate-updatedb.timer - Update the plocate database daily
> Loaded: loaded (/lib/systemd/system/plocate-updatedb.timer; disabled;
> vendor preset: enabled)
The postinst script enables it (through dh_installsystemd), so this really
indicates something or someone disabled it after installation.
> root@khufu:~# systemctl status plocate-updatedb.timer
> ○ plocate-updatedb.timer - Update the plocate database daily
> Loaded: loaded (/lib/systemd/system/plocate-updatedb.timer; disabled;
> vendor preset: enabled)
The postinst script enables it (through dh_installsystemd), so this really
indicates something or someone disabled it after installation.
Ron Murray
Apr 18, 2022, 4:00:03 PM4/18/22
to
Here's what it says:
root@khufu:~# systemctl status plocate-updatedb.timer
○ plocate-updatedb.timer - Update the plocate database daily
Loaded: loaded (/lib/systemd/system/plocate-updatedb.timer; disabled; vendor preset: enabled)
Active: inactive (dead)
Trigger: n/a
Triggers: ● plocate-updatedb.service
I noticed the "disabled" line, so I enabled it. Now it says
root@khufu:~# systemctl status plocate-updatedb.timer
○ plocate-updatedb.timer - Update the plocate database daily
Loaded: loaded (/lib/systemd/system/plocate-updatedb.timer; enabled; vendor preset: enabled)
Active: inactive (dead)
Trigger: n/a
Triggers: ● plocate-updatedb.service
We'll see how it goes tonight.
--
Ron Murray <rj...@rjmx.net> PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761
Ron Murray
Apr 18, 2022, 4:50:03 PM4/18/22
to
You're right, of course.
However, I'm the only user of this box, and I'd never heard of systemd timers, or even plocate, until yesterday. I certainly don't recall disabling it. Strange.
Anyway, let's see if it runs tonight, and if it does, we can close this bug.
Thanks,
.....Ron
0 new messages