Follow

Troubleshooting Message Handler

Scenario

Syslog messages are not appearing in the Event Manager from any servers. How can you test if the Message Handler is working correctly by generating syslog messages locally.

 

Resolution 

 Check if Windows Firewall or any other Firewall/AntiVirus application is blocking the syslog messages from reaching Traverse and allow incomng traffic on port 514.

 

Troubleshooting Steps

Syslog uses port number 514

Run a netstat command to determine which process ID’s (PID) are listening on port 514

 

2014-10-22_1026.png

 

Open Task manager to determine the process name which corresponds with the PID

 

2014-10-22_1029.png

 

The message handler process listens on port 7693.

Run netstat command again to determine if the PID corresponds to the message handler process.

 

2014-10-22_1036.png

Use a syslog message generator tool to confirm that the messages are being received.

e.g http://www.snmpsoft.com/freetools/sysloggen.html



2014-10-22_1125_001.png

 

Tail the the <Traverse Home>\logs\messages.log to see the generated syslog message

 

2014-10-22_1125.png



Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.