ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » stdout vs stderr in terms of error msg contents

Post new topic  Reply to topic
 stdout vs stderr in terms of error msg contents « View previous topic :: View next topic » 
Author Message
lamtbs
PostPosted: Sun Nov 06, 2016 7:58 pm    Post subject: stdout vs stderr in terms of error msg contents Reply with quote

Acolyte

Joined: 07 Nov 2005
Posts: 57
Location: Hong Kong

Hello all,

my customer wants to do some simple monitoring of overall health of IIB by log monitoring, e.g.
BIP2002 The IBM Integration Bus service has stopped.
BIP2005 Unsuccessful IBM Integration Bus service initialization.
etc etc
They could be of "I", "W", "E" types

While we have both stdout and stderr,

- is one dedicated for "E" type of messages?
- or how are the 2 logs' segregation of messages defined?
- or in fact the messages can appear in both logs at the same time?

Thanks!
Back to top
View user's profile Send private message Send e-mail MSN Messenger
mqjeff
PostPosted: Mon Nov 07, 2016 5:16 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

... I don't think you should be monitoring either stdout or stderr of the IIB process.

You should be monitoring the file (or the windows event log) that your syslogd writes IIB messages to. With a bit of tuning of the syslogd conf, you can direct these to individual files - or pipe to a shell scrip that can sort individual broker messages to different files, or even just do the work you need.

Without worrying about stdout and stderr.
_________________
chmod -R ugo-wx /
Back to top
View user's profile Send private message
lamtbs
PostPosted: Mon Nov 07, 2016 5:53 am    Post subject: Reply with quote

Acolyte

Joined: 07 Nov 2005
Posts: 57
Location: Hong Kong

Oh,

sorry I didn't say it clearly, what I meant to say was to "monitor the stdout / stderr "file" for those BIP messages" (we are on AIX)

I was just wondering which file, stdout or stderr to scan for the BIP messages.

I was interest to know about startup / shutdown (scheduled or mishap), so some of them are Info type BIP messages, while others may be Error type BIP messages.

Not sure if stderr only store "E" messages? in that case if I just monitor stderr file, will I miss any BIP messages that I need?

Thanks!
Back to top
View user's profile Send private message Send e-mail MSN Messenger
Vitor
PostPosted: Mon Nov 07, 2016 5:59 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

lamtbs wrote:
Not sure if stderr only store "E" messages? in that case if I just monitor stderr file, will I miss any BIP messages that I need?


You should speak to the sys admins for your AIX box.

IIB sends BIP messages on all *NIX platforms using the syslog daemon. Therefore messages are segregated (or indeed suppressed) based on the settings of the syslog.conf file, which also controls their destination file.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » stdout vs stderr in terms of error msg contents
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.