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 console freezing/crash

NetXMS console freezing/crash

Scheduled Pinned Locked Moved Support
2 Posts 2 Posters 16.9k 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.
  • C
    C
    CrUser
    wrote on last edited by
    #1

    Hello, I tried to install the NetXMS version 5.2.5. This version of the server works without problems, but my client (console) freezes constantly, remains in a state of not responding. There is no rule when console is frozen, simply after a few clicks on the icons of the objects in the tree view, the screen remains frozen and the current server time stop, and the Windows system reports that the application is in the status of not responding. I waited up to 10 minutes but the console does not return to normal operation.
    After the forced close of the console (close task in Task manager) and start console again, everything works correctly. I looked at the log from the server and I don't see any server error, obviously the problem occurs on the console. Does anyone know this problem and maybe have a solution for it. I have many years of experience working with NetXMS version 3.2 and I have never encountered a problem similar to this.

    Thanks for any help,

    Tomislav

    1 Reply Last reply
    0
    • F
      F
      Filipp Sudanov
      wrote on last edited by
      #2

      Hello,

      How many alarms do you have in NetXMS? You can do "sh st" command in server debug console to see the number. In 5.2 it worked that way that if Alarms tab was opened at some moment, it stayed in background and consumed resources. This will be fixed in 5.3

      One recent finding is that Stacked line charts can lead to behavior like this - this is currently being fixed.

      And you can check .nxmc4/nxmc.log file in your home folder for any errors

      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