| Author |
Message
|
| dileep1985 |
 Posted: Wed Oct 18, 2017 8:01 am Post subject: Not able to start broker as service in multiinstance |
 |
|
Novice
Joined: 15 Jul 2017
Posts: 15
|
Hi All,
We have created a new multiinstance queue manager using NFS. When we try to start the broker , getting below error
BIP8249E: Cannot start the WebSphere MQ service for integration node {0} and queue manager {1}. The WebSphere MQ return code is {2}.
There was an error when starting the WebSphere MQ service for an integration node.
Check the reason for the WebSphere MQ error and take any suggested corrective action.
MQ error is coming as below. Can you please help
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6119 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred |
| ('13 - Permission denied' from open.) |
| FDCSequenceNumber :- 0 |
| Arith1 :- 13 (0xd) |
| Comment1 :- '13 - Permission denied' from open. |
|
id
uid=500(iibadmin) gid=500(mqm) groups=500(mqm),503(mqbrkrs) |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Oct 18, 2017 8:05 am Post subject: Re: Not able to start broker as service in multiinstance |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| dileep1985 wrote: |
| | ('13 - Permission denied' from open.) |
Despite the group memberships you post, the OS thinks that id is not allowed to open some file. Verify file permissions.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| dileep1985 |
| Posted: Wed Oct 18, 2017 9:02 am Post subject: Re: Not able to start broker as service in multiinstance |
|
|
Novice
Joined: 15 Jul 2017
Posts: 15
|
| Vitor wrote: |
| dileep1985 wrote: |
| | ('13 - Permission denied' from open.) |
Despite the group memberships you post, the OS thinks that id is not allowed to open some file. Verify file permissions. |
Thanks for the update. Could you please help to elaborate on this. Which folder it can be. As I am struggling with this |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Oct 18, 2017 9:30 am Post subject: Re: Not able to start broker as service in multiinstance |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| dileep1985 wrote: |
| Vitor wrote: |
| dileep1985 wrote: |
| | ('13 - Permission denied' from open.) |
Despite the group memberships you post, the OS thinks that id is not allowed to open some file. Verify file permissions. |
Could you please help to elaborate on this. |
Like the error says, "unexpected system return code". The "system" in this context is the OS on which MQ is running. "Permission denied" sounds like a Unix/Linux to me, and when MQ has tried to open something, MQ got that instead of a file handle.
| dileep1985 wrote: |
| Which folder it can be. |
Any file or folder MQ is trying to use. Given the permissions you posted, and making the assumption you've both left the folder permissions at the installation defaults and already checked them, I'd turn my attention to the NFS mount. I'd start by checking with the admins that it's mounted correctly and it's the correct level of NFS to support multi-instance.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Oct 18, 2017 1:24 pm Post subject: Re: Not able to start broker as service in multiinstance |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
| Vitor wrote: |
| dileep1985 wrote: |
| | ('13 - Permission denied' from open.) |
Despite the group memberships you post, the OS thinks that id is not allowed to open some file. Verify file permissions. |
The service id needs to be part of the local mqm and mqbrokers groups on both nodes!... and for a multi-instance qmgr / broker you should use domain accounts and not the SYSTEM account that is local and has a different SID on each box! ... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| dileep1985 |
| Posted: Mon Oct 23, 2017 3:27 am Post subject: |
|
|
Novice
Joined: 15 Jul 2017
Posts: 15
|
Thanks for all your replies. Issue got resolved. It is mistake from our side.
While installing multi instance broker, during accept license step , i have executed the step to accept licence for single installation. This resulting in causing the broker to create the work path as /home which does not having the permission. This caused the permission errors.
I have reinstalled the broker by accepting the licence as global. So work path of broker created as /var/mqsi. This solved the issue. |
|
| Back to top |
|
|
|
|
