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 » Broker Syslog Daemon Configuration

Post new topic  Reply to topic
 Broker Syslog Daemon Configuration « View previous topic :: View next topic » 
Author Message
skrv
PostPosted: Wed Oct 28, 2015 10:24 am    Post subject: Broker Syslog Daemon Configuration Reply with quote

Centurion

Joined: 26 Oct 2012
Posts: 118

any one know the steps involved in setting up the syslog daemon for message broker on soalris platform?
Back to top
View user's profile Send private message
skrv
PostPosted: Wed Oct 28, 2015 10:36 am    Post subject: Reply with quote

Centurion

Joined: 26 Oct 2012
Posts: 118

I have below steps for a broker on Linux, where i do see /var/log/messages folder. But in Solaris i dont see /var/log/messages folder. So not sure what will the below step needs to be replaced with : authpriv.*  /var/log/messages

· Log on as root
· touch /var/mqsi/syslog/syslog.user
· chown mqadmin:mqbrkrs /var/mqsi/syslog/syslog.user
· chmod 640 /var/mqsi/syslog/syslog.user
· Add the following line to the /etc/syslog.conf :
/etc/syslog.conf
# MQ Specific logging
# MQ Specific logging
user.debug /var/mqsi/syslog/syslog.user
authpriv.*  /var/log/messages
· Restart the syslog daemon
Back to top
View user's profile Send private message
mqjeff
PostPosted: Wed Oct 28, 2015 10:37 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

https://developer.ibm.com/answers/questions/173320/can-i-configure-iib-or-wmb-syslog-output-to-separa.html

There used to be a couple of technotes that talked about this, but my bookmarks don't work any more.

_________________
chmod -R ugo-wx /
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Oct 28, 2015 10:41 am    Post subject: Reply with quote

Grand High Poobah

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

skrv wrote:
I have below steps for a broker on Linux, where i do see /var/log/messages folder. But in Solaris i dont see /var/log/messages folder.


I think the Solaris equivalent is /var/adm/messages
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
skrv
PostPosted: Wed Oct 28, 2015 10:48 am    Post subject: Reply with quote

Centurion

Joined: 26 Oct 2012
Posts: 118

thanks, I will try /var/adm/messages and see if it works.

can u explain below 2 steps?

user.debug /var/mqsi/syslog/syslog.user
authpriv.*  /var/adm/messages

this will capture all broker related INFO/WARNINGS/ERRORS ??
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Oct 28, 2015 11:32 am    Post subject: Reply with quote

Grand High Poobah

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

skrv wrote:
can u explain below 2 steps?

user.debug /var/mqsi/syslog/syslog.user
authpriv.*  /var/adm/messages


You should really ask your Solaris admin this but AFAIK the first line directs user messages of debug or higher (and broker emits messages as "user") to that log file. If there's anything else on the box that uses "user" it will capture those as well. The second line captures security errors to the named log file, adding weight to my belief that's the location of the OS syslog in Solaris.

skrv wrote:
this will capture all broker related INFO/WARNINGS/ERRORS ??


As well as all messages from other software using the same config, and I would urge you to speak to the OS admin before making changes to syslog.conf, even if you have the root access to do so.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
skrv
PostPosted: Wed Oct 28, 2015 11:45 am    Post subject: Reply with quote

Centurion

Joined: 26 Oct 2012
Posts: 118

so if my broker user ID is 'mqsi', do i need to replace user.debug with mqsi.debug? from below commind?

user.debug /var/mqsi/syslog/syslog.user
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Oct 28, 2015 11:55 am    Post subject: Reply with quote

Grand High Poobah

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

skrv wrote:
so if my broker user ID is 'mqsi', do i need to replace user.debug with mqsi.debug? from below commind?

user.debug /var/mqsi/syslog/syslog.user


No.

The "user" literal is the facility broker uses - see here and here.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
skrv
PostPosted: Wed Oct 28, 2015 11:57 am    Post subject: Reply with quote

Centurion

Joined: 26 Oct 2012
Posts: 118

thanks
Back to top
View user's profile Send private message
skrv
PostPosted: Thu Oct 29, 2015 9:34 am    Post subject: Reply with quote

Centurion

Joined: 26 Oct 2012
Posts: 118

does below entry log all the INFO/WARNING/ERROR of broker activity to the broker log?

user.info /var/mqsi/syslog/syslog.user
Back to top
View user's profile Send private message
skrv
PostPosted: Thu Oct 29, 2015 9:36 am    Post subject: Reply with quote

Centurion

Joined: 26 Oct 2012
Posts: 118

user.debug /var/mqsi/syslog/syslog.user

user.debug is not logging anything to the broker log
Back to top
View user's profile Send private message
Vitor
PostPosted: Thu Oct 29, 2015 9:58 am    Post subject: Reply with quote

Grand High Poobah

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

Speak to your Solaris sys prog. Which I recommended you do first.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
skrv
PostPosted: Thu Oct 29, 2015 9:59 am    Post subject: Reply with quote

Centurion

Joined: 26 Oct 2012
Posts: 118

yeah, it seems he also doesnt know much, so i was basically helping him....
Back to top
View user's profile Send private message
Vitor
PostPosted: Thu Oct 29, 2015 10:03 am    Post subject: Reply with quote

Grand High Poobah

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

Then repost your question on a Solaris forum.

If the syslog daemon isn't outputting anything then it's a problem with the daemon.

It's of course possible broker isn't sending anything to the log, but I discount that possibility. You should at least see start up and shut down info messages.

You could try testing it with *.info and see if that catches anything. If that doesn't work either the daemon is definitely hosed.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
skrv
PostPosted: Thu Oct 29, 2015 10:06 am    Post subject: Reply with quote

Centurion

Joined: 26 Oct 2012
Posts: 118

ok let me try below before posting anything to solaris forum

*.info /var/mqsi/syslog/syslo.user
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 » Broker Syslog Daemon Configuration
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.