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:
Sent: Tue January 30, 2024 09:15 AM
From: Juan Reforme
Subject: MQ's status is Running elsewhere
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:
Sent: Tue January 30, 2024 09:02 AM
From: Nipun Goel
Subject: MQ's status is Running elsewhere
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
Original Message:
Sent: Tue January 30, 2024 07:07 AM
From: Juan Reforme
Subject: MQ's status is Running elsewhere
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
------------------------------