Page 1 of 1

QueueManager error (sis)

Posted: Fri Jan 05, 2007 6:17 pm
by heupink
hi all.

All of a sudden, I'm seeing lot's of these errors in scalix-sis-indexer.log:

2007-01-05 20:43:50,448 ERROR [QueueManager] [BatchUpdater.processMods:63] Failed to get reference modifier for user 5271000006b71324-9.341.78.291
java.io.IOException: Lock obtain timed out: Lock@/var/opt/scalix/i7/tomcat/temp/lucene-432db62a5349dff04c5f863420c41380-write.lock
at org.apache.lucene.store.Lock.obtain(Lock.java:56)
at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:254)
at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:244)
at org.apache.lucene.index.IndexModifier.init(IndexModifier.java:148)
at org.apache.lucene.index.IndexModifier.<init>(IndexModifier.java:124)
at com.scalix.sis.util.IndexUtil.getReferenceIndexModifier(IndexUtil.java:62)
at com.scalix.index.manager.BatchUpdater.processMods(BatchUpdater.java:60)
at com.scalix.index.manager.QueueManager.processQueue(QueueManager.java:127)
at com.scalix.index.manager.QueueManager.run(QueueManager.java:73)
at java.lang.Thread.run(Unknown Source)


The user number (5271000006b71324-9.341.78.291) is always the same.

What does this mean?

Posted: Thu Jan 11, 2007 6:48 am
by heupink
result:

Code: Select all

omsearch -e "GLOBAL-UNIQUE-ID=5271000006b71324-9.341.78.291" -m @all-attr@ -v
[OM 16954] Entry not in the Directory


so... that looks like an inconsistancy...

Any ideas how to proceed?

Posted: Thu Jan 18, 2007 2:30 pm
by ahathaway
That's the SIS URL for a user, not the Global Unique ID..

Indexing is discussed here (page 159): http://www.scalix.com/documents/Scalix_Admin_Guide_11.0_Draft1.pdf
and here (page 104): http://www.scalix.com/documents/Scalix_Install_Guide_11.0_Draft1.pdf

You'll need to use omshowu to find the user that SIS URL is associated with. Here's a command that will pull all users and feed them back through omshowu to get full details:

Code: Select all

omshowu -m all | gawk -F\/ '{print $1}' | xargs -i omshowu -n "{}" | \
    grep -B 16 '5271000006b71324-9.341.78.291'


That should return the relevant user.

--Aaron


heupink wrote:result:

Code: Select all

omsearch -e "GLOBAL-UNIQUE-ID=5271000006b71324-9.341.78.291" -m @all-attr@ -v
[OM 16954] Entry not in the Directory


so... that looks like an inconsistancy...

Any ideas how to proceed?

Posted: Thu Jan 18, 2007 4:02 pm
by heupink
thanks for replying!! :-)

I have TWO user sis urls that are generating the errors now:
1271000006b71324-9.341.78.291 and
5271000006b71324-9.341.78.291

feeding them both to the command gives NO results, both times.

checking with my own personal sis url gives the expected result (my own account details) meaning the command itself works perfectly.

So, it looks as if sis tries to index users that don't exist at all??

Posted: Thu Jan 18, 2007 4:14 pm
by ahathaway
After replying, I ran into a similar problem, at least with the write-lock files. On at least one occasion, restarting tomcat left some lock files hanging out.

Here's how I fixed it:

Code: Select all

# Stop tomcat
/etc/init.d/scalix-tomcat stop

# Make sure it's *really* stopped--if no output is returned
# tomcat is stopped
ps -ef | grep jav[a]

# Go to tomcat temp directory
cd /var/opt/scalix/i7/tomcat/temp/

# Remove any stale lucene lock files
rm -f lucene-*

# Start tomcat back up
/etc/init.d/scalix-tomcat start

# Watch SIS's log output for a while
tail -f /var/opt/scalix/i7/tomcat/logs/scalix-sis-indexer.log


You might also check the indexer directories to see if those indexes actually exist (/var/opt/scalix/i7/indexes/)

--Aaron


heupink wrote:thanks for replying!! :-)

I have TWO user sis urls that are generating the errors now:
1271000006b71324-9.341.78.291 and
5271000006b71324-9.341.78.291

feeding them both to the command gives NO results, both times.

checking with my own personal sis url gives the expected result (my own account details) meaning the command itself works perfectly.

So, it looks as if sis tries to index users that don't exist at all??
[/code]

Posted: Thu Jan 18, 2007 4:30 pm
by heupink
so...

this looks pretty good...

I've just tried your solution (simply removing the lock files) and all errors are GONE now.

Thanks!