Hm okay...
So this lucene bug can result in a total crash of sipXecs?
-----Original Message-----
From: sipx-users-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of George
Niculae
Sent: maandag 9 mei 2011 21:24
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Problems with sipregistrar service
On Mon, May 9, 2011 at 4:35 PM, Henry Dogger <h.dog...@telecats.nl>
wrote:
> George,
>
> I'm absolutely sure no import is running...
> The job status is not showing any imports, and the import was started
two weeks ago with about 300 users.
> Is there any process on which I can grep which shows a import
running/hanging on the background?
Then I think you hit again that Lucene issue, drop indexes and see if
it gets better.
"2011-04-18T09:05:15.724000Z":116832:JAVA:ERR:server1.mydomain.local
:background:00000000:LuceneUtils:"ignoring error on close"
java.lang.IllegalStateException: docs out of order (-2 < 0 )
at
org.apache.lucene.index.SegmentMerger.appendPostings(SegmentMerger.java:
335)
at
org.apache.lucene.index.SegmentMerger.mergeTermInfo(SegmentMerger.java:2
98)
at
org.apache.lucene.index.SegmentMerger.mergeTermInfos(SegmentMerger.java:
272)
at
org.apache.lucene.index.SegmentMerger.mergeTerms(SegmentMerger.java:236)
at
org.apache.lucene.index.SegmentMerger.merge(SegmentMerger.java:89)
at
org.apache.lucene.index.IndexWriter.mergeSegments(IndexWriter.java:709)
at
org.apache.lucene.index.IndexWriter.mergeSegments(IndexWriter.java:686)
at
org.apache.lucene.index.IndexWriter.flushRamSegments(IndexWriter.java:65
6)
at
org.apache.lucene.index.IndexWriter.close(IndexWriter.java:402)
George
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
