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