Submit a ticketCall us

Putting Your Logs Where They Belong with the New SolarWinds Log Manager for Orion

The new SolarWinds® Log Manager for Orion® finally puts your log data right where it belongs, in the heart of your Orion console. Gain insight into the performance of your infrastructure by monitoring your logs in a unified console allowing you to see a wealth of information about the health and performance of your network and servers.

Reserve a Seat for Wednesday May 23rd 11am CDT | Reserve a Seat for Tuesday May 22nd 10:30am GMT | Reserve a Seat for Tuesday May 22nd 1pm SGT / 3pm AEST

Home > Success Center > Kiwi Syslog Server > Kiwi Syslog setting up Unix machine

Kiwi Syslog setting up Unix machine

Table of contents

Updated: August 24, 2016

Overview

This is how you set up a Unix machine to send syslog messages on Kiwi Syslog Server.

Environment

  • All versions of Kiwi Syslog

Steps

Note: With a Unix host, you need super user privileges to modify the files following files:
/etc/syslog.conf
/etc/hosts

  1. Restart (HUP) the Syslog Server on the Unix box.
  2. Use vi or any text file editor of your choice to modify the /etc/hosts file. Sample hosts file:

    #
    # Internet host table
    #

    127.0.0.1                localhost
    192.168.230.23        loghost


    This allows you to use the hostname loghost to direct your messages to. 
    The IP address used for loghost should be the IP address of the Windows or NT box you are running Kiwi Syslog Server on.
  3. Use vi or any text file editor of your choice to modify the /etc/syslog.conf file. Sample syslog.conf file:

    # Syslog configuration file.

    #

    *.err;kern.notice;auth.notice                        /dev/console

    *.err;kern.debug;daemon.notice;mail.crit        /var/adm/messages

     

    *.alert;kern.err;daemon.err                        operator

    *.alert                                                root

     

    *.emerg                                                @loghost

    mail.debug                                                @loghost

    You will notice that all facilities with a level of emerg will be forwarded to the loghost (defined in the hosts file) and any mail alerts with a level of debug will also be forwarded.

  4. The general idea is Facility.Level <TAB> @loghost

  5. Save this file after editing and restart the Syslog Server on the Unix box for it to take effect.
  6. Find the syslog Server process ID, and send it a SIGHUP signal.
  7. Test if the syslog server is writing messages using the logger command, such as logger –p user.emerg Unix test message.
  8. If in doubt resort to man syslogd.

 

 

Last modified

Tags

Classifications

Public