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 » IBM MQ Installation/Configuration Support » dspmqver error on newly installed MQ 7.0.1.3

Post new topic  Reply to topic
 dspmqver error on newly installed MQ 7.0.1.3 « View previous topic :: View next topic » 
Author Message
szfamman
PostPosted: Mon May 09, 2016 1:05 am    Post subject: dspmqver error on newly installed MQ 7.0.1.3 Reply with quote

Newbie

Joined: 07 Jul 2014
Posts: 9

Hello guys,

I have a redhat 6.6. OS.
I've installed MQ 7.0.1.3 with rpm (packaged i've installed were: MQSeriesRuntime, MQSeriesServer, MQSeriesMan, MQSeriesJava, MQSeriesJRE; all of them for version 7.0.1.3 and x86_64)
I have also installed gsk7bas-7.0-4.27.i386 and gsk7bas64-7.0-4.27.x86_64 packages.

Whenever i'm trying to execute dspmqver i get the following error:
Code:
dspmqver: symbol lookup error: /lib64/libmqxzu_r.so: undefined symbol: zutCommonAnchor


But when i try it from the installation directory, it's working:
Quote:
[root@myhost]# /opt/mqm/bin/dspmqver
Name: WebSphere MQ
Version: 7.0.1.3
CMVC level: p701-103-100813
BuildType: IKAP - (Production)


I've tried " ldd /bin/dspmqver", and i see the library there:
Quote:
[root@myhost]# ldd /bin/dspmqver
linux-vdso.so.1 => (0x00007fff529ff000)
libmqmcs_r.so => /opt/mqm/lib64/libmqmcs_r.so (0x00007f2cd93db000)
libmqxzu_r.so => /lib64/libmqxzu_r.so (0x00000036e7600000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003676800000)
libdl.so.2 => /lib64/libdl.so.2 (0x0000003676c00000)
libc.so.6 => /lib64/libc.so.6 (0x0000003676400000)
libm.so.6 => /lib64/libm.so.6 (0x0000003677000000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x0000003678800000)
/lib64/ld-linux-x86-64.so.2 (0x0000003676000000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x0000003678000000)


After that, i used nm (with a grep for less data):
Quote:
[root@myhost]# nm -D /lib64/libmqxzu_r.so | grep zutCo
U zutCommonAnchor
00000036e768a930 T zutConnectConfig
00000036e7684ce0 T zutCopyCno


Any idea what's happening? Why is zutCommonAnchor undefined?
Thanks in advance!
Tom
Back to top
View user's profile Send private message
rammer
PostPosted: Mon May 09, 2016 3:00 am    Post subject: Reply with quote

Partisan

Joined: 02 May 2002
Posts: 359
Location: England

What happens if you run it as the mqm user? Im thinking it probably needs the path setting up in the profile or something like that.
Back to top
View user's profile Send private message
szfamman
PostPosted: Mon May 09, 2016 3:05 am    Post subject: Reply with quote

Newbie

Joined: 07 Jul 2014
Posts: 9

Hi rammer!

rammer wrote:
What happens if you run it as the mqm user? Im thinking it probably needs the path setting up in the profile or something like that.


The same:
Code:
dspmqver: symbol lookup error: /lib64/libmqxzu_r.so: undefined symbol: zutCommonAnchor
Back to top
View user's profile Send private message
rammer
PostPosted: Mon May 09, 2016 3:38 am    Post subject: Reply with quote

Partisan

Joined: 02 May 2002
Posts: 359
Location: England

rammer wrote:
What happens if you run it as the mqm user? Im thinking it probably needs the path setting up in the profile or something like that.


Im not logged onto any servers at moment to check my configurations, but have you got /opt/mqm/bin set in the PATH for mqm ID ?
Back to top
View user's profile Send private message
zpat
PostPosted: Mon May 09, 2016 4:39 am    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5849
Location: UK

Why install a version of MQ that is out of support?

Also, if you must use 7.0.1.xx, there are a number of later fixpacks available.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error.
Back to top
View user's profile Send private message
szfamman
PostPosted: Mon May 09, 2016 5:17 am    Post subject: Reply with quote

Newbie

Joined: 07 Jul 2014
Posts: 9

zpat wrote:
Why install a version of MQ that is out of support?

Also, if you must use 7.0.1.xx, there are a number of later fixpacks available.


As far as i know, we'll move to version 8, but first we'd like to test the upgrade from this version to 8. And firstly, we need an environment with this exact version.


rammer wrote:

What happens if you run it as the mqm user? Im thinking it probably needs the path setting up in the profile or something like that.


Thank you rammer for pointing out to the path. I totally forgot to check that...
I seems that somehow all the MQ executables (amq*, crtmq*, dspmq*, endmq*, runmq*, setmq*, strmq*) from a different version were inside the /bin folder, but there shouldn't be any...
And under the /usr/bin folder we can find the symlinks to the correct executables (i erased and reinstalled everything to double check the executables, and the wrong ones were in the /bin folder the whole time).

For example:
Code:
[root@myhost~]# ls -l /bin | grep dspmqver
-r-xr-xr-x  1 2005  2005  110269 Apr 29  2014 dspmqver

Correct executable:
Code:
[root@myhost~]# ls -l /usr/bin | grep dspmqver
lrwxrwxrwx  1 root root         21 May  9 14:16 dspmqver -> /opt/mqm/bin/dspmqver


The PATH variable contains both /bin and /usr/bin:
Code:
[root@myhost~]# echo $PATH
/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin


Now, /bin comes before /usr/bin, that's why it's being chosen. Trying "which dspmqver" also returns the wrong one of course.

So thank you again for pointing out to that, i might still be searching for some mysterious solution without your little help.

Long story short: stay awake, and don't forget to check the path!

Thanks,
Tom
Back to top
View user's profile Send private message
mqjeff
PostPosted: Mon May 09, 2016 6:41 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

I forget if mq v7.0 has a setmqenv.
_________________
chmod -R ugo-wx /
Back to top
View user's profile Send private message
rammer
PostPosted: Mon May 09, 2016 6:42 am    Post subject: Reply with quote

Partisan

Joined: 02 May 2002
Posts: 359
Location: England

mqjeff wrote:
I forget if mq v7.0 has a setmqenv.


didnt that come in 7.1 when it allowed you to start running multiple installs?
Back to top
View user's profile Send private message
mqjeff
PostPosted: Mon May 09, 2016 7:14 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

rammer wrote:
mqjeff wrote:
I forget if mq v7.0 has a setmqenv.


didnt that come in 7.1 when it allowed you to start running multiple installs?


I forget.

Sounds correct, though.
_________________
chmod -R ugo-wx /
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Installation/Configuration Support » dspmqver error on newly installed MQ 7.0.1.3
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.