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. Problems with PING subagent after update to V2.2.1

Problems with PING subagent after update to V2.2.1

Scheduled Pinned Locked Moved Support
22 Posts 4 Posters 59.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.
  • S
    S
    Ēriks Jenkēvics
    wrote on last edited by
    #8

    Could you please verify that the PING subagent is in the list opened by Right click on pinging node -> Tools -> Info -> Agent -> Subagent list. And that you get this entry in your agent log once it is started:

    *I* Subagent "PING" (ping.nsm) loaded successfully (version 2.2.1-14-g375721606)
    
    1 Reply Last reply
    0
    • Dani@M3TU
      Dani@M3TU
      Dani@M3T
      wrote on last edited by
      #9

      I checked that before. Yes subagent is in subagent list (Version 2.2.1 and the value '0x0000000002320A90' in the 4. column).
      In agent log file the line:

      2017.12.08 17:02:18.457 *I* Subagent "PING" (ping.nsm) loaded successfully (version 2.2.1)
      

      So the subagent is loaded.

      1 Reply Last reply
      0
      • S
        S
        Ēriks Jenkēvics
        wrote on last edited by
        #10

        Ok and is there anything in the log similar to this line: "Unable to add ICMP ping target from configuration file."?

        1 Reply Last reply
        0
        • Dani@M3TU
          Dani@M3TU
          Dani@M3T
          wrote on last edited by
          #11

          no, nothing like this in the agent log. Not in normal log and not in debuglog.
          In debuglog I see lines like this:

          2017.12.08 16:09:47.364 *D* [VCS-1915] Requesting parameter "Icmp.PacketLoss(gw1.domain1.intern)"
          2017.12.08 16:09:47.364 *D* [VCS-1916] Requesting parameter "Icmp.AvgPingTime(gw1.domain1.intern)"
          2017.12.08 16:09:47.364 *D* [VCS-1906] Requesting parameter "Icmp.AvgPingTime(gw1.domain2.intern)"
          2017.12.08 16:09:47.364 *D* [VCS-1901] GetParameterValue(): result is 0 (SUCCESS)
          2017.12.08 16:09:47.364 *D* [VCS-1915] GetParameterValue(): result is 404 (UNKNOWN_PARAMETER)
          2017.12.08 16:09:47.365 *D* DataCollector: polling DCI 1779 "Icmp.PacketLoss(gw1.domain3.intern)"
          2017.12.08 16:09:47.365 *D* DataCollector: polling DCI 1778 "Icmp.AvgPingTime(gw1.domain3.intern)"
          2017.12.08 16:09:47.365 *D* [VCS-1913] GetParameterValue(): result is 0 (SUCCESS)
          2017.12.08 16:09:47.365 *D* DataCollector: polling DCI 6386 "Icmp.AvgPingTime(gw1.domain4.intern)"
          2017.12.08 16:09:47.365 *D* [VCS-1918] Requesting parameter "Icmp.PacketLoss(gw1.domain3.intern)"
          2017.12.08 16:09:47.365 *D* DataCollector: polling DCI 6385 "Icmp.PacketLoss(gw1.domain4.intern)"
          2017.12.08 16:09:47.365 *D* [VCS-1906] GetParameterValue(): result is 404 (UNKNOWN_PARAMETER)
          2017.12.08 16:09:47.365 *D* [VCS-1919] Requesting parameter "Icmp.AvgPingTime(gw1.domain3.intern)"
          2017.12.08 16:09:47.365 *D* [VCS-1921] Requesting parameter "Icmp.PacketLoss(gw1.domain4.intern)"
          2017.12.08 16:09:47.365 *D* [VCS-1918] GetParameterValue(): result is 404 (UNKNOWN_PARAMETER)
          2017.12.08 16:09:47.365 *D* [VCS-1919] GetParameterValue(): result is 404 (UNKNOWN_PARAMETER)
          

          I can send you a debuglog of the pinging agent if that helps. But I can't share it in the forum

          1 Reply Last reply
          0
          • S
            S
            Ēriks Jenkēvics
            wrote on last edited by
            #12

            Could you, please, provide the output of "nxagentd -C"? Don`t forget to edit out any sensitive data, I am interested specifically in the PING subtree.

            1 Reply Last reply
            0
            • Dani@M3TU
              Dani@M3TU
              Dani@M3T
              wrote on last edited by
              #13

              here the output of the agent on the NetXMS server itself (linux). I had to change a few sensitive data and removed some of the ping targets...
              If you need the unchanged output, you can give me another communication channel.

              config
               +- CORE
               |   +- DebugLevel
               |   |    value: 0
               |   +- MasterServers
               |   |    value: 127.0.0.1
               |   |    value: 172.16.10.45
               |   |    value: nms.domain.intern
               |   +- ListenPort
               |   |    value: 4700
               |   +- LogFile
               |   |    value: /var/log/nxagentd.log
               |   +- RequireAuthentication
               |   |    value: yes
               |   +- RequireEncryption
               |   |    value: yes
               |   +- EnabledCiphers
               |   |    value: 1
               |   +- SharedSecret
               |   |    value: replaced
               |   +- MaxSessions
               |   |    value: 64
               |   +- SessionIdleTimeout
               |   |    value: 60
               |   +- FileStore
               |   |    value: /opt/netxms/var/nxagentd
               |   +- StartupDelay
               |   |    value: 5
               |   +- EnableSubagentAutoload
               |   |    value: yes
               |   +- SubAgent
               |   |    value: portcheck.nsm
               |   |    value: ping.nsm
               |   |    value: logwatch.nsm
               |   |    value: ecs.nsm
               |   |    value: netsvc.nsm
               |   |    value: filemgr.nsm
               |   |    value: ssh.nsm
               |   |    value: pgsql.nsm
               |   +- ExternalParameter
               |   |    value: ServiceCheck.DNS(*):/usr/bin/dig +noall +short @$1 $2 A | grep -c $3 | sed  's/0/x/g;s/[^x]/0/g;s/x/1/g'
               |   +- ExecTimeout
               |   |    value: 10000
               |   +- Action
               |        value: top: /usr/bin/top -s -b -n 1
               |        value: netstat: /bin/netstat -p --inet
               |        value: IPconfig: /sbin/ifconfig
               |        value: ListUpdates: /usr/bin/zypper list-updates
               +- filemgr
               |   +- RootFolder
               |        value: /root
               |        value: /opt
               |        value: /etc
               |        value: /usr/src
               |        value: /var/log
               +- ping
                   +- DefaultPacketSize
                   |    value: 46
                   +- Timeout
                   |    value: 2000
                   +- PacketRate
                   |    value: 24
                   +- Target
                        value: 172.16.10.1:gw1.domain1.intern
                        value: 172.16.50.1:gw2.domain1.intern
                        value: 172.16.41.1:gw4.domain1.intern
                        value: 172.16.101.10:gw10.domain1.intern
                        value: 172.16.90.1:router1.domain1.intern
                        value: 172.16.20.1:gw1.domain5.intern
                        value: 172.16.70.1:gw1.domain4.intern
                        value: 192.168.30.1:gw1.domain3.intern
                        value: 8.8.4.4:dns2.google.com
              
              1 Reply Last reply
              0
              • S
                S
                Ēriks Jenkēvics
                wrote on last edited by
                #14

                Could you try changing the PING subagent section in config to uppercase? As in:

                *PING
                DefaultPacketSize = 46
                ...
                
                1 Reply Last reply
                0
                • Dani@M3TU
                  Dani@M3TU
                  Dani@M3T
                  wrote on last edited by
                  #15

                  I changed "[ping]" to "[PING]", but no change in problem.

                  I have all agent config files and policies in INI-style, the sections like this:

                  [ping]
                  ...
                  

                  is it necessairy to change to "*PING"-style? I couldn't see anything about that in changelog.

                  1 Reply Last reply
                  0
                  • S
                    S
                    Ēriks Jenkēvics
                    wrote on last edited by
                    #16

                    It shouldn`t change anything, it was just a guess :).
                    Could you let me know which Linux distribution you are using, what kernel etc... Also, which version of Windows?

                    1 Reply Last reply
                    0
                    • Dani@M3TU
                      Dani@M3TU
                      Dani@M3T
                      wrote on last edited by
                      #17

                      There are a few different systems and OS. All tests for this troubleshooting here I made on 2systems:

                      1. Windows 2012 R2 english with all current patches
                      2. SuSE Linux, kernel 3.12.67

                      Same problems on both of them

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

                        Hi,

                        we just fixed this bug. If you are building from sources, you can just re-build agent from current "stable-2.2" branch in our repository or replace file src/agent/subagents/ping/ping.cpp with attached one in your current source tree and rebuild. I'll also repack Windows installers.

                        Best regards,
                        Victor


                        ping.cpp

                        1 Reply Last reply
                        0
                        • Dani@M3TU
                          Dani@M3TU
                          Dani@M3T
                          wrote on last edited by
                          #19

                          Hi Victor

                          I just replaced the ping.cpp in the src and recompiled the agent on linux. That fixed the problem! Thank you Victor!

                          Can you please inform, when you have rebuilt the windows agent packages. Then I can replace the other agents with PING subagent in use.

                          thanks
                          Dani

                          1 Reply Last reply
                          0
                          • Dani@M3TU
                            Dani@M3TU
                            Dani@M3T
                            wrote on last edited by
                            #20

                            Hi Victor

                            Do you have an ETA for the patched Windows agent binary?

                            thanks
                            Dani

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

                              Hi,

                              here you can download patched Windows agents: https://netxms.org/download/patches/019/

                              Best regards,
                              Victor

                              1 Reply Last reply
                              0
                              • Dani@M3TU
                                Dani@M3TU
                                Dani@M3T
                                wrote on last edited by
                                #22

                                Hi Victor

                                Thank you for the patched versions. I already tested on Win2012R2 and Win10. Success!
                                I will deploy it now to the other devices where PING subagent is used.

                                best reagrds
                                Dani

                                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