| Author |
Message
|
| venkat kurra |
 Posted: Sat Mar 03, 2007 9:38 am Post subject: WMQ v 6 fix 2 upgrade issue on AIX 5.3 |
 |
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
Hi,
I upgraded MQ fix pack2 on multiple AIX servers. Some reason only one server giving me trouble.
I stopped all mq apps. None of mq process running (ps -ef|grep mq). But when i try to upgrade fix2 but getting the following error,
You seem to have an MQ queue manager still running.
You must stop all MQ processing, and stop the Queue
Manager(s) by using the endmqm command before trying to
install/update/delete the MQ product.
update: Failed while executing the mqm.txclient.rte.pre_u script.
same error repeated for all components (server,cleint..etc).
I am sure MQ processes stopped on the server.
Smitty options are..
PREVIEW only? (install operation will NOT occur) (first time.. yes) no
COMMIT software updates? no
SAVE replaced files? yes
AUTOMATICALLY install requisite software? yes
EXTEND file systems if space needed? no
VERIFY install and check file sizes? yes
DETAILED output? yes
Process multiple volumes? no
ACCEPT new license agreements? yes
Preview new LICENSE agreements? no
I do not understnad why this server is different from other AIX servers.
Any idea? Any commands to trouble shoot?
Thanks,
Venkat
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
 |
| Philip Morten |
| Posted: Sat Mar 03, 2007 10:29 am Post subject: |
|
|
Master
Joined: 07 Mar 2002
Posts: 230
Location: Hursley Park
|
If you set the environment variable INST_DEBUG=1 before starting smit then the script will be traced and you can see why it thinks there is something running. It will probably be that some process is still attached to MQ shared memory.
_________________
Philip Morten
The postings on this site are my own and do not necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| venkat kurra |
| Posted: Sat Mar 03, 2007 11:12 am Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
I thought uninstall fix1 (roll back to base) shudn't work, if the mq process is running and then tried uninstall fix1...but uninstall went well with out any issue (Now dapmqver - 6.0.0.0).
if i try to install fix1 then the same issue ... very strange.
i set the environmnet INST_DEBUG=1 before smit. Where i can see the trace file?
You seem to have an MQ queue manager still running.
You must stop all MQ processing, and stop the Queue
Manager(s) by using the endmqm command before trying to
install/update/delete the MQ product.
update: Failed while executing the mqm.txclient.rte.pre_u script.
installp: The installation has FAILED for the "usr" part
of the following filesets:
mqm.txclient.rte 6.0.1.1
installp: Cleaning up software for:
mqm.txclient.rte 6.0.1.1
Filesets processed: 1 of 9 (Total time: 1 secs).
installp: APPLYING software for:
mqm.server.rte 6.0.1.1
--- repat for all components-----
summary as follows..
Installation Summary
--------------------
Name Level Part Event Result
-------------------------------------------------------------------------------
mqm.txclient.rte 6.0.1.1 USR APPLY FAILED
mqm.txclient.rte 6.0.1.1 USR CLEANUP SUCCESS
mqm.server.rte 6.0.1.1 USR APPLY FAILED
mqm.server.rte 6.0.1.1 USR CLEANUP SUCCESS
mqm.man.en_US.data 6.0.1.1 SHARE APPLY FAILED
mqm.man.en_US.data 6.0.1.1 SHARE CLEANUP SUCCESS
mqm.keyman.rte 6.0.1.1 USR APPLY FAILED
mqm.keyman.rte 6.0.1.1 USR CLEANUP SUCCESS
mqm.java.rte 6.0.1.1 USR APPLY FAILED
mqm.java.rte 6.0.1.1 USR CLEANUP SUCCESS
mqm.client.rte 6.0.1.1 USR APPLY FAILED
mqm.client.rte 6.0.1.1 USR CLEANUP SUCCESS
mqm.base.sdk 6.0.1.1 USR APPLY FAILED
mqm.base.sdk 6.0.1.1 USR CLEANUP SUCCESS
mqm.base.samples 6.0.1.1 USR APPLY FAILED
mqm.base.samples 6.0.1.1 USR CLEANUP SUCCESS
mqm.base.runtime 6.0.1.1 USR APPLY FAILED
mqm.base.runtime 6.0.1.1 USR CLEANUP SUCCESS
thanks for the help.
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
| vennela |
| Posted: Sun Mar 04, 2007 10:39 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Have you cleaned the shared memory semaphoers etc? |
|
| Back to top |
|
|
| venkat kurra |
| Posted: Sun Mar 04, 2007 11:09 am Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
yes i did ..
ipcs -s |grep mqm
ipcs -m |grep mqm
ipcrm -s <pid>
ipcrm -m <pid>
also checked ipcs -s and ipcs -m for all ....only root has some.
Do i need to care about root shared memory stuff?
An other question...Does a reboot clean up the shared memory issue?
I belive this server rebooted recently and then i tried mq upgrade with out starting any mq/broker processes (auto startup scripts are not ready yet).
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Mar 04, 2007 3:34 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20702
Location: LI,NY
|
Rebooting would certainly clear the process that is still attached to the qmgr.
Another way to try and clear that process would be to try and restart the qmgr. It will tell you that you can't as process x y and z are still attached to the qmgr. Kill those processes (you might have to coordinate with the owner apps), start the qmgr and shut it right down again. Then clear the memory (amqiclen).
After that you should be ready for the upgrade.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| venkat kurra |
| Posted: Sun Mar 04, 2007 6:30 pm Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
I thought same thing and tried couple of attempts ( restart queue manager, stop the qmgr, ps -ef|grep mq ,clean up shared memory..etc).
Bad thing ...i was able to roll back (fix1 to base) and i could't go forward. Very begining it was v6 fix1..just to identify the problem i attempted to roll back to base and it went well with out any issue. If the process is running ...roll back should fail. Looks like upgrade only having this issue.
Tomorrow morning i am planning for the server reboot. I know it's not a good idea ..... but there is no other options before open a ticket with iBM.
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
| Nigelg |
| Posted: Mon Mar 05, 2007 1:18 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
Do you have any user-created directories in /var/mqm/qmgrs, i.e. directories which are not the names of qmgrs (or SYSTEM)? I vaguely remember this causing a problem for amqiclen (shared memory & semaphore cleaner) when it is run as part of the install script.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| venkat kurra |
| Posted: Mon Mar 05, 2007 12:43 pm Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
Thank you very much for that info. Upgrade keep failing due to a .txt file uner /var/mqm/qmgrs. Once i remove that .txt then the upgrade went well.
IBM folks,
Please change the error description for this type of problem. On Aix if you have a user defined file or directory under /var/mqm/qmgrs then the upgrade failed with the below error,
You seem to have an MQ queue manager still running.You must stop all MQ processing, and stop the Queue Manager(s) by using the endmqm command before trying to install/update/delete the MQ product.
the above statement is different from the actual root cause(verify mq user data).
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Tue Mar 06, 2007 1:41 am Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
Do you have an application running, which uses MQ? You should first stop the application and then stop the QMgr.
If this does not work (or you do not know the appliation), disable the automatic startup of the QMgr and reboot the system.
_________________
Regards
Hubert |
|
| Back to top |
|
|
|
|
