On 05/24/18 04:41, Eric Wong wrote: > Konstantin Ryabitsev <[email protected]> wrote: >> Sorry I missed your reply! Yes, you're correct -- applying the above patch >> makes all tests pass. I'm guessing it's also the reason why I'm seeing the >> "already locked" error in my other tests, too: >> >> $ public-inbox-index /var/lib/public-inbox/meta.git >> Exception: Unable to get write lock on >> /var/lib/public-inbox/meta.git/public-inbox/xapian15: already locked > > OK, that Xapian bug should be worked around in > https://public-inbox.org/meta/[email protected]/ > > And pushed as commit c339a14b11c57e7b330f4efef6903bcbea2b3463 > ("workaround Xapian OFD locks w/o close-on-exec")
Hmm... I'm still getting the same error, though, if I try to re-run public-inbox-index: $ git clone --mirror https://public-inbox.org/meta Cloning into bare repository 'meta.git'... remote: Counting objects: 7524, done. remote: Compressing objects: 100% (164/164), done. remote: Total 7524 (delta 52), reused 0 (delta 0) Receiving objects: 100% (7524/7524), 3.80 MiB | 13.91 MiB/s, done. Resolving deltas: 100% (3770/3770), done. $ export PI_CONFIG=/etc/public-inbox/config $ public-inbox-index /var/lib/public-inbox/meta.git The above succeeds, but if I try to run it again right away: $ public-inbox-index /var/lib/public-inbox/meta.git Exception: Unable to get write lock on /var/lib/public-inbox/meta.git/public-inbox/xapian15: already locked Is this easier solved by upgrading to the version of xapian > 1.2.22? I can probably nag the Epel packager to do that if it's a legitimate bug in Xapian. Best, -- Konstantin Ryabitsev Director, IT Infrastructure Security The Linux Foundation
signature.asc
Description: OpenPGP digital signature
