Technote (troubleshooting)
Problem(Abstract)
The information on this document describes how to configure a basic Syslogd Server and a Client.
Resolving the problem
Configuring a Basic Syslog Server and Client on AIX.
Special Notices:Please use this information with care. IBM will not be responsible for damages of any kind resulting from its use. The use of this information is the sole responsibility of the customer and depends on the customer's ability to evaluate and integrate this information into the customer's operational environment.
ContentsConfiguring the Syslog Server.
Configuring the Syslog Client.
About this documentThe information on this document describes how to configure a basic Syslogd Server and a Client.
In the Example System bones (9.3.84.250) will be the Syslog Server and System bestbso (9.3.84.66)
will be the Syslog Client.
Configuring the Syslog Server.This configuration example will be using " *.debug " which will log everything on the system. # vi /etc/syslog.conf
*.debug /tmp/syslog.out rotate size 100k files 4
This entry will rotate the syslog.out file when it reaches 100k and will keep 4 files in the rotation.
Save the /etc/syslog.conf file and touch /tmp/syslog.out
# touch /tmp/syslog.out
# refresh -s syslogd0513-095 The request for subsystem refresh was completed successfully.
NOTE: The syslogd daemon has configuration flags -r and -R that when used will not allow the syslogd daemon to accept remote logging from clients.
-r Suppresses logging of messages received from remote hosts.
-R When specified, disables the facility to receive messages from the network using the internet domain socket.
Make sure these flags are not set when starting the daemon. It can be checked with:
# ps -ef |grep syslogd
root 569406 200806 0 Dec 22 - 0:01 /usr/sbin/syslogd -r
If any of these flags are running, then you must stop syslogd, clear out the entries from ODM and restart the daemon.
# stopsrc -s syslogd
# chssys -s syslogd -a ""
# startsrc -s syslogd
The -r flag should not show up.# ps -ef |grep syslogd
root 569406 200806 0 Dec 22 - 0:01 /usr/sbin/syslogd
NOTE: The syslogd daemon listens on port 514, if there is a firewall in between, make sure this port is opened.
Configuring the Syslog Client.This configuration example will be using " *.debug " which will log everything on the system.
ContentsConfiguring the Syslog Server.
Configuring the Syslog Client.
About this documentThe information on this document describes how to configure a basic Syslogd Server and a Client.
In the Example System bones (9.3.84.250) will be the Syslog Server and System bestbso (9.3.84.66)
will be the Syslog Client.
Configuring the Syslog Server.This configuration example will be using " *.debug " which will log everything on the system. # vi /etc/syslog.conf
*.debug /tmp/syslog.out rotate size 100k files 4
This entry will rotate the syslog.out file when it reaches 100k and will keep 4 files in the rotation.
Save the /etc/syslog.conf file and touch /tmp/syslog.out
# touch /tmp/syslog.out
# refresh -s syslogd0513-095 The request for subsystem refresh was completed successfully.
NOTE: The syslogd daemon has configuration flags -r and -R that when used will not allow the syslogd daemon to accept remote logging from clients.
-r Suppresses logging of messages received from remote hosts.
-R When specified, disables the facility to receive messages from the network using the internet domain socket.
Make sure these flags are not set when starting the daemon. It can be checked with:
# ps -ef |grep syslogd
root 569406 200806 0 Dec 22 - 0:01 /usr/sbin/syslogd -r
If any of these flags are running, then you must stop syslogd, clear out the entries from ODM and restart the daemon.
# stopsrc -s syslogd
# chssys -s syslogd -a ""
# startsrc -s syslogd
The -r flag should not show up.# ps -ef |grep syslogd
root 569406 200806 0 Dec 22 - 0:01 /usr/sbin/syslogd
NOTE: The syslogd daemon listens on port 514, if there is a firewall in between, make sure this port is opened.
Configuring the Syslog Client.This configuration example will be using " *.debug " which will log everything on the system.
#vi /etc/syslog.conf
*.debug @bones.austin.ibm.com
This entry will forward any information logged by " *.debug " to the Syslog Server bones.austin.ibm.com.
Save the /tmp/syslog.conf file and refresh the syslogd daemon.
# refresh -s syslogd
0513-095 The request for subsystem refresh was completed successfully.
To test the setup we can use the logger command.
# logger "This is a test"
You should see logged message in /tmp/syslog.out file on the Syslog Server bones.
To have better control over syslogd and its' logs, please refer to the man pages for further information.
*.debug @bones.austin.ibm.com
This entry will forward any information logged by " *.debug " to the Syslog Server bones.austin.ibm.com.
Save the /tmp/syslog.conf file and refresh the syslogd daemon.
# refresh -s syslogd
0513-095 The request for subsystem refresh was completed successfully.
To test the setup we can use the logger command.
# logger "This is a test"
You should see logged message in /tmp/syslog.out file on the Syslog Server bones.
To have better control over syslogd and its' logs, please refer to the man pages for further information.
No comments:
Post a Comment