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

M

Mystery

@Mystery
Unfollow Follow
About
Posts
42
Topics
14
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Re: No More "SYS_NODE_DOWN" Events, Only "SYS_NODE_UNREACHABLE" Since Recent Version
    M Mystery
    Support

    Hello, Ok:)

    SYS_NODE_DOWN Offline EPP is here (+ Events SYS_NODE_DOWN, defined Source Objects):

    • Alarm

    EPP for SYS_NODE_UP Alarm:

    • Server Actions:

    • Timer Cancellations all 3 Delay timer keys.

    I think problem is due to not getting SYS_NODE_DOWN first ... only SYS_NODE_UNREACHABLE AND SYS_ICMP_UNREACHABLE.


  • Re: No More "SYS_NODE_DOWN" Events, Only "SYS_NODE_UNREACHABLE" Since Recent Version
    M Mystery
    Support

    Hello, I have same problem ... Problem is when SYS_NODE_DOWN emails are sent after few polls and SYS_NODE_UP with blocking timer key ... so the result is I am getting SPAM of SYS_NODE_UP emails.


  • Data Collection Configuration - Trigger email when node goes down
    M Mystery
    Support

    Hello, yes the timer was running. Probably I found an issue, I had same name of timers and first policy canceled the timer so the second one sent email. Dumb error. Thank you:)


  • Data Collection Configuration - Trigger email when node goes down
    M Mystery
    Support

    This one is bugged way more.

    Ofline email:
    Condition: IF source object is one of the following: Ustredna.CPU1.Policka AND SYS_NODE_DOWN

    Online email:
    Condition: IF source object is one of the following: Ustredna.CPU1.Policka AND SYS_NODE_UP

    This is what happened with node:

    And we got only ONLINE emails 😞

    There should be a 180 sec delay with NODE_DOWN_NOTIFICATION_%i
    Which is correct behaviour, email is not recieved.
    BUT Do not run if timer with key NODE_DOWN_NOTIFICATION_%i is active is not working and it sent email 😞

    Any idea? Thank you.


  • Data Collection Configuration - Trigger email when node goes down
    M Mystery
    Support

    Thank you. I will apply EPP to the container — that should do the trick.
    The DCI thresholds are working fine and repeatable without any issues, but sending repeated emails via EPP could be a problem. I don't want to configure 100 server actions with hourly delays.
    I'll try to handle that part with a script. Thanks again.
    By the way, there might be a bug in the

    SYS_NODE_DOWN
    

     event.
    I followed the documentation on how to send an email when a node goes down and then comes back up.
    Specifically, this part:

    If, in addition, we want to send a notification when a node comes up, but only if a notification about it going down was sent: https://netxms.org/documentation/adminguide/_images/delayed_action_2.png

    Somehow, I'm receiving "ONLINE" emails even though there was no "OFFLINE" event.
    For example, in one case, there was no

    SYS_NODE_DOWN
    

     event at all — only

    SYS_NODE_UP
    

    , which triggered the email.
    The blocking part

    NODE_DOWN_NOTIFICATION_%i
    

     doesn't seem to be working.
    This node has only ICMP polling.
    Do you have any idea how to fix this?

    Thank you:)


  • Data Collection Configuration - Trigger email when node goes down
    M Mystery
    Support

    Hello,
    Thank you for the link to the documentation. It seems that EPP is a much better approach.
    May I ask a few more questions?

    1. If I want to assign source objects to a list of objects, is that possible? Or do I have to select them one by one?
    2. Is it possible to select an entire container with nodes in the Infrastructure section?
    3. In the Server Actions section, I have a mail action with a delay. Can I configure it to repeat, for example, every hour while a node is down?

    Thank you for the information 🙂


  • Data Collection Configuration - Trigger email when node goes down
    M Mystery
    Support

    Hello, I have few more questions. When SYS_NODE_DOWN trigger EPP to send email, is it possible to send it after some time, like if this node is 3-5 polls (3-5 min) down instead of instantly (or delayed) send this notification? I would like to prevent spamming when node is flapping.

    Is there any option how to send email from EPP, when node is down (for example 60 min) and goes online? Like device is offline for 5 min (send email) and devices goes online (send me email about it again).

    I still think Data Collection Configuration from template and binding to nodes is better, I can poll these values faster and trigger Deactivation event when node is online. Like this one:

    Can I get SYS_NODE_DOWN to Data Collection Configuration like internal metric?
    Thank you for help.


  • Data Collection Configuration - Trigger email when node goes down
    M Mystery
    Support

    Hello,

    can you help me to figure out, how to send emails from Data Colection Configuration when node goes down?
    I have mailing template with some collecting parameters. 
    I would like to set up some parameter with threshold which collect something like Internal:ICMP ping: packet loss when >99% ... but this took too long to (when node goes down it jumps like 1,3,5% per poll) . Is there any better approach?
    Some nodes have only ICMP ping (not NetXMS agent or SNMP). When I browse Metric to collect from internal Origin, there is only ICMP ping which don't work well.

    Thank you:)


  • Sending mail from Event Processing Policy not working
    M Mystery
    Support

    Thank you, it helped:)


  • Sending mail from Event Processing Policy not working
    M Mystery
    Support

    I tried disabling (+save) and reenabling (+save) and EP is still not working. If you don't mind, database query would be helpfull.
    Thank you:)


  • Sending mail from Event Processing Policy not working
    M Mystery
    Support

    Ok, thank you for info. 
    Is there any way how to fix these bad imported EPPs? Like disable and enable etc? Or should I delete them and create again?

    I couldn't upgrade the server, there were many errors in the upgrading process so I had to make it this way.


  • Sending mail from Event Processing Policy not working
    M Mystery
    Support

    MariaDB [netxms]> select rule_id, flags, comments from event_policy where rule_id in (59, 78);
    +---------+-------+-----------------------------------------+
    | rule_id | flags | comments                                |
    +---------+-------+-----------------------------------------+
    |      59 |  7936 | Network Device is OFFLINE - Send E-mail |
    |      78 |  7936 | Test new                                |
    +---------+-------+-----------------------------------------+
    2 rows in set (0,001 sec)


  • Sending mail from Event Processing Policy not working
    M Mystery
    Support

    Yes, XML (from 2.2 version) of this rule ID is here:
    Do you need some more details?

    <rule id="5">
    			<guid>0cdde918-dc08-4096-9418-0197355b2833</guid>
    			<flags>7936</flags>
    			<alarmMessage>%m</alarmMessage>
    			<alarmKey></alarmKey>
    			<alarmSeverity>5</alarmSeverity>
    			<alarmTimeout>0</alarmTimeout>
    			<alarmTimeoutEvent>43</alarmTimeoutEvent>
    			<script></script>
    			<comments>Network Device is OFFLINE - Send E-mail</comments>
    			<sources>
    			</sources>
    			<events>
    				<event id="100032">
    					<name>Network_Device_not_OK</name>
    				</event>
    			</events>
    			<actions>
    				<action id="16">
    					<guid>9b8807fa-f8d4-4ad7-ac5d-61f85cd27795</guid>
    					<timerDelay>
    0</timerDelay>
    					<timerKey>
    </timerKey>
    				</action>
    			</actions>
    			<timerCancellations>
    			</timerCancellations>
    			<pStorageActions>
    			</pStorageActions>
    		</rule>
    	<event id="100032">
    			<name>Network_Device_not_OK</name>
    			<guid>06cdfff3-bce6-4bbd-8c02-0a444a29e90f</guid>
    			<code>100032</code>
    			<severity>4</severity>
    			<flags>1</flags>
    			<message>NetXMS - Cisco Router/Switch/ASA IS OFFLINE!</message>
    			<description></description>
    		</event>
    

  • Sending mail from Event Processing Policy not working
    M Mystery
    Support

    I exported all EPPs from old verions of NetXMS and imported to new NetXMS instance. 
    Somehow, the imported ones are not working (sending emails).
    I created new EPP with same definitions and email is sent.

    See rule 60 is not working while rule 79 is working. Strange.
    I also see a new row in the notification log.
    There is no rule with "stop event processiong" checkbox.


  • Sending mail from Event Processing Policy not working
    M Mystery
    Support

    In the notification log, there are only rows from testing events.
    In the event log, there is correct event, which should send these emails as event processing policy define that.

    {
      "id": 11134,
      "rootId": 0,
      "code": 100074,
      "name": "Network_Device_not_OK",
      "timestamp": 1747638739,
      "originTimestamp": 1747638739,
      "origin": 0,
      "source": 356,
      "zone": 0,
      "dci": 1137,
      "severity": 4,
      "message": "NetXMS - OFFLINE :-( ",
      "lastAlarmKey": "",
      "lastAlarmMessage": "",
      "tags": null,
      "parameters": [
        {
          "name": "dciName",
          "value": "ICMP.PacketLoss"
        },
        {
          "name": "dciDescription",
          "value": "ICMP ping: packet loss"
        },
        {
          "name": "thresholdValue",
          "value": "99"
        },
        {
          "name": "currentValue",
          "value": "100"
        },
        {
          "name": "dciId",
          "value": "0x00000471"
        },
        {
          "name": "instance",
          "value": ""
        },
        {
          "name": "isRepeatedEvent",
          "value": "1"
        },
        {
          "name": "dciValue",
          "value": "100"
        },
        {
          "name": "operation",
          "value": "4"
        },
        {
          "name": "function",
          "value": "0"
        },
        {
          "name": "pollCount",
          "value": "5"
        },
        {
          "name": "thresholdDefinition",
          "value": "last(5) \u003e 99"
        }
      ]
    }
    

  • Sending mail from Event Processing Policy not working
    M Mystery
    Support

    Hello, I just migrated our NetXMS instance from 2.2 to the latest version of NetXMS (5.2.1).
    Somehow the Event Processing Policy do not send emails. 
    First, I had to configure new row in Notification Channels - done.
    In the Tools - Send notification - I tried to send me test email - done, email recieved.
    In the Event Processing Policy - I have custom event code and server action - send email (called "Network_Device_not_OK").
    In the Actions Configuration - I have row "Network Device not OK" with Send notification and correct Channel name (which I tested and recieved email before) with my Recipient's address, subject and mesage text.

    I have mailing template which polls ICPM ping packet loss (origin: internal) - last(5) polled values > 99 triggers Event "Network_Device_not_OK "

    I can see that in Event Log - correct Event, message, ... But my email is nowhere.
    Can you help me to fix that? It was working in previous version.

    One more question, do you know how to send emails from template and polled values better than ICMP ping - packet loss? Some devices do not have agents or SNMP configured, so I want to get notified when they go offline (but not all - thats why I use template and apply only to specifiec ones) and also not instantly? Thats why I wait for like 5 polls to notify me.

    Thank you in advance.


  • NetXMS update 2.2.10 to newest
    M Mystery
    Support

    Hello,

    I have very old version of NetXMS and I would like to update it to the newest version. Is it possible to install fresh server with latest version and migrate DB from 2.2.10 to 4.X?

    If not, does anybody know how to fix this error when I try to update it via apt-get update on old version of debian?

    /var/lib/dpkg/info/netxms-server:amd64.postinst: 89: /var/lib/dpkg/info/netxms-server:amd64.postinst: /usr/bin/nxdbmgr: Permission denied
    

    Or when I try to compile it manually via

     sh ./configure --with-server --with-mysql --with-agent --enable-unicode --with-pcre=/opt/pcre/lib64
    

     
    configure: error: libpcre32 is requred which I have installed before

    Thank you very much 🙂


  • Upgrade 2.2.10 to 3.3.315 Your database has format version X, but server is Y
    M Mystery
    Support

    Somehow service is trying to start older version of server.
    Anyway if I run manually netxmsd from console, it load right version NetXMS Server V3.3.315 Build 3.3-315-g5360e23aa3 (UNICODE) Ready
    But after a while, there is a SIGSEGV error and it stops.

    2020.05.18 10:43:25.592 *I* [db.drv            ] Database driver "sqlite.ddr" loaded and initialized successfully
    2020.05.18 10:43:26.392 *I* [                  ] NetXMS Server started

    NetXMS Server V3.3.315 Build 3.3-315-g5360e23aa3 (UNICODE) Ready
    Enter "help" for command list or "down" for server shutdown
    System Console

    netxmsd: 2020.05.18 10:43:26.645 *I* [                  ] Listening for syslog messages on UDP socket 0.0.0.0:514
    2020.05.18 10:43:26.645 *I* [                  ] Listening for syslog messages on UDP socket :::514
    2020.05.18 10:43:26.645 *I* [                  ] SocketListener/MobileDevices: listening on 0.0.0.0:4747
    2020.05.18 10:43:26.645 *I* [                  ] SocketListener/MobileDevices: listening on [0.0.0.0]:4747
    2020.05.18 10:43:26.646 *I* [                  ] SocketListener/Clients: listening on 0.0.0.0:4701
    2020.05.18 10:43:26.646 *I* [                  ] SocketListener/Clients: listening on [0.0.0.0]:4701
    2020.05.18 10:43:26.646 *I* [                  ] Listening for SNMP traps on UDP socket 0.0.0.0:162
    2020.05.18 10:43:26.646 *I* [                  ] Listening for SNMP traps on UDP socket :::162
    2020.05.18 10:43:26.646 *I* [                  ] SocketListener/AgentTunnels: listening on 0.0.0.0:4703
    2020.05.18 10:43:26.646 *I* [                  ] SocketListener/AgentTunnels: listening on [0.0.0.0]:4703
    Unauthorized access to memory (SIGSEGV)


  • Upgrade 2.2.10 to 3.3.315 Your database has format version X, but server is Y
    M Mystery
    Support

    Hello, I upgraded from scratch our NetXMS instance from 2.2.10 to 3.3.315 on Linux debian
    nxdbmgr check OK
    nxdbmgr upgrade after 10 days OK
    nxagentd run ok

    When i run service netxmsd start
    it says running but in /var/log/netxms.log I can see Errors:

    2020.05.18 08:08:03.608 Log file opened (rotation policy 2, max size 16777216)
    2020.05.18 08:08:04.058 *I* Platform subagent "/usr/local/lib/netxms/linux.nsm" successfully loaded
    2020.05.18 08:08:04.203 *I* Database driver "mysql.ddr" loaded and initialized successfully
    2020.05.18 08:08:04.694 *E* Your database has format version 32.12, but server is compiled for version 22.40

    When I restarted server and these services are autostart, it started server somehow with same error:

    2020.05.18 08:25:28.024 *I* [logger            ] Log file opened (rotation policy 2, max size 16777216)
    2020.05.18 08:25:28.028 *I* [                  ] Code page set to ISO8859-1
    2020.05.18 08:25:28.029 *I* [                  ] Platform subagent "/usr/local/lib/netxms/linux.nsm" successfully loaded
    2020.05.18 08:25:28.031 *I* [db.drv            ] Database driver "mysql.ddr" loaded and initialized successfully
    2020.05.18 08:25:28.031 *E* [                  ] Unable to bind socket for local admin interface (98 Address already in use)
    2020.05.18 08:25:33.329 *I* [                  ] Server ID 2BE33A49B3270BF8
    2020.05.18 08:25:33.668 *I* [                  ] Server certificate not set
    2020.05.18 08:25:35.592 *E* Your database has format version 32.12, but server is compiled for version 22.40
    2020.05.18 08:25:44.241 *I* [db.drv            ] Database driver "sqlite.ddr" loaded and initialized successfully
    2020.05.18 08:25:51.643 *I* [db.drv            ] Database driver "sqlite.ddr" loaded and initialized successfully

    But all values and history on nodes are empty, even netxms server node is saying there is running agent 2.2.10.
    Somehow DB is for 3.3.X and server instalation is older.

    Any tips how to fix this?
    Thank you.


  • Duplicate emails after update to 2.2.10
    M Mystery
    Support

    Hello, after update to version 2.2.10 I am experiencing problem with sending duplicate emails.
    I checked configuration and it seems there should be only one email when node goes down or up.

    The time difference between both e-mail is from 1 sec to 1 minute and the interesting point is that I have been playing with some UTF8 changes in emails body and one email is without UTF8 characters and second one is with UTF8 char. When I check Actions Configuration, I can only see that email skeletons with UTF8. There is also only one Action in DB, so there must be somewhere problem but I don't know how to debug that. Any idea? Will Syslog Monitor help or where can I see processed e-mails?

    Thank you in advance.

  • 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