Author |
Message
|
nadk |
Posted: Mon Feb 04, 2008 10:51 pm Post subject: plz HELP! ERROR IN INSTLTN: AMQ7153: A license could not... |
|
|
Novice
Joined: 04 Feb 2008 Posts: 11
|
After installing WAS (having MQ 5.3) on hpux machine, when i start the server i receive an error in SystemOut.log:
QueueManagerM E MSGS0101E: Start Queue Manager command failed with exit code: 16
d72200 JMSService E MSGS0001E: Starting the JMS Server failed with exception: java.lang.Exception: MSGS0101E: Start Queue Manager command failed with exit code: 16
at com- ibm-ws- messaging-QueueManagerManager-startQueueManager(QueueManagerManager.java:394)
--------------------------------------------------------------------------------------
When i checked createMQ.hostName_server1.log , i found out:
AMQ7153: A license could not be installed for this copy of WebSphere MQ.
rc=71
Issuing: env strmqm -od port=0,ExitReason=16 WAS_hostName_server1
AMQ8118: WebSphere MQ queue manager does not exist.
rc=16
---------------------------------------------------------------------------------
This is definitely a machine problem as it succeeds on another hpux machine but not on this one. Plz help! |
|
Back to top |
|
 |
Vitor |
Posted: Tue Feb 05, 2008 2:18 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Are you sure there's a license on the failing machine? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
nadk |
Posted: Tue Feb 05, 2008 2:29 am Post subject: |
|
|
Novice
Joined: 04 Feb 2008 Posts: 11
|
hi vitor,
thnx a lot 4 replying.I cant see any licenses dir. I checked mq_install.log and found:
AMQ8101: WebSphere MQ error (0) has occurred.
wmsetup: 04Feb08 00:37:45 ... RC 71 from setmqcap
Ok here are d facts which i think are important. please lemme know what u think about the problem (sorry am a newbie to this):
-There is no "amqcap.inf" in /var/mqm/qmgrs/@SYSTEM
- When i run "setmqcap 2(say)", error comes as
AMQ8101: WebSphere MQ error (0) has occurred.
Please convey your thoughts asap |
|
Back to top |
|
 |
Vitor |
Posted: Tue Feb 05, 2008 2:43 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
AFAIK AMQ8101 is when the error can't be identified or the message catalog can't be found.
You say you installed WAS on a machine with MQv5.3 on it - was it a pre-existing MQ or did you install it at the same time as WAS?
It still sounds a lot like the license wasn't installed because the machine wasn't set up properly. Which is of course hopelessly wrong if it was a pre-existing, previously working MQ install! _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
nadk |
Posted: Tue Feb 05, 2008 2:54 am Post subject: |
|
|
Novice
Joined: 04 Feb 2008 Posts: 11
|
No i installed fresh WAS alongwith MQ v5.3 at the same time. This worked on another hpux machine but not working with this. Can you please explain what you mean by:
"It still sounds a lot like the license wasn't installed because the machine wasn't set up properly." |
|
Back to top |
|
 |
Philip Morten |
Posted: Tue Feb 05, 2008 2:57 am Post subject: |
|
|
Master
Joined: 07 Mar 2002 Posts: 230 Location: Hursley Park
|
Return code 71 from setmqcap is usually because /var is full or not writeable _________________ Philip Morten
The postings on this site are my own and do not necessarily represent IBM's positions, strategies or opinions. |
|
Back to top |
|
 |
nadk |
Posted: Tue Feb 05, 2008 3:01 am Post subject: |
|
|
Novice
Joined: 04 Feb 2008 Posts: 11
|
i checked and found that /var:
:dr-xr-xr-x
:1170040 Kb free.
Memory is enough,do u think it should be writable? |
|
Back to top |
|
 |
nadk |
Posted: Tue Feb 05, 2008 3:03 am Post subject: |
|
|
Novice
Joined: 04 Feb 2008 Posts: 11
|
No i checked on the other machine where the installation worked and /var's permissions are same dr-xr-xr-x. So this isnt the problem i guess |
|
Back to top |
|
 |
Vitor |
Posted: Tue Feb 05, 2008 3:04 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Philip Morten wrote: |
Return code 71 from setmqcap is usually because /var is full or not writeable |
nadk wrote: |
i checked and found that /var:
:dr-xr-xr-x
|
 _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Philip Morten |
Posted: Tue Feb 05, 2008 3:08 am Post subject: |
|
|
Master
Joined: 07 Mar 2002 Posts: 230 Location: Hursley Park
|
Is root in group mqm ? _________________ Philip Morten
The postings on this site are my own and do not necessarily represent IBM's positions, strategies or opinions. |
|
Back to top |
|
 |
nadk |
Posted: Tue Feb 05, 2008 3:11 am Post subject: |
|
|
Novice
Joined: 04 Feb 2008 Posts: 11
|
yes, mqm: : 102: mqm,root |
|
Back to top |
|
 |
Philip Morten |
Posted: Tue Feb 05, 2008 3:14 am Post subject: |
|
|
Master
Joined: 07 Mar 2002 Posts: 230 Location: Hursley Park
|
can you, as root, run setmqcap manually
/opt/mqm/bin setmqcap -1
echo $? _________________ Philip Morten
The postings on this site are my own and do not necessarily represent IBM's positions, strategies or opinions. |
|
Back to top |
|
 |
nadk |
Posted: Tue Feb 05, 2008 3:19 am Post subject: |
|
|
Novice
Joined: 04 Feb 2008 Posts: 11
|
On
-/opt/mqm/bin setmqcap -1
AMQ8101: WebSphere MQ error (0) has occurred.
-echo $?
71 |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Feb 05, 2008 4:29 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
The permission set "r-xr-xr-x" means that /var is not writeable. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Feb 05, 2008 11:53 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
jefflowrey wrote: |
The permission set "r-xr-xr-x" means that /var is not writeable. |
To the extent of appearing obtuse I suggest that we make sure that on installation he did not specify a different file system than the default /var/mqm for the mq data files...
and if that was not the case then /var/mqm will definitely need to be drwxrwxr-x and usually owned by mqm:mqm
 _________________ MQ & Broker admin |
|
Back to top |
|
 |
|