URGENT! New 8..5.1 on Linux install indexing overload CPU

Hi

We upgraded 11 servers over the weekend. 9 on Windows and 2 on Linux Z

10 servers are behaving properly but one of the Linux 64bit is acting up bad.

From what I see, Indexing gets hung on a database (never the same) and just fills up CPU until the server crash.

This has happened 4 times since the upgrade.

The other Linux is running fine as well as all the Windows.

This server has one difference where it is installed in a Partitioned schema with 2 other servers… The only thing is that 2 other servers have not been started yet. They will be for the near future.

I have a PMR and I have uploaded everything including the Core dump but so far, no call back

Anyone else might have an Idea? Could I remove all the FT folders and restart the server to let them rebuild?

Jacques

Subject: Update

I have finally restarted the server and stopped the Index and the Runjava task and the server has been behaving.

It looks like the old KVOOP problem found it’s way back in 8.5.1?

Jacques

Subject: Update 2

We were able to restart the server and stop the indexer yesterday. The server ran very well for the whole night and this morning we were having about 275 people on it.Then the Indexer started on it’s own… And all went to hell. Right now, the CPU is pinned at 80% and people have to close Lotus Notes to get failed over (mainly because the server is only partially responding)…

Is this happening only to me?

Jacques