Author |
Message
|
vam |
Posted: Mon Aug 22, 2011 8:47 am Post subject: SYSLOG study |
|
|
Acolyte
Joined: 16 Mar 2010 Posts: 70
|
Hello MQSeries Team,
Generally when we start/stop the broker I will be checking whether the flow have been started from BROKER Admin(GUI) perspective.
But recently I came to know that we need to check the syslog for it to see if there exist any issues (i.e, semaphores,process....).I am not clear about this could you please let me know how to go thorugh it and what we need to check ? |
|
Back to top |
|
 |
lancelotlinc |
Posted: Mon Aug 22, 2011 9:51 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
|
Back to top |
|
 |
mqjeff |
Posted: Mon Aug 22, 2011 9:53 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
did you look here?
If not, why not? If so, what did you find? Was some part of it confusing? Which part? |
|
Back to top |
|
 |
vam |
Posted: Mon Aug 22, 2011 10:09 am Post subject: SYSLOG study |
|
|
Acolyte
Joined: 16 Mar 2010 Posts: 70
|
Yes I can find the log file in the directory: /var/log.
I mean to ask you what are the thinkgs I need to look in the log file.I didnt come across such situation. |
|
Back to top |
|
 |
smdavies99 |
Posted: Mon Aug 22, 2011 10:16 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
Perhaps the syslog daemon has had its defalt directory changed.
If you have read access lok at the sslog config file.
something like
/etc/syslog.conf
There could be a line at the end that has user.* at the start.
This can be followed by a path to the file where ALL the broker BIP messages are writen. For example
user.* /log/broker/wmbevent.log
This is all pretty standard Unix/Linux Sysadmin stuff. Your system admin WILL be able to help you here. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
mqjeff |
Posted: Mon Aug 22, 2011 10:21 am Post subject: Re: SYSLOG study |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
vam wrote: |
I mean to ask you what are the thinkgs I need to look in the log file.I didnt come across such situation. |
You need to look at the things that are related to Broker.
Then you need to decide what they mean and whether or not they represent issues. |
|
Back to top |
|
 |
lancelotlinc |
Posted: Mon Aug 22, 2011 11:48 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
Quote: |
tail has a special command line option -f (follow) that allows a file to be monitored. Instead of just displaying the last few lines and exiting, tail displays the lines and then monitors the file. As new lines are added to the file by another process, tail updates the display. This is particularly useful for monitoring log files. The following command will display the last 10 lines of messages and append new lines to the display as new lines are added to messages:
tail -f /var/adm/messages
In cases when the user is following a log file that rotates then it is advisable to use the -F option as it keeps folllowing the log even when it is recreated, renamed, or removed as part of log rotation.
tail -F /var/adm/messages
To interrupt tail while it is monitoring, break-in with Ctrl+C. This command can be run "in the background" with &,
|
_________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
Back to top |
|
 |
Vitor |
Posted: Mon Aug 22, 2011 11:52 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
lancelotlinc wrote: |
Quote: |
tail has a special command line option -f (follow) that allows a file to be monitored. Instead of just displaying the last few lines and exiting, tail displays the lines and then monitors the file. As new lines are added to the file by another process, tail updates the display. This is particularly useful for monitoring log files. The following command will display the last 10 lines of messages and append new lines to the display as new lines are added to messages:
tail -f /var/adm/messages
In cases when the user is following a log file that rotates then it is advisable to use the -F option as it keeps folllowing the log even when it is recreated, renamed, or removed as part of log rotation.
tail -F /var/adm/messages
To interrupt tail while it is monitoring, break-in with Ctrl+C. This command can be run "in the background" with &,
|
|
This is a very good way of monitoring a log file. It tells the OP nothing he didn't already know about what to look for in the output of the tail command. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
lancelotlinc |
Posted: Mon Aug 22, 2011 11:56 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
Sir Vitor,
I am straining very hard not to post the link to the WM663 class. Don't make me do it.
Lance
Training ...!!  _________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
Back to top |
|
 |
Vitor |
Posted: Mon Aug 22, 2011 12:01 pm Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
lancelotlinc wrote: |
I am straining very hard not to post the link to the WM663 class. |
When the strain becomes too much, keep straining. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
|