| Author |
Message
|
| Gideon |
 Posted: Mon Mar 21, 2011 3:57 pm Post subject: Can not start broker |
 |
|
Chevalier
Joined: 18 Aug 2009
Posts: 403
|
I installed WMB 7.0.0.2 on RHEL 6, which is supported according to this link:
http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27017129
I isntalled under root
Then I switched to mqm via "su mqm"
After installation, I started mqsiprofile with the ". ./mqsiprofile" command,
and I created a broker:
| Code: |
bash-4.1$ ./mqsicreatebroker LQM2 -q LQM2
WebSphere MQ queue manager created.
Directory '/var/mqm/qmgrs/LQM2' created.
Creating or replacing default objects for LQM2.
Default objects statistics : 65 created. 0 replaced. 0 failed.
Completing setup.
Setup completed.
WebSphere MQ queue manager 'LQM2' starting.
5 log records accessed on queue manager 'LQM2' during the log replay phase.
Log replay for queue manager 'LQM2' complete.
Transaction manager state recovered for queue manager 'LQM2'.
WebSphere MQ queue manager 'LQM2' 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. |
This was successful, then I tried to start the broker:
| Code: |
bash-4.1$ ./mqsistart LQM2
BIP8875W: The component verification for 'LQM2' has finished, but one or more checks failed.
One or more of the component verification checks failed.
Check the error log for preceding error messages.
bash-4.1$ pwd
/opt/ibm/mqsi/7.0/bin |
I opened the /var/log/messages file and found the following:
| Code: |
/build/S700_P/src/CommandLine/ImbCmdLib/ImbComponentVerification.cpp: 207: ImbComponentVerification::verify: :
Mar 21 14:00:37 ex5b WebSphere Broker v7002[24623]: (LQM2)[1]BIP8873I: Starting the component verification for component 'LQM2'. : LQM2.mqsistart: /build/S700_P/src/CommandLine/ImbCmdLib/ImbComponentVerification.cpp: 81: ImbComponentVerification::verify: :
Mar 21 14:00:37 ex5b WebSphere Broker v7002[24623]: (LQM2)[1]BIP8893E: Unable to access file '/var/mqsi/LQM2_bipcvp_temp.tmp' with user ID 'mqm'. Additional information for IBM support: open NULL. : LQM2.mqsistart: /build/S700_P/src/CommandLine/ImbCmdLib/ImbEnvironmentVerification.cpp: 1070: ImbEnvironmentVerification::fileIO: :
Mar 21 14:00:37 ex5b WebSphere Broker v7002[24623]: (LQM2)[1]BIP8895E: Verification failed. Environment variable 'MQSI_REGISTRY' is incorrect or missing. : LQM2.mqsistart: /build/S700_P/src/CommandLine/ImbCmdLib/ImbEnvironmentVerification.cpp: 518: ImbEnvironmentVerification::verify: :
Mar 21 14:00:37 ex5b WebSphere Broker v7002[24623]: (LQM2)[1]BIP8907E: Verification failed. Unable to verify Java level. : LQM2.mqsistart: /build/S700_P/src/CommandLine/ImbCmdLib/ImbEnvironmentVerification.cpp: 520: ImbEnvironmentVerification::verify: :
Mar 21 14:00:37 ex5b |
How can I fix this ?
Thanks |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Mon Mar 21, 2011 10:57 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
I'm not sure about the error but I do know that you are doing some things wrong.
Firstly, once you have executed the mqsiprofile, ALL the mqsi commands are in your path (echo $PATH if you don't believe me...)
So you don't need to be in the .../bin directory to issue the commands.
a
| Code: |
mqsistart <brokername>
|
should suffice.
My tip would be to:-
1) edit the .bashrc of the mqm user and include in it
| Code: |
. /opt/ibm/mqsi/7.0/bin/mqsiprofile
|
Then exit from the mqm user and then su to it in the following way.
Note, the '-' is important. Look at the 'man' or 'info' pages on su to find out the difference.
Then try to execute the mqsi commands and report any errors back here.
_________________
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: Tue Mar 22, 2011 3:58 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
davies is right, looks like you forgot to source the mqsi profile before you issued the mqsistart command. I wouldn't use mqm as your service id for broker, try mqbrkrs.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Gideon |
| Posted: Tue Mar 22, 2011 6:17 am Post subject: |
|
|
Chevalier
Joined: 18 Aug 2009
Posts: 403
|
The problem goes away once I chmod 777 the /var/mqsi directory
Has that happened to anyone else before |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Mar 22, 2011 6:26 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Did you follow the install procedure? Did you source the mqsi profile? chmod'ing the files is not the proper resolution.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Mar 22, 2011 6:48 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
From the WebSphere Message Broker Installation Guide v7:
| Quote: |
Security on Linux and UNIX systems. Set up the required security on Linux and UNIX systems before you install WebSphere Message Broker.
1. Log in to the system. On Linux and on other UNIX computers, your user ID must have root authority to complete installation.
2. Create a new security group called mqbrkrs.
3. Add your current logon ID to the group mqbrkrs. |
Did you do this?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Gideon |
| Posted: Tue Mar 22, 2011 3:32 pm Post subject: |
|
|
Chevalier
Joined: 18 Aug 2009
Posts: 403
|
smdavies99
I looked up the su - command in the man pages. It said that was a login in, instead of a simple switch user. Therefore the su - would invoke the .bashrc
So I tried it out and got the following:
| Code: |
[root@ex5b etc]#
[root@ex5b etc]# cd /var/mqm
[root@ex5b mqm]# cat .bashrc
. /opt/ibm/mqsi/7.0/bin/mqsiprofile
[root@ex5b mqm]#
[root@ex5b mqm]# su - mqm
-bash-4.1$
-bash-4.1$ exit
logout
[root@ex5b mqm]# su mqm
MQSI 7.0.0.2
/opt/ibm/mqsi/7.0
bash-4.1$ |
This looks wrong from what I read. The su - command should have invoked the mqsiprofile, not the simple su command by itself. Did I miss something? |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Tue Mar 22, 2011 5:09 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| Gideon wrote: |
| Did I miss something? |
bash attempts to execute commands from different files, depending on whether it's interactive, a login shell, or a non-login shell.
| Quote: |
Interactive login shell:- /etc/profile
- ~/.bash_profile or ~/.bash_login or ~/.profile
- ...
- ~/.bash_logout (upon exit)
Interactive non-login shell: |
Generally, anything that's exportable or only needs to run at login can go in the profile, and anything that's not exportable or needs to run for each shell can go in the bashrc. Consult the bash references or man pages for more details. |
|
| Back to top |
|
|
|
|
