What can cause a failure to create new alarm properties?
Hi Jeroen
I'm not able to tell you what exactly can cause the failure. I can tell you how to investigate it.
If you would try this and it occurs again, keep note of the time.
- Could you see some kind of error/notice in the information events?
- Did the Client logging show anything? (i.e. System Center/Logging -> tab pages "Cube" and "Communication").
- Does the SLNet.txt log file give any clues?
- Initiate an SLNet Client Test Tool follow when you reproduce the issue.
- There aren't any RTE's on the system are there? (check SLWatchdog2.txt)
What might also help your investigation is:
- What's the DM version?
- is it a cluster/single DM?
- Zenoss is that an element?
- When was the last time you created a new property?
In other words, what changed since last time? - Do you get this wherever you try to create a property (i.e. any view, service, alarm, element) or is it isolated?
I hope this'll help you further 🙂
Do you see something in the SLNet logging? During normal operation a "Update Property Config" line should be added there when you add a new property.
If nothing incriminating is shown there, I would check the Cube logging for clues around that timestamp.