Scalix Indexing Service is DoS'ing my server

[obrien.dan]

Hello all,

I've recently setup Scalix 11.1. and ran into some issues with scalix-tomcat interfering with my existing tomcat installation, where I cannot run the web based scalix services at the same time as my existing web services. Last week I set it up as a stand-alone POP3 / SMTP server, at least until I can find time to work out the tomcat issues, and everything has been working fine. Yesterday I noticed my webpages were taking forever to load, and finally apache locked itself up and had to be restarted. I did some digging and found this in my apache access_log

Code: Select all

--snip--
XX.XX.XX.XX - - [27/Jun/2007:14:40:28 -0400] "GET /sis/indexer?fn=delete&uid=090000006f841764-61.621.942.27&dref=0001120c60c6c19c&pdref=00011c0014b741e4 HTTP/1.1" 404 288 "-" "-"
XX.XX.XX.XX - - [27/Jun/2007:14:40:38 -0400] "GET /sis/indexer?fn=delete&uid=090000006f841764-61.621.942.27&dref=0001120c60c6c19c&pdref=00011c0014b741e4 HTTP/1.1" 404 288 "-" "-"
XX.XX.XX.XX - - [27/Jun/2007:14:40:49 -0400] "GET /sis/indexer?fn=delete&uid=090000006f841764-61.621.942.27&dref=0001120c60c6c19c&pdref=00011c0014b741e4 HTTP/1.1" 404 288 "-" "-"
XX.XX.XX.XX - - [27/Jun/2007:14:40:59 -0400] "GET /sis/indexer?fn=delete&uid=090000006f841764-61.621.942.27&dref=0001120c60c6c19c&pdref=00011c0014b741e4 HTTP/1.1" 404 288 "-" "-"
XX.XX.XX.XX - - [27/Jun/2007:14:41:09 -0400] "GET /sis/indexer?fn=delete&uid=090000006f841764-61.621.942.27&dref=0001120c60c6c19c&pdref=00011c0014b741e4 HTTP/1.1" 404 288 "-" "-"


And this in my apache error_log

Code: Select all

--snip--
[Wed Jun 27 14:42:14 2007] [error] [client XX.XX.XX.XX] File does not exist: /home/nwebuser/public_html/sis
[Wed Jun 27 14:42:25 2007] [error] [client XX.XX.XX.XX] File does not exist: /home/nwebuser/public_html/sis
[Wed Jun 27 14:42:35 2007] [error] [client XX.XX.XX.XX] File does not exist: /home/nwebuser/public_html/sis
[Wed Jun 27 14:42:46 2007] [error] [client XX.XX.XX.XX] File does not exist: /home/nwebuser/public_html/sis
[Wed Jun 27 14:42:56 2007] [error] [client XX.XX.XX.XX] File does not exist: /home/nwebuser/public_html/sis


The messages just cycle over and over in an almost endless loop until i shut down scalix server.

I've tried to stop the indexer service with omoff but that just spits out the following

Code: Select all

[root@XX.XX.XX.XX ~]# omoff -d 0 Index 
omoff : [OM 4904] Sub-system cannot be started, stopped or reset: 'Index'
No subsystems shut down.


After some searching I found that I'm not the 1st one to have a similar problem, but no one seems to have an answer on how to fix it.

I really would like to use Scalix, but at this rate I fear I may need to find another alternative. Any help would be greatly appreciated.

Regards,
Dan O'Brien

[Valerion]

That means the SIS (Search and Index Service) is not running properly. It is one of the tomcat components. Make sure it's installed and running, and that the apache tomcat connector info is correct (check /etc/opt/scalix-tomcat/connector/jk/instance-<servername>.conf for the vhost definition).

The Indexer is listed as a critical core service and can't be shut down without bringing Scalix as a whole down.

[obrien.dan]

Sorry for the delay in my response, I've been away for a few days. Thanks for your reply.

I've disabled both the Scalix-Tomcat instance and the mod_jk connector because it wasn't playing nice with my existing Tomcat / mod_jk setup and I've been using it as a POP3 server only. In so far from all the experience I've had over the past few weeks with Scalix, it appears that my only options are (1 ) install scalix on a standalone machine, (2 ) use another MTA.

[Valerion]

Or you can try to get the two tomcat instances to coexist peacefully. I've done that myself before, not too hard, but you have to understand tomcat a bit before you can do that. What exactly are you having issues with letting them coexist?

[obrien.dan]

I think it's just a port conflict, though I haven't had much time to dig deeper. I originally posted my issues here. I started to look into how Scalix / Scalix-Tomcat is setup, but I have about 50 other things on my plate so this has been at the bottom of my priority list.