| Author |
Message
|
| someonesumit |
 Posted: Fri Oct 22, 2010 2:03 am Post subject: Queue manager status is showing as running elsewhere |
 |
|
Novice
Joined: 18 Sep 2009
Posts: 16
|
Hi, I am facing very unique issue in MQ.
MQ version is at V 7.0.1.0 and running on Enterprise Linux Server release 5.3. The queue manager is not setup to run as Multi instance queue manager. but when we use dspmq, it is showing as running elsewhere.
Please suggest me and find the error logs below.
Please find the details below:
$ dspmq -m QMSBLT5 -o all
QMNAME(QMSBLT5) STATUS(Running elsewhere) DEFAULT(no) STANDBY(Not permitted)
$ dspmq
QMNAME(QMSBLT5) STATUS(Running elsewhere)
$ strmqm QMSBLT5
WebSphere MQ queue manager 'QMSBLT5' starting.
WebSphere MQ queue manager 'QMSBLT5' is already running elsewhere. It does not
permit standby instances.
$ more AMQ3570.0.FDC
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Fri October 22 2010 01:28:42 CDT |
| UTC Time :- 1287728922.283765 |
| UTC Time Offset :- -300 (CST) |
| Host Name :- ausodqnts05 |
| Operating System :- Linux 2.6.18-128.4.1.0.1.el5PAE |
| PIDS :- 5724H7224 |
| LVLS :- 7.0.1.0 |
| Product Long Name :- WebSphere MQ for Linux (x86 platform) |
| Vendor :- IBM |
| Probe Id :- XY077003 |
| Application Name :- MQM |
| Component :- xtrGetTraceLock |
| SCCS Info :- lib/cs/unix/generic/amqxparx.c, 1.222 |
| Line Number :- 450 |
| Build Date :- Aug 13 2009 |
| CMVC level :- p000-L090813 |
| Build Type :- IKAP - (Production) |
| Effective UserID :- 40010 (mqm) |
| Real UserID :- UNKNOWN |
| Program Name :- endmqm |
| Addressing mode :- 32-bit |
| Process :- 3570 |
| Process(Thread) :- 3570 |
| Thread :- 1 |
| ThreadingModel :- PosixThreads |
| UserApp :- FALSE |
| Last HQC :- 0.0.0-0 |
| Last HSHMEMB :- 0.0.0-0 |
| 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 |
| ('43 - Identifier removed' from semop.) |
| FDCSequenceNumber :- 0 |
| Arith1 :- 43 (0x2b) |
| Comment1 :- '43 - Identifier removed' from semop. |
| |
+-----------------------------------------------------------------------------+ |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Fri Oct 22, 2010 2:17 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Is this a new setup or an existing setup that no longer works?
If it is a new setup, go back to the MQ system requirements and review them *very closely* with regards to your file systems.
Make sure that you have not done things like mount portions of mq file systems on NFSv3 network shares or things like that.
If it is an existing setup that no longer works, review the change that occurred between now and "the last time it worked". |
|
| Back to top |
|
|
| ramires |
| Posted: Fri Oct 22, 2010 3:09 am Post subject: |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
|
| Back to top |
|
|
| someonesumit |
| Posted: Fri Oct 22, 2010 4:34 am Post subject: |
|
|
Novice
Joined: 18 Sep 2009
Posts: 16
|
| This is not a new setup. This setup we have from past 6 months. We have MQ integration with seibel. Filesystem is local to server, it is not network share. The setup is on Oracle On demand server. After the issues comes, the status of queue manager changed to running elsewhere. It is normal queue manager not a multi-instance. So I am worried why it shows as running elsewhere. |
|
| Back to top |
|
|
| exerk |
| Posted: Fri Oct 22, 2010 4:43 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
So end it and restart it using the appropriate command, which may not have been the case when it was started.
_________________
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 |
|
|
| someonesumit |
| Posted: Fri Oct 22, 2010 6:05 am Post subject: |
|
|
Novice
Joined: 18 Sep 2009
Posts: 16
|
When I am trying to end the queue manager , it is showing
Queue manager is not available.
I tried clearing the ipcs also, but it didn't work. Even I don't see any mqm process running.
I think , server needs to be bounced.
Please let me know your suggestion. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Oct 22, 2010 6:19 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| When was the last time it started successfully? What changed between then and now? |
|
| Back to top |
|
|
| someonesumit |
| Posted: Sat Oct 23, 2010 10:19 pm Post subject: |
|
|
Novice
Joined: 18 Sep 2009
Posts: 16
|
| I am not aware, when it started last time. But there was no change from MQ Side. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Oct 24, 2010 8:49 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Upgrade to 7.0.1.3 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mvic |
| Posted: Tue Oct 26, 2010 5:11 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| someonesumit wrote: |
| I tried clearing the ipcs also, but it didn't work. |
That sometimes (rarely) helps, and sometimes makes matters worse than they were before.
I suggest you open a PMR and ask IBM support to investigate this problem. |
|
| Back to top |
|
|
| John89011 |
| Posted: Tue Oct 26, 2010 9:57 am Post subject: |
|
|
Voyager
Joined: 15 Apr 2009
Posts: 94
|
| Is your server clustered (node0, node1)? If so then I think your system might have done a partial failover where the file system was not mounted properly so when you check the QM status on node0 you might see 'running elsewhere' and on node1 you'll see 'QM not available' |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Oct 26, 2010 11:14 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| John89011 wrote: |
| Is your server clustered (node0, node1)? If so then I think your system might have done a partial failover where the file system was not mounted properly so when you check the QM status on node0 you might see 'running elsewhere' and on node1 you'll see 'QM not available' |
The OP stated "...queue manager is not setup to run as Multi instance queue manager..." in the first post in the thread 
_________________
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 |
|
|
| Shuyin |
| Posted: Fri Jan 11, 2013 9:07 am Post subject: |
|
|
Novice
Joined: 26 Jul 2012
Posts: 23
|
| someonesumit wrote: |
| I am not aware, when it started last time. But there was no change from MQ Side. |
Hi someonesumit!!
are you still having that issue? |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jan 11, 2013 10:02 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Shuyin wrote: |
| are you still having that issue? |
As I said here, in the 3 years since this thread was active a solution has probably been found.
Why are you randomly posting questions on old threads?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
