| Author |
Message
|
| BBM |
 Posted: Tue Jun 19, 2012 6:21 am Post subject: MQ 7.1 upgrade leads to symlink to libmqmcs.so disappearing |
 |
|
Master
Joined: 10 Nov 2005
Posts: 217
Location: London, UK
|
Hi,
We recently upgraded one of our Solaris 10 MQ server installs to MQ 7.1
After running the upgrade we ran /opt/mqm/bin/setmqinst
We only have one MQ install on the server.
So far so good and MQ operates normally.
However, when we try to start up our qpasa montoring agent it complains that libmqmcs. does not exist.
Running ldd against the qpasa process we get this:
/opt/qpasa# ldd qpcfg
librt.so.1 => /lib/librt.so.1
libsocket.so.1 => /lib/libsocket.so.1
libnsl.so.1 => /lib/libnsl.so.1
libdl.so.1 => /lib/libdl.so.1
libmqm.so => /usr/lib/libmqm.so
libmqmcs.so => (file not found)
libmqmzse.so => (file not found)
libc.so.1 => /lib/libc.so.1
libaio.so.1 => /lib/libaio.so.1
libmd.so.1 => /lib/libmd.so.1
libmp.so.2 => /lib/libmp.so.2
libscf.so.1 => /lib/libscf.so.1
libmqe.so => /opt/mqm/lib/libmqe.so
libdoor.so.1 => /lib/libdoor.so.1
libuutil.so.1 => /lib/libuutil.so.1
libgen.so.1 => /lib/libgen.so.1
libm.so.2 => /usr/lib/libm.so.2
libthread.so.1 => /usr/lib/libthread.so.1
It seems that two of the MQ libraries no longer have symbolic links from /usr/lib after the upgrade.
Reading the manual it's not immediately clear what best practice is to remedy the situation, ie do we add a symbolic link manually or play around with crtmqenv.
I'm a little surprised that the product has been altered so that existing apps won't work after the upgrade to enable the multi-install feature which surely only a minority will use.
BBM |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Jun 19, 2012 7:04 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You need to run setmqinst in every shell that accesses MQ.
This includes the shell that starts your qpasa agent. |
|
| Back to top |
|
|
| BBM |
| Posted: Tue Jun 19, 2012 7:13 am Post subject: |
|
|
Master
Joined: 10 Nov 2005
Posts: 217
Location: London, UK
|
Hi,
We opened a PMR for this and SETMQINST does not fix this without modifications to the file it uses.
The reason for this is that IBM have decided to comment out the two files that our app needed from the instinfo.tsk file which SETMQINST uses.
Here is the extract from /opt/mqm/instinfo.tsk that shows the two libraries commented out:
# SymLink:
# Name=/usr/lib/libmqmcs.so
# Target=+MQ_INSTALLATION_PATH+/lib/libmqmcs.so
# Activity=PRIMARY
# SymLink:
# Name=/usr/lib/64/libmqmcs.so
# Target=+MQ_INSTALLATION_PATH+/lib64/libmqmcs.so
# Activity=PRIMARY
IBM advised us to uncomment these entries to get our (widely used) monitoring app qpasa working.
This is something they have been asked a few times apparently...
BBM |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Jun 19, 2012 9:26 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| WMQ 7.5 is out very shortly. Why bother with 7.1? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jun 19, 2012 12:12 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
I guess I was misreading your note.
You need to run setmqENV in every shell, not setmqinst.
but I guess I don't know at this point if that would have fixed it, if setmqinst didn't.
It would probably be helpful to other people if you updated your PMR to ask L2 to create a technote on the subject... |
|
| Back to top |
|
|
| BBM |
| Posted: Wed Jun 20, 2012 12:07 am Post subject: |
|
|
Master
Joined: 10 Nov 2005
Posts: 217
Location: London, UK
|
Thanks for the replies - I will ask IBM to update the PMR - I have asked them why this change was made - probably old libraries that were being referenced I imagine.
We are not waiting for 7.5 as there seems to be little advantage over 7.1 for us. We are upgrading to 7.1 to get the built-in security exit functionality. |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Jun 20, 2012 12:12 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| I would guess 7.5 might contain some fixes for the functions introduced in 7.1. |
|
| Back to top |
|
|
| mvic |
| Posted: Thu Jun 21, 2012 4:01 pm Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| BBM wrote: |
| We are not waiting for 7.5 as there seems to be little advantage over 7.1 for us. We are upgrading to 7.1 to get the built-in security exit functionality. |
I believe 7.5 is available now.
Speak to your IBM sales rep. |
|
| Back to top |
|
|
| JasonE |
| Posted: Fri Jun 22, 2012 2:03 pm Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
| Quote: |
| The reason for this is that IBM have decided to comment out the two files that our app needed from the instinfo.tsk file which SETMQINST uses |
Which part of libmqmcs is a documented MQ external API which should be available to applications? In normal use, why should it need to be available...
Might start to explain why it wasnt in the task file... |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jun 22, 2012 8:54 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I think the question goes more like:
How do you handle a dual environment for your monitoring tool (7.0 and 7.1) on the same server? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| JasonE |
| Posted: Tue Jun 26, 2012 12:50 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
| Quote: |
| How do you handle a dual environment for your monitoring tool (7.0 and 7.1) on the same server? |
If its accessing any local files, use the installation paths, and if you have to (worst case) get those paths from mqinst.ini if it exists else the default path.
If using the MQI, ensure you are configured to pick up the latest installed versions of the libmqm for example, which means if you pick up 7.1, it can talk to any qmgr on the box even 7.0.1. This may mean using LD_LIBRARY_PATH rather than compiled in RPATH's for example.
I still dont understand why libmqmcs would be required - it hosts no MQ API - Maybe I'm missing something. |
|
| Back to top |
|
|
| BBM |
| Posted: Tue Jun 26, 2012 2:28 am Post subject: |
|
|
Master
Joined: 10 Nov 2005
Posts: 217
Location: London, UK
|
fjb_saper - we are running a single version of MQ not a dual environment. We upgraded from 7.01 to 7.1 by removing 7.01 and installing 7.1 and converting the queue managers following the upgrade.
These libraries get commented out of the install script that setmqinst runs after you have upgraded to 7.1.
JasonE - I've pursued the PMR and IBM are saying the same thing, why would a monitoring product require these libraries in the first place.
MQ 7.1 can find these libraries without the symlinks in place apparently so the symlinks are not necessary that's why they were commented out.
I have opened a ticket with BMC the company that make Qpasa! to determine why the product references these internal libraries. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jun 26, 2012 5:14 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| BBM wrote: |
fjb_saper - we are running a single version of MQ not a dual environment. We upgraded from 7.01 to 7.1 by removing 7.01 and installing 7.1 and converting the queue managers following the upgrade.
These libraries get commented out of the install script that setmqinst runs after you have upgraded to 7.1.
JasonE - I've pursued the PMR and IBM are saying the same thing, why would a monitoring product require these libraries in the first place.
MQ 7.1 can find these libraries without the symlinks in place apparently so the symlinks are not necessary that's why they were commented out.
I have opened a ticket with BMC the company that make Qpasa! to determine why the product references these internal libraries. |
I know the Industry (and myself) will keep the name QPasa alive... However I have to ask you what version you are using... It might well be that the version of QPasa you are using is not the latest / V7.1 ready one...
Any response yet from BMC?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mvic |
| Posted: Tue Jun 26, 2012 6:33 pm Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| BBM wrote: |
JasonE - I've pursued the PMR and IBM are saying the same thing, why would a monitoring product require these libraries in the first place.
MQ 7.1 can find these libraries without the symlinks in place apparently so the symlinks are not necessary that's why they were commented out.
I have opened a ticket with BMC the company that make Qpasa! to determine why the product references these internal libraries. |
In the past, the application programming guide gave instructions to include libmqmcs in the link. In recent times it has not been required. There was some technical historic justification for why this was required (no longer applicable I think) to do with satisfying the linker requirements on Solaris. Nowadays - for how long, I don't know, but take a look in the historic versions of the MQ application programming guide - MQ application building guidance has changed to say you don't need to link directly with libmqmcs when building your app on Solaris. |
|
| Back to top |
|
|
| BBM |
| Posted: Wed Jun 27, 2012 7:25 am Post subject: |
|
|
Master
Joined: 10 Nov 2005
Posts: 217
Location: London, UK
|
Hi,
BMC have come back and echoed mvic's comment exactly.
Instructions to link to this library were given back in the application programming guide for MQ 5.2 (http://publib.boulder.ibm.com/iseries/v5r2/ic2924/books/csqzal05.pdf) though this is not required any longer.
IBM have escalated the PMR to the labs to confirm the situation.
I can't bring myself to call Qpasa! Middleware Management Performance and Availibility just yet - too big a mouthful! We are running 5.0 build 50 fixpack 1 hotfix D - which does not officially support v7.1 but works.
Apparently fixpack 2 is just around the corner which adds official support for 7.1, but this is by the by for this issue according to BMC.
Thanks very much for all the very useful replies.
BBM |
|
| Back to top |
|
|
|
|
