MQSeries.net :: View topic

emileke · Posted: Fri Aug 03, 2007 6:33 am Post subject: SYSLOG

I tell our UNIX admin to follow the documentation to setup the SYSLOG for WMB but I see nothing in the System or User log. Here is what they say the do, what else need to be done:
On Linux and UNIX systems, all WebSphere Message Broker messages (other than those generated by the command line utilities) are sent to the syslog, so it is useful to redirect user messages to a separate file.

Before you create a broker on Linux or UNIX systems, configure the syslog daemon to redirect user messages to a file called user.log:

Log on as root.
Enter the following commands to create a file called user.log.
On UNIX systems, enter the command:
touch /var/adm/user.log
chown root:mqbrkrs /var/adm/user.log
chmod 640 /var/adm/user.log
On Linux, enter the command:
touch /var/log/user.log
chown root:mqbrkrs /var/log/user.log
chmod 640 /var/log/user.log
Add the following line to the /etc/syslog.conf file to redirect debug level messages to the file user.log:
On UNIX systems, enter the command:
user.info /var/adm/user.log
On Linux, enter the command:
user.info /var/log/user.log
You can use user.* - instead of user info in the preceding examples.
* means that information, notice, warning, and debug messages are caught
- means that syslog does not synchronize the file after writing to it.
There is a performance gain, although you might lose some data if the machine crashes immediately after it has written to the file.
You can add similar lines to direct information, warning, and error messages to user.log.
Restart the syslog daemon.
On AIX, enter the command:
refresh -s syslogd
On HP-UX and Solaris, enter the command:
kill -HUP 'cat /etc/syslog.pid'
On Linux, enter the command:
/etc/init.d/syslogd restart
or
/etc/rc.d/init.d/syslogd restart
for systems where rc.d is not a soft link