MQ

MQ

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

  • 1.  MQ's status is Running elsewhere

    Posted 01/30/24 07:07 AM

    Hi All,

    The scenario: after AWS Instance freeze, the server was restart it. The problem is that MQ can't start since the status as running elsewhere.

    "The QM is associated with installation 'Installation1'. IBM MQ Queue Manager is already running elsewhere. It doesn't permit standby instances."

    How can I fix this?

    Thank you.



    ------------------------------
    Juan Reforme
    ------------------------------


  • 2.  RE: MQ's status is Running elsewhere

    Posted 01/30/24 09:02 AM

    Hi, It seems like you have a multi instance setup.

    Please have a look at:

    https://www.ibm.com/support/pages/placing-queue-manager-standby-status



    ------------------------------
    Nipun Goel
    Infrastructure Engineer
    DNB Bank ASA
    Oslo
    ------------------------------



  • 3.  RE: MQ's status is Running elsewhere

    Posted 01/30/24 09:16 AM

    Hi Goel,

    No, we don't want multi instance setup. But, the MQ's configuration is place on AWS EFS shared disk. So, maybe that's why if suddenly terminate and create a new instance the problem happens. 

    Thank you



    ------------------------------
    Juan Reforme
    ------------------------------

    Original Message


  • 4.  RE: MQ's status is Running elsewhere

    Posted 01/30/24 09:30 AM

    Then probably the EFS was not released by the server completely and thus a new queue manager has been created on another server. Is your server part of an auto scaling group, because that may explain why this has happened.



    ------------------------------
    Nipun Goel
    Infrastructure Engineer
    DNB Bank ASA
    Oslo
    ------------------------------

    Original Message


  • 5.  RE: MQ's status is Running elsewhere

    Posted 01/30/24 11:33 AM
    If the qmgr is multi-instance and on one server it was started as a single-instance then when you try to start it on the standy server it will give an error.  so the fix is:  stop the qmgr (endmqm <qmgrname> and start it as a multi-instance (strmqm -x gmqrname).  Then go to the server where it is in Running elsewhere" status and do strmqm -x qmgrname.  This should fix it back as a full-fledged multi-instance qmgr with a standy instance ready to take over if needbe.

    Let me know if you have any questions or concerns.  
    The contents of this email are intended only for the recipient(s) listed above. If you are not the intended recipient, you are directed not to read, disclose, distribute, or otherwise use this transmission. If you have received this email in error, please notify the sender immediately and delete the transmission. Delivery of this message is not intended to waive any applicable privileges.



    Original Message


Related Content