Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Kiwi Syslog Server > Unable to Bind to UDP Port 514

Unable to Bind to UDP Port 514

Table of contents
No headers

Updated May 5th, 2016

 

Issue: Unable to bind to port 514 (or similar).

 

Cause: Kiwi Syslog Daemon error log shows a message like this or similar to this due to a single process bound to a port at any one time. User needs to locate the offending process and shut it down before restarting Kiwi Syslog Daemon again. 

 

Resolution: In order to bind to the correct port to receive syslog messages, you need to perform the following steps:

  1. Determine which process is using the required port by opening a Windows command prompt and type in the following:  
    • netstat -ano.
    • Upon typing the command, it displays a list of proccesses and ports they are bound to. 
  2. Locate the process identifier (PID) of the offeding process then open the Windows Task Manager and use this to determine the proccess with the matching PID and then shut it down.
    • Note:If your Windows Task Manager does not display the PID then this option can be enabled by clicking View, and then Select Columns
  3. Once you have shutdown the offending process, you should be able to restart Kiwi Syslog Daemon and have it successfully bind to the correct port and start receiving syslog messages.
Last modified

Tags

Classifications

Public