| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Successful install, but can not create broker |
« View previous topic :: View next topic » |
| Author |
Message
|
| Gideon |
 Posted: Wed Jan 04, 2012 12:18 pm Post subject: Successful install, but can not create broker |
 |
|
Chevalier
Joined: 18 Aug 2009
Posts: 403
|
I installed WMB 7.0.0.0 on Linux THEL 5.6
The permissions were set properly:
| Code: |
[root@final03 log]# groups mqm
mqm : mqm mqbrkrs
[root@final03 log]# id mqm
uid=101(mqm) gid=501(mqm) groups=501(mqm),502(mqbrkrs) |
I installed WMB
The following is the otp of my mqsi7_install.log file (located in /root)
| Code: |
(Jan 4, 2012 1:49:43 PM), mqsi.Setup, com.ibm.wizard.platform.linux.LinuxRegistryServiceImpl, dbg.registry, reading VPD from /root/vpd.properties
(Jan 4, 2012 1:49:43 PM), mqsi.Setup, com.ibm.ismp.beans.wizard.actions.WriteToLogWizardAction, dbg, BIP8621: Install of IBM WebSphere Message Broker 7.0 has started
(Jan 4, 2012 1:50:53 PM), mqsi.Setup, com.ibm.ismp.beans.wizard.conditions.UserGroupExistenceWizardBeanCondition, dbg, System OS Name: Linux
(Jan 4, 2012 1:50:53 PM), mqsi.Setup, com.ibm.ismp.beans.wizard.conditions.UserGroupExistenceWizardBeanCondition, dbg, Temporary file created: /tmp/ismp001/2433602.tmp
(Jan 4, 2012 1:50:53 PM), mqsi.Setup, com.ibm.ismp.beans.wizard.conditions.UserGroupExistenceWizardBeanCondition, dbg, Group set to mqbrkrs.
(Jan 4, 2012 1:50:53 PM), mqsi.Setup, com.ibm.ismp.beans.wizard.conditions.UserGroupExistenceWizardBeanCondition, dbg, Group checking complete. OK now equals: true
(Jan 4, 2012 1:50:53 PM), mqsi.Setup, com.ibm.ismp.beans.wizard.conditions.UserGroupExistenceWizardBeanCondition, dbg, Returning from evaluateTrueCondition() with: true
(Jan 4, 2012 1:50:53 PM), mqsi.Setup, com.ibm.ismp.beans.wizard.conditions.UserGroupExistenceWizardBeanCondition, dbg, System OS Name: Linux
(Jan 4, 2012 1:50:53 PM), mqsi.Setup, com.ibm.ismp.beans.wizard.conditions.UserGroupExistenceWizardBeanCondition, dbg, Temporary file created: /tmp/ismp001/4835747.tmp
(Jan 4, 2012 1:50:53 PM), mqsi.Setup, com.ibm.ismp.beans.wizard.conditions.UserGroupExistenceWizardBeanCondition, dbg, Owner set to mqm.
(Jan 4, 2012 1:50:53 PM), mqsi.Setup, com.ibm.ismp.beans.wizard.conditions.UserGroupExistenceWizardBeanCondition, dbg, Group checking complete. OK now equals: true
(Jan 4, 2012 1:50:53 PM), mqsi.Setup, com.ibm.ismp.beans.wizard.conditions.UserGroupExistenceWizardBeanCondition, dbg, Returning from evaluateTrueCondition() with: true
(Jan 4, 2012 1:50:53 PM), mqsi.Setup, com.ibm.ismp.beans.wizard.conditions.UserGroupExistenceWizardBeanCondition, dbg, System OS Name: Linux
(Jan 4, 2012 1:50:53 PM), mqsi.Setup, com.ibm.ismp.beans.wizard.conditions.UserGroupExistenceWizardBeanCondition, dbg, Temporary file created: /tmp/ismp001/4903933.tmp |
The following is the end of my mqsi7_install.log file:
| Code: |
(Jan 4, 2012 1:52:38 PM), mqsi.Setup, com.ibm.ismp.beans.wizard.conditions.WizardActionSuccessfulWizardBeanCondition, dbg, (Install status = 3)
(Jan 4, 2012 1:52:38 PM), mqsi.Setup, com.installshield.wizardx.conditions.PlatformWizardBeanCondition, dbg.platform, target platform: name="Linux" version="2.6.18-238.el5" arch="x86"
(Jan 4, 2012 1:52:38 PM), mqsi.Setup, com.installshield.wizardx.conditions.PlatformWizardBeanCondition, dbg.platform, condition platform: name="Windows .*" version="." arch="."
(Jan 4, 2012 1:52:38 PM), mqsi.Setup, com.installshield.wizardx.conditions.PlatformWizardBeanCondition, dbg.platform, target platform: name="Linux" version="2.6.18-238.el5" arch="x86"
(Jan 4, 2012 1:52:38 PM), mqsi.Setup, com.installshield.wizardx.conditions.PlatformWizardBeanCondition, dbg.platform, condition platform: name="Windows .*" version="." arch="."
(Jan 4, 2012 1:52:39 PM), mqsi.Setup, com.installshield.wizardx.conditions.PlatformWizardBeanCondition, dbg.platform, target platform: name="Linux" version="2.6.18-238.el5" arch="x86"
(Jan 4, 2012 1:52:39 PM), mqsi.Setup, com.installshield.wizardx.conditions.PlatformWizardBeanCondition, dbg.platform, condition platform: name="Windows .*" version="." arch="."
(Jan 4, 2012 1:52:39 PM), mqsi.Setup, com.ibm.ismp.beans.wizard.actions.WriteToLogWizardAction, dbg, BIP8622: Install of IBM WebSphere Message Broker 7.0 has finished successfully |
(What does install status of 3 mean ????)
Below is the creation of the Broker:
(mqsiprofile contains in .profile of /var/mqm)
| Code: |
[root@final03 tmp]# su - mqm
MQSI 7.0.0.0
/opt/ibm/mqsi/7.0
-bash-3.2$ mqsicreatebroker WQM8 -q WQM8
WebSphere MQ queue manager created.
Directory '/var/mqm/qmgrs/WQM8' created.
Creating or replacing default objects for WQM8.
Default objects statistics : 65 created. 0 replaced. 0 failed.
Completing setup.
Setup completed.
WebSphere MQ queue manager 'WQM8' starting.
5 log records accessed on queue manager 'WQM8' during the log replay phase.
Log replay for queue manager 'WQM8' complete.
Transaction manager state recovered for queue manager 'WQM8'.
WebSphere MQ queue manager 'WQM8' 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.
BIP8071I: Successful command completion.
-bash-3.2$
-bash-3.2$
-bash-3.2$ mqsistart WQM8
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$ mqsilist
BIP1285I: Broker 'WQM8' on queue manager 'WQM8' is stopped.
BIP8071I: Successful command completion.
|
As you can see, the broker does not start
The /var/log/messages file contained the following:
| Code: |
Jan 4 14:56:31 final03 WebSphere Broker v7000[26263]: (WQM8)[15]BIP2111E: Message broker internal error: diagnostic information 'ImbUuid::ImbUuid() reported 'Failed to create a UUID' with values... '1''. : WQM8.agent: /build/S000_P/src/AdminAgent/ImbDeployManagerCacheRefreshThread.cpp: 198: ImbDeployManagerCacheRefreshThread::run: :
Jan 4 14:57:33 final03 WebSphere Broker v7000[26263]: (WQM8)[15]BIP2111E: Message broker internal error: diagnostic information 'ImbUuid::ImbUuid() reported 'Failed to create a UUID' with values... '1''. : WQM8.agent: /build/S000_P/src/AdminAgent/ImbDeployManagerCacheRefreshThread.cpp: 198: ImbDeployManagerCacheRefreshThread::run: :
Jan 4 14:58:35 final03 WebSphere Broker v7000[26263]: (WQM8)[15]BIP2111E: Message broker internal error: diagnostic information 'ImbUuid::ImbUuid() reported 'Failed to create a UUID' with values... '1''. : WQM8.agent: /build/S000_P/src/AdminAgent/ImbDeployManagerCacheRefreshThread.cpp: 198: ImbDeployManagerCacheRefreshThread::run: :
Jan 4 14:59:37 final03 WebSphere Broker v7000[26263]: (WQM8)[15]BIP2111E: Message broker internal error: diagnostic information 'ImbUuid::ImbUuid() reported 'Failed to create a UUID' with values... '1''. : WQM8.agent: /build/S000_P/src/AdminAgent/ImbDeployManagerCacheRefreshThread.cpp: 198: ImbDeployManagerCacheRefreshThread::run: : |
Any idea of what I should do next (This is the second time I installed, I reinstalled the OS and isntalled again, but I get the same results, and I have performed this isntallation with these OS and software versions many times before. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Wed Jan 04, 2012 12:42 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Failed to create a UUID is a fundamental install or OS configuration issue.
You either need to review the entire OS package set compared to a known, working one, and then review all of the file permissions on the installed files against a new one.... and then review the user rights of the user executing the mqsi commands...
Or open a PMR. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Jan 04, 2012 1:13 pm Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Jan 04, 2012 1:34 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
A few points
1) Why are you not following SOP and using a dedicated user to run the broker under. Do not use 'mqm' There are many posts here describing the very situation you are in.
2) Why didn't you patch the installation to say 7.0.0.3? This will be the 1st thing IBM will reccommend you do if you raise a PMR. (Actually I'm surprised that mqjeff didn't suggest it. He normally does...  ).
_________________
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: Thu Jan 05, 2012 8:37 am Post subject: |
|
|
Chevalier
Joined: 18 Aug 2009
Posts: 403
|
lancelotlinc:
I re-read Captuer 6, and I wrote a summery below:
| Code: |
Chpter 6 Preparing the system
- Checking the Kernal configuration (p 48)
(Basically says there are no config settings for WMB, but there are for WMQ
My MQ is working perfectly, its my WMB that is having a problem with the UUID,
but I tried these sysctl settings anyway, but the system did not change
- Check Security settings on Linux (p 40)
- Log in as root
- Create the group mqbrkrs
- INstall WMQ
- Add the login id to mqbrkrs |
I still cant quite seem to find the problem, which part of Chapter 6 were you referring to ?
Thanks |
|
| Back to top |
|
|
| Gideon |
| Posted: Thu Jan 05, 2012 8:41 am Post subject: |
|
|
Chevalier
Joined: 18 Aug 2009
Posts: 403
|
mqjeff:
I have a know working WMB of the same level on another machine, and am about to review the file permissions.
Are there any directories and files I should pay close attention to ?
Thanks |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Jan 05, 2012 9:00 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
I refer the honorable Gentlemen to a post I made earlier
| smdavies99 wrote: |
A few points
1) Why are you not following SOP and using a dedicated user to run the broker under. Do not use 'mqm' There are many posts here describing the very situation you are in.
|
Plus what is the primary Group of the user who is going to be running broker?
Will this interfere with the proper operation of the underlying product?
Look at the difference beteeen the -G and -g options to the 'useradd' command.
| Code: |
-g, --gid GROUP force use GROUP for the new user account
-G, --groups GROUPS list of supplementary groups for the new
user account
|
for example
| Code: |
useradd -g mqbrkrs -G mqm brokeradmin
|
then later
| Code: |
mqsicreagebroker MYBROKER -q FRED -u brokeradmin
(or thereabouts)
|
Please refer to the numerous posts in this forum that cover the very problem you are experiencing.
_________________
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 |
|
|
| lancelotlinc |
| Posted: Thu Jan 05, 2012 9:07 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
1. What is the name of the service Id you are using to start broker with?
2. What is the Primary Group this Id belongs to?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Gideon |
| Posted: Thu Jan 05, 2012 1:35 pm Post subject: |
|
|
Chevalier
Joined: 18 Aug 2009
Posts: 403
|
On the machine that works, I use mqm as the primary
| Code: |
[root@HX5-3 ~]# su - mqm
MQSI 7.0.0.1
/opt/ibm/mqsi/7.0
-bash-3.2$ whoami
mqm
-bash-3.2$ id mqm
uid=101(mqm) gid=501(mqm) groups=501(mqm),502(mqbrkrs)
-bash-3.2$
-bash-3.2$ mqsicreatebroker WQM5 -q WQM5 -i mqm -t
WebSphere MQ queue manager created.
Directory '/var/mqm/qmgrs/WQM5' created.
Creating or replacing default objects for WQM5.
Default objects statistics : 65 created. 0 replaced. 0 failed.
Completing setup.
Setup completed.
WebSphere MQ queue manager 'WQM5' starting.
5 log records accessed on queue manager 'WQM5' during the log replay phase.
Log replay for queue manager 'WQM5' complete.
Transaction manager state recovered for queue manager 'WQM5'.
WebSphere MQ queue manager 'WQM5' 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.
-bash-3.2$
-bash-3.2$ mqsistart WQM5
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$ mqsilist
BIP1284I: Broker 'WQM5' on queue manager 'WQM5' is running.
BIP1284I: Broker 'WQM4' on queue manager 'WQM4' is running. |
|
|
| Back to top |
|
|
| Gideon |
| Posted: Thu Jan 05, 2012 1:36 pm Post subject: |
|
|
Chevalier
Joined: 18 Aug 2009
Posts: 403
|
On the machine that does not work, I have tried using both mqm and mqbrkrs, example:
| Code: |
-bash-3.2$ whoami
mqm
-bash-3.2$ id mqm
uid=101(mqm) gid=502(mqbrkrs) groups=502(mqbrkrs),501(mqm)
-bash-3.2$
-bash-3.2$ mqsicreatebroker WQM4 -q WQM4 -i mqm -t
WebSphere MQ queue manager created.
Directory '/var/mqm/qmgrs/WQM4' created.
Creating or replacing default objects for WQM4.
Default objects statistics : 65 created. 0 replaced. 0 failed.
Completing setup.
Setup completed.
WebSphere MQ queue manager 'WQM4' starting.
5 log records accessed on queue manager 'WQM4' during the log replay phase.
Log replay for queue manager 'WQM4' complete.
Transaction manager state recovered for queue manager 'WQM4'.
WebSphere MQ queue manager 'WQM4' 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.
-bash-3.2$
-bash-3.2$ mqsistart WQM4
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$ mqsilist
BIP1285I: Broker 'WQM1' on queue manager 'WQM1' is stopped.
BIP1285I: Broker 'WQM4' on queue manager 'WQM4' is stopped.
BIP1285I: Broker 'WQM2' on queue manager 'WQM2' is stopped.
BIP8071I: Successful command completion. |
|
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Jan 05, 2012 1:43 pm Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| Gideon wrote: |
On the machine that works, I use mqm as the primary
| Code: |
[root@HX5-3 ~]# su - mqm
MQSI 7.0.0.1
/opt/ibm/mqsi/7.0
-bash-3.2$ whoami
mqm
-bash-3.2$ id mqm
uid=101(mqm) gid=501(mqm) groups=501(mqm),502(mqbrkrs)
-bash-3.2$
-bash-3.2$ mqsicreatebroker WQM5 -q WQM5 -i mqm -t
WebSphere MQ queue manager created.
Directory '/var/mqm/qmgrs/WQM5' created.
Creating or replacing default objects for WQM5.
Default objects statistics : 65 created. 0 replaced. 0 failed.
Completing setup.
Setup completed.
WebSphere MQ queue manager 'WQM5' starting.
5 log records accessed on queue manager 'WQM5' during the log replay phase.
Log replay for queue manager 'WQM5' complete.
Transaction manager state recovered for queue manager 'WQM5'.
WebSphere MQ queue manager 'WQM5' 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.
-bash-3.2$
-bash-3.2$ mqsistart WQM5
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$ mqsilist
BIP1284I: Broker 'WQM5' on queue manager 'WQM5' is running.
BIP1284I: Broker 'WQM4' on queue manager 'WQM4' is running. |
|
This is incorrect. mqm should not be used as the service Id.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Jan 05, 2012 1:45 pm Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| Gideon wrote: |
On the machine that does not work, I have tried using both mqm and mqbrkrs, example:
| Code: |
-bash-3.2$ whoami
mqm
-bash-3.2$ id mqm
uid=101(mqm) gid=502(mqbrkrs) groups=502(mqbrkrs),501(mqm)
-bash-3.2$
-bash-3.2$ mqsicreatebroker WQM4 -q WQM4 -i mqm -t
WebSphere MQ queue manager created.
Directory '/var/mqm/qmgrs/WQM4' created.
Creating or replacing default objects for WQM4.
Default objects statistics : 65 created. 0 replaced. 0 failed.
Completing setup.
Setup completed.
WebSphere MQ queue manager 'WQM4' starting.
5 log records accessed on queue manager 'WQM4' during the log replay phase.
Log replay for queue manager 'WQM4' complete.
Transaction manager state recovered for queue manager 'WQM4'.
WebSphere MQ queue manager 'WQM4' 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.
-bash-3.2$
-bash-3.2$ mqsistart WQM4
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$ mqsilist
BIP1285I: Broker 'WQM1' on queue manager 'WQM1' is stopped.
BIP1285I: Broker 'WQM4' on queue manager 'WQM4' is stopped.
BIP1285I: Broker 'WQM2' on queue manager 'WQM2' is stopped.
BIP8071I: Successful command completion. |
|
What is the primary group for mqbrkrs.
When you mqsistart your broker, did you first sudo - mqbrkrs ?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Gideon |
| Posted: Thu Jan 05, 2012 2:37 pm Post subject: |
|
|
Chevalier
Joined: 18 Aug 2009
Posts: 403
|
I took everyones suggestion, and created a brokeradmin account (that I was not using previously)
The Primary Group for that brokeradmin is 'mqbrkrs'
Here is what happened:
| Code: |
[root@final03 ~]# id brokeradmin
uid=501(brokeradmin) gid=502(mqbrkrs) groups=502(mqbrkrs),501(mqm)
[root@final03 ~]#
[root@final03 ~]# su - brokeradmin
[brokeradmin@final03 ~]$
[brokeradmin@final03 ~]$ . /opt/ibm/mqsi/7.0/bin/mqsiprofile
MQSI 7.0.0.1
/opt/ibm/mqsi/7.0
[brokeradmin@final03 ~]$ mqsicreatebroker WQM6 -q WQM6 -i mqm -t
WebSphere MQ queue manager created.
Directory '/var/mqm/qmgrs/WQM6' created.
Creating or replacing default objects for WQM6.
Default objects statistics : 65 created. 0 replaced. 0 failed.
Completing setup.
Setup completed.
WebSphere MQ queue manager 'WQM6' starting.
5 log records accessed on queue manager 'WQM6' during the log replay phase.
Log replay for queue manager 'WQM6' complete.
Transaction manager state recovered for queue manager 'WQM6'.
WebSphere MQ queue manager 'WQM6' 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.
[brokeradmin@final03 ~]$
[brokeradmin@final03 ~]$
[brokeradmin@final03 ~]$ mqsistart WQM6
BIP8096I: Successful command initiation, check the system log to ensure that the component started without problem and that it continues to run without problem.
[brokeradmin@final03 ~]$ mqsilist
BIP1285I: Broker 'WQM1' on queue manager 'WQM1' is stopped.
BIP1285I: Broker 'WQM4' on queue manager 'WQM4' is stopped.
BIP1285I: Broker 'WQM2' on queue manager 'WQM2' is stopped.
BIP1285I: Broker 'WQM6' on queue manager 'WQM6' is stopped.
BIP8071I: Successful command completion.
[brokeradmin@final03 ~]$
|
This should be correct. Any ideas ? |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Jan 05, 2012 10:46 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| Quote: |
[brokeradmin@final03 ~]$ mqsicreatebroker WQM6 -q WQM6 -i mqm -t
|
Why do you persist in using 'mqm' as the account under which broker is going to run?
Please read the numerous posts here (both in this thread and in many other ones) about this issue.
_________________
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 |
|
|
| lancelotlinc |
| Posted: Fri Jan 06, 2012 5:42 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| Gideon wrote: |
I took everyones suggestion, and created a brokeradmin account (that I was not using previously)
The Primary Group for that brokeradmin is 'mqbrkrs'
Here is what happened:
| Code: |
[root@final03 ~]# id brokeradmin
uid=501(brokeradmin) gid=502(mqbrkrs) groups=502(mqbrkrs),501(mqm)
[root@final03 ~]#
[root@final03 ~]# su - brokeradmin
[brokeradmin@final03 ~]$
[brokeradmin@final03 ~]$ . /opt/ibm/mqsi/7.0/bin/mqsiprofile
MQSI 7.0.0.1
/opt/ibm/mqsi/7.0
[brokeradmin@final03 ~]$ mqsicreatebroker WQM6 -q WQM6 -i mqm -t
WebSphere MQ queue manager created.
Directory '/var/mqm/qmgrs/WQM6' created.
Creating or replacing default objects for WQM6.
Default objects statistics : 65 created. 0 replaced. 0 failed.
Completing setup.
Setup completed.
WebSphere MQ queue manager 'WQM6' starting.
5 log records accessed on queue manager 'WQM6' during the log replay phase.
Log replay for queue manager 'WQM6' complete.
Transaction manager state recovered for queue manager 'WQM6'.
WebSphere MQ queue manager 'WQM6' 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.
[brokeradmin@final03 ~]$
[brokeradmin@final03 ~]$
[brokeradmin@final03 ~]$ mqsistart WQM6
BIP8096I: Successful command initiation, check the system log to ensure that the component started without problem and that it continues to run without problem.
[brokeradmin@final03 ~]$ mqsilist
BIP1285I: Broker 'WQM1' on queue manager 'WQM1' is stopped.
BIP1285I: Broker 'WQM4' on queue manager 'WQM4' is stopped.
BIP1285I: Broker 'WQM2' on queue manager 'WQM2' is stopped.
BIP1285I: Broker 'WQM6' on queue manager 'WQM6' is stopped.
BIP8071I: Successful command completion.
[brokeradmin@final03 ~]$
|
This should be correct. Any ideas ? |
This is incorrect. Re-re-re-read Chapter 6 of the install guide.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
|
|
|
  |
Goto page 1, 2 Next |
Page 1 of 2 |
|
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
|
|
|
|
