Team,
We upgrade one of our LL installations to 9.7.1 from 9.5.1. (this is our second installation. We have 3 installations due to huge setup here).
In this upgrade, things went smooth. We have 2 front end with 3 LL instances and one seperate admin machine.
In the admin machine though livelink service crashes every one hour (not the admin server but livelink service).
We are in March 2009 patch.
We see similar kind of logs (below) when it crashes. OT support is also scrambling to find a reason.
Gurus, can you help me here. It looks like extractor process is in the middle of extraction when this happens.
It says bad allocation. I guess memory is being killed somewhere. We are monitoring memory also but of no use since it does not spike huge before the crash.
Log[7] : [-1187642304]_WriteObject content ref
loc[\\exfilestore\pd\exfile\0052\259\52259846.dat] Log[7] :
IndexLibrary.UpdateLibraryNodeIterator::Next() processing
R<'Seq'=52259845,'Operation'=1,'DataID'=52259845,'VersionNum'=0> Log[7] :
[-1187642288]ExportToIPool: AddOrReplaceataId=52259845&Version=1
RMClassificationMetaData Error selecting against rimsNodeClassification for
nodeId 52259845 Log[7] : [-1187642226]_WriteObject content ref
loc[\\exfilestore\pd\exfile\0052\259\52259845.dat] Log[7] :
IndexLibrary.UpdateLibraryNodeIterator::Next() processing
R<'Seq'=52259844,'Operation'=1,'DataID'=52259844,'VersionNum'=0> Log[7] :
[-1187642210]ExportToIPool: AddOrReplaceataId=52259844&Version=1 07/26/2009
15:37:21 [2092808424] LLServer caught an exception: bad allocation;
terminating. 07/26/2009 15:37:21 [2092808569] LLI thread 4 shutdown (thread
exiting) Socket object auto-closed
We upgrade one of our LL installations to 9.7.1 from 9.5.1. (this is our second installation. We have 3 installations due to huge setup here).
In this upgrade, things went smooth. We have 2 front end with 3 LL instances and one seperate admin machine.
In the admin machine though livelink service crashes every one hour (not the admin server but livelink service).
We are in March 2009 patch.
We see similar kind of logs (below) when it crashes. OT support is also scrambling to find a reason.
Gurus, can you help me here. It looks like extractor process is in the middle of extraction when this happens.
It says bad allocation. I guess memory is being killed somewhere. We are monitoring memory also but of no use since it does not spike huge before the crash.
Log[7] : [-1187642304]_WriteObject content ref
loc[\\exfilestore\pd\exfile\0052\259\52259846.dat] Log[7] :
IndexLibrary.UpdateLibraryNodeIterator::Next() processing
R<'Seq'=52259845,'Operation'=1,'DataID'=52259845,'VersionNum'=0> Log[7] :
[-1187642288]ExportToIPool: AddOrReplaceataId=52259845&Version=1
RMClassificationMetaData Error selecting against rimsNodeClassification for
nodeId 52259845 Log[7] : [-1187642226]_WriteObject content ref
loc[\\exfilestore\pd\exfile\0052\259\52259845.dat] Log[7] :
IndexLibrary.UpdateLibraryNodeIterator::Next() processing
R<'Seq'=52259844,'Operation'=1,'DataID'=52259844,'VersionNum'=0> Log[7] :
[-1187642210]ExportToIPool: AddOrReplaceataId=52259844&Version=1 07/26/2009
15:37:21 [2092808424] LLServer caught an exception: bad allocation;
terminating. 07/26/2009 15:37:21 [2092808569] LLI thread 4 shutdown (thread
exiting) Socket object auto-closed