When the client tries to start the element in production, they receive the following error:
"
Starting the protocol for SR1.TMDR.PROD failed. Not enough storage is available to complete this operation. (hr = 0x8007000E)
"
Under element log I can see the same output from SLElement (64bit) and SLDataMiner (32bit) processes.
There are 10 other elements running the same version (Alcatel SR Manager) on that DMA server without any issues.
I’ve checked the 32-bit processes on the affected DMA server (SLProtocol, SLDataMiner, SLDMS, etc.), and none of them reach a memory usage of 4GB (the upper limit for 32-bit processes), with virtual bytes also well within limits.
SLElement(64bit process) memory usage is around 9GB, which is still lower than on other DMA servers in the cluster.
Note: The client restarted the cluster after the initial occurrence of this issue. However, after the restart, when the element was starting, the same error reappeared.
Here is the overview of DataMiner Processes (32/64bit):
Hi Laurens, thank you for your response.
There is ~200GB free on local C: drive.
In terms of DB, Cassandra Cluster is used. It consists of 20 nodes distributed across 2 data centers, with 10 nodes in each DC. More than enough space is left on each of those nodes as well.
Hi Matej
As it seems to be directly related to Not enough storage to complete this operation - DataMiner Dojo, I assume you also checked the provided RNs?
When checking the memory usage, did you check the Virtual Bytes, as Laurens indicated here? automation script - not enough storage is available to complete this operation - DataMiner Dojo
Note - it might be best to check this via the trending of the Microsoft Platform element
You mention the client restarted the cluster. What would you maybe mean that the DM got restarted which hosted this element? (no reboot?)
Is this a new or old element?
Are there any noteworthy differences between the 10 other elements?
Do these elements/protocols handle large data sets? e.g. large tables
Can you see anything in the element log? Anything out of the ordinary, e.g. reading the elementdata that takes a long time (although this would cause other issues)
If the above won't help you, I would start looking into logs like SLDataminer, SLNet, SLDBConnection, SLErrors, SLErrorsInProtocol specifically on the time of occurrence.
Note - you can always contact techsupport@skyline.be for assistance.
Hi Robin, thank you for your answer.
I will post my answers to your questions in new dojo answer below, because I want to add figures as well.
And is there free disk space available both in the C drive and the location where the database data is stored?