Scalix Forums

After upgrading to 11.0.1, new messages are not being indexed. Using outlook or webmail, I do not see messages received after the upgrade in the search results. I can see the indexer service is running with omstat -s, `/etc/init.d/scalix-tomcat status` indicates that tomcat is running, and there are around 700 files waiting to be indexed in ~/indexwork. I do not see any errors in the logfiles that seem to be related to this... What do I need to do to get the indexer to start scanning messages again?

I am not sure if this is related, but SWA did not work after the upgrade and I followed the recommendations in this thread: viewtopic.php?t=6018.

Thanks,
Steve

Hi!

I would suggest you to re-create the message store index using the command "sxmkindex",
please refer to the man page of the command for details. It would be better if you run the
command without options so that the index gets created for the complete message store.

Please feel free to reply with your concerns.

Thanks,
Subir

Hi Subir,

I do have concerns with this approach, since I would not expect to have to run again after upgrading to a maintanence release... When I ran sxmkindex after upgrading to Scalix 11.0.0, it took nearly 5 days to complete.

Anyway, I tried running the command again and it completed much faster this time. However, it looks like it did not do anything since the system is almost idle and I do not see any activity in the scalix-sis-search.log and scalix-sis-indexer.log log files. What should I try next?

Thanks,
Steve

Hi Steve,

I would request you to refer to the heading "Upgrading to the Search and Index Service"
on page 98 of the Scalix Installation guide at:
http://www.scalix.com/documents/Scalix_Install_Guide_11.0.1.pdf
This section describes the resolution to the issue.

Thanks,
Subir

Hi Steve,

As you have mentioned there are about 700 files to be indexed, I would like you to edit the
values in /var/opt/scalix/s4/sis/sis.properties file for:
index.max.queue.size=1000
search.max.results=1000

Restart scalix-tomcat service, to see if the issue gets resolved.

Thanks,
Subir

Hi Subir,

Sorry about the delay, did not have a chance to put this change in until today. I just made the changes to the sis.properties file and restarted scalix, scalix-postgres and scalix-tomcat. Now I am seeing many index.browse processes and the logfiles are showing signs of sis working.

I will check on the system later this weekend to see if I can search for emails that I received after the upgrade.

Thanks!
Steve

I just tried searching again today and your suggestion fixed the problem.

Thanks again!
Steve

This issue has occured again... We have 5815 files in the indexwork directory and SIS is not processing them. I have increased the index.max.queue.size to 7000 and restarted tomcat, hoping that would solve the problem. I do not see any activity in SIS's log and running sxmkindex again doesn't seem to help.

Any suggestions on how to get SIS started again?

Thanks,
Steve

It looks like changing that property got SIS to start working again. I checked the indexwork directory again this morning and there are 3530 messages