Hi,
We have a system that was installed some time ago, originally running on version 9.x, and currently managing around 800 elements.
Since then, we've upgraded to a newer version. As you're aware, newer versions come with increased hardware requirements. Following the upgrade, we initially experienced an issue where the elements information appeared as not initialized, although all their data was still visible via Web Access Monitoring.
The main issue we’re facing now is that when the server starts up, the CPU usage spikes to 100% while loading the elements. This causes DataMiner to crash and restart, resulting in a continuous loop. To break the cycle, I manually stopped most of the elements so I could at least access Cube. I'm now able to view information on the running elements, but I have to start them manually, one by one.
My question is: is there an option to delay the startup of elements, so that Cube can load first and the elements can be initialized gradually afterward? This would help reduce the CPU load during startup.
keep in mind we are looking into having the system upgraded but until then we need to still be able to monitor our sites.
Hi Zean,
I know that this option exists: initial attribute | DataMiner Docs
However, this would require temporarily modifying the connectors, which might not be ideal in your case.
A better alternative could be to create a script that pauses all elements (to avoid you to do that when you want to restart the system), and then another one that starts them up gradually — for example, starting X elements every few minutes. This would help spread the CPU load over time and avoid overload during system startup.
Kind regards,