| Author |
Message
|
| Gideon |
 Posted: Wed Mar 16, 2011 1:39 pm Post subject: Install issue |
 |
|
Chevalier
Joined: 18 Aug 2009
Posts: 403
|
I installed WMB 7 on RHEL 6 and get the following 'warning':
| Code: |
Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay [1] 1
Installing IBM WebSphere Message Broker 7.0. Please wait...
|-----------|-----------|-----------|------------|
0% 25% 50% 75% 100%
|||||||||||||||||||||||||||||||||||||||||||||||||
Creating WorkPath...
Warning: UNIXProcess.forkAndExec native error: No such file or directory
Please wait...
-------------------------------------------------------------------------------
The InstallShield Wizard has successfully installed IBM WebSphere Message
Broker 7.0. Choose Finish to exit the wizard.
Press 3 to Finish or 4 to Redisplay [3] |
Is this significant. What is actually happening ?
Thanks |
|
| Back to top |
|
 |
| Gideon |
| Posted: Wed Mar 16, 2011 2:15 pm Post subject: |
|
|
Chevalier
Joined: 18 Aug 2009
Posts: 403
|
I tried to create a broker, and got the following error:
| Code: |
bash-4.1$ pwd
/opt/ibm/mqsi/7.0/bin
bash-4.1$ whoami
mqm
bash-4.1$ . ./mqsiprofile
MQSI 7.0.0.1
/opt/ibm/mqsi/7.0
bash-4.1$ ./mqsicreatebroker LINUXQM -q LINUXQM
(LINUXQM.mqsicreatebroker)[1]BIP2229W: Warning: abend file directory (/var/mqsi/common/errors) open failed: errno 2. Using directory /tmp 0
Failed to open file /var/mqsi/common/log/LINUXQM.mqsicreatebroker.trace.bin.0 with error No such file or directory
Failed to open file /var/mqsi/common/log/LINUXQM.mqsicreatebroker.userTrace.bin.0 with error No such file or directory
BIP8011E: Unable to create the components configuration data.
The command is unable to store the component's configuration data.
Ensure that the userid that is running this command has adequate authority to update the configuration or registry files. Without this authority the registry or configuration files cannot be updated. Also check that the broker name does not contain invalid characters or is too long. |
I have adequite privilege (su mqm), but the directory is not there
| Code: |
bash-4.1$ cd /var/mqsi
bash-4.1$ cd common
bash: cd: common: No such file or directory
bash-4.1$ ls
install.properties |
How can I resolve this ? |
|
| Back to top |
|
|
| Gideon |
| Posted: Wed Mar 16, 2011 2:31 pm Post subject: |
|
|
Chevalier
Joined: 18 Aug 2009
Posts: 403
|
I suspect I have a missiong RHEL package
The MQ isntall is based on RPM and always tells you what package you need.
Any idea what packages are required for WMB |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Mar 16, 2011 2:51 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
More information about what went wrong during install is available in the mqsi7_install.log file that will have been created in the home directory of the user that ran the installer.
The System Requirements page for Broker v7 for Linux should mention explicitly all of the software pre-requirements that you need before install. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Mar 16, 2011 10:33 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
To echo mqjeff's comment
| Quote: |
The System Requirements page for Broker v7 for Linux should mention explicitly all of the software pre-requirements that you need before install.
|
I would expect that as RHEL 6 only came out at the back end of 2010 WMB7.0.0.0 may well not install on RHEL6.
As he states, examining the logs may well help. Please post anything interesting here.
How standard/OOTB is your RHEL Install?
I did have some issues with 7.0.0.1 on Fedora 14. Those were more down to dependency packaging in F14. And before anyone pipes in, I know that Fedora is not a supported platform. As an RHCE and also a Fedora tester I like to you know test these things just to see what breaks. I am sure there is someone in the Hursley Team who is checking all their Websphere products on RHEL6 & the latest SLES/SLED releases.
_________________
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 Mar 17, 2011 6:14 am Post subject: |
|
|
Chevalier
Joined: 18 Aug 2009
Posts: 403
|
|
| Back to top |
|
|
| Gideon |
| Posted: Thu Mar 17, 2011 6:16 am Post subject: |
|
|
Chevalier
Joined: 18 Aug 2009
Posts: 403
|
|
| Back to top |
|
|
| Gideon |
| Posted: Thu Mar 17, 2011 6:22 am Post subject: |
|
|
Chevalier
Joined: 18 Aug 2009
Posts: 403
|
The log is clean, and does not contain any warnings or errors.
The "ForkandExec' showed on the installation display means its trying to start a program that does not exist at that point. The directory was not created or populated, so it can not call the program.
So the 'error' that occurred, happened before this point |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Mar 17, 2011 8:22 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
So despite seeing
| Quote: |
| Warning: UNIXProcess.forkAndExec native error: No such file or directory |
you do not see any repeat or remention of that in the mqsi7_install.log file?
Or is the log "otherwise" clean?
The error from mqsicreatebroker indicates that /var/mqsi/common/error does not appear to exist.
Is that correct? does that directory exist, or not? is it writeable by the user that tried to run mqsicreatebar?
Is the user mqm in the mqbrkrs group? |
|
| Back to top |
|
|
| dbaltazar |
| Posted: Fri Jul 01, 2011 1:00 pm Post subject: Failed to open file /var/mqsi/common/log/LINUXQM.mqsicreateb |
|
|
Newbie
Joined: 09 Mar 2009
Posts: 7
|
About the first error, I receive the same message and resolve creating the folders.
I suggest you create these directories manually (with 777 permissions to be safe for initial testing) as a workaround?:
/var/mqsi/brokers
/var/mqsi/common/log
/var/mqsi/components
/var/mqsi/registry
Best Regards! |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jul 01, 2011 9:11 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Looking at the OP's post, he is trying to do this with user mqm.
I would suggest he first verify that user mqm is part of the xxbrokers group.
(xxbrokers group from memory. Verify documentation for exact name).
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Jul 01, 2011 11:34 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
If you look at the source of the script that creates the /var/mqsi files you will see that it does not use bash as its shell. It uses KSH!
The solution is to install the ksh shell rpm.
This is easily overlooked in an install. This is why we always build broker linux systems using a kickstart file that includes ksh and libXp etc.
If you are building a 64bit version then you may well have to include the 32bit rpm as well (if available, but for libXp it is) because parts of broker (viz eclipse) is a 32bit image not 64bit.
The above is all due to an intensive session of 'I'm going to get to the bottom of this if it kills me' work.
The error message
| Code: |
Warning: UNIXProcess.forkAndExec native error: No such file or directory
|
is due to the missing ksh shell and not due to a missing file in the broker kit.
IMHO, this is a defect in broker. The script could easily be modified to use bash OR the installation docs updated to specifically mention that for this bit of the installation, you MUST have the ksh shell installed.
I hope this explanation helps a few people.
_________________
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 Jul 05, 2011 4:32 am Post subject: Re: Failed to open file /var/mqsi/common/log/LINUXQM.mqsicre |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| dbaltazar wrote: |
About the first error, I receive the same message and resolve creating the folders.
I suggest you create these directories manually (with 777 permissions to be safe for initial testing) as a workaround?:
/var/mqsi/brokers
/var/mqsi/common/log
/var/mqsi/components
/var/mqsi/registry
Best Regards! |
WRONG.
Do not perform any manual steps other than those clearly called out in Chapter six of the installation guide.
The reason Gideon is facing these errors, is he did not follow the steps exactly.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
|
|
