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. Cannot connect agent

Cannot connect agent

Scheduled Pinned Locked Moved Support
5 Posts 2 Posters 39.3k 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.
  • N
    N
    Nikk
    wrote on last edited by
    #1

    Hi,

    I have the following situation - I installed NetXMS agent on server which is located in remote site without proxy enabled. There is another NetXMS agent who is working like a proxy. So, from console I when i poll proxy everything is like it should be (agent found), but when i poll the new agent I get:

    [04.11.2013 14:05:45] **** Poll request sent to server ****
    [04.11.2013 14:05:45] Poll request accepted
    [04.11.2013 14:05:45] Starting configuration poll for node 192.168.0.5
    [04.11.2013 14:05:45] Checking node's capabilities...
    [04.11.2013 14:05:45]    Checking NetXMS agent...
    [04.11.2013 14:05:46]    Checking SNMP...
    [04.11.2013 14:07:46] POLL ERROR: Request timed out[04.11.2013 14:07:46] **** Poll failed ****

    [04.11.2013 14:24:41] **** Poll request sent to server ****
    [04.11.2013 14:24:41] Poll request accepted
    [04.11.2013 14:24:41] Starting configuration poll for node 192.168.0.5
    [04.11.2013 14:24:41] Checking node's capabilities...
    [04.11.2013 14:24:41]    Checking NetXMS agent...
    [04.11.2013 14:24:50] Capability check finished
    [04.11.2013 14:24:50] Checking interface configuration...
    [04.11.2013 14:24:50] Unable to get interface list from node
    [04.11.2013 14:24:50]    Interface "unknown" is no longer exist
    [04.11.2013 14:24:50] Interface configuration check finished
    [04.11.2013 14:24:50] Checking node name
    [04.11.2013 14:24:50] Syncing node name with DNS
    [04.11.2013 14:24:59] Finished configuration poll for node ServerFTP
    [04.11.2013 14:24:59] Node configuration was not changed after poll
    [04.11.2013 14:24:59] **** Poll completed successfully ****

    The device does respond to icmp pings and agent is running.

    There is even some communication between the proxy and the agent:

    root@metrumftp:~# tcpdump -i any port 4700
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on any, link-type LINUX_SLL (Linux cooked), capture size 96 bytes
    14:16:44.697975 IP 192.168.0.5.55781 > 192.168.0.4.4700: S 1847646415:1847646415(0) win 14600 <mss 1460,sackOK,timestamp 369447284 0,nop,wscale 6>
    14:16:44.698003 IP 192.168.0.4.4700 > 192.168.0.5.55781: S 1883842181:1883842181(0) ack 1847646416 win 5792 <mss 1460,sackOK,timestamp 1363491413 369447284,nop,wscale 6>
    14:16:44.698111 IP 192.168.0.5.55781 > 192.168.0.4.4700: . ack 1 win 229 <nop,nop,timestamp 369447284 1363491413>
    14:16:44.698309 IP 192.168.0.4.4700 > 192.168.0.5.55781: F 1:1(0) ack 1 win 91 <nop,nop,timestamp 1363491413 369447284>
    14:16:44.698438 IP 192.168.0.5.55781 > 192.168.0.4.4700: . ack 2 win 229 <nop,nop,timestamp 369447284 1363491413>
    14:16:44.798277 IP 192.168.0.5.55781 > 192.168.0.4.4700: F 1:1(0) ack 2 win 229 <nop,nop,timestamp 369447309 1363491413>
    14:16:44.798289 IP 192.168.0.4.4700 > 192.168.0.5.55781: . ack 2 win 91 <nop,nop,timestamp 1363491423 369447309>
    14:16:58.582404 IP 192.168.0.5.55782 > 192.168.0.4.4700: S 2718119023:2718119023(0) win 14600 <mss 1460,sackOK,timestamp 369450754 0,nop,wscale 6>
    14:16:58.582433 IP 192.168.0.4.4700 > 192.168.0.5.55782: S 2098537924:2098537924(0) ack 2718119024 win 5792 <mss 1460,sackOK,timestamp 1363492802 369450754,nop,wscale 6>
    14:16:58.582544 IP 192.168.0.5.55782 > 192.168.0.4.4700: . ack 1 win 229 <nop,nop,timestamp 369450754 1363492802>
    14:16:58.582698 IP 192.168.0.4.4700 > 192.168.0.5.55782: F 1:1(0) ack 1 win 91 <nop,nop,timestamp 1363492802 369450754>
    14:16:58.582809 IP 192.168.0.5.55782 > 192.168.0.4.4700: . ack 2 win 229 <nop,nop,timestamp 369450754 1363492802>
    14:16:58.682761 IP 192.168.0.5.55782 > 192.168.0.4.4700: F 1:1(0) ack 2 win 229 <nop,nop,timestamp 369450779 1363492802>

    Server debug shows, that Communication with agent 192.168.0.4 failed (Connection broken).

    I'm stuck here and can't find the solution to this. If i need to provide more information, just tell.
    Any help would be appreciated.

    Thanks in advance,
    Nikk

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

      Can you show me configs for both agents?

      Best regards,
      Victor

      1 Reply Last reply
      0
      • N
        N
        Nikk
        wrote on last edited by
        #3

        Here is the proxy config:

        #
        # Sample configuration file for NetXMS agent

        EnableWatchdog = yes

        MasterServers = Our_external_address
        LogFile = {syslog}
        LogFile = /var/log/nxagentd.log
        EnableProxy = yes
        EnableSNMPProxy = yes

        SubAgent = /usr/local/lib/netxms/portcheck.nsm
        SubAgent = /usr/local/lib/netxms/ping.nsm
        SubAgent = /usr/local/lib/netxms/linux.nsm
        SubAgent = /usr/local/lib/netxms/logwatch.nsm

        And the agents config:

        MasterServers = Our_external_address
        LogFile = {syslog}
        LogFile = /var/log/nxagentd.log
        CreateCrashDumps = yes
        DumpDirectory = /var/log/nxagentdump

        SubAgent = /usr/local/lib/netxms/portcheck.nsm
        SubAgent = /usr/local/lib/netxms/ping.nsm
        SubAgent = /usr/local/lib/netxms/linux.nsm
        SubAgent = /usr/local/lib/netxms/ecs.nsm
        SubAgent = /usr/local/lib/netxms/logwatch.nsm
        SubAgent = /usr/local/lib/netxms/sms.nsm

        EnableWatchdog = yes

        Thanks in advance,
        Nikk

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

          You should use IP address of proxy agent in MasterServers parameter on destination agent, because destnation agent will receive connection from proxy agent's IP address.

          Best regards,
          Victor

          1 Reply Last reply
          0
          • N
            N
            Nikk
            wrote on last edited by
            #5

            Such a stupid mistake, thank you for guiding me in right direction 🙂

            Nikk

            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