ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Start Broker error

Post new topic  Reply to topic
 Start Broker error « View previous topic :: View next topic » 
Author Message
Gideon
PostPosted: Mon Apr 04, 2011 9:46 am    Post subject: Start Broker error Reply with quote

Chevalier

Joined: 18 Aug 2009
Posts: 403

I am using WMB 7.0.0.2 on RHEL 6, which is supported on that platform

I created a broker, no errors reported on the screen, or in the log

I then start the broker, but the log reports errors:

Code:
Apr  4 08:23:15 ex5b WebSphere Broker v7002[4074]: (LQM3)[1]BIP8873I: Starting the component verification for component 'LQM3'. : LQM3.mqsistart: /build/S700_P/src/CommandLine/ImbCmdLib/ImbComponentVerification.cpp: 81: ImbComponentVerification::verify: :
Apr  4 08:23:18 ex5b WebSphere Broker v7002[4189]: (LQM3.service)[1]BIP2228E: Severe error: /build/S700_P/src/CommonServices/Unix/ImbGlobalMutexHelper.cpp 660 opendir Abend file: /var/mqsi/common/errors/LQM3.service.4189.1.abend action: abort
Apr  4 08:23:18 ex5b abrt[4193]: saved core dump of pid 4189 (/opt/ibm/mqsi/7.0/bin/bipservice) to /var/spool/abrt/ccpp-1301919798-4189.new/coredump (1421312 bytes)
Apr  4 08:23:18 ex5b abrtd: Directory 'ccpp-1301919798-4189' creation detected
Apr  4 08:23:18 ex5b abrtd: Registered Database plugin 'SQLite3'
Apr  4 08:23:18 ex5b abrtd: Executable '/opt/ibm/mqsi/7.0/bin/bipservice' doesn't belong to any package
Apr  4 08:23:18 ex5b abrtd: Corrupted or bad crash /var/spool/abrt/ccpp-1301919798-4189 (res:4), deleting


I can not find the core dump specified. the following is the view of the bipservice from /var/ibm/mqsi/7.0/bin:

Code:
-rwxr-xr-x. 1 bin bin 3059212 Dec  6 18:15 bipbroker
-rwxr-xr-x. 1 bin bin  455840 Dec  6 18:14 bipcwfworker.wrk
-rwxr-xr-x. 1 bin bin  476986 Dec  6 18:15 biphttplistener
-rwxr-xr-x. 1 bin bin  331453 Dec  6 18:13 bippdfworker.wrk
-rwxr-xr-x. 1 bin bin  132221 Dec  6 18:15 bipservice
-rwxr-xr-x. 1 bin bin 1574583 Dec  6 18:14 biptdsworker.wrk
-rwxr-xr-x. 1 bin bin  724937 Dec  6 18:13 bipxmlworker.wrk


So it should have execute permission. Any ideas ?
Back to top
View user's profile Send private message Send e-mail
lancelotlinc
PostPosted: Mon Apr 04, 2011 9:55 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

When you installed Broker, did you follow the required security steps? Such as creating mqbrkrs group, running the Broker from mqbrkrs user, and sourcing the mqsi profile?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
smdavies99
PostPosted: Mon Apr 04, 2011 10:59 am    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

Is this a new installation? i.e. has broker been run on this system before?

IF you, are you sure that the install completed cottectly?
At the end of the install, the installer creates the uninstaller THEN it creates the workpath.
I've seen some examples of a broker install apparently working but the workpat is not created.
You can verify this by seeing if all the requisite directories are present in /var/mqsi
If they are missing then the mqsicreateworkpath will do the job for you.

RHEL 6 has changed whole lot in how things are packaged. You have to add a number of 'not in the installer selections' (Especially on 64bit which I see that you are running) to get 1) WMQ to install 2) strmqfg to run without error & 3) broker to install properly by creating the workpath files & directories at the end of the install operation. I have a sample kickstart file that seems to work on RHEL 6. (I'm a RHCE....)
I know what the missing packages for these issues are. However moving to Scientific Linux and installing the same things still causes problems.
The Broker installer is written in Java but nothing appears in the logs to indicate what is missing.

Naturally, I could be barking mad...
_________________
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
View user's profile Send private message
Gideon
PostPosted: Mon Apr 04, 2011 12:22 pm    Post subject: Reply with quote

Chevalier

Joined: 18 Aug 2009
Posts: 403

smdavies99:

Yes, I created the mqbrkrs group, and added the group to mqm (from which I am running the mqsi commands), and I sourced the mqsiprofile command

smdavies99:

This is a new install on a clean system.

After the install was completed, the following files were not created, so I created them manually, and then performed a chmod 777 on them:

Code:
       /var/mqsi/brokers
       /var/mqsi/common
       /var/mqsi/common/log
       /var/mqsi/components
       /var/mqsi/registry


Then I had to perofmr a chmod 777 on the already existing file

Code:
   /var/mqsi


I just perofrmed the following:

Code:
bash-4.1$ echo $MQSI_WORKPATH
/var/mqsi
bash-4.1$ cd /var/mqsi
bash-4.1$ ls
brokers  common  components  install.properties  registry
bash-4.1$ ls -la
total 28
drwxrwxrwx.  6 root root 4096 Apr  4 08:33 .
drwxr-xr-x. 24 root root 4096 Mar 23 06:18 ..
drwxrwxrwx.  2 root root 4096 Mar 23 08:39 brokers
drwxrwxrwx.  4 root root 4096 Mar 23 08:58 common
drwxrwxrwx.  7 root root 4096 Apr  4 08:33 components
-rw-r--r--.  1 root root   26 Mar 23 08:29 install.properties
drwxrwxrwx.  7 root root 4096 Apr  4 08:33 registry


So I have a workpath created, however, this appears to be the issue you are referring to.

So should I actually create another workpath on top of the one I already created ?

Would you be willing to post the fix script you referred to ?

Thanks
Back to top
View user's profile Send private message Send e-mail
smdavies99
PostPosted: Mon Apr 04, 2011 12:37 pm    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

You didn't correctly create the workpath by just creating the directories.

You need to use the
Code:

mqsicreateworkpath /var/mqsi

command.

This will also set the right permissions.

I'll post the list of rpm's that are needed later.
_________________
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
View user's profile Send private message
smdavies99
PostPosted: Mon Apr 04, 2011 9:22 pm    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

Here are the list of items (still a work in progress) that should be installed.
Code:

# Stuff needed for wmq & wbi on 64bit
libXpm
libXpm.i686
libXaw
libXaw.i686
libXp
libXp.i686
libXmu
libXmu.i686
libcanberra
libcanberra.i686
libcanberra-gtk2
libcanberra-gtk2.i686
gtk2
gtk2.i686
gtk2-engines
gtk2-engines.i686
PackageKit-gtk-module
PackageKit-gtk-module.i686
# end of stuff needed for wbi & wmq of 64bit rhel.

This is taken from a kickstart file but they can be combined into a single 'yum' command.
My take on this (and I welcome any confirmation from the IBMer's) is that the installer is a 32bit thingy even on a 64bit system.

My other tip to help resolve dependencies is to put all the WMQ rpm's into a single directory. This includes any fixpack ones. Then I normally delete any unwanted *Msg*.rpm's. Then I create a repository using the 'createrepo' command. Finally I add the repo details to a file in the /etc/yum.repos.d/.
Then I can use 'yum' in the following way.
Code:

yum install MQS*

This way the dependencies for WMQ (with the gsk bits) get automatically resolved and installed in one go.

All this palava is due to RH repackaging a lot of stuff so that the distro is a lot les bloated than RHEL 5. Well, that's my take on it anyway.
_________________
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
View user's profile Send private message
lancelotlinc
PostPosted: Tue Apr 05, 2011 3:47 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

IMHO, you are better off deleting all and restarting the installation. You need to follow the step-by-step instructions in the installation guide. No where in that guide does it tell you to chmod anything. If you installed the software per the instructions, the software will work. Especially check Chapter 6, pages 39 to 48 of the installation guide. These steps are done before, not after, you install the binaries.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
smdavies99
PostPosted: Tue Apr 05, 2011 4:03 am    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

lancelotlinc wrote:
IMHO, you are better off deleting all and restarting the installation. You need to follow the step-by-step instructions in the installation guide. No where in that guide does it tell you to chmod anything. If you installed the software per the instructions, the software will work. Especially check Chapter 6, pages 39 to 48 of the installation guide. These steps are done before, not after, you install the binaries.


One of the issues that I suspect is happening is also discussed here
http://www.mqseries.net/phpBB2/viewtopic.php?p=299638&

I've seen this myself if you don't have all the requisite RPM's installed. One symptom of this is also the failure of the runtime installer to work in anything but console mode.

The error message seen in the above post is an indication that the mqsicreateworkpath command may well have not been invoked. There are no indications in the mqsi*.log of a failure. It has to be down to some missing dependency that does not seem to be documented.

The OP here can simply delete the directories he has created and run the mqsicreateworkpath command. Then his broker should work properly, provided and as you have hinted, that there is nothing else wrong.
We have a RHEL 6.0 Kickstart file that installs everything we need to get broker and the toolkit installed graphically should we deem it necessecary.
All I'm looking for is for the RT installer to stop using rpm directly and use yum or PackageKit instead. Perhaps this will happen in V8? It would be nice.
_________________
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
View user's profile Send private message
lancelotlinc
PostPosted: Tue Apr 05, 2011 4:08 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

I just completed an RHEL install (on three RHEL boxes), and it went perfectly, no WMB issues. I still have an issue with ODBC on one of those boxes, but it is due to the fact that I need a DB2 Activation key for the DB2 client, I believe.

From what Gideon has said, he did not follow the installation guide. This is why his system is so messed up. I don't know first hand, but if I guessed, I would guess that he ran the installer without performing the steps in Chapter 6 first. This is why his file permissions are all messed up.

If he had performed ALL the steps in Chapter 6, he would not need to chmod anything. "I'm just saying..."
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
Gideon
PostPosted: Tue Apr 05, 2011 9:34 am    Post subject: Reply with quote

Chevalier

Joined: 18 Aug 2009
Posts: 403

I got this all to work with the following:

Code:
        yum groupinstall "Compatibility libraries"

        yum install libstdc++.so.5

        yum install compatstc+33

        yum install ksh


and then using the mqsicreateworkpath command to complete
Back to top
View user's profile Send private message Send e-mail
Gideon
PostPosted: Tue Apr 05, 2011 9:44 am    Post subject: Reply with quote

Chevalier

Joined: 18 Aug 2009
Posts: 403

lancelotlinc:

I have this working now, but I want to back track and double check everything.

I am going through http://publib.boulder.ibm.com/infocenter/wmbhelp/v7r0m0/index.jsp

I do not see the Chapter 6 you mention.

Could you please provide me a link so I can double check and see if I had origianlly missed anything

Thanks
Back to top
View user's profile Send private message Send e-mail
lancelotlinc
PostPosted: Tue Apr 05, 2011 10:03 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

Gideon wrote:
lancelotlinc:

I have this working now, but I want to back track and double check everything.

I am going through http://publib.boulder.ibm.com/infocenter/wmbhelp/v7r0m0/index.jsp

I do not see the Chapter 6 you mention.

Could you please provide me a link so I can double check and see if I had origianlly missed anything

Thanks


Its not posted on the site. It is in the binary downloads for the product.

WebSphere Message Broker V7.0.0.x Quick Start Guide for Multiplatform Multilingual

There is a PDF file in there called "installationguide.pdf

Chapter 6 has crucial information and those steps must be completed prior to you installing the product. You obviously skipped those steps and installed the product without reading the manual.


_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Start Broker error
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.