| Author |
Message
|
| Gideon |
 Posted: Tue Dec 13, 2011 11:36 am Post subject: Can not start broker |
 |
|
Chevalier
Joined: 18 Aug 2009
Posts: 403
|
I am running WMB 7.0.0.1, but can not fully start my broker
I start by executing mqsiprofile and checking for mqbrkrs
| Code: |
-bash-3.2$ . /opt/ibm/mqsi/7.0/bin/mqsiprofile
MQSI 7.0.0.1
/opt/ibm/mqsi/7.0
-bash-3.2$ whoami
mqm
-bash-3.2$ groups mqm
mqm : mqm mqbrkrs
-bash-3.2$ cat /etc/group | grep mqm
mqm:x:501:
mqbrkrs:x:502:mqm
-bash-3.2$ |
Then I show the qmgrs and brokers that are existing:
| Code: |
-bash-3.2$ dspmq
QMNAME(WQM1) STATUS(Running)
-bash-3.2$ mqsilist
BIP1281I: No brokers have been defined on this machine.
BIP8071I: Successful command completion. |
The I create a new broker:
| Code: |
Tue Dec 13 13:51:51 EST 2011
-bash-3.2$ mqsicreatebroker WQM2 -q WQM2
WebSphere MQ queue manager created.
Directory '/var/mqm/qmgrs/WQM2.000' created.
Creating or replacing default objects for WQM2.
Default objects statistics : 65 created. 0 replaced. 0 failed.
Completing setup.
Setup completed.
WebSphere MQ queue manager 'WQM2' starting.
5 log records accessed on queue manager 'WQM2' during the log replay phase.
Log replay for queue manager 'WQM2' complete.
Transaction manager state recovered for queue manager 'WQM2'.
WebSphere MQ queue manager 'WQM2' started.
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.
The setmqaut command completed successfully.
BIP8071I: Successful command completion. |
Then I try to start the broker:
| Code: |
-bash-3.2$ mqsilist
BIP1285I: Broker 'WQM2' on queue manager 'WQM2' is stopped.
BIP8071I: Successful command completion.
-bash-3.2$ mqsistart WQM2
BIP8096I: Successful command initiation, check the system log to ensure that the component started without problem and that it continues to run without problem.
-bash-3.2$
-bash-3.2$ mqsilist
BIP1285I: Broker 'WQM2' on queue manager 'WQM2' is stopped.
BIP8071I: Successful command completion. |
The I look in /var/log/messages
| Code: |
Dec 13 13:54:18 final03 WebSphere Broker v7001[13266]: (WQM2)[1]BIP8873I: Starting the component verification for component 'WQM2'. : WQM2.mqsistart: /build/S700_P/src/CommandLine/ImbCmdLib/ImbComponentVerification.cpp: 81: ImbComponentVerification::verify: :
Dec 13 13:54:18 final03 WebSphere Broker v7001[13320]: (WQM2)[1]BIP2001I: The WebSphere Message Broker service has started at version 7001; process ID 13325. : WQM2.service: /build/S700_P/src/AdminAgent/ControlProcess/Linux/ImbControlService.cpp: 354: ImbControlService::StartNewAA: :
Dec 13 13:54:18 final03 WebSphere Broker v7001[13325]: (WQM2)[1]BIP2866I: WebSphere Message Broker administration security is inactive. : WQM2.agent: /build/S700_P/src/AdminAgent/ImbDeployManagerSecurityManager.cpp: 103: ImbDeployManagerSecurityManager::ImbDeployManagerSecurityManager: :
Dec 13 13:54:18 final03 WebSphere Broker v7001[13325]: (WQM2)[3]BIP2121E: The thread bootstrap code caught an unhandled exception on thread '4'. : WQM2.agent: /build/S700_P/src/CommonServices/Linux/ImbOsThread.cpp: 274: ImbOsThread::threadBootStrap: :
Dec 13 13:54:18 final03 WebSphere Broker v7001[13325]: (WQM2)[4]BIP2121E: The thread bootstrap code caught an unhandled exception on thread '4'. : WQM2.agent: /build/S700_P/src/CommonServices/Linux/ImbOsThread.cpp: 274: ImbOsThread::threadBootStrap: :
Dec 13 13:54:18 final03 WebSphere Broker v7001[13325]: (WQM2)[3]BIP2178E: Failed to create a UUID (Error code = '1'). : WQM2.agent: /build/S700_P/src/CommonServices/Unix/ImbUuid.cpp: 480: ImbUuid::ImbUuid: :
Dec 13 13:54:18 final03 WebSphere Broker v7001[13325]: (WQM2)[4]BIP2178E: Failed to create a UUID (Error code = '1'). : WQM2.agent: /build/S700_P/src/CommonServices/Unix/ImbUuid.cpp: 480: ImbUuid::ImbUuid: :
Dec 13 13:54:18 final03 WebSphere Broker v7001[13325]: (WQM2)[16]BIP2121E: The thread bootstrap code caught an unhandled exception on thread '16'. : WQM2.agent: /build/S700_P/src/CommonServices/Linux/ImbOsThread.cpp: 274: ImbOsThread::threadBootStrap: :
Dec 13 13:54:18 final03 WebSphere Broker v7001[13325]: (WQM2)[16]BIP2178E: Failed to create a UUID (Error code = '1'). : WQM2.agent: /build/S700_P/src/CommonServices/Unix/ImbUuid.cpp: 480: ImbUuid::ImbUuid: : |
Any ideas? |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Dec 13, 2011 11:43 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Code: |
| BIP2178E: Failed to create a UUID (Error code = '1'). |
This is a fairly significant problem, and almost certainly at the root of the issue.
You should verify that you have the product correctly installed - check your mqsi_install logs for any errors.
Then double-check the file ownership on /var/mqsi and the product install directory, and make sure that the broker id has the right permissions. |
|
| Back to top |
|
|
| bloomy |
| Posted: Thu Dec 15, 2011 12:43 pm Post subject: |
|
|
Acolyte
Joined: 11 Feb 2009
Posts: 61
Location: Bloomington, IL USA
|
@Gideon
What did you find out on this, were you able to resolve it. If you are still seeing the issue, can you check if there are abend files in /var/mqsi/common/errors. If there are any abend files, what do you see as the failure reason in them? |
|
| Back to top |
|
|
| anhnt |
| Posted: Sat Dec 17, 2011 12:45 am Post subject: |
|
|
Acolyte
Joined: 03 Aug 2003
Posts: 54
|
Hi Gideon,
You try to add a entry(your ip,your hostname) into /etc/hosts following:
example: 192.168.1.2 mbhost
anhnt |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sat Dec 17, 2011 3:13 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| Quote: |
You try to add a entry(your ip,your hostname) into /etc/hosts following:
example: 192.168.1.2 mbhost |
What is your reasoning behing this suggestion?
_________________
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 |
|
|
| mqjeff |
| Posted: Sat Dec 17, 2011 6:35 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| smdavies99 wrote: |
| Quote: |
You try to add a entry(your ip,your hostname) into /etc/hosts following:
example: 192.168.1.2 mbhost |
What is your reasoning behing this suggestion? |
Failure to create a UUID is a very low level, fundamental issue that is almost certainly an installation problem or a badly mangled file system problem of some kind.
If modification to /etc/hosts had any impact on this, I would be significantly surprised. I can see it having some slight affect, if it was the network stack that was significantly mangled or overly-administered. but it's not the first place to look by a long shot. |
|
| Back to top |
|
|
| ranieri.mazili |
| Posted: Sat Feb 04, 2012 7:17 am Post subject: Strange, but works |
|
|
Newbie
Joined: 04 Feb 2012
Posts: 1
|
Just to let you know, I was facing the same problem as Gideon, and after modify my /etc/hosts files as described by anhnt, it started to work.
I know that it's very very very strange, but works...
I was facing this problem using RHEL 6 + WebSphere Message Broker V8.
What I think... Message Broker uses the hostname and some TCP connection to create the user or something that it was trying, as the hostname was not configured at /etc/hosts, it couldn't find where to connect, as consequence, it couldn't create the "user".
P.S: The biggest part of people usually don't perform this step, because in RHEL installation, you can setup you network settings, so it configures /etc/hosts for you automacally. If you let to setup network in another time, your /etc/hosts needs to be configured manually. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Feb 04, 2012 7:46 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
following some other posts I would think that you should give these events a chance:
- delete the broker using mqm and the -w flag (remove files)
- create a new userid (brksvcid?) in the mqbrkrs group (primary) and mqm group(secondary)
- use brksvcid to create the a new broker (should have all files with the right permissions)
- use brksvcid to start the broker. Verify broker is running fine.
- use brksvcid to stop the broker.
- try and start the broker with mqm. Verify whether it worked or not.
- let us know the results
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kirankatthula |
| Posted: Tue May 21, 2013 5:03 am Post subject: Issue resolved |
|
|
Novice
Joined: 16 Oct 2012
Posts: 10
|
| I got the same issue but by adding ip and hostname in /etc/hosts resolved my issue |
|
| Back to top |
|
|
|
|
