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. NetXMS loading time

NetXMS loading time

Scheduled Pinned Locked Moved Support
4 Posts 3 Posters 55.0k 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.
  • D
    D
    dersonik
    wrote on last edited by
    #1

    It takes 1-2h for load NETXMS process - ubuntu 14.03
    CPU usage is very high.
    4GB RAM and SSD

    Any ideas what causing issues?

    1 Reply Last reply
    0
    • D
      D
      dersonik
      wrote on last edited by
      #2

      How to clean database from old DCI or alerts?

      I Found the problem, when NETXMS starting syncing/loading all alerts - I have over 1 million and how to clean this? Can't terminate because time out

      1 Reply Last reply
      0
      • T
        T
        Tursiops
        wrote on last edited by
        #3

        Hi,

        I believe reducing the AlarmHistoryRetentionTime from the default of 180 days, followed by running the housekeeper process (which usually runs once a night, but can be triggered by opening the NetXMS Server Console and running "hkrun") should clean that up somewhat. The housekeeper may run for a very long time though.
        Same with DCI data, you can set a DefaultDCIRetentionTime (or per DCI) as well as EventLog, AuditLog, Syslog and SNMPTrapRetentionTime.

        Not sure what database you are running. If it's Postgres, make sure your autovacuums are running properly, especially on the raw_dci_values table.

        Cheers

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

          Hi,

          I suggest to either truncate alarms table completely (but you will lose all alarm history) or delete alarms older than certain time before starting netxmsd. You can do this by running query

          DELETE FROM alarms WHERE last_change_time < ?;

          Replace placeholder with actual time stamp. It is in UNIX time format, you can use this calculator to get value: https://www.epochconverter.com/.

          Best regards,
          Victor

          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