Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Kiwi Syslog Server > Kiwi Sys - Knowledgebase Articles > Kiwi Syslog Daemon Quick Start Guide

Kiwi Syslog Daemon Quick Start Guide

Updated March 11th, 2016


This article provides steps to help you troubleshoot and get started with Kiwi Syslog Daemon.


All Kiwi Syslog Daemon versions


If you have installed Kiwi Syslog Daemon but are not receiving syslog messages from your devices, the first troubleshooting step is confirm that they are actually being sent.


SolarWinds recommends using an application called Ethereal, (© 2017 Alexander Open Systems, available at, obtained on June 28, 2017.). This application provides the ability to capture traffic that is sent to your systems Network Interface Card. By capturing this traffic you will be able to determine whether or not the syslog messages are actually arriving at your system.

Syslog Messages Are Not Being Sent

If they are not being sent, then you will need to check the settings on the network device itself. We find that often the device requires a reboot for the settings to take effect.

Information and links for most devices, can be found in the Kiwi Syslog Daemon Help file under the heading "Configure devices to send syslog messages"

  1. You may have a firewall installed such as ZoneAlarm which blocks access to this port. If you are running a Windows 2003 server, the Windows firewall is turned on by default.
  2. You may have another application running that uses UDP port 514 to listen on. You will need to identify what that process is.

Syslog Messages Are Being Sent

If your devices are sending syslog messages, but Kiwi Syslog Daemon doesn't show any logging on display or in a file, SolarWinds recommends the following steps:

  1. From File > Setup > Defaults/Import/Export > select "Load the default rules and settings".
  2. Click OK.
  3. Stop and restart the application. You should start seeing the messages on the display.
  4. Download a copy of Kiwi SyslogGen from the Download Kiwi Products page and use it to send test messages from your remote servers, and/or other machines. This will establish if the syslog messages can be received, and that Kiwi Syslog Daemon is working correctly.
  5. Ensure that you do not have the "lock" icon enabled in the Kiwi Syslog Daemon Main window. If the lock icon is enabled, you will not be able to view messages in the display windows.
  6. Reboot the system Kiwi Syslog Daemon is installed on.
  7. Open the errorlog.txt file in the C:\Program Files\Syslogd folder for some indication as to what is wrong.
  8. Go to Manage > Debug options > Get diagnostic information. Send SolarWinds support the generated diagnostic information as a .zip file.
  9. Export your settings by going to File > Export Settings to INI File. Send SolarWinds Support this saved file as an attachment.

Determine the Process Identifier Number

To determine the process identifier number, which is bound to 514:

  1. Navigate to Windows > Start > Run > enter command: netstat
  2. In Task Manager, ensure you have set your Options > Select Columns to include PID. This will allow you to see which process the number relates to. End the identified process/s and restart Kiwi Syslog Daemon.


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.




Last modified