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. Syslog source became <unknown>

Syslog source became <unknown>

Scheduled Pinned Locked Moved Support
9 Posts 3 Posters 16.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.
  • K
    K
    w00t
    wrote on last edited by
    #1

    We recently upgraded NetXMS 1.2.17 to 2.0.3 (1.2.17 > 2.0.2 > 2.0.3) but the syslog data from existing nodes are being displayed as <unknown>. However nodes (Same model and firmware from <unknown> syslog data) added after upgrade to 2.0.3 are being identified correctly. Any ideas?

    1 Reply Last reply
    0
    • K
      K
      w00t
      wrote on last edited by
      #2

      After upgrading to 2.0.4 and performed nxdbmgr upgrade, previously known source in syslog became <unknown>. What's the debug level for Syslog logging?

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

        What are your "SyslogIgnoreMessageTimestamp" and "SyslogNodeMatchingPolicy" server configuration variables configured to?

        Also, did you get it working before 2.0.4, or is this the same issue persisting from 2.0.2/2.0.3?

        1 Reply Last reply
        0
        • K
          K
          w00t
          wrote on last edited by
          #4

          SyslogIgnoreMessageTimestamp and SyslogNodeMatchingPolicy are 0. It's working properly in 1.2.x branch but not after upgrade to 2.0.x branch.

          1 Reply Last reply
          0
          • T
            T
            tomaskir
            wrote on last edited by
            #5

            Please run tcpdump (or wireshark or similiar) and look at the actual packets of the incoming syslog messages.

            What IP address do they come from?
            If you put ">that_ip_address" into the object tree filter, does it find anything (make sure to prefix the IP with ">")?

            The source IP address of the syslog message packet gets looked up across all your nodes present in NetXMS.
            Are you sure you have a node with the address of the syslog messages present in NetXMS?

            Bonus info: are syslogs coming over IPv4 or IPv6?

            1 Reply Last reply
            0
            • K
              K
              w00t
              wrote on last edited by
              #6

              The IPv4 address of Syslog source does have a node found by using filter ">ip_address" and match its "primary host name" field.

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

                Hi,

                it shows <unknown> in "Source" column of syslog monitor? That means that server was unable to find node object by source IP address or host name. Are you using zones? If not, could you please run command (on NetXMS server console):

                nxadm -c "show index nodeaddr"

                and check that problematic node's source address is there?

                Best regards,
                Victor

                1 Reply Last reply
                0
                • K
                  K
                  w00t
                  wrote on last edited by
                  #8

                  Hi Victor,

                  I'm using zones and "show index nodeaddr" returns nothing.

                  1 Reply Last reply
                  0
                  • K
                    K
                    w00t
                    wrote on last edited by
                    #9

                    Hi Victor,

                    I deleted then re-added a node and the source can display properly but the "show index nodeaddr" still return nothing.

                    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