error after scalix upgrade

[sgreen]

I just upgraded to 11.4.4 and I got the following error.
I have checked both drefs and it is an appointment which is indeed on the users calendar.
Users are able to move emails and such just fine, this seems to be just an issue for the indexer.
omsolve suggested contacting scalix, but I would rather not use points if this is a benign issue.
So what should I do?

ERROR Indexer (Indexer ) 07.01.09 02:47:56
[OM.DMON 3007] The SIS has been unable to process the Indexer's request. Details:
SIS could not handle this request.
Reason: 500 (Internal Server Error)
Indexer Service has discarded the message:
User name: Kyle Bernard /scalix
IndexId: b92ded3f-491c8627-4a451236-143c7f9
Attempted action: Add item 00460461b4e0ef00 to folder 00010781a3573283

[sgreen]

If any scalix folks think this is a big deal please tell me and I will go ahead and use the points.

[sgreen]

This happens each time our sysadmin team is mailed a tripwire report from a certain server, I would be happy to give a copy of one of these messages.

[itsupport_ublox]

Same Error-messages/issues here, if told that this is serious from Scalix people, ready to pay and open a call.

[mikethebike]

sgreen,

I would be tempted to go into that user's mailbox, and use the "lm" option to list the MAPI properties of the MAPi folders...looks like something has gone screwy with that mailbox (does this happen for all users?)

I have a good MAPI guide from previous incarnations if you would like a copy...goes through all the MAPI proerties stuff.

Mick

[itsupport_ublox]

here, it seems that this issue comes from upgrade, and nearly every user has such error messages.

greets

Mike

[sgreen]

Mike that MAPI guide would be great to have. The users I see that are impacted are not premium though so they don't even use MAPI.

[mario_aac]

Hi,

Yesterday I have upgraded from 11.4.1>11.4.4 (SB SLES 10.1)
log is full of OM 3007

Code: Select all

ERROR                          Indexer       (Indexer       ) 07.08.09 12:21:07
[OM.DMON 3007] The SIS has been unable to process the Indexer's request. Details:
SIS could not handle this request.
Reason: 403 (Forbidden)
Indexer Service has discarded the message:
         User name: Jane Doe /scalix
         IndexId: 390000c0-48625d85-4a4b2f40-59fbd6
         Attempted action: Delete item 000c87799372a9e2 from folder 000188c4d4f14b7a


Also mobile webmail interface was broken - config file instead of values held %DBNAME% (etc.) in particular places - restored config from backup. I'm still looking for config responsible for SIS part - might be broken the same way.

[mario_aac]

Yep, check ~/sx/sis/sis.properties - the problematic entries were index.client.whitelist and search.client.whitelist - simply #' them and restartscalix-tomcat. After upgrade they were set to %INDEX-WHITELIST% and %SEARCH-WHITELIST%

[sgreen]

mario_aac;
my search.client.whitelist and indexadmin.client.whitelist are set to the ip of the scalix server, should I comment those out?

[mario_aac]

You can try commenting them out, then if it helps it would mean, that services are connecting to sis on/from different ip than specified.
Increase logging in log4j for sis to DEBUG, and you should see in sis-search and sis-index logs some helpful clues.

[itsupport_ublox]

i get as an error message:

SIS could not handle this request.
Reason: 500 (Internal Server Error)
Indexer Service has discarded the message:
User name:
IndexId: e65822c3-487f2a0d-49b7dedd-9e3d39
Attempted action: Update the flags of item 0057cfde9c424719 in folder 0
056c4d6ec92629d

greets

Mike

[rudi]

Hi,
I have the same error:

omsolve -n OM.DMON 3007
-------------------------------------------------------------------------------
Error Group: OM.DMON Error Number: 3007

The SIS has been unable to process the Indexer's request. Details:
[][][][][][][][][][]

The SIS has been unable to process the Indexer's request, as indicated by
the SIS's HTTP response code.

Please contact Scalix.
-------------------------------------------------------------------------------

an I have to contact Scalix

Any solutions?

[bammers]

Hi guys,

As you have noticed, the upgrade to 11.4.4 does indeed expose some new error messages from the SIS indexer. However, as some of you suspected, they are not fatal and can be safely ignored. The underlying cause is that not all mail message headers comply fully with the relevant RFC specs and are rejected by the SIS. This situation has always existed, it is just that logging in 11.4.4 is more sensitive which is why you have started to notice them.

There is also a bug fix in progress to clean up the message headers to remove the problem at source.

Please watch this thread for details on when the fix will be ready.

- Bammers

[andreas]

I hvae also these problem!
Is there any solution now?