| Author |
Message
|
| KIT_INC |
 Posted: Mon Nov 04, 2013 11:13 am Post subject: BIP8233E creating multi instance broker |
 |
|
Knight
Joined: 25 Aug 2006
Posts: 589
|
Trying to create amulti-instance broker on V7004.
I already have q multiinstance Qmgr (QM1) running (V7019)
The command
mqsicreatebroker Mybrk -q QM1 -e /MQHA/DATA/mqsi -d defined
I received error
BIP8233E: Multi-instance Broker Mybrk, or an instance of that broker, cannot be created because the shared workpath /MQHA/DATA/mqsi does not exist.
The broker instance needs to reference the shared workpath that cannot be accessed, or cannot be located.
Check that the server hosting the shared workpath is accessible.
/MQHA/DATA/mqsi is NFS mount with the following attributes
ls -l /MQHA/DATA/mqsi
drwxrwx--- 2 mqm mqm 80 Nov 4 2013 mqsi
both mqsi and mqbrkrs are a memeber of mqm.
I can successfukly perform mkdir under /MQHA/DATA/mqsi either login as mqm or mqsi from the Linux server which I perform the mqsicreaytebroker command.
Any suggestion ? What user Id does the command use to try to access the shared NFS folder ? |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Mon Nov 04, 2013 11:46 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
What is the ownership (both user, group etc) of the shared directory?
Have you logged on with the broker ID and tried to access the directory?
What about supplying a username/password for the broker ID?
My guess is that you are following the example in the documentation. That is where you are going wrong. The docs leave a lot to be desired in this section.
_________________
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 |
|
|
| KIT_INC |
| Posted: Mon Nov 04, 2013 12:18 pm Post subject: |
|
|
Knight
Joined: 25 Aug 2006
Posts: 589
|
| Quote: |
| What about supplying a username/password for the broker |
I read the mqsicreatbroker command in the info center and cannot find any parameters where I can specify a user ID password.
That's why I was also asking if anybody know what user ID does this command use to access the shared folder. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Nov 04, 2013 12:58 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| who is running the command? |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Nov 04, 2013 1:23 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| KIT_INC wrote: |
| Quote: |
| What about supplying a username/password for the broker |
I read the mqsicreatbroker command in the info center and cannot find any parameters where I can specify a user ID password.
That's why I was also asking if anybody know what user ID does this command use to access the shared folder. |
For V7.0.0.4
| Code: |
C:\>mqsicreatebroker /
BIP8920W: Creates a broker.
Syntax (for Microsoft Windows platforms):
mqsicreatebroker brokerName -i serviceUserId -a servicePassword -q queueManager
Name [-g configurationChangeTimeout] [-k internalConfigurationTimeout] [-w workP
ath] [-e sharedWorkpath] [-l userLilPath] [-t] [-m] [-v statisticsMajorInterval]
[-P httpListenerPort] [-c icuConverterPath] [-y ldapPrincipal -z ldapCredential
s] [-x userExitPath] [-o operationMode] [-s adminSecurity] [-d MQService]
Command Options:
'brokerName' the name of the broker.
'-i serviceUserId' the user ID that the broker runs under and that by default i
s used to connect to external resources.
'-a servicePassword' the password for the broker user ID.
'-q queueManagerName' the WebSphere MQ queue manager that the broker will use.
The queue manager is created if it does not exist.
'-g configurationChangeTimeout' the maximum time (in seconds) allowed for a use
r configuration request to be processed.
'-k internalConfigurationTimeout' the maximum time (in seconds) allowed for an
internal configuration change to be processed.
'-w workPath' the directory in which trace logs are written.
'-e sharedWorkPath' the directory in which registry and configuration data is s
hared between multiple instances of this broker.
'-l userLilPath' the directory from which the broker searches for user-supplied
libraries.
'-t' enables WebSphere MQ fastpath for this broker (not supported on all platfo
rms).
'-m' indicates that migration is required from an WebSphere publish/subscribe b
roker.
'-v statisticsMajorInterval' the time (in minutes) for the duration of the inte
rval for collecting statistics archive records.
'-P httpListenerPort' the port that the broker's HTTP listener uses.
'-c icuConverterPath' delimited ';' list of paths to search for ICU converters
or converter packages.
'-y ldapPrincipal' the LDAP Principal (user ID).
'-z ldapCredentials' the LDAP Credentials (password).
'-x userExitPath' the directory from which the broker searches for all user exi
ts. This path is added to the system library search path (PATH,LIBPATH,LD_LIBRAR
Y_PATH,SHLIBPATH) for the execution group process only.
'-o operationMode' the broker operation mode. Valid values that you can set are
'entry', 'starter', 'adapter' and 'enterprise'. The default mode is 'enterprise
' unless you have the Trial Edition, in which case the default mode is 'trial'.
'-s adminSecurity' activates broker administration security. Valid values that
you can set are 'active' and 'inactive'. The default is 'inactive'.
'-d MQService' start the broker as a WebSphere MQ Service when the queue manage
r starts. Valid values that you can set are 'defined' and 'undefined'. The defau
lt is 'undefined'.
BIP8002E: Selected flag '/' badly formed.
Command flag should be properly specified.
Correct and reissue the command.
C:\>
|
_________________
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: Mon Nov 04, 2013 1:26 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| smdavies99 wrote: |
| KIT_INC wrote: |
| Quote: |
| What about supplying a username/password for the broker |
I read the mqsicreatbroker command in the info center and cannot find any parameters where I can specify a user ID password.
That's why I was also asking if anybody know what user ID does this command use to access the shared folder. |
For V7.0.0.4
|
the -i and -a flags only apply on Windows, they are not relevant on Unix. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Nov 04, 2013 8:32 pm Post subject: Re: BIP8233E creating multi instance broker |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| KIT_INC wrote: |
Trying to create amulti-instance broker on V7004.
I already have q multiinstance Qmgr (QM1) running (V7019)
The command
mqsicreatebroker Mybrk -q QM1 -e /MQHA/DATA/mqsi -d defined
I received error
BIP8233E: Multi-instance Broker Mybrk, or an instance of that broker, cannot be created because the shared workpath /MQHA/DATA/mqsi does not exist.
The broker instance needs to reference the shared workpath that cannot be accessed, or cannot be located.
Check that the server hosting the shared workpath is accessible.
/MQHA/DATA/mqsi is NFS mount with the following attributes
ls -l /MQHA/DATA/mqsi
drwxrwx--- 2 mqm mqm 80 Nov 4 2013 mqsi
both mqsi and mqbrkrs are a memeber of mqm.
I can successfukly perform mkdir under /MQHA/DATA/mqsi either login as mqm or mqsi from the Linux server which I perform the mqsicreaytebroker command.
Any suggestion ? What user Id does the command use to try to access the shared NFS folder ? |
how about changing the permissions to
drwxrws--- mqm mqbrokers -------- mqsi ?
Just a thought 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Nov 04, 2013 11:51 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
the -i and -a flags only apply on Windows, they are not relevant on Unix.[/quote]
Just to be clear that the V9 InfoCentre says
| Code: |
-i serviceUserId
(Deprecated) This parameter is included for compatibility with earlier versions.
-a servicePassword
(Deprecated) This parameter is included for compatibility with earlier versions.
|
I'll have to read up on how to create a broker without those params on Linux. It has been a while since I have had to do it and I have a set of scripts that normally do it for me and they use the -i -a options.. They will need updating.
_________________
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: Tue Nov 05, 2013 6:29 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| smdavies99 wrote: |
| I'll have to read up on how to create a broker without those params on Linux. It has been a while since I have had to do it and I have a set of scripts that normally do it for me and they use the -i -a options.. They will need updating. |
The user that is used as the service user on Unix is the user that executes mqsistart. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Nov 05, 2013 6:45 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| mqjeff wrote: |
| smdavies99 wrote: |
| I'll have to read up on how to create a broker without those params on Linux. It has been a while since I have had to do it and I have a set of scripts that normally do it for me and they use the -i -a options.. They will need updating. |
The user that is used as the service user on Unix is the user that executes mqsistart. |
Yes. That is it exactly. doing this (mqsistart) incorrectly can lead to all sorts of problems.
It is a pity the worked example shown in the docs/Infocentre does not include BOTH Unix/Linux and Windows commands. Yes, I know that a good number of people don't recommend using Windows in Production but some companies are welded at the hip to the Microsoft Mantra.
_________________
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 |
|
|
| KIT_INC |
| Posted: Tue Nov 05, 2013 7:02 am Post subject: |
|
|
Knight
Joined: 25 Aug 2006
Posts: 589
|
The environment is Linux.
The mqsicreatebroker command was issued by mqm .
As I mentioned the NFS folder was own by mqm
/MQHA/DATA/mqsi is NFS mount with the following attributes
ls -l /MQHA/DATA/mqsi
drwxrwx--- 2 mqm mqm 80 Nov 4 2013 mqsi
That's why I thought that the command may be using a different ID to access the folder.
I just checked another system that NFS folder has
/MQHA/DATA/mqsi
ls -l /MQHA/DATA/mqsi
drwxrwx--- 2 mqsi mqbrkrs 80 Nov 4 2013 mqsi
I tried to issue chown from root
chown mqsi:mqbrkrs mqsi
But I received invalid argument. I did a quick google search, some one says that ownership of NFS4 files can only be done at the NFS server. Not sure if this correct. If so I'll have to get the Linux NFS team to fix it for me. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Nov 05, 2013 7:08 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It's not recommended that you run a broker as the mqm user, unless you are running the broker as a trusted application.
it's not recommended that you issue mqsicreatebroker from a user that will not end up being the broker service user.
The errors that you've shown do indicate something is wrong with the NFS mount. |
|
| Back to top |
|
|
|
|
