| Author |
Message
|
| stickx |
 Posted: Wed Apr 22, 2015 10:55 pm Post subject: Can't start nor clear MQ broker |
 |
|
Newbie
Joined: 22 Apr 2015
Posts: 6
|
Hi guys,
I'm a bit of an MQ noob, was hoping you guys could point me in the right direction. Google was of no help  . (commands would be great)
Parent (HEAD_OFF) lost its FC card a couple of days ago and it has sent everything a little crazy.
MQ Version: 6.0.2.3
when trying to start mq broker (strmqbrk):
| Code: |
04/23/2015 04:42:48 PM - Process(27058.1) User(trivers) Program(runmqbrk)
AMQ5806: WebSphere MQ Publish/Subscribe broker started for queue manager
HEAD_OFF.
EXPLANATION:
WebSphere MQ Publish/Subscribe broker started for queue manager HEAD_OFF.
ACTION:
None.
-------------------------------------------------------------------------------
04/23/2015 04:42:48 PM - Process(27058.4) User(trivers) Program(runmqbrk)
AMQ6174: The dynamically loadable shared library '/var/mqm/exits//MQPCF_r' was
not found. The system returned error number '2' and error message 'No such file
or directory'. The queue manager will continue without this module.
EXPLANATION:
This message applies to UNIX systems. The shared library
'/var/mqm/exits//MQPCF_r' was not found.
ACTION:
Check that the file exists, and is either fully qualified or is in the
appropriate director, also check the file access permissions.
-------------------------------------------------------------------------------
04/23/2015 04:42:48 PM - Process(27061.1) User(trivers) Program(amqfcxba)
AMQ5819: An WebSphere MQ Publish/Subscribe broker stream has ended abnormally.
EXPLANATION:
The broker stream (SYSTEM.BROKER.DEFAULT.STREAM ) has ended
abnormally for reason 20805800. The broker will attempt to restart the stream.
If the stream should repeatedly fail then the broker will progressively
increase the time between attempts to restart the stream.
ACTION:
Investigate why the problem occurred and take appropriate action to correct the
problem. If the problem persists, contact your IBM service representative.
----- amqfpica.c : 858 --------------------------------------------------------
04/23/2015 04:42:48 PM - Process(27058.1) User(trivers) Program(runmqbrk)
AMQ5855: WebSphere MQ Publish/Subscribe broker ended.
EXPLANATION:
An attempt has been made to run the broker (HEAD_OFF) but the broker has ended
for reason '5804:frcE_BROKER_DEAD'.
ACTION:
Determine why the broker ended. The message logs for the queue manager might
contain more detailed information on why the broker cannot be started. Resolve
the problem that is preventing the command from completing and reissue the
strmqbrk command.
----- amqfcxca.c : 1068 -------------------------------------------------------
|
When trying to clear the broker:
| Code: |
----- amqfcxca.c : 1068 -------------------------------------------------------
04/23/2015 04:41:13 PM - Process(26822.1) User(trivers) Program(clrmqbrk)
AMQ5848: WebSphere MQ Publish/Subscribe broker (HEAD_OFF) has failed to remove
references to relation (955_T) for reason '0:'.
EXPLANATION:
An attempt has been made to remove references to broker (955_T) from broker
(HEAD_OFF) using the clrmqbrk command, but the request has been unsuccessful.
ACTION:
Determine why the clrmqbrk command cannot complete successfully. The message
logs for the queue manager might contain more detailed information on why the
broker cannot be deleted. Resolve the problem that is preventing the command
from completing and then reissue the clrmqbrk command.
----- amqfcxga.c : 996 --------------------------------------------------------
04/23/2015 04:41:13 PM - Process(26822.1) User(trivers) Program(clrmqbrk)
AMQ5848: WebSphere MQ Publish/Subscribe broker (HEAD_OFF) has failed to remove
references to relation (955_T) for reason '5848:frcE_BROKER_CLEAR_FAILED'.
EXPLANATION:
An attempt has been made to remove references to broker (955_T) from broker
(HEAD_OFF) using the clrmqbrk command, but the request has been unsuccessful.
ACTION:
Determine why the clrmqbrk command cannot complete successfully. The message
logs for the queue manager might contain more detailed information on why the
broker cannot be deleted. Resolve the problem that is preventing the command
from completing and then reissue the clrmqbrk command.
----- amqfcxga.c : 1018 -------------------------------------------------------
|
|
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Apr 23, 2015 6:18 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Is there a specific reason that user trivers is running the mq pub/sub broker and not user mqm ? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| stickx |
| Posted: Thu Apr 23, 2015 8:09 am Post subject: |
|
|
Newbie
Joined: 22 Apr 2015
Posts: 6
|
| fjb_saper wrote: |
| Is there a specific reason that user trivers is running the mq pub/sub broker and not user mqm ? |
Its a custom application from SAP that they dropped and we have to try and support ourselves :/ |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Apr 23, 2015 11:50 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| stickx wrote: |
| fjb_saper wrote: |
| Is there a specific reason that user trivers is running the mq pub/sub broker and not user mqm ? |
Its a custom application from SAP that they dropped and we have to try and support ourselves :/ |
what is the return from the id command?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| stickx |
| Posted: Thu Apr 23, 2015 4:25 pm Post subject: |
|
|
Newbie
Joined: 22 Apr 2015
Posts: 6
|
| fjb_saper wrote: |
what is the return from the id command? |
| Code: |
uid=63103(trivers) gid=51129(tegroup) groups=1000(mqm),51129(tegroup),51131(sapsys)
|
|
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Apr 24, 2015 4:59 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Can you resolve the shared library problem? MQPCF_r.so ?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Apr 24, 2015 5:23 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Can you upgrade the queue manager to a v7 level, to use the proper pub/sub engine instead of the 'fuji broker' ?
Can you please try stopping the pub/sub broker and then starting it as mqm? |
|
| Back to top |
|
|
| stickx |
| Posted: Sun Apr 26, 2015 4:53 pm Post subject: |
|
|
Newbie
Joined: 22 Apr 2015
Posts: 6
|
| fjb_saper wrote: |
| Can you resolve the shared library problem? MQPCF_r.so ? |
That library error is an oddity.
We have this same setup in other environments, but that MQPCF_r file is never required, nor does it exist.
Do you have any idea what the library would be used for? |
|
| Back to top |
|
|
| stickx |
| Posted: Sun Apr 26, 2015 4:57 pm Post subject: |
|
|
Newbie
Joined: 22 Apr 2015
Posts: 6
|
| mqjeff wrote: |
Can you upgrade the queue manager to a v7 level, to use the proper pub/sub engine instead of the 'fuji broker' ?
|
I'm not really sure whats involved in upgrading to v7... sounds big.
| mqjeff wrote: |
| Can you please try stopping the pub/sub broker and then starting it as mqm? |
| Code: |
-------------------------------------------------------------------------------
04/27/2015 10:54:31 AM - Process(19089.1) User(mqm) Program(runmqbrk)
AMQ5806: WebSphere MQ Publish/Subscribe broker started for queue manager
HEAD_OFF.
EXPLANATION:
WebSphere MQ Publish/Subscribe broker started for queue manager HEAD_OFF.
ACTION:
None.
-------------------------------------------------------------------------------
04/27/2015 10:54:31 AM - Process(19089.4) User(mqm) Program(runmqbrk)
AMQ6174: The dynamically loadable shared library '/var/mqm/exits//MQPCF_r' was
not found. The system returned error number '2' and error message 'No such file
or directory'. The queue manager will continue without this module.
EXPLANATION:
This message applies to UNIX systems. The shared library
'/var/mqm/exits//MQPCF_r' was not found.
ACTION:
Check that the file exists, and is either fully qualified or is in the
appropriate director, also check the file access permissions.
-------------------------------------------------------------------------------
04/27/2015 10:54:31 AM - Process(19092.7) User(mqm) Program(amqfcxba)
AMQ5882: WebSphere MQ Publish/Subscribe broker has written a message to the
dead-letter queue.
EXPLANATION:
The broker has written a message to the dead-letter queue
(SYSTEM.DEAD.LETTER.QUEUE ) for reason
'2087:MQRC_UNKNOWN_REMOTE_Q_MGR'. Note. To save log space, after the first
occurrence of this message for stream (SYSTEM.BROKER.DEFAULT.STREAM
), it will only be written periodically.
ACTION:
If the message was not deliberately written to the dead-letter queue, for
example by a message broker exit, determine why the message was written to the
dead-letter queue, and resolve the problem that is preventing the message from
being sent to its destination.
----- amqfqxaa.c : 679 --------------------------------------------------------
04/27/2015 10:54:31 AM - Process(19092.1) User(mqm) Program(amqfcxba)
AMQ5819: An WebSphere MQ Publish/Subscribe broker stream has ended abnormally.
EXPLANATION:
The broker stream (SYSTEM.BROKER.DEFAULT.STREAM ) has ended
abnormally for reason 20805800. The broker will attempt to restart the stream.
If the stream should repeatedly fail then the broker will progressively
increase the time between attempts to restart the stream.
ACTION:
Investigate why the problem occurred and take appropriate action to correct the
problem. If the problem persists, contact your IBM service representative.
----- amqfpica.c : 858 --------------------------------------------------------
04/27/2015 10:54:32 AM - Process(19089.1) User(mqm) Program(runmqbrk)
AMQ5855: WebSphere MQ Publish/Subscribe broker ended.
EXPLANATION:
An attempt has been made to run the broker (HEAD_OFF) but the broker has ended
for reason '5804:frcE_BROKER_DEAD'.
|
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Apr 27, 2015 4:39 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| I'm suspicious about the extra / in the path to the exit. |
|
| Back to top |
|
|
| stickx |
| Posted: Mon Apr 27, 2015 5:12 pm Post subject: |
|
|
Newbie
Joined: 22 Apr 2015
Posts: 6
|
| mqjeff wrote: |
| I'm suspicious about the extra / in the path to the exit. |
Extra slashes don't matter in linux systems.
I don't think thats the sign of a problem. |
|
| Back to top |
|
|
|
|
