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 » General IBM MQ Support » Omegamon XE for Messaging - situations not firing.

Post new topic  Reply to topic
 Omegamon XE for Messaging - situations not firing. « View previous topic :: View next topic » 
Author Message
morrisea
PostPosted: Sun Jul 25, 2010 10:17 pm    Post subject: Omegamon XE for Messaging - situations not firing. Reply with quote

Novice

Joined: 09 Apr 2006
Posts: 21
Location: South Africa

Hello,

We have Omegamon XE for Messaging v7.00.02 installed across AIX, Windows 2003 SP2 and Windows 2000 SP4, MQ v 7.0.1.2, MQ v6.0.2.3 and MQ v 5.3 CSD07 respectively.

Amoungst other things we are monitoring the situations MQSeries_Listener_Stopped and MQSeries_hannel_Initiator_Problem. These to situations are not firing and being displayed on the Portal. I suspect it is because we do not use default log paths for MQ. Please confirm it checks the AMQ0001.LOG file for these errors. If it does, how do I alter the path where it can find the log files.

If I am off track, any other help would be appreciated. Many thanks.
Back to top
View user's profile Send private message
harwinderr
PostPosted: Mon Jul 26, 2010 12:05 am    Post subject: Reply with quote

Voyager

Joined: 29 Jan 2002
Posts: 90

These situations are sampled, so you should check what the sampling interval is set to in the situation editor. There could be a delay of at-least that many minutes before it will show up on console. If you want, you can reduce the sampling interval to 1 min, so that you will get alerted sooner. However frequent samplings consume more resources.

This doesn't has anything to do with the log paths for MQ. The situation checks the listener status through MQSC commands.
Back to top
View user's profile Send private message Yahoo Messenger MSN Messenger
morrisea
PostPosted: Mon Jul 26, 2010 12:13 am    Post subject: Reply with quote

Novice

Joined: 09 Apr 2006
Posts: 21
Location: South Africa

Hi Harwinderr,

The sampling interval is every 2 mins and after 2 consective "True" results it should fire. I tested it on AIX running MQ v 7.0.1.2 and Windows running MQ v 5.3 CSD07. With MQ v 5.3 you cannot check Listener status with MQSc commands. I suspect that this is the problem there, but it doesn't explain the MQ v 7.0.1.2 not firing.
Back to top
View user's profile Send private message
harwinderr
PostPosted: Mon Jul 26, 2010 2:09 am    Post subject: Reply with quote

Voyager

Joined: 29 Jan 2002
Posts: 90

MQ 5.3 is not supported by OMXE Agent V 7.0 and above.
Confirm in the Agent logs that the situation is started.
Back to top
View user's profile Send private message Yahoo Messenger MSN Messenger
morrisea
PostPosted: Mon Jul 26, 2010 2:42 am    Post subject: Reply with quote

Novice

Joined: 09 Apr 2006
Posts: 21
Location: South Africa

Hi harwinderr,

I looked in /opt/IBM/ITM/logs # more QM_BROKER51::MQ.LG0 and the last entry for MQSeries_Listener_Stopped is :

1100722112234086KRAIRA000 Starting SARS_MQSeries_Listener_Stopped <3566249933,208668623> for KMQ.QMLSSTATUS.

I also checked the agent is running :

[prdmqdbn2] /opt/IBM/ITM/bin # ./cinfo -r

*********** Mon Jul 26 12:34:15 GMT+02:00 2010 ******************
User: root Groups: system bin sys security cron audit lp mqbrkrs
Host name : prdmqdbn2 Installer Lvl:06.21.00.02
CandleHome: /opt/IBM/ITM
***********************************************************
Host Prod PID Owner Start ID ..Status
prdmqdbn2 ul 229880 root Jul None ...running
prdmqdbn2 ux 225602 root Jul None ...running
prdmqdbn2 mq 307290 root Jul QM_BROKER51 ...running

However in the logs I see I am getting an authorization error (2035).

07/26/10 12:31:58 KMQMI223E Request for channel status failed. RC=0, CompCode=2, Reason=2035, Channel=*, QMgr=QM_BROKER51
07/26/10 12:31:58 KMQMI226E Request for channel data failed. RC=0, CompCode=2, Reason=2035, Channel=*, QMgr=QM_BROKER51
07/26/10 12:32:07 KMQMI218E Request for displaying lsstatus failed. RC=0, CompCode=2, Reason=2035
07/26/10 12:33:07 KMQMI218E Request for displaying lsstatus failed. RC=0, CompCode=2, Reason=2035
07/26/10 12:33:59 KMQMI109E MQ inquire command error. CC=0X2 Reason=0X7F3
07/26/10 12:33:59 KMQMI109E MQ inquire command error. CC=0X2 Reason=0X7F3
07/26/10 12:33:59 KMQMI109E MQ inquire command error. CC=0X2 Reason=0X7F3

I can't see where there can be an authorization issue on the queue manager though. Omegamon is installed as Root and we don't have SSL or OAM on the queue manager illustrated above.

Thank you for your time assisting me on these issues.
Back to top
View user's profile Send private message
morrisea
PostPosted: Mon Jul 26, 2010 2:43 am    Post subject: Reply with quote

Novice

Joined: 09 Apr 2006
Posts: 21
Location: South Africa

Hi harwinderr,

I looked in /opt/IBM/ITM/logs # more QM_BROKER51::MQ.LG0 and the last entry for MQSeries_Listener_Stopped is :

1100722112234086KRAIRA000 Starting SARS_MQSeries_Listener_Stopped <3566249933,208668623> for KMQ.QMLSSTATUS.

I also checked the agent is running :

[prdmqdbn2] /opt/IBM/ITM/bin # ./cinfo -r

*********** Mon Jul 26 12:34:15 GMT+02:00 2010 ******************
User: root Groups: system bin sys security cron audit lp mqbrkrs
Host name : prdmqdbn2 Installer Lvl:06.21.00.02
CandleHome: /opt/IBM/ITM
***********************************************************
Host Prod PID Owner Start ID ..Status
prdmqdbn2 ul 229880 root Jul None ...running
prdmqdbn2 ux 225602 root Jul None ...running
prdmqdbn2 mq 307290 root Jul QM_BROKER51 ...running

However in the prdmqdbn2_mq_1279527964.log logs I see I am getting an authorization error (2035).

07/26/10 12:31:58 KMQMI223E Request for channel status failed. RC=0, CompCode=2, Reason=2035, Channel=*, QMgr=QM_BROKER51
07/26/10 12:31:58 KMQMI226E Request for channel data failed. RC=0, CompCode=2, Reason=2035, Channel=*, QMgr=QM_BROKER51
07/26/10 12:32:07 KMQMI218E Request for displaying lsstatus failed. RC=0, CompCode=2, Reason=2035
07/26/10 12:33:07 KMQMI218E Request for displaying lsstatus failed. RC=0, CompCode=2, Reason=2035
07/26/10 12:33:59 KMQMI109E MQ inquire command error. CC=0X2 Reason=0X7F3
07/26/10 12:33:59 KMQMI109E MQ inquire command error. CC=0X2 Reason=0X7F3
07/26/10 12:33:59 KMQMI109E MQ inquire command error. CC=0X2 Reason=0X7F3

I can't see where there can be an authorization issue on the queue manager though. Omegamon is installed as Root and we don't have SSL or OAM on the queue manager illustrated above.

Thank you for your time assisting me on these issues.
Back to top
View user's profile Send private message
harwinderr
PostPosted: Mon Jul 26, 2010 3:01 am    Post subject: Reply with quote

Voyager

Joined: 29 Jan 2002
Posts: 90

The root user doesn't has OAM authorizations to connect to the queue manager by default. I think that's the reason for the 2035 errors. For quick resolution you can add root user to the mqm group, but it's best to start the agent with mqm user id.
Back to top
View user's profile Send private message Yahoo Messenger MSN Messenger
morrisea
PostPosted: Mon Jul 26, 2010 3:14 am    Post subject: Reply with quote

Novice

Joined: 09 Apr 2006
Posts: 21
Location: South Africa

I switched user to mqm and now get the following error (the 2035 has disappeared). It looks like I am going to have to get my authorizations sorted.

Open failed for meta file : /opt/IBM/ITM/aix523/mq/hist/QM_BROKER51/QMEVENTH.hdr
07/26/10 13:11:25 KMQMI184E Error in opening /opt/IBM/ITM/aix523/mq/hist/QM_BROKER51/QMEVENTH file
07/26/10 13:11:25 KMQMI185E Error in writing to /opt/IBM/ITM/aix523/mq/hist/QM_BROKER51/QMEVENTH file. Write is not successful or data lost
Source file is : /opt/IBM/ITM/aix523/mq/hist/QM_BROKER51/QMEVENTH
Definition file is : /opt/IBM/ITM/aix523/mq/hist/QM_BROKER51/QMEVENTH.hdr
Source file will be renamed to : /opt/IBM/ITM/aix523/mq/hist/QM_BROKER51/QMEVENTH.old
Destination file is : /opt/IBM/ITM/aix523/mq/hist/QM_BROKER51/QMEVENTH.arc
Delimitor set as :
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Mon Jul 26, 2010 10:59 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

looks like now you have file properties and ownership problems in IBM/ITM/bin...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
harwinderr
PostPosted: Tue Jul 27, 2010 4:26 am    Post subject: Reply with quote

Voyager

Joined: 29 Jan 2002
Posts: 90

Quote:
looks like now you have file properties and ownership problems in IBM/ITM/bin...


yes, more probably in the logs and config directory. To fix this you can either:

a) use secureMain (in bin directory) to fix the permission problems, or

b) Uninstall OMXE, re-install and start the MQ agent under mqm user id.
Back to top
View user's profile Send private message Yahoo Messenger MSN Messenger
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Omegamon XE for Messaging - situations not firing.
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.