no search result on new created contacts - old contacts are found
-
if you migrated from Zarafa to Kopano you need to check that your search.cfg is correct and (at least for me) it helped by deleting the old index files and starting from scratch. It took a while to perform the first search, but it has been working perfectly well since.
-
@mcostan said in no search result on new created contacts - old contacts are found:
if you migrated from Zarafa to Kopano you need to check that your search.cfg is correct and (at least for me) it helped by deleting the old index files and starting from scratch. It took a while to perform the first search, but it has been working perfectly well since.
As I wrote, we just copied the mysql database and the attachment folder to a a fresh installed kopano server.
-
check search.cfg
and also the log file /var/log/kopano/search.log
make sure the search daemon is working and check what search.log says
It should be very self explanatory.
-
@anotherandy said in no search result on new created contacts - old contacts are found:
hi @cmks ,
can you give us some more details?
Are the packages installed by subscription or did you use the packages?
Have you checked the logfiles under /var/log/kopano/*?
Is your search configured correctly?
https://documentation.kopano.io/kopanocore_administrator_manual/configure_kc_components.html#configure-kopano-search
Best regards
AndreasDear Andreas,
we installed using the package manager with packages from a subscription. We checked the log files, in the search log there where a lot of MAPI_E_INVALID_ENTRYID messages.
server.cfg / search.cfg were configured well.
What we did now, before starting the complete reindex, ist running kopano-search-upgrade-findroots.py and the script fixed two entries. While reindexing there were a lot of warnings and errors in the log (see my other post). After finishing the initial index process (at 17:23:08) the log gets calm:
2017-12-11 17:23:08,909 - index1 - WARNING - output on stderr:
Can’t create config directory (/.w3m)!..
2017-12-12 03:46:16,270 - index0 - WARNING - output on stderr:
Can’t create config directory (/.w3m)!..
2017-12-12 06:25:53,750 - index1 - WARNING - output on stderr:
Can’t create config directory (/.w3m)!..What is the cause of these (/.w3m) messages?
Regards
-
to me it looks like there is something wrong in the installation. I haven’t seen anything like that before in the search.log files.
Is everything else in Kopano working?
Perhaps try removing the kopano-search packages and try installing them again?
Also check that search.cfg has a writable path where the indices will be stored?
-
@mcostan Kopano works fine. Kopano-search creates and ongoing modifies all its files under /var/lib/kopano/search. The direcotry is owned by kopano:kopano. Searching in the WebApp is working, results as expected (since reindexing).
search config:
index_path = /var/lib/kopano/search/
#run_as_user = kopano
#run_as_group = kopano
#pid_file = /var/run/kopano/search.pid
#running_path = /var/lib/kopano
limit_results = 1000
#sslkey_file = /etc/kopano/ssl/search.pem
#sslkey_pass = replace-with-server-cert-password
server_bind_name = file:///var/run/kopano/search.sock
ssl_private_key_file = /etc/kopano/search/privkey.pem
ssl_certificate_file = /etc/kopano/search/cert.pem
log_method = file
#log_level = 3
log_file = /var/log/kopano/search.log
log_timestamp = 1
#search_engine = xapian
term_cache_size = 256M
#index_exclude_properties = 007D 0064 0C1E 0075 678E 678F
index_processes = 3
#index_junk = yes
suggestions = yes
index_attachments = yes
index_attachment_max_size = 15MNothing special.
Best regards
-
@cmks said in no search result on new created contacts - old contacts are found:
/var/lib/kopano/search/
have you tried
stopping kopano-search
thenrm -fr /var/lib/kopano/search/.
and then restarting kopano-search?
-
@mcostan Sorry, I forgot to mention, since reindexing was done all contacts are found. So reindexing (and maybe running kopano-search-upgrade-findroots.py) fixed the problem for now.
I’m still on this thread to figure out the cause why it stopped working (and of the unexpected log entries).
Best regards
-
perhaps you still had some indices left over from Zarafa, not sure.
Anyway when in the past I had issues (long long time ago) the solution was to do what I said above, i.e. stop search, erase the indexes, then start again and wait for it to index them again.
-
@cmks Good to hear its working now.
But it looks like you’re running kopano as root? You really shoudln’t ;-)
Please mark the case as solved.
Best regards -
@anotherandy said in no search result on new created contacts - old contacts are found:
@cmks Good to hear its working now.
But it looks like you’re running kopano as root? You really shoudln’t ;-)
Please mark the case as solved.
Best regardsEven if the user/group entries in all configs are commented out there seems to be a default configuration, at least on debian with subscription installation, which leads to user “kopano” and group “kopano”:
Output of “ps -eo euser,ruser,suser,fuser,egroup,comm”
kopano kopano kopano kopano kopano kopano-presence
kopano kopano kopano kopano kopano kopano-server
kopano kopano kopano kopano kopano kopano-ical
kopano kopano kopano kopano kopano kopano-monitor
kopano kopano kopano kopano kopano kopano-spooler
kopano kopano kopano kopano kopano kopano-search
kopano kopano kopano kopano kopano kopano-dagent
kopano kopano kopano kopano kopano kopano-ical
kopano kopano kopano kopano kopano kopano-dagent
kopano kopano kopano kopano kopano kopano-spooler
kopano kopano kopano kopano kopano kopano-search
kopano kopano kopano kopano kopano kopano-search
kopano kopano kopano kopano kopano kopano-search
kopano kopano kopano kopano kopano kopano-search -
@anotherandy said in no search result on new created contacts - old contacts are found:
@cmks Good to hear its working now.
But it looks like you’re running kopano as root? You really shoudln’t ;-)
Please mark the case as solved.
Best regardsIt is not really solved - we made it working again - but the cause, why indexing of new objects was stopped, is not figured out.
