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. Agent wouldn't return values

Agent wouldn't return values

Scheduled Pinned Locked Moved Support
3 Posts 2 Posters 32.7k 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.
  • T
    T
    troffasky
    wrote on last edited by
    #1

    Server: 192.168.160.1
    Agent: 192.168.160.3
    Version: 2.0-RC2

    Agent config file:


    # Log File
    LogFile=/var/log/nxagentd
    DebugLevel = 3
    # IP white list, can contain multiple records separated by comma.
    # CIDR notation supported for subnets.
    MasterServers=127.0.0.0/8,192.168.160.1/32

    RequireAuthentication = no
    EnableProxy = yes
    EnableSNMPProxy = yes


    Added agent to server as a new node. Can see details in Overview. Can't poll anything from node though:


    [2015.11.19 13:43:33] **** Poll request sent to server ****
    [2015.11.19 13:43:33] Poll request accepted
    [2015.11.19 13:43:33] Starting configuration poll for node monitoring.xxx.local
    [2015.11.19 13:43:33] Checking node's capabilities...
    [2015.11.19 13:43:33] Capability check finished
    [2015.11.19 13:43:33] Checking interface configuration...
    [2015.11.19 13:43:39] Unable to get interface list from node
    [2015.11.19 13:43:43] Interface configuration check finished
    [2015.11.19 13:43:43] Checking node name
    [2015.11.19 13:43:43] Node name is OK
    [2015.11.19 13:43:43] Reading list of installed software packages
    [2015.11.19 13:43:43] Unable to get information about installed software packages
    [2015.11.19 13:43:54] Finished configuration poll for node monitoring.xxx.local
    [2015.11.19 13:43:54] Node configuration was not changed after poll
    [2015.11.19 13:43:54] **** Poll completed successfully ****


    I can use nxget to fetch info:


    # nxget 192.168.160.3 'Net.Interface.Description(eth0)'
    eth0


    Turn up debugging on agent to 5, restart agent, try again:


    [19-Nov-2015 13:42:59.183] [INFO ] NetXMS Agent started
    [19-Nov-2015 13:43:02.576] [DEBUG] Incoming connection from 192.168.160.1
    [19-Nov-2015 13:43:02.576] [DEBUG] Connection from 192.168.160.1 accepted
    [19-Nov-2015 13:43:02.659] [DEBUG] Incoming connection from 192.168.160.3
    [19-Nov-2015 13:43:03.091] [DEBUG] Connection from 192.168.160.3 rejected
    [19-Nov-2015 13:43:03.091] [DEBUG] [session:0] Established proxy connection to 192.168.160.3:4700
    [19-Nov-2015 13:43:03.091] [DEBUG] [session:0] CommSession::disconnect()
    ...repeats...
    [19-Nov-2015 13:43:58.190] [DEBUG] [session:0] Session with 192.168.160.1 closed


    ...so it's using itself as a proxy to talk to itself, but not from 127.0.0.1, from its interface that faces the server.

    Is this the expected behaviour? The zone that it's in *did* have this server set up as the default proxy for the zone, but I put it back after it stopped working [I guess I know why now]. Checked the node's properties, it is not configured to use itself to poll itself.

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

      Hi,

      from log file it seems agent tries to use itself as proxy. What is currently set as proxy for this node's zone? Can you share screenshots of zone configuration and node's "communication" property page?

      Best regards,
      Victor

      1 Reply Last reply
      0
      • T
        T
        troffasky
        wrote on last edited by
        #3

        At the time this was logged, neither the node nor the zone had a proxy configured, but the zone does now have this particular agent as its proxy [as that was my original intention] and it's working fine now.

        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