| Author |
Message
|
| NickEdwards28 |
 Posted: Tue Apr 25, 2006 2:11 am Post subject: mqsideploy errors maybe caused by environment variables |
 |
|
Newbie
Joined: 25 Apr 2006
Posts: 3
Location: UK
|
We're in the process of setting up a back end deployment of .bar files to a WBI 6.0 broker on Linux using MKS. Basically, the .bar files are dropped in to a directory and the mqsideploy command is run against them to deploy to the broker.
However, the problem we have is that we get the error:
error while loading shared libraries: libImbCmdLib.so: cannot open shared object file: No such file or directory
When I do an ldd on mqsideploy I see that there are lots of objects that are not found, although they do in fact exist:
/etc/libcwait.so => /etc/libcwait.so (0xb75e7000)
libImbCmdLib.so => not found
libPlatFormSupport.so => not found
libicuuc.so.32 => not found
libCommonServices.so => not found
libPersonality.so => not found
libMessageServices.so => not found
libbipnativetrace.so => not found
libm.so.6 => /lib/tls/libm.so.6 (0xb75b6000)
libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0xb7502000)
libpthread.so.0 => /lib/tls/libpthread.so.0 (0xb74f2000)
libdl.so.2 => /lib/libdl.so.2 (0xb74ef000)
libbipstlport_gcc.so => not found
libmqm_r.so => /usr/lib/libmqm_r.so (0xb74c9000)
libmqmcs_r.so => /usr/lib/libmqmcs_r.so (0xb733e000)
libmqmzse.so => /usr/lib/libmqmzse.so (0xb733b000)
libjvm.so => not found
libc.so.6 => /lib/tls/libc.so.6 (0xb7203000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0xb75eb000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb71fa000)
libmqz_r.so => /opt/mqm/lib/libmqz_r.so (0xb7159000)
I am not sure, but I think this may be due to the following environment variables being blank:
LIB
CLASSPATH
NLSPATH
plus others - it's a new installation...
Can anyone tell me:
1. What this problem is being caused by?
2. What environment variables need to be set?
3. And what to?
Many thanks
Nick
PS. This is pretty new to me so I apologise in advance for any dumb statements above or in subsequent questions... |
|
| Back to top |
|
 |
| fschofer |
| Posted: Tue Apr 25, 2006 2:58 am Post subject: |
|
|
Knight
Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany
|
|
| Back to top |
|
|
| NickEdwards28 |
| Posted: Tue Apr 25, 2006 5:23 am Post subject: |
|
|
Newbie
Joined: 25 Apr 2006
Posts: 3
Location: UK
|
| Thanks - we have sorted this out now. |
|
| Back to top |
|
|
| mrlinux |
| Posted: Thu Apr 27, 2006 6:26 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Can you post the resolution for the rest of us
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| NickEdwards28 |
| Posted: Thu Apr 27, 2006 6:30 am Post subject: |
|
|
Newbie
Joined: 25 Apr 2006
Posts: 3
Location: UK
|
It was a really silly schoolboy error.
Basically, we were trying to run as root - no luck. Then we tried as su mqsiuser and still no luck.
However, when we did su - mqsiuser the environment varibales got picked up and it worked.
Obvious when you know the answer(!)  |
|
| Back to top |
|
|
| mrlinux |
| Posted: Thu Apr 27, 2006 6:35 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Thanks for the answer, I know the su vs su - have caught many people even me a couple of times.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
|
|
