Bug#1009143: plocate: Similar issue here
On Mon, Apr 18, 2022 at 04:50:58PM -0400, James Cloos wrote: > SG> This was fixed in plocate 1.1.12. ... Which version are you running? > as i mentioned the sbc has buster, so: > > ii plocate1.1.8-2~bpo10+1 armhfmuch faster locate And also, a very old kernel? /* Steinar */ -- Homepage: https://www.sesse.net/
Bug#1009143: plocate: Similar issue here
oh. is that all it is. ... so the reporter's issue is certainly different. SG> This was fixed in plocate 1.1.12. ... Which version are you running? as i mentioned the sbc has buster, so: ii plocate1.1.8-2~bpo10+1 armhfmuch faster locate -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6
Bug#1009143: plocate: Similar issue here
On Mon, Apr 18, 2022 at 12:32:20AM -0400, James Cloos wrote: > the strace output ends with: > > openat(AT_FDCWD, "/var/lib/plocate/", O_WRONLY|O_LARGEFILE|O_TMPFILE, 0640) > = -1 EISDIR (Is a directory) > > i've only seen it on arm32 buster, though. It shouldn't end there, though; if the kernel doesn't support O_TMPFILE (which suggests it's pretty old by now), it should fall back to mkstemp(). This was fixed in plocate 1.1.12. And in any case, it wouldn't then really be different from cron. Which version are you running? /* Steinar */ -- Homepage: https://www.sesse.net/
Bug#1009143: plocate: Similar issue here
> "SG" == Steinar H Gunderson writes: SG> If so, I don't understand why running updatedb manually doesn't do anything. SG> Perhaps there are multiple issues in play on the same bug number. *perhaps* he gets something similar to what i see on one arm32 buster sbc: updatedb exits complaining that $CWD is a directory. (cf below :) i've not had a chance to debug that beyond trying --debug-pruning and trying it from a variety of current directories and uids, all w/o benefit. the strace output ends with: openat(AT_FDCWD, "/var/lib/plocate/", O_WRONLY|O_LARGEFILE|O_TMPFILE, 0640) = -1 EISDIR (Is a directory) i've only seen it on arm32 buster, though. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6
Bug#1009143: plocate: Similar issue here
Yes. Once I've figured out what the problem is, I'll file another bug report. -- Ron Murray PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761 On Sun, 2022-04-17 at 23:27 +0200, Steinar H. Gunderson wrote: > On Sun, Apr 17, 2022 at 04:39:30PM -0400, Ron Murray wrote: > > Sorry, perhaps I wasn’t too clear. Running updatedb manually > > works fine. > > I just had to do it again. I think the only issue is the auto > > update. > > I think that should be on a different bug, then. > > /* Steinar */
Bug#1009143: plocate: Similar issue here
On Sun, Apr 17, 2022 at 04:39:30PM -0400, Ron Murray wrote: >Sorry, perhaps I wasn’t too clear. Running updatedb manually works fine. >I just had to do it again. I think the only issue is the auto update. I think that should be on a different bug, then. /* Steinar */ -- Homepage: https://www.sesse.net/
Bug#1009143: plocate: Similar issue here
Ah. Sorry, perhaps I wasn’t too clear. Running updatedb manually works fine. I just had to do it again. I think the only issue is the auto update. -- Ron Murray PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761 > On Apr 17, 2022, at 16:14, Steinar H. Gunderson wrote: > > On Sun, Apr 17, 2022 at 04:07:21PM -0400, Ron Murray wrote: >> I think the problem is that the cron.daily plocate job isn't being run. >> I'd suspect the systemd timer doesn't work, but I'm not sure. I'll hack >> the cron.daily/plocate script to save some diagnostic information, and >> perhaps that'll help. > > If so, I don't understand why running updatedb manually doesn't do anything. > Perhaps there are multiple issues in play on the same bug number. > > /* Steinar */ > -- > Homepage: https://www.sesse.net/
Bug#1009143: plocate: Similar issue here
On Sun, Apr 17, 2022 at 04:07:21PM -0400, Ron Murray wrote: > I think the problem is that the cron.daily plocate job isn't being run. > I'd suspect the systemd timer doesn't work, but I'm not sure. I'll hack > the cron.daily/plocate script to save some diagnostic information, and > perhaps that'll help. If so, I don't understand why running updatedb manually doesn't do anything. Perhaps there are multiple issues in play on the same bug number. /* Steinar */ -- Homepage: https://www.sesse.net/
Bug#1009143: plocate: Similar issue here
I think the problem is that the cron.daily plocate job isn't being run. I'd suspect the systemd timer doesn't work, but I'm not sure. I'll hack the cron.daily/plocate script to save some diagnostic information, and perhaps that'll help. Thanks, .Ron -- Ron Murray PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761 On Sun, 2022-04-17 at 21:38 +0200, Steinar H. Gunderson wrote: > On Sat, Apr 09, 2022 at 07:50:09PM -0400, Ron Murray wrote: > > Steinar, you may be right about problems with the upgrade. I > > started > > looking into this earlier today because 'locate' couldn't find > > files > > that I knew were present in the filesystem. Based on what you said, > > I > > checked plocate.db and siscovered that it hadn't been updated since > > December 30. The files I was looking for had, of course, been added > > since then. > > That's strange; do you know if the updatedb.plocate command was ever > actually > run? Did it output anything to the error log? > > I've tried reproducing this by installing mlocate and then upgrading, > but I can't get it to break. > > > I also note that there's still a 'locate' in /etc/cron.daily, > > which > > runs '/usr/bin/updatedb.findutils'. Should these be still on the > > sysytem? Could they be interfering with plocate? > > No, it's entirely independent. > > /* Steinar */
Bug#1009143: plocate: Similar issue here
On Sat, Apr 09, 2022 at 07:50:09PM -0400, Ron Murray wrote: >Steinar, you may be right about problems with the upgrade. I started > looking into this earlier today because 'locate' couldn't find files > that I knew were present in the filesystem. Based on what you said, I > checked plocate.db and siscovered that it hadn't been updated since > December 30. The files I was looking for had, of course, been added > since then. That's strange; do you know if the updatedb.plocate command was ever actually run? Did it output anything to the error log? I've tried reproducing this by installing mlocate and then upgrading, but I can't get it to break. >I also note that there's still a 'locate' in /etc/cron.daily, which > runs '/usr/bin/updatedb.findutils'. Should these be still on the > sysytem? Could they be interfering with plocate? No, it's entirely independent. /* Steinar */ -- Homepage: https://www.sesse.net/
Bug#1009143: plocate: Similar issue here
Package: plocate Version: 1.1.15-2 Followup-For: Bug #1009143 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Steinar, you may be right about problems with the upgrade. I started looking into this earlier today because 'locate' couldn't find files that I knew were present in the filesystem. Based on what you said, I checked plocate.db and siscovered that it hadn't been updated since December 30. The files I was looking for had, of course, been added since then. So I rm'd plocate.db and ran updatedb, and now plocate can find files. It seems, then, that the plocate database is not being updated (at least on my box, anyway. I'm not sure of the exact cause of this problem. I looked at 'plocate' in /etc/cron.daily, and noted that it relies on systemd to launch updatedb using the timer function. I'm not too familiar with that function (yet), but there seems to be a plocate-updatedb.timer file in /lib/systemd/system/plocate-updatedb.timer, echoed in other places. I also note that there's still a 'locate' in /etc/cron.daily, which runs '/usr/bin/updatedb.findutils'. Should these be still on the sysytem? Could they be interfering with plocate? Thanks, .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.2.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 libzstd11.4.10+dfsg-1 plocate recommends no packages. Versions of packages plocate suggests: ii powermgmt-base 1.36 ii systemd-sysv250.4-1 - -- no debconf information -BEGIN PGP SIGNATURE- iQJCBAEBCgAsFiEETZlw4yMXM0sUHntjEvfoZbXi52EFAmJSG6AOHHJqbXhAcmpt eC5uZXQACgkQEvfoZbXi52Ej5RAArhBI7eazbkL0u767wc/EN1Bq1n2Hm7Eu/+/d ja3YG+a8yT3oFCqMNvn8wzAp65AGnwQCQkm/2/MVyKYbR0z6CBUszRfGXDFvBSLn fypPhSO6McE4HMGDuH/iN/a94kILGqX6/C/wUVACcKVPogn8W+Me4qz29gKB1E9U fm07NT3riao7jgZxDJWKlG990Cg/sp0Wzn3CBnsB/0BdQK3WPbpAmMPw1I1BvRyq WyR5zm5jeeBId04eC01ddvt29oGFSlSWQABufItviQH3JEo/vFUhu/6Uo89hsjO0 47CRSNZpNAqpwA3bEO51eH9j4DrPqp2tBAuchq5wcBIenJ++hd0ywADggpB4YWrS Hv7HophbGI7wEUIWx40XvSea/5wNVJPOcGHXLAg9rhemERvNNcqk+lIiUL2mK4aw 6BOSswbvD4HxTvUMyxdWCn974Kuu8vRYbaVRMNyL1wZEgAG6PToFCML3WYthH2iS 8r2vutssqhHXaYzuOXtVvM5XtWyoBwwQMXnTqN9DuY9wQ/KgNRfji/CJ2+iUXfJu 0mXYUutZGK4bJqzy/BjBGcW75sPGqvdAiCNJM1XAlRqX7uWCzP5Bw2GSRSI7F5yg fXC6XFEKNyPk+o5Nz7rAJwrEFBqJrhiZYpbiz106tJ7rXz9r2e11mBmyEsNa5tNL mWZbmB4= =CcIJ -END PGP SIGNATURE-
