Hello All,
A dataminer agent with 0 elements on the server is stuck at 99% loading. We can see in SLDataMiner this is the last line in the log for the last 20 minutes.
2024/01/25 13:26:01.676|SLDataMiner|CDataMiner::CreateModules|DBG|-1|** Starting Creation DataMiner Modules ...
And the only activity we can see is in SL XML
2024/01/25 13:26:24.512|SLXML|1636|6540|CXmlLockLog::Lock_Log|CRU|-1|File_28:THREAD 6540 WAITING FOR WRITE ACCESS (NO READERS; WRITER 19376/1)
2024/01/25 13:26:24.665|SLXML|1636|6540|CXmlLockLog::Lock_Log|CRU|-1|File_28:THREAD 6540 HAS WRITE ACCESS (157 ms)
We wanted to know if this is a known issue of the SLXml process being a bottleneck for a DataMiner agent to restart, and if so is there anything we can do to remedy this slow start-up.
Thank you,
Ryan
Hi Ryan,
you should be able to see more information in SLErrors file, I doubt SLXml is actual reason for DM being stuck at 99% but without logs from SLErrors it’s hard to say what the issue was. If it happens again please upload logs from SLErrors and we will be able to help you out more.
Hi Ryan,
It’s also advised to take the Log Collector dumps to contact our Support in case of issues. techsupport@skyline.be
I see that this question has been inactive for some time. Has this been resolved in the meantime? If yes, could select the answer to indicate that the question is now resolved?
As this question has now been open for a long time and there has been no further reaction from you, I will now close it. If you do wish to investigate this further, feel free to post a new question or contact techsupport@skyline.be for assistance.
If I understand it correctly, it took more than 20 minutes to start a DMA node with 0 elements on it? Something is indeed going wrong then...
Does this server have internet access? If starting up the processes is slow, it might be because the server has outdated revocation lists... If there is no internet access, this cannot be updated automatically... Not sure if that's the case here, but I vaguely remember a case like this.
Bert
It’s back up now. But we would like to understand if there is something that causes SLXml to behave like this?