Description of problem: This post on the discuss mailing list best describes it: From: "Bit Twister2" (via discuss Mailing List) <discuss@ml.mageia.org> To: discuss@ml.mageia.org Reply-To: discuss@ml.mageia.org Subject: Re: [discuss] locate quit working Date: Tue, 6 Sep 2022 07:56:06 -0500 Sender: discuss-request@ml.mageia.org X-Mailer: Claws Mail 3.19.0 (GTK+ 2.24.33; x86_64-mageia-linux-gnu) X-Spam-Level: On Tue, 6 Sep 2022 07:54:45 -0400 "Pierre Fortin" (via discuss Mailing List) <discuss@ml.mageia.org> wrote: > On Tue, 6 Sep 2022 00:31:37 -0500 Bit Twister2 wrote: > > >On Tue, 6 Sep 2022 00:23:36 -0400 > >"Pierre Fortin" (via discuss Mailing List) <discuss@ml.mageia.org> > >wrote: > > > >> Hi, > >> > >> locate on Cauldron(mga9) was working fine a few weeks ago. Now, I'm > >> getting: > >> $ locate rsyncd > >> /var/lib/plocate/plocate.db: No such file or directory > >> > >> plocate is installed. Re-installing does not help; after re-install > >> /var/lib/plocate only contains CACHEDIR.TAG > >> > >> Should I bug this or am I missing something? > > > >I can not install the plocate package via mcc. > >All I can find is mlocate. > >Installed it, ran updatedb. and locate has no problems running. > > > Hmm... are you running mga8? Hehe, pretty sure. Was a clean network install using Sep 5 20:28 Mageia-Cauldron-netinstall-nonfree-x86_64.iso # cat /etc/release Mageia release 9 (Cauldron) for x86_64 > I don't see mlocate in mga9, only > plocate... # cat /etc/release Mageia release 9 (Cauldron) for x86_64 $ get_src_rpm updatedb Looked for : updatedb Using : /usr/bin/updatedb Installed rpm : mlocate-0.26-14.mga8 rpm short name: mlocate Source rpm : mlocate-0.26-14.mga8.src.rpm Information : https://pagure.io/mlocate Packager : umeabot <umeabot> Summary : A utility for finding files by name via a central database $ Will open a bug... Thanks. And I thought it funny I could see plocate rpm on prinction mirror but could not find it in MCC . $ grep plocate *009*idx core-0009.0.x86_64.idx:plocate-1.1.15-1.mga9.x86_64.rpm 155K 17-Aug-2022 14:01 Frap my fault. My set_mirror script has a bug, it set mga8 media, not cauldron. removed mlocate, set cauldron media, installed polcate, and locate fails. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
As a workaround run updatedb by hand as root. Looks like plocate-updatedb.timer isn't enabled/started by default after install to update plocate db daily.
CC: (none) => jani.valimaa
updatedb resolved the error Then I started plocate-updatedb.time via mcc Is "disabled" correct blow? $ systemctl status plocate-updatedb.timer ● plocate-updatedb.timer - Update the plocate database daily Loaded: loaded (/usr/lib/systemd/system/plocate-updatedb.timer; disabled; preset: disabled) Active: active (waiting) since Tue 2022-09-06 12:33:21 EDT; 2min 8s ago Until: Tue 2022-09-06 12:33:21 EDT; 2min 8s ago Trigger: Wed 2022-09-07 02:07:51 EDT; 13h left Triggers: ● plocate-updatedb.service Sep 06 12:33:21 pf.pfortin.com systemd[1]: Started Update the plocate database daily. At least, it ran once and I can run updatedb manually as a workaround...
Do we want it to be enabled by default? Most users don't use locate. Those who do use it, will most likely first want to edit PRUNEPATHS etc. before running updatedb for the first time.
CC: (none) => marja11
Since mageia-release-9-0.24.mga9 plocate-updatedb.timer is enabled and started by default after plocate install [1]. Same way as mlocate-updatedb.timer is or was. Default and sane updatedb.conf originating from mlocate is also shipped with plocate. [1] https://svnweb.mageia.org/packages?view=revision&revision=1884582
(In reply to Jani Välimaa from comment #4) > Since mageia-release-9-0.24.mga9 plocate-updatedb.timer is enabled and > started by default after plocate install [1]. Same way as > mlocate-updatedb.timer is or was. > > Default and sane updatedb.conf originating from mlocate is also shipped with > plocate. > > [1] https://svnweb.mageia.org/packages?view=revision&revision=1884582 Thanks. Closing as fixed, then. @ Pierre Feel free to reopen if needed.
Status: NEW => RESOLVEDResolution: (none) => FIXED