NetXMS Support Forum

hi,

i'm a new user of netxms and a french speaker; i'll try my best to explain my problem in english. since a few day, when i restart my server, afer a few minute or functioning ,i get too much netxms alarm for the same node. in a minute, node's status change many time (minor to normal, normal to minor); when it happens, you can't work on netxms application, and the the heap size increases to 500M or more of 990M. How can i do to solve this please

Hi!

What is exact alarm message?

Best regards,
Victor

"name of node:node status changed to MINOR", "name of node:node status changed to NORMAL" like a winking until you exit the application

Looks like you have rule in event processing policy for events SYS_NODE_NORMAL, SYS_NODE_WARNING, SYS_NODE_MINOR, SYS_NODE_MAJOR, SYS_NODE_CRITICAL. Usually you should not generate alarms from those events.

Best regards,
Victor

i don't have any rules in event processing policy for that events. and something that i've seen is that, when it start happens, the cpu usage of the server stay at the high level (more than 90 %) during the execution of netxms (netxms more than 40%, nxmc more than 35%) so the server start to work very slow.

Can you please provide a screenshot of your event processing policy? Also, what NetXMS version you are using?

Best regards,
Victor

good morning, screenshot is in the attachement; i'm using the 1.2.13 version

It's hard to tell anything from rule comments only I need to see rules expanded. To avoid making lot of screenshots you can export all rules and attach xml file. Go to Tools -> Export configuration, and add all rules to the export. Then press "Save" icon to save it into XML file.

Best regards,
Victor

ok, this is it in the attached file

I only see event in exported file, not event processing policy rules. Did you add rules for export?

Best regards,
Victor

oh sorry, i forgot to add rules; this the right file in attachement.

best regards.

Hi!

It seems that rule named "Show alarm when node is down" has any event as a source (probably SYS_NODE_DOWN that was there originally was accidentally deleted) - that way it generates alarm on every event (including node status change events), thus triggering infinite loop of alarm creation. Add SYS_NODE_DOWN back and everything should be fine.

Best regards,
Victor

it works! thanks a lot for your prompt reaction. now netxms 1.2.13 is running find on my server.

thank you,
christian