| Author |
Message
|
| psn |
 Posted: Tue Jun 17, 2003 10:33 pm Post subject: syslog Infos WMQI 2.1 CSD04 on AIX 5.2 |
 |
|
Disciple
Joined: 30 Oct 2002
Posts: 193
Location: France
|
Hi,
We have installed WMQI 2.1 CSD04 on AIX 5.2 it works well but we do not have errors information in the syslog.
What kann I do ?
Thanks
psn |
|
| Back to top |
|
 |
| vmcgloin |
| Posted: Wed Jun 18, 2003 12:16 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
| Do you have /etc/syslog.conf configured correctly? |
|
| Back to top |
|
|
| psn |
| Posted: Wed Jun 18, 2003 1:42 am Post subject: syslog |
|
|
Disciple
Joined: 30 Oct 2002
Posts: 193
Location: France
|
and what must be exactly be configured ?
thanks
psn |
|
| Back to top |
|
|
| vmcgloin |
| Posted: Wed Jun 18, 2003 3:04 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
Well I'm not sure where it is in the doc but we add the following line on any machine with a new WMQI installation:
user.debug /var/log/syslog.user
Then you need to restart the syslog daemon.
To be honest I'm not sure the differences with AIX 5.2 in this area. |
|
| Back to top |
|
|
| jhalstead |
| Posted: Wed Jun 18, 2003 3:06 am Post subject: |
|
|
Master
Joined: 16 Aug 2001
Posts: 258
Location: London
|
I think this is what you need to do.
Log in as root.
Enter the following commands to create a file called syslog:
touch /var/wmqi/syslog
chown root:mqbrkrs /var/wmqi/syslog
chmod 750 /var/wmqi/syslog
Add the following line to the file /etc/syslog.conf to re-direct debug
level messages to the file syslog file:
user.debug /var/wmqi/syslog
Restart the syslog daemon using the command:
refresh -s syslogd
Good luck
jamie |
|
| Back to top |
|
|
| jhalstead |
| Posted: Wed Jun 18, 2003 3:11 am Post subject: |
|
|
Master
Joined: 16 Aug 2001
Posts: 258
Location: London
|
| I always seem to post at the same time as Vicky... ?! |
|
| Back to top |
|
|
| vmcgloin |
| Posted: Wed Jun 18, 2003 3:17 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
Great minds... or something like that  |
|
| Back to top |
|
|
| Ian |
| Posted: Wed Jun 18, 2003 3:55 am Post subject: |
|
|
Disciple
Joined: 22 Nov 2002
Posts: 152
Location: London, UK
|
Hi,
Under NT this is always available via the Event log, but under Unix this must be configured and is covered in the manuals (which is normally a good place to start) ...
Websphere MQ Integrator v2.1 - Admin Guide, Chapter 3 The Broker, Creating a broker, Configuring the local error log
| Code: |
The broker generates messages during its operation to indicate its status and the
success or failure of its operation. It writes these messages to the syslog (on UNIX
systems) or to the Windows NT Event log (Application view). The syslog entries
are identified by the string WMQIv210 and include a message number of the form
BIPnnnn that you can look up in the WebSphere MQ Integrator Messages book to
retrieve further information and recommended actions.
For example, it records:
- Unsuccessful attempts to write a message to an MQSeries output queue.
- Errors that it detects when interacting with databases.
- Inability to parse an input message.
On Windows NT, the Event log is always available and you do not need to
configure this log.
On UNIX, you must configure your system (or check that it is already configured)
to define the syslog location. For example, to enable syslog to direct readable
output from the broker to a text file called wmqisyslog:
Step 1. Put the following line in the syslog configuration file (the default file is
/etc/syslog.conf):
user.info /tmp/wmqisyslog
If the syslog configuration file does not already exist, you can create it.
Step 2. The output file wmqisyslog must already exist before it can be written to.
Therefore, create the file by using, for example:
touch /tmp/wmqisyslog
Step 3. The syslogd daemon needs to reread the configuration file to activate the
command. Therefore, make the syslogd re-scan its configuration file. On
AIX, enter the command:
refresh -s syslogd
On Sun Solaris and HP-UX, enter the command:
kill -HUP )cat /etc/syslog.pid)
For other syslog options, see the documentation for your particular UNIX platform.
|
Websphere MQ Integrator for AIX v2.1 - Installation Guide, Chapter 4 Configuring a Broker domain, Creating a broker
| Code: |
Configure Syslog on AIX --> Edit syslog configuration file
Log on as root and edit
# /etc/syslog.conf
To send user facility messages to
Append:
& save
(*see header of syslog.conf for alternatives)
all*
/var/log/syslog.user
user.debug /var/log/
syslog.user
syslog.conf
|
_________________
Regards, Ian |
|
| Back to top |
|
|
| psn |
| Posted: Wed Jun 18, 2003 3:56 am Post subject: syslog.conf |
|
|
Disciple
Joined: 30 Oct 2002
Posts: 193
Location: France
|
Hi,
I have check my syslog.conf. It is configured as follow:
*.debug /var/adm/syslog
the file syslog already exist on /var/adm but is empty when I try a Flow with errors.
best regards
psn |
|
| Back to top |
|
|
| Ian |
| Posted: Wed Jun 18, 2003 4:40 am Post subject: |
|
|
Disciple
Joined: 22 Nov 2002
Posts: 152
Location: London, UK
|
Each log itema are tagged with a "Facility" and a "Priority"
Facility identifies the source (auth, cron, kern, user ...)
Priority identifies the importance (debug, info, warning, critical ...)
Your entry would appear correct (*.debug)
Have you tried restarting the syslog daemon ?
command: refresh -s syslogd
_________________
Regards, Ian |
|
| Back to top |
|
|
|
|
