| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Problem creating Broker |
« View previous topic :: View next topic » |
| Author |
Message
|
| Gideon |
 Posted: Tue Apr 19, 2011 12:36 pm Post subject: Problem creating Broker |
 |
|
Chevalier
Joined: 18 Aug 2009
Posts: 403
|
I am using RHEL 6 with WMB 7.0.0.2, and have no problem creating brokers.
However, when I create a trusted broker, I get a strange error:
| Code: |
[root@WEST5 mq]# cat /etc/issue
Red Hat Enterprise Linux Server release 6.0 (Santiago)
Kernel \r on an \m
[root@WEST5 mq]#
[root@WEST5 mq]# su mqm
MQSI 7.0.0.2
/opt/ibm/mqsi/7.0
bash-4.1$ dspmqver
Name: WebSphere MQ
Version: 7.0.1.0
CMVC level: p000-L090813
BuildType: IKAP - (Production)
bash-4.1$
bash-4.1$ groups
mqm mqbrkrs
bash-4.1$
bash-4.1$ dspmqver
Name: WebSphere MQ
Version: 7.0.1.0
CMVC level: p000-L090813
BuildType: IKAP - (Production)
bash-4.1$
bash-4.1$ dspmq
QMNAME(WQM1) STATUS(Running)
QMNAME(WQM2) STATUS(Running)
bash-4.1$
bash-4.1$ mqsilist
BIP1284I: Broker 'WQM1' on queue manager 'WQM1' is running.
BIP8071I: Successful command completion.
bash-4.1$
bash-4.1$ mqsicreatebroker WQM2 -q WQM2 -t
BIP8138E: Userid '' cannot be used by this component.
The userId selected cannot be used by the component. This may be because the userId does not have the required authorization or that the userId is invalid for operations that the component requires, for example, if a component is to use fastbind (-t) on UNIX platforms it must use the ServiceUserId 'mqm'.
Check that the user has the required authority to create files and retry.
bash-4.1$
bash-4.1$ mqsicreatebroker WQM3 -q WQM3 -t
BIP8138E: Userid '' cannot be used by this component.
The userId selected cannot be used by the component. This may be because the userId does not have the required authorization or that the userId is invalid for operations that the component requires, for example, if a component is to use fastbind (-t) on UNIX platforms it must use the ServiceUserId 'mqm'.
Check that the user has the required authority to create files and retry.
bash-4.1$ |
This should not be happening, since I am inside of mqm, Mqm is a member of the correct groups. I do not see the issue.
Does anyone see what I am missing ? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Tue Apr 19, 2011 12:52 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Quote: |
Name: WebSphere MQ
Version: 7.0.1.0
|
Try and upgrade to 7.0.1.4
Did you check that mqm is a member of mqbrokers?
Usually it is the other way round...
Also your su is missing a dash
Try
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Apr 19, 2011 9:17 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| Quote: |
| if a component is to use fastbind (-t) on UNIX platforms it must use the ServiceUserId 'mqm'. |
Did you try to specify 'mqm' as the user under which Broker is going to operate?
IMHO this has nowt to do with where you are creating the user.
Would you like to explain what you hope to gain by doing this? I'm interested only because I've used the -t option on Windows but never on Unix/Linux.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| Gideon |
| Posted: Wed Apr 20, 2011 6:44 am Post subject: |
|
|
Chevalier
Joined: 18 Aug 2009
Posts: 403
|
smdavies99
Thanks, setting the user (instead of simply performing a 'switch user', worked well. Kind of odd you have to use the -i for trusted, but do not have to use that for non-trusted
| Code: |
bash-4.1$ mqsicreatebroker WQM2 -q WQM2 -i mqm -t
AMQ8110: WebSphere MQ queue manager already exists.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
BIP8071I: Successful command completion. |
|
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
