| Author |
Message
|
| andre.vorob |
 Posted: Sun Mar 25, 2012 10:22 pm Post subject: Queue manager doesn`t start periodically with the start ofMQ |
 |
|
Newbie
Joined: 25 Mar 2012
Posts: 4
|
Hi! Need your help...
Our server restarts every morning. QM Service restarts well.
But sometimes Queue manager instance doesn`t start (although it`s set "Automatic"). There are no errors on the screen...
Tell me plz what may I correct to solve this problem?
Some time ago I haven`t this problem... Nothing changes in the configuration.
Sorry for mistakes in English language.. |
|
| Back to top |
|
 |
| exerk |
| Posted: Mon Mar 26, 2012 12:02 am Post subject: Re: Queue manager doesn`t start periodically with the start |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| andre.vorob wrote: |
| ...There are no errors on the screen... |
But what errors are recorded within the queue manager error logs, general WMQ error logs and FDC files (if any) and Event Viewer (I'm assuming Windows is the platform).
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| andre.vorob |
| Posted: Mon Mar 26, 2012 3:33 am Post subject: |
|
|
Newbie
Joined: 25 Mar 2012
Posts: 4
|
the list of errors in the Event Viewer:
"6177
An error has been detected, and the MQ error recording routine has been called.
5525
The Object Authority Manager has failed to complete an MQ request.
9508
The connection attempt to queue manager 'MQRC_SECURITY_ERROR' failed with reason code 2.
9508
The connection attempt to queue manager 'QM.RE47' failed with reason code 2063.
9409
The repository manager ended abnormally."
Next errors I think not such important after that...
I`m novice in MQ, tell me plz in such way should I solve this problem.
Thanks...
I`ve read that 2063 is MQRC_SECURITY_ERROR. It seems that it`s problem with current user trying to start MQ service?
I have local user db2admin in "mqm" group. What`s can be wrong? |
|
| Back to top |
|
|
| exerk |
| Posted: Mon Mar 26, 2012 4:37 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
What else is using that queue manager? Why is a DB Admin account in the mqm group?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| andre.vorob |
| Posted: Mon Mar 26, 2012 4:49 am Post subject: |
|
|
Newbie
Joined: 25 Mar 2012
Posts: 4
|
Two servers, 2 WAS profiles at first and 1 WAS profile at second.
Db2admin is only system login name which is chosen by the previous sysadmin. =) |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Mar 26, 2012 4:52 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
It would be so helpful if you took the time to mention which version of WMQ you're using and, as we seem to have established it's Windows, which flavour?
| andre.vorob wrote: |
| I`ve read that 2063 is MQRC_SECURITY_ERROR. It seems that it`s problem with current user trying to start MQ service? |
So which user are you using to start the service? If there was a problem with the user you'd get a 2035 not a 2063.
| andre.vorob wrote: |
| I have local user db2admin in "mqm" group. |
That's nice. Why? Why does db2admin need mqm membership? If this is the user you're trying to start the WMQ service with, why?
Here's another important point. If the db2admin user is local, are all the other users involved local? Is the user trying to start the service, the user running the queue manager processes or any of the other involved users domain accounts? Does your authentication process use LDAP or similar external lookup?
A 2063 is an error from the security system; if there was a problem with the user a 2035 would be the more likely code. If this is an intermitant problem my first guess is that you're usng a domain account and/or LDAP and the domain/LDAP service is not always available when WMQ is starting up so WMQ throws a 2063.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Mar 26, 2012 4:54 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| andre.vorob wrote: |
| Db2admin is only system login name which is chosen by the previous sysadmin. =) |
Then your WMQ is almost certainly configured incorrectly; no-one who knows how WMQ works (or how WAS works) would do that. I'm slightly surprised the WAS admin team & your security audit signed off on that, they typically don't like that "single point of access / keys to the kingdom" sort of solution.
I stand by my previous comments.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| andre.vorob |
| Posted: Mon Mar 26, 2012 11:56 pm Post subject: |
|
|
Newbie
Joined: 25 Mar 2012
Posts: 4
|
| I`ve added user _domain_.db2admin into 'mqm' Win user group. Today queue manager have started without any problems... I`ll track situation and write of possible changes. Thanks! |
|
| Back to top |
|
|
| exerk |
| Posted: Mon Mar 26, 2012 11:58 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
I suggest you look for whether the queue manager has XA connections somewhere...
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
|
|
