| Author |
Message
|
| csmith28 |
 Posted: Fri Jan 15, 2010 10:38 am Post subject: Heads up, files in /var/mqm/qmgrs can be bad mmmkay.... |
 |
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
I was trying to migrate from WMQ6.0.1.0 to WMQ7.0.1.0 on AIX 5300-08.
I stopped the MQManager and confirmed there were no mqm processes running and attempted to perform the upgrade but I kept getting this error:
| Quote: |
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. |
Using ipcs I saw a few left over Shared Memory Segments and Semaphores that the ipcrm command could not kill so I disabled the startup scripts for the MQManager and rebooted to get rid of them.
When the server came back up, I tried the upgrade again and got the same error in smit. Then while waiting for IBM to respond to the ticket I opened one of the MQManager Support guys sent me an email asking that I try again because he had just removed some files he had created in /var/mqm/qmgrs.
I tried again, it worked.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial.
Last edited by csmith28 on Sun Jan 17, 2010 5:55 am; edited 1 time in total |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Fri Jan 15, 2010 11:28 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
Carefully read this
According to IBM ipcrm should never be needed and reported immediately...
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jan 15, 2010 11:34 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Michael Dag wrote: |
Carefully read this
According to IBM ipcrm should never be needed and reported immediately... |
According to that ipcrm should not be needed for normal administrative tasks. IMHO going from one version to another is not a normal, business as usual activity and you might have to use such means. Though clearly you shouldn't need to. But often you do.
I agree unreservedly that if the typical bounce procedure for the queue manager is:
- Issue endmqm
- Wait 5 mins
- Issue endmqm -i
- Use ipcrm to clean up
- Issue strmqm
then there are a number of serious issues that need to be addressed.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| csmith28 |
| Posted: Fri Jan 15, 2010 12:18 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
Thanks guys I wasn't aware of the ipcrm thingy but in this particular instance after I disable the MQManager start up scripts and rebooted the server I was still getting the same error saying I had an MQManager running even though I had prevented all the WMQSeries activity from starting in the first place. That is to say, there were no shared memory resources to remove.
Then once the files that were placed in /var/mqm/qmgrs were removed the error went away and the upgrade was successful.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Jan 15, 2010 1:32 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| because he had just removed some files he had created in /var/mqm/qmgrs. |
I'm curious... what files did he create in the qmgrs directory? and why? It's not the WMQ sysadmins filepath; rather, it belongs to WMQ software.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| csmith28 |
| Posted: Fri Jan 15, 2010 1:58 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
Honestly, I don't know. I didn't get a chance to look before he deleted them and he was sort of embarrassed so I didn't press the issue.
However he did promise not to do it again.
Only thing I can do is speculate that the /var/mqm/qmgrs directory is a "Special" directory for mqseries. Normally the only files or directories in that directory are the @SYSTEM directory and the directories that contain the MQManager definitions, logs etc for which it is named and some bit of code looked there during the installation, found those files and for some reason it caused that error to be thrown.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jan 15, 2010 2:31 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
I would not be surprised to find that some part of the install script did an ls on /var/mqm/qmgrs and used that to figure out names of qmgrs that might exist.
Especially given that the install script probably has to assume that /usr/mqm/bin (or whatever) has been removed and so can't assume that dspmq exists still (or ever existed). |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Fri Jan 15, 2010 10:09 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| mqjeff wrote: |
I would not be surprised to find that some part of the install script did an ls on /var/mqm/qmgrs and used that to figure out names of qmgrs that might exist.
Especially given that the install script probably has to assume that /usr/mqm/bin (or whatever) has been removed and so can't assume that dspmq exists still (or ever existed). |
Jeff, I think you are correct and I have seen this problem before. The install script thinks that rogue files or dirs in the /var/mqm/qmgrs directory are qmgrs and they are running. The same problem can occur when installing Fix Packs. Removing them fixes the problem.
Its unrelated to IPC resources (shared memory & semaphores).
_________________
Glenn |
|
| Back to top |
|
|
|
|
