| Author |
Message
|
| smdavies99 |
 Posted: Thu Feb 20, 2014 6:07 am Post subject: RFE - Improve MSCS Startup Failure error msg content |
 |
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=45297
I'm suffering at the hands of the gremlins again. My brokers won't start in an MSCS environment.
The error message you get really does not give you a real hint as to what the problem is.
The message stating that the broker can't be registered is silly. There is a service created with all the correct login and group membership details and the shared path is correct so what is the real reason?
Is the security on the directories wrong?
Are you trying to do this under the wrong account?
It says nothing that can really give you a clue.
The RFE is to improve the data reported when the startup fails.
_________________
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 |
|
 |
| smdavies99 |
| Posted: Thu Feb 20, 2014 9:59 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
In case anyone doubts the need for this improvement take a look at the data below.
Node 1. Create the Broker
| Code: |
E:\scripts\01-MAA\iibscripts\02-CCZBRKR>cre_CCZBRKR_bkr.bat
--
-- Create the Broker Itself
--
mqsicreatebroker CCZBRKR -q CCZBRKR -i XXXDOMAIN\mbservice -a MQ@@123 -e E:\IIB_DATA\CCZBRKR
BIP8071I: Successful command completion.
--
--
Environment variable the Effective runtime level not defined
--
mqsichangebroker CCZBRKR -f all
BIP8071I: Successful command completion.
mqsireportbroker CZZBRKR
BIP8927I: Broker Name 'CCZBRKR'
Last mqsistart path = ''
mqsiprofile install path = 'C:\IBM\MQSI\9.0.0.1'
Work path = 'C:\ProgramData\Application Data\IBM\MQSI'
Broker UUID = ''
Process id = '0'
Queue Manager = 'CCZBRKR'
User lil path = ''
User exit path = ''
Active user exits = ''
LDAP principal = ''
LDAP credentials = ''
ICU converter path = ''
Trusted (fastpath) Queue Manager application = 'false'
Configuration change timeout = '300' seconds
Internal configuration timeout = '60' seconds
Statistics major interval = '60' minutes
Operation mode = 'advanced'
Fixpack capability level = 'all' (effective level '9.0.0.1')
Broker registry format = 'v9.0'
Administration security = 'inactive'
Multi-instance Broker = 'true'
Shared Work Path = 'E:\IIB_DATA\CCZBRKR\mqsi'
Start as WebSphere MQ Service = 'undefined'
HTTP listener port = '7080'
Cache manager policy = 'disabled'
Cache manager port range = '2800-2819'
Integration registry hostname = ''
BIP8071I: Successful command completion.
E:\scripts\01-MAA\iibscripts\02-CCZBRKR>mqsiservice CCZBRKR
BIPmsgs en_US
Console OEM CP=437, ICU CCSID=5348
Default codepage=ibm-5348_P100-1997, in ascii=ibm-5348_P100-1997
JAVA console codepage name=cp437
Install Path = C:\IBM\MQSI\9.0.0.1
Shared Work Path = E:\IIB_DATA\CCZBRKR\mqsi
Local Work Path = C:\ProgramData\Application Data\IBM\MQSI
process id = 0
service userId = .\XXXDOMAIN\mbservice
general default userId = XXXDOMAIN\mbservice
queue manager = CCZBRKR
MQ installation path = C:\IBM\WMQ
pubsub migration = no
fastpath Queue Manager = no
configuration timeout = 300
configuration delay timeout = 60
statistics major interval = 60
ComponentType = Broker
Fixpack capability level = all (effective level 9.0.0.1)
BIP8071I: Successful command completion.
E:\scripts\01-MAA\iibscripts\02-CCZBRKR>mqsistart CCZBRKR
BIP8096I: Successful command initiation, check the system log to ensure that the component started without problem and that it continues to run without problem.
E:\scripts\01-MAA\iibscripts\02-CCZBRKR>mqsilist
BIP1295I: Broker 'CCZBRKR' is an active multi-instance or High Availability broker that is running on queue manager 'CCZBRKR'.
BIP8071I: Successful command completion.
E:\scripts\01-MAA\iibscripts\02-CCZBRKR>mqsistop CCZBRKR
BIP8071I: Successful command completion.
E:\scripts\01-MAA\iibscripts\02-CCZBRKR>
|
All good so far
Move everything over to the other node and add the instance
| Code: |
E:\scripts\01-MAA\iibscripts\02-CCZBRKR>cre_CCZBRKR_bkr.bat ADD
-------------- ADD Broker instance for CCZBRKR -------------------------------
mqsiaddbrokerinstance CCZBRKR -i XXXDOMAIN\mbservice -a MQ@@123 -e E:\IIB_DATA\CCZBRKR
AMQ7272: WebSphere MQ configuration information already exists.
BIP8071I: Successful command completion.
mqsireportbroker CCZBRKR
BIP8927I: Broker Name 'CCZBRKR'
Last mqsistart path = 'C:\IBM\MQSI\9.0.0.1'
mqsiprofile install path = 'C:\IBM\MQSI\9.0.0.1'
Work path = 'C:\ProgramData\Application Data\IBM\MQSI'
Broker UUID = ''
Process id = '0'
Queue Manager = 'CCZBRKR'
User lil path = ''
User exit path = ''
Active user exits = ''
LDAP principal = ''
LDAP credentials = ''
ICU converter path = ''
Trusted (fastpath) Queue Manager application = 'false'
Configuration change timeout = '300' seconds
Internal configuration timeout = '60' seconds
Statistics major interval = '60' minutes
Operation mode = 'advanced'
Fixpack capability level = 'all' (effective level '9.0.0.1')
Broker registry format = 'v9.0'
Administration security = 'inactive'
Multi-instance Broker = 'true'
Shared Work Path = 'E:\IIB_DATA\CCZBRKR\mqsi'
Start as WebSphere MQ Service = 'undefined'
HTTP listener port = '7080'
Cache manager policy = 'disabled'
Cache manager port range = '2800-2819'
Integration registry hostname = ''
BIP8071I: Successful command completion.
E:\scripts\01-MAA\iibscripts\02-CCZBRKR>mqsiservice CCZBRKR
BIPmsgs en_US
Console OEM CP=437, ICU CCSID=5348
Default codepage=ibm-5348_P100-1997, in ascii=ibm-5348_P100-1997
JAVA console codepage name=cp437
Install Path = C:\IBM\MQSI\9.0.0.1
Shared Work Path = E:\IIB_DATA\CCZBRKR\mqsi
Local Work Path = C:\ProgramData\Application Data\IBM\MQSI
process id = 0
service userId = .\XXXDOMAIN\mbservice
general default userId = XXXDOMAIN\mbservice
queue manager = CCZBRKR
MQ installation path = C:\IBM\WMQ
pubsub migration = no
fastpath Queue Manager = no
configuration timeout = 300
configuration delay timeout = 60
statistics major interval = 60
ComponentType = Broker
Fixpack capability level = all (effective level 9.0.0.1)
BIP8071I: Successful command completion.
E:\scripts\01-MAA\iibscripts\02-CCZBRKR>mqsistart CCZBRKR
BIP8096I: Successful command initiation, check the system log to ensure that the
component started without problem and that it continues to run without problem.
E:\scripts\01-MAA\iibscripts\02-CCZBRKR>mqsilist
BIP1292I: The multi-instance or High Availability broker 'CCZBRKR' on queue mana
ger 'CCZBRKR' has stopped.
BIP8071I: Successful command completion.
E:\scripts\01-MAA\iibscripts\02-CCZBRKR>
|
Authorizations.
1) the XXXDOMAIN\mbservice account is a member of mqbrkrs (local) and Domain mb (global) + mqm and Domain mq.
2) The XXXDOMAIN\mbservice has full access to the drive containing the shared path directory.
If I reverse the process and create the broker on Node 2 and add it on Node 1 the same issue applies.
IMHO an error message saying that the service could not be registered is inadequate.
The Customer site where this is happening is a new IBM customer but raising a PMR is considered a loss of face and is not allowed despite me telling them that they have paid for it. The 'keys' to their IBM account are guarded like the Crown Jewels. People here don't ask questions unless they are told to by their boss.
The sad thing is that the test environment (totally separate VMWAre based) uses all the same scripts etc and works perfectly. The only difference is that the DC on this network is Windows Server 2012 and not 2008 as is used on the Test setup. I shall have to investigate that when I get back into the office next week.
But in the meantime if someone has a spark of genius and can point me in the right direction they will be suitably rewarded.
_________________
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 |
|
|
| Michael Dag |
| Posted: Fri Feb 21, 2014 12:58 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
So your Broker, does not start, you can not create a PMR for political reasons and now you raise an RFE to improve the output?
Who is working on analysing and fixing the problem?
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| Gralgrathor |
| Posted: Fri Feb 21, 2014 1:12 am Post subject: |
|
|
Master
Joined: 23 Jul 2009
Posts: 297
|
| smdavies99 wrote: |
| raising a PMR is considered a loss of face and is not allowed |
That's seriously odd. Isn't it possible to collect the data and raise the PMR under your own account, or some other account? |
|
| Back to top |
|
|
| zpat |
| Posted: Fri Feb 21, 2014 1:22 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
I open loads of PMRs. Mainly for defects rather than assistance (usage) - but sometimes the latter.
The attitude that one mustn't ask for help but muddle on within a limited set of knowledge is responsible for some very poor decisions.
Always ask an expert when in doubt, or even just to review what you think would work, to see if a better way exists.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Feb 21, 2014 1:27 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| Gralgrathor wrote: |
| smdavies99 wrote: |
| raising a PMR is considered a loss of face and is not allowed |
That's seriously odd. Isn't it possible to collect the data and raise the PMR under your own account, or some other account? |
Yep, trying to resolve that.
Remember that in some parts of the world admitting that you can't do something is considered a major failure/loss of face. Using the word 'No' is also a major foopah.
_________________
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 |
|
|
| smdavies99 |
| Posted: Fri Feb 21, 2014 1:30 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| Michael Dag wrote: |
So your Broker, does not start, you can not create a PMR for political reasons and now you raise an RFE to improve the output?
Who is working on analysing and fixing the problem? |
The issue is that the error message is a Catch-all and not specific enough. If it was then I wouldn't need to even consider the RFE.
Instead of saying 'Can't register the broker' when the real problem is 'user not a member of the mqbrkrs group', why not say so? etc etc etc
There used to be a lot of problems getting the MQ Domain account and privs setup correctly. Now the error messages and a google will tell you all you need to know. that is what I'm looking for 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 |
|
|
| Gralgrathor |
| Posted: Fri Feb 21, 2014 1:33 am Post subject: |
|
|
Master
Joined: 23 Jul 2009
Posts: 297
|
| smdavies99 wrote: |
| Remember that in some parts of the world admitting that you can't do something is considered a major failure/loss of face |
Humans are seriously odd animals, I know.
But I would think that a PMR might equally well be a chance to show that somebody else (IBM in this case) made an error. That can't be considered loss offace, is it? |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Feb 21, 2014 5:34 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Gralgrathor wrote: |
| That can't be considered loss offace, is it? |
Loss of face is in the eye of the beholder, and I too have encountered this belief that PMRs do not come free with the IBM license but are charged for.
Remember also you need the IBM Customer Number and association with it to raise the PMR for the customer.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Feb 21, 2014 5:42 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
| smdavies99 wrote: |
| Remember that in some parts of the world admitting that you can't do something is considered a major failure/loss of face. Using the word 'No' is also a major foopah. |
Please keep in mind that your responsibilities are to the larger organization, and not just to the individuals that hired or supervise you.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Gralgrathor |
| Posted: Fri Feb 21, 2014 6:05 am Post subject: |
|
|
Master
Joined: 23 Jul 2009
Posts: 297
|
| bruce2359 wrote: |
| responsibilities are to the larger organization |
And if your direct superiors explicitly prohibit a course of action, despite your best efforts to argue your case? |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Feb 21, 2014 6:27 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Gralgrathor wrote: |
| bruce2359 wrote: |
| responsibilities are to the larger organization |
And if your direct superiors explicitly prohibit a course of action, despite your best efforts to argue your case? |
Depends if you're a full term employee or a contractor. 
Also depends on the culture of the larger organization. I've known sites where going over the heads of your direct superiors would result in trouble, even if you were acting from honest motives and were techincally correct.
All depends on the management ethos.
Also getting a bit off topic for this thread.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Gralgrathor |
| Posted: Fri Feb 21, 2014 6:52 am Post subject: |
|
|
Master
Joined: 23 Jul 2009
Posts: 297
|
| Vitor wrote: |
| Also getting a bit off topic for this thread. |
I wonder what Shakespeare would have had to say on the topic of verbose startup failure error messages. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Feb 21, 2014 7:07 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Before anyone asks the obvious, the createbroker and addbrokerinstance were done at elevated priv levels.(run as Administrator)
_________________
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 |
|
|
| Vitor |
| Posted: Fri Feb 21, 2014 7:09 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Gralgrathor wrote: |
| Vitor wrote: |
| Also getting a bit off topic for this thread. |
I wonder what Shakespeare would have had to say on the topic of verbose startup failure error messages. |
"So what does this magic box do then?"
Unless he had qualifications in computing they didn't discuss when I studied the man's life at school?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
