| Author |
Message
|
| akiramoto |
 Posted: Fri Jun 25, 2010 9:52 am Post subject: Can't connect to local broker - MessageBroker 7.0 |
 |
|
Newbie
Joined: 10 May 2005
Posts: 5
|
Hello,
I have an installation of Message Broker 7.0 and MQ 7.0.1.2 on SUSE Linux Enterprise Server 11.
I am using the user wbi, that belongs to groups mqm and mqbrkrs.
I have created a new broker:
wbi@VM-SLES11:~> mqsicreatebroker BROKER -q QMBROKER -i wbi -a password
....
wbi@VM-SLES11:~> mqsistart BROKER
BIP8096I: Successful command initiation, check the system log to ensure that the component started without problem and that it continues to run without problem.
When I issued command mqsilist, the following error occurs:
wbi@VM-SLES11:~> mqsilist BROKER
BIP1046E: Unable to connect with the queue manager (Either the machine does not have an IP address, or no cryptography service is available).
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.
Also, I can connect to Queue Manager QMBROKER using MQ Explorer, but can't connect to broker BROKER using MB Explorer.
What am I doing wrong? Is there any other configuration that I should execute?
Thanks in advance,
Last edited by akiramoto on Fri Jun 25, 2010 12:13 pm; edited 1 time in total |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Jun 25, 2010 10:08 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I thought this was a clear indication?
| Quote: |
| BIP1046E: Unable to connect with the queue manager (Either the machine does not have an IP address, or no cryptography service is available). |
Does this mean that the connection is attempted as a client connection? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| akiramoto |
| Posted: Fri Jun 25, 2010 10:19 am Post subject: |
|
|
Newbie
Joined: 10 May 2005
Posts: 5
|
fjb_saper,
I don't think so, I am at same machine... Just trying to configure a local broker... Is there any other configuration/installation that I missed? Or maybe some security activity that I should do with MQ?
Thanks, |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jun 25, 2010 10:23 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| akiramoto wrote: |
| I don't think so, I am at same machine... |
That doesn't mean you're not using a client connection. Doesn't mean you are, but doesn't preclude it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| akiramoto |
| Posted: Fri Jun 25, 2010 10:32 am Post subject: |
|
|
Newbie
Joined: 10 May 2005
Posts: 5
|
Vitor,
Ok...
What MQ configuration should I look?
Thanks! |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jun 25, 2010 10:48 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Is the user a member of mqm?
Is the user a member of mqbkrs?
Did you enable administrative security on the broker? |
|
| Back to top |
|
|
| akiramoto |
| Posted: Fri Jun 25, 2010 10:51 am Post subject: |
|
|
Newbie
Joined: 10 May 2005
Posts: 5
|
Hi mqjeff,
User is member of both groups:
wbi@VM-SLES11:~> groups
mqm root mqbrkrs
I didn't enabled administrative security, it's the default configuration.
Thanks, |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jun 25, 2010 11:16 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| akiramoto wrote: |
What MQ configuration should I look?
|
Verify that the create broker command didn't throw any errors, and the SYSTEM.BROKER objects exist on the queue manager. Also confirm you can still access the queue manager via MQ Explorer
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| akiramoto |
| Posted: Fri Jun 25, 2010 11:32 am Post subject: |
|
|
Newbie
Joined: 10 May 2005
Posts: 5
|
Hi Vitor,
mqsicreatebroker didn't throw any errors:
...
BIP8071I: Successful command completion.
SYSTEM.BROKER objects were created successfully and I still have access to queue manager QMBROKER using MQ Explorer.
At MB Explorer, it shows that BROKER is active, but when I try to connect to, it shows an error that couldn't connect.
Thanks, |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Fri Jun 25, 2010 12:45 pm Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
|
| Back to top |
|
|
| skunkvasu |
| Posted: Tue Jan 18, 2011 12:41 am Post subject: |
|
|
Newbie
Joined: 18 Jan 2011
Posts: 2
|
| akira , was this resolved? I am facing an issue similar to this |
|
| Back to top |
|
|
| kjloh |
| Posted: Tue Apr 19, 2011 7:15 pm Post subject: |
|
|
Newbie
Joined: 19 Apr 2011
Posts: 3
|
Hi Just wonder if there is any solution or new findings on this. I have encountered this problem as well. and from the syslog, it seems to me message broker process and message flow is running.
the following change was done (which I am not sure if it is relate to this):
(1) update patch to 7002.
(2) change IP address of the host.
thank you very much |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Apr 19, 2011 7:28 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Are you trying to use SSL to connect to the broker?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Apr 19, 2011 9:26 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| Quote: |
.
(2) change IP address of the host.
|
Methinks therein lies the problem. How did you change the IP address? did it involve a subnet change? What is the output of
| Code: |
ifconfig
cat /etc/sysconfig/network-scripts/ifcfg-eth*
cat /etc/resolv.conf
|
Unless you do that properly your TCP/IP stack will not be working very well at all.
Did you reboot after the IP address change? I normaly do this to prove that the IP change has worked.
This is one of the reasons why to use DHCP. This makes handing Addy changes easy. Don't forget you can reserve an IP addy for a MAC Address in most decent DHCP servers. Then faffing around with fixed IP's can be (in many circumstances) a thing of the past.
_________________
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 |
|
|
| kjloh |
| Posted: Tue Apr 19, 2011 10:33 pm Post subject: |
|
|
Newbie
Joined: 19 Apr 2011
Posts: 3
|
Thank you so much for the info.
No there is no SSL.
for that IP change, it is a HACMP change. and yes, I think the subnet mask is modified. Server are rebooted after the change. the QM itself and the HACMP are working fine after the change.
for what I don't understand is how Broker (especially the mqsilist command) affect by this. is it possible to explain how IP change could affect broker? is broker tied to any fixed ip/subnet during broker creation? is there any setting I can set in broker so that i can get mqsilist to work again?
I shall get back those info when I got them. |
|
| Back to top |
|
|
|
|
