Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

C

christian_k

@christian_k
Unfollow Follow
About
Posts
7
Topics
1
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • too much alarm
    C christian_k
    Support

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

    thank you,
    christian


  • too much alarm
    C christian_k
    Support

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

    best regards.


    events&rules


  • too much alarm
    C christian_k
    Support

    ok, this is it in the attached file


    events


  • too much alarm
    C christian_k
    Support

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


    event_processing_policy.JPG


  • too much alarm
    C christian_k
    Support

    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.


  • too much alarm
    C christian_k
    Support

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


  • too much alarm
    C christian_k
    Support

    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

  • Login

  • Don't have an account? Register

  • Login or register to search.
Powered by NodeBB Contributors
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups