grosjo / fts-xapian

Dovecot FTS plugin based on Xapian
GNU Lesser General Public License v2.1
91 stars 19 forks source link

Error: FTS Xapian: Optimize UID inexistant #123

Closed Philippe23 closed 9 months ago

Philippe23 commented 2 years ago

I've started getting a few errors like these within the last month:

doveadm(XXX): Error: FTS Xapian: Optimize UID=5449 inexistant
doveadm(XXX): Error: FTS Xapian: Optimize UID=486212 inexistant
doveadm(XXX): Error: FTS Xapian: Optimize UID=486215 inexistant

The "XXX" user has always been the same so far.

What does it mean and what can I do about it?

grosjo commented 2 years ago

Kindly test latest git

Philippe23 commented 2 years ago

I'm running latest now. I'll report back when I see another error.

symphorien commented 1 year ago

I also get about 500 of such errors when running doveadm fts optimize -A as recommended by the readme. I'm on version 1.5.5 Upgrading to current master 438b4e474ee26fa4606c0b06f8eb69f1cd6e0f55 fixes this message.

bsdice commented 1 year ago

@grosjo Hi... could you please release a new version with this fix so Arch picks it up? Getting 2000 lines each night. ;-) Thanks!

grosjo commented 1 year ago

Just put verbose=0 in the conf file

fts_xapian = partial=2 full=20 verbose=0

symphorien commented 1 year ago

ah so it's just a harmless warning?

bsdice commented 1 year ago

Hrm... Arch has 1.5.5 from 2022-04-17, also I already had verbose=0 active but messages are still present. Merci bien!

Philippe23 commented 1 year ago

I'm running latest now. I'll report back when I see another error.

Just to report back in: since building against HEAD sometime near the end of April, I have not had these errors re-occur.

Cutting a 1.5.6 would get this fix to more people. (nudge, nudge)

nachtbraker commented 1 year ago

@grosjo I'm seeing the same problem on FreeBSD. I agree that a new release would fix this, otherwise the pkg for FreeBSD will not receive this fix.

brittAnderson commented 9 months ago

Despite having set verbose=0 in the conf and using version 1.5.5 I am seeing these errors as well. Using archlinux package for installation. Happy to provide additional details if useful. Would be happy just understanding what is causing these errors so I know whether I can safely ignore. Thank you.

grosjo commented 9 months ago

Ok, will issue new package

grosjo commented 9 months ago

Released 1.5.6