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

  1. Home
  2. Support
  3. Subnet Deleted - Flooding Events

Subnet Deleted - Flooding Events

Scheduled Pinned Locked Moved Support
3 Posts 2 Posters 9.2k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • F
    F
    fj89j
    wrote on last edited by
    #1

    Hi

    Since installing 1.2.10, events haven't worked properly. The event log is constantly hit with:

    20.12.2013 09:31:44 <unknown> Normal SYS_SUBNET_DELETED Subnet deleted

    This generally leaves the current timestamp shown in the event log as being 20 minutes or so behind the current time, as it must be processing so much. It also makes sense, as alerts from hosts being down, etc. are taking forever to process, if at all.

    This happened in an upgraded database and then when other issues came to light, I started from scratch, so this is in a new database, fresh install.

    Any ideas what could be causing this?

    Thanks

    1 Reply Last reply
    0
    • V
      V
      Victor Kirhenshtein
      wrote on last edited by
      #2

      Hi!

      It's a bug in 1.2.10 - you got lots of such events for each object deletion. It's harmless, just annoying. To prevent excessive number of records in event log, go to event configuration and uncheck "write to event log" option for SYS_SUBNET_DELETED event. We plan to release version 1.2.11 in the end of december which will fix some important issues in 1.2.10. If problem is serious, I can provide a patch for 1.2.10 as well.

      Best regards,
      Victor

      1 Reply Last reply
      0
      • F
        F
        fj89j
        wrote on last edited by
        #3

        Thanks for coming back to me so fast Victor.

        It is causing an issue with alerts at the moment in a big way, however, I'd rather wait till the end of the month for a fix in 1.2.11, rather than creating work for you.

        The strange thing with this is that is does seem to stop processing all other events. Thinking back, it may have been an issue when I deleted a host not that long after installing and then it just spams the event monitor with that message. There are probably upwards of 4000 nodes that is has detected, so this may have just pushed it over the edge.

        Have a great Christmas and I look forward to the new version!

        1 Reply Last reply
        0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • 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