Strange question....all documentation about upgrading to 3.x talks about changing "unixhierarchysep: yes", and we're actually using this value for years also on 2.5.x.
I will need to shutdown cyrus imapd when changing this option.
Will squatter run anyway with cyrus down?
Sonicle S.r.l. : http://www.sonicle.com
eXoplanets : https://gabrielebulfon.bandcamp.com/album/exoplanets
Da: Robert Stepanek <rsto@xxxxxxxxxxxxxxxx>
A: Gabriele Bulfon via Info <info@xxxxxxxxxxxxxxxxxx>
Data: 7 giugno 2021 16.48.36 CEST
Oggetto: Re: xapian problems
Does it work if you set the following in imapd.conf?unixhierarchysep: noOn Fri, Jun 4, 2021, at 4:08 PM, Gabriele Bulfon via Info wrote:Thanks! The only log i find is inside imapd.log (which is where we send local6.debug).Here I only see these about Xapian:Jun 4 07:09:56 wwwclone squatter[6691]: [ID 621814 local6.notice] indexing mailboxesJun 4 07:09:56 wwwclone squatter[6691]: [ID 793630 local6.info] indexing mailbox user/TEST1@xxxxxxxxxxx...Jun 4 07:09:56 wwwclone squatter[6691]: [ID 793630 local6.info] indexing mailbox user/TEST2@xxxxxxxxxxx...Jun 4 07:09:56 wwwclone squatter[6691]: [ID 793630 local6.info] indexing mailbox user/admin@xxxxxxxxxxx...Jun 4 07:09:56 wwwclone squatter[6691]: [ID 275131 local6.notice] skiplist: recovered /sonicle/var/imap/domain/s/sonicle.com/user/a/admin.conversations (31 records, 3352 bytes) in 0 secondsJun 4 07:09:56 wwwclone squatter[6691]: [ID 229495 local6.info] skiplist: checkpointed /sonicle/var/imap/domain/s/sonicle.com/user/a/admin.conversations (31 records, 3244 bytes) in 0.004 secJun 4 07:09:56 wwwclone squatter[6691]: [ID 919696 local6.notice] Xapian: 20 bytes in part FROMJun 4 07:09:56 wwwclone squatter[6691]: [ID 919696 local6.notice] Xapian: 19 bytes in part TOJun 4 07:09:56 wwwclone squatter[6691]: [ID 919696 local6.notice] Xapian: 23 bytes in part SUBJECTJun 4 07:09:56 wwwclone squatter[6691]: [ID 919696 local6.notice] Xapian: 10 bytes in part TYPEJun 4 07:09:56 wwwclone squatter[6691]: [ID 919696 local6.notice] Xapian: 9 bytes in part TYPEJun 4 07:09:56 wwwclone squatter[6691]: [ID 919696 local6.notice] Xapian: 10 bytes in part TYPEJun 4 07:09:56 wwwclone squatter[6691]: [ID 919696 local6.notice] Xapian: 9 bytes in part TYPEJun 4 07:09:56 wwwclone squatter[6691]: [ID 919696 local6.notice] Xapian: 24 bytes in part TYPEJun 4 07:09:56 wwwclone squatter[6691]: [ID 919696 local6.notice] Xapian: 573 bytes in part BODYJun 4 07:09:56 wwwclone squatter[6691]: [ID 919696 local6.notice] Xapian: 710 bytes in part BODYJun 4 07:09:56 wwwclone squatter[6691]: [ID 919696 local6.notice] Xapian: 200 bytes in part BODYJun 4 07:09:56 wwwclone squatter[6691]: [ID 919696 local6.notice] Xapian: 205 bytes in part BODYJun 4 07:09:56 wwwclone squatter[6691]: [ID 919696 local6.notice] Xapian: 33 bytes in part ATTACHMENTNAMEJun 4 07:09:56 wwwclone last message repeated 1 timeSonicle S.r.l. : http://www.sonicle.comeXoplanets : https://gabrielebulfon.bandcamp.com/album/exoplanetsDa: Robert Stepanek <rsto@xxxxxxxxxxxxxxxx>
A: Gabriele Bulfon via Info <info@xxxxxxxxxxxxxxxxxx>
Data: 4 giugno 2021 8.41.05 CEST
Oggetto: Re: xapian problemsOn Fri, Jun 4, 2021, at 8:40 AM, Robert Stepanek wrote:Hi,On Thu, Jun 3, 2021, at 11:53 AM, Gabriele Bulfon via Info wrote:sonicle@wwwclone:/sonicle/etc$ mdb coreLoading modules: [ libc.so.1 ld.so.1 ]> $C[...]ffffdf7fffdff0d0 libxapian-1.5.so.0.0.0`_ZN6Xapian16WritableDatabaseC1ERKSsii+0x69c()ffffdf7fffdff220 libcyrus_imap.so.0.0.0`xapian_dbw_open+0xd3()ffffdf7fffdff260 libcyrus_imap.so.0.0.0`end_message_update+0x7c()ffffdf7fffdff380 libcyrus_imap.so.0.0.0`index_getsearchtext+0x801()ffffdf7fffdff3e0 libcyrus_imap.so.0.0.0`flush_batch+0xf8()ffffdf7fffdff460 libcyrus_imap.so.0.0.0`search_update_mailbox+0x1d3()ffffdf7fffdff8d0 index_one+0x463()ffffdf7fffdff900 do_indexer+0x7e()ffffdf7fffdff9c0 main+0x776()ffffdf7fffdff9d0 _start+0x6c()What may have happened?Is there any initialization I should run for xapian?It looks as if Xapian doesn't find the database file it is instructed to open. Can you inspect in the core the 'path' string argument in Xapian::WritableDatabase. Or alternatively the first string in the 'char **paths' argument in xapian_dbw_open?Or just check the syslog, which should thankfully already report the erroneous path :)Cheers,Robert