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

H

hitzi

@hitzi
Unfollow Follow
About
Posts
5
Topics
3
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Alarm Parameter %6 is empty
    H hitzi
    Support

    Hi,

    I check the free space of the filesystem with this parameter FileSystem.Free(F:). This works great.
    But when I define a alarm with the text "File system %6 is low on free space (ony %4GB remains)" parameter %4 is working but parameter %6 is empty. I think should %6 display "F:" if I interpret this tutorial right: https://wiki.netxms.org/wiki/How_to_send_e-mail_notification_when_disk_space_is_low

    Or is there another way to display the used drive letter in the alarm message?

    Thanks
    hitzi


  • Text encoding in E-mails is wrong since version 4
    H hitzi
    Support

    Oh, I didn't check this part of the configs.
    We use MailEncoding=iso-8859-1 in the smtp config. iso-8859-1 includes the german umlauts. Is it a bug or should we use another mail encoding?


  • Text encoding in E-mails is wrong since version 4
    H hitzi
    Support

    Hi,

    we use E-Mail for some alarms. The E-Mail is defined in this way:
    Subject: [%s] %n: %m
    Text: [%s] %n: %m - %<currentValue>

    The Problem is that %s and %m don't display the german umlauts. It shows a wrong char instead.The same configuration worked fine with before the update to version 4.

    Thanks and best regards
    Thomas


  • Very slow when terminate/solve alarms
    H hitzi
    Support

    Thank you.


  • Very slow when terminate/solve alarms
    H hitzi
    Support

    Hi,

    when I terminate/solve for example 10 alarms at once it could last up to 3-4 minutes until the alarms are really terminated - I even get a timeout on the webui. The process netxmsd.exe consumes 25-30% CPU in all this time. Why does this happen and why is it so slow?

    NetXMS runs on a Windows 2012 R2 Server with a MSSQL Express database.
    show stats:
    Objects: 1897
    Monitored nodes: 301
    Collectible DCIs: 3936
    Active alarms: 34931

    There are not that many nodes but the database size is 7GB. Why is this db so big and could this the problem which slows down terminating/solving alarms? I already shrinked/compress the db- this reduced the size from 8,5GB to 7GB.

    show pollers: results most of the time is one object from type stat. From time to time there are more pollers.

    The screenshot is from the time when I terminated 10 alarms at once.


    netxms.jpg

  • 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