| Author |
Message
|
| gilberthg |
 Posted: Wed Feb 01, 2012 3:48 pm Post subject: CreateEx Group error if localhost specified |
 |
|
Novice
Joined: 01 Feb 2012
Posts: 14
Location: Costa Rica
|
Hi
I'm new to MQ Message Broker and to the formum. Thank you for being patient ...
I just installed MQ Message Broker ToolKit V 8 , in a redhat linux server
When I try to create an execution group , with mqsicreateexecutiongroup the command does not work when I specify the server's ip, or localhost , or the servername .
If I ommit this ( the -i option ) , the command works well.
The problem is that the Default Configuration wizards fails creating the default execution group ....
I created the default group at the toolkit and works fine too.
Running the samples, for example the Coordinated Request Reply , fails executing with the default 'localhost' at the client application. If I erase localhost, the sample app works fine again.
I do not want to leave the enviroment like this because I'm a newbi and may be some issues I will get will be reationed whit this ip problem...
So theres is some problem with my server configuration but I can not figure out what is it. I have checked network connection, hosts file , security ( group membership to mqm ) ....
My host file looks like this :
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.0.122 linuxggs |
|
| Back to top |
|
 |
| exerk |
| Posted: Thu Feb 02, 2012 1:12 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Moving this to the Broker forum...
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Feb 02, 2012 6:05 am Post subject: Re: CreateEx Group error if localhost specified |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| gilberthg wrote: |
I just installed MQ Message Broker ToolKit V 8 , in a redhat linux server
When I try to create an execution group , with mqsicreateexecutiongroup the command does not work when I specify the server's ip, or localhost , or the servername |
We assume from this you installed the runtime components as well as the Toolkit?
If I ommit this ( the -i option ) , the command works well.
| gilberthg wrote: |
My host file looks like this :
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.0.122 linuxggs |
Are you using IPv4 & IPv6? Have you got all the necessary configurations set up? Is it possible you're feeding an IPv4 address to an IPv6 stack that's not translating it properly?
I agree this sounds like an IP problem rather than a broker one. I'd speak to your sys admins in the first instance & see if they have any ideas.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| gilberthg |
| Posted: Thu Feb 02, 2012 8:29 am Post subject: |
|
|
Novice
Joined: 01 Feb 2012
Posts: 14
Location: Costa Rica
|
Thank you very much.
1- We don't have IPV6 active.
This is my ifconfig's results:
eth0 Link encap:Ethernet HWaddr 00:19:DB:D2:B4:FE
inet addr:192.168.0.122 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::219:dbff:fed2:b4fe/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2121 errors:0 dropped:0 overruns:0 frame:0
TX packets:278 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:221563 (216.3 KiB) TX bytes:73622 (71.8 KiB)
Interrupt:23 Base address:0xa000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:480 (480.0 b) TX bytes:480 (480.0 b)
2- I'm giving you an example of the behavior.
This commands works fine :
mqsicreateexecutiongroup MB8BROKER -e ejemplo4
BIP1124I: Creating execution group 'ejemplo4' on broker 'MB8BROKER'...
BIP1117I: The execution group was created successfully.
The broker has initialized the execution group.
BIP8071I: Successful command completion.
3- This one does not :
"
mqsicreateexecutiongroup -i localhost -p 1414 -q MB8QMGR -e ejemplo5
BIP1044I: Connecting to the queue manager...
BIP1046E: Unable to connect with the queue manager (Could not connect to queue manager 'MB8QMGR' (MQ reason code 2538)).
The utility encountered a problem while attempting to connect to the queue manager to put a message to the broker's request queue.
Ensure that the correct connection parameters have been supplied to the utility. Also ensure that the queue manager is running and that the current user is able to access the queues beginning SYSTEM.BROKER. If this error text includes an MQ reason code, look up the meaning behind the error in the Application Programming Reference guide and proceed as appropriate.
"
Same result wiht 127.0.0.1 ,or the atual IP
3- I'm running the applications locally, I think I will not worry about security issues as if I were working from a real client box .
Thanks again, |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Feb 02, 2012 8:46 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| gilberthg wrote: |
| BIP1046E: Unable to connect with the queue manager (Could not connect to queue manager 'MB8QMGR' (MQ reason code 2538)). |
Are you sure that the queue manager is correctly set up to accept incoming IP connections (running listener, open firewall, etc)?
Research the 2538 error code and follow the suggested actions.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| gilberthg |
| Posted: Thu Feb 02, 2012 9:52 am Post subject: |
|
|
Novice
Joined: 01 Feb 2012
Posts: 14
Location: Costa Rica
|
Hi ,
I think I'm a little confused about wich port the Q Manager really uses, 2414 or 1414 ...
Any way, I check the two ones at the firewall to be open.
The default Q Manager is running the listener at 2414 , so I run the create group with that port and now I get a 2035 error.
I'm sure I have the correct security because I can do anything wiht the toolkit connected with my user.
Here the result :
"
mqsicreateexecutiongroup -i localhost -p 2414 -q MB8QMGR -e ejemplo5
BIP1044I: Connecting to the queue manager...
BIP1046E: Unable to connect with the queue manager (The user 'ggutierrez' is not authorized to connect to queue manager 'MB8QMGR' (MQ reason code 2035 while trying to connect)).
The utility encountered a problem while attempting to connect to the queue manager to put a message to the broker's request queue.
Ensure that the correct connection parameters have been supplied to the utility. Also ensure that the queue manager is running and that the current user is able to access the queues beginning SYSTEM.BROKER. If this error text includes an MQ reason code, look up the meaning behind the error in the Application Programming Reference guide and proceed as appropriate.
"
Kind regards , |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Feb 02, 2012 10:09 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| gilberthg wrote: |
| I think I'm a little confused about wich port the Q Manager really uses, 2414 or 1414 ... |
It uses the one it's been defined to use. 1414 is the WMQ default, 2414 (IIRC) is the one the default broker setup's queue manager uses. You were quoting 1414 in the command hence the 2538.
| gilberthg wrote: |
I run the create group with that port and now I get a 2035 error.
I'm sure I have the correct security because I can do anything wiht the toolkit connected with my user. |
Define "anything". Can you deploy to the default execution group (if created) or any other broker activity, or are you saying that the Toolkit works fine?
Because the Toolkit doesn't use the queue manager & hence doesn't need the security.
| gilberthg wrote: |
| BIP1046E: Unable to connect with the queue manager (The user 'ggutierrez' is not authorized to connect to queue manager 'MB8QMGR' (MQ reason code 2035 while trying to connect)). |
That very much says it all. Connect authority (at least) for that user is perceived to be missing.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| gilberthg |
| Posted: Thu Feb 02, 2012 11:32 am Post subject: |
|
|
Novice
Joined: 01 Feb 2012
Posts: 14
Location: Costa Rica
|
Mmm
I say works fine because I run, for example the "Coordinated Request Reply sample" and it works. Only when I'm sending messages I erase the "localhost" at the dialog box, and it works ( I supose same behavior of the craeteexgroup ) ...
I pretty sure authority is Ok, because I check it out with this command :
dspmqaut -m MB8QMGR -n SYSTEM.DEFAULT.LOCAL.QUEUE -t queue -p ggutierrez
Entity ggutierrez has the following authorizations for object SYSTEM.DEFAULT.LOCAL.QUEUE:
get
browse
put
inq
set
crt
dlt
chg
dsp
passid
passall
setid
setall
clr
And with my user using MQ Explorer I can connect to the Q Manager...
Other ideas? |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Feb 02, 2012 12:03 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| gilberthg wrote: |
| Entity ggutierrez has the following authorizations for object SYSTEM.DEFAULT.LOCAL.QUEUE: |
Don't use the SYSTEM queues for anything. Define yourself a new local queue.
And it's not the authority against that or any other queue that's causing the 2035:
| gilberthg wrote: |
| BIP1046E: Unable to connect with the queue manager (The user 'ggutierrez' is not authorized to connect to queue manager 'MB8QMGR' (MQ reason code 2035 while trying to connect)). |
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| gilberthg |
| Posted: Thu Feb 02, 2012 12:46 pm Post subject: |
|
|
Novice
Joined: 01 Feb 2012
Posts: 14
Location: Costa Rica
|
Thank you for beging patient
I think you want that I check the authority over the Q Manager, right ?
In that case , here it is , and it's ok too :
dspmqaut -m MB8QMGR -t qmgr -p ggutierrez
Entity ggutierrez has the following authorizations for object MB8QMGR:
inq
set
connect
altusr
crt
dlt
chg
dsp
setid
setall
ctrl
system |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Feb 02, 2012 1:03 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| gilberthg wrote: |
| Thank you for beging patient |
You've caught me on a good day. The day is nearly over.
| gilberthg wrote: |
| I think you want that I check the authority over the Q Manager, right ? |
Yes, and this is not a good way:
| gilberthg wrote: |
| dspmqaut -m MB8QMGR -t qmgr -p ggutierrez |
The -p parameter is only good on Windows.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| gilberthg |
| Posted: Fri Feb 03, 2012 9:30 am Post subject: |
|
|
Novice
Joined: 01 Feb 2012
Posts: 14
Location: Costa Rica
|
Thanks again,
Ok, at Unix we only have groups' authorization.
So I checked :
dspmqaut -m MB8QMGR -t qmgr -g mqm
Entity mqm has the following authorizations for object MB8QMGR:
inq
set
connect
altusr
crt
dlt
chg
dsp
setid
setall
ctrl
system
And you can see my user in these groups :
groups ggutierrez
ggutierrez : mqm mqbrkrs
So I can not figure out whats the problem... |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Feb 03, 2012 9:39 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| gilberthg wrote: |
| So I can not figure out whats the problem... |
Clearly the software's broken. Raise a PMR.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Feb 03, 2012 8:27 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Vitor wrote: |
| gilberthg wrote: |
| So I can not figure out whats the problem... |
Clearly the software's broken. Raise a PMR. |
Did you say your qmgr was WMQ 7.0 or WMQ 7.1?
If 7.1 did you set the permissions on the channel to allow mqm? (more than setting mcauser. There is new channel permissions in V 7.1)
Do you have an exit like blockip preventing the use of mqm?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
