ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum IndexGeneral IBM MQ Supportstrmqm leading to STATUS(Ending preemptively)

Post new topicReply to topic Goto page 1, 2  Next
strmqm leading to STATUS(Ending preemptively) View previous topic :: View next topic
Author Message
yanaK
PostPosted: Tue Jul 14, 2020 6:42 pm Post subject: strmqm leading to STATUS(Ending preemptively) Reply with quote

Acolyte

Joined: 28 May 2020
Posts: 68

Hi

I am trying to start my queue manager and within few seconds seeing STATUS(Ending preemptively) and then it ends. I see this in the AMQERR01.LOG:

07/14/2020 07:07:38 PM - Process(5683.1) User(mqm) Program(amqrrmfa)
Host(t569) Installation(Installation1)
VRMF(7.1.0.1) QMgr(MQPSEA)
Code:

AMQ9410: Repository manager started.

EXPLANATION:
The repository manager started successfully.
ACTION:
None.
-------------------------------------------------------------------------------
07/14/2020 07:07:38 PM - Process(5655.1) User(mqm) Program(amqzxma0)
                    Host(t569) Installation(Installation1)
                    VRMF(7.1.0.1) QMgr(MQPSEA)

AMQ5008: An essential WebSphere MQ process 5683 (amqrrmfa) cannot be found and
is assumed to be terminated.

EXPLANATION:
1) A user has inadvertently terminated the process. 2) The system is low on
resources.  Some operating systems terminate processes to free resources.  If
your system is low on resources, it is possible it has terminated the process
so that a new process can be created.
ACTION:
WebSphere MQ will stop all MQ processes.  Inform your systems administrator.
When the problem is rectified WebSphere MQ can be restarted.
----- amqzxmb0.c : 9914 -------------------------------------------------------
07/14/2020 07:07:38 PM - Process(5682.9) User(mqm) Program(amqzmuf0)
                    Host(t569) Installation(Installation1)
                    VRMF(7.1.0.1) QMgr(MQPSEA)

AMQ5976: 'WebSphere MQ Distributed Pub/Sub Command Task' has ended.

EXPLANATION:
'WebSphere MQ Distributed Pub/Sub Command Task' has ended.
ACTION:

-------------------------------------------------------------------------------
07/14/2020 07:07:38 PM - Process(5682.10) User(mqm) Program(amqzmuf0)
                    Host(t569) Installation(Installation1)
                    VRMF(7.1.0.1) QMgr(MQPSEA)

AMQ5976: 'WebSphere MQ Distributed Pub/Sub Publish Task' has ended.

EXPLANATION:
'WebSphere MQ Distributed Pub/Sub Publish Task' has ended.
ACTION:

-------------------------------------------------------------------------------
07/14/2020 07:07:40 PM - Process(5682.8) User(mqm) Program(amqzmuf0)
                    Host(t569) Installation(Installation1)
                    VRMF(7.1.0.1) QMgr(MQPSEA)

AMQ5976: 'WebSphere MQ Distributed Pub/Sub Fan Out Task' has ended.

EXPLANATION:
'WebSphere MQ Distributed Pub/Sub Fan Out Task' has ended.
ACTION:

-------------------------------------------------------------------------------
07/14/2020 07:07:40 PM - Process(5682.7) User(mqm) Program(amqzmuf0)
                    Host(t569) Installation(Installation1)
                    VRMF(7.1.0.1) QMgr(MQPSEA)

AMQ5976: 'WebSphere MQ Distributed Pub/Sub Controller' has ended.

EXPLANATION:
'WebSphere MQ Distributed Pub/Sub Controller' has ended.
ACTION:

-------------------------------------------------------------------------------
07/14/2020 07:08:26 PM - Process(5655.1) User(mqm) Program(amqzxma0)
                    Host(t569) Installation(Installation1)
                    VRMF(7.1.0.1) QMgr(MQPSEA)

AMQ8004: WebSphere MQ queue manager 'MQPSEA' ended.

EXPLANATION:
WebSphere MQ queue manager 'MQPSEA' ended.
ACTION:
None.


I ran df -k in /var/mqm and saw max Use% is 85. I increased the primary log to 4 from 3 and secondary log to 6 from 5 (using circular logging) and rebooted the server. No luck.

I see 4 distinct Probe Ids (8 FDC files were generated):

| Probe Id :- XC130004
| Probe Id :- ZX086131
| Probe Id :- ZX085131
| Probe Id :- ZX005025

Not sure what else to do?

Please help.

Thanks
YanaK
Back to top
View user's profile Send private message
hughson
PostPosted: Tue Jul 14, 2020 9:36 pm Post subject: Re: strmqm leading to STATUS(Ending preemptively) Reply with quote

Grand Master

Joined: 09 May 2013
Posts: 1464
Location: Bay of Plenty, New Zealand

yanaK wrote:
Code:
-------------------------------------------------------------------------------
07/14/2020 07:07:38 PM - Process(5655.1) User(mqm) Program(amqzxma0)
                    Host(t569) Installation(Installation1)
                    VRMF(7.1.0.1) QMgr(MQPSEA)

AMQ5008: An essential WebSphere MQ process 5683 (amqrrmfa) cannot be found and
is assumed to be terminated.

EXPLANATION:
1) A user has inadvertently terminated the process. 2) The system is low on
resources.  Some operating systems terminate processes to free resources.  If
your system is low on resources, it is possible it has terminated the process
so that a new process can be created.
ACTION:
WebSphere MQ will stop all MQ processes.  Inform your systems administrator.
When the problem is rectified WebSphere MQ can be restarted.


I see 4 distinct Probe Ids (8 FDC files were generated):

| Probe Id :- XC130004
| Probe Id :- ZX086131
| Probe Id :- ZX085131
| Probe Id :- ZX005025


I assume some of these FDC files describe why the amqrrmfa (Cluster Repository Manager) process ended abnormally?

Can you run ffstsummary at least, give us a clue what the FDCs are about?

Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software
Back to top
View user's profile Send private message Visit poster's website
yanaK
PostPosted: Tue Jul 14, 2020 9:41 pm Post subject: Reply with quote

Acolyte

Joined: 28 May 2020
Posts: 68

Code:
AMQ3884.0.FDC  2020/07/14 19:04:45.794783-7 Installation1 amqrrmfa  3884        1 XC130004 xehExceptionHandler            STOP                           OK
 AMQ3850.0.FDC  2020/07/14 19:04:47.162173-7 Installation1 amqzxma0  3850        1 ZX005025 zxcProcessChildren             zrcX_PROCESS_MISSING           OK
 AMQ3875.1.FDC  2020/07/14 19:05:34.446889-7 Installation1 amqzmur0  3875        1 ZX086131 amqzmur0                       zrcE_UNEXPECTED_ERROR          OK
 AMQ3875.1.FDC  2020/07/14 19:05:34.460979-7 Installation1 amqzmur0  3875        2 ZX086131 amqzmur0                       OK                             OK
 AMQ3875.1.FDC  2020/07/14 19:05:34.465873-7 Installation1 amqzmur0  3875        3 ZX086131 amqzmur0                       OK                             OK
 AMQ3875.1.FDC  2020/07/14 19:05:34.470569-7 Installation1 amqzmur0  3875        4 ZX086131 amqzmur0                       OK                             OK
 AMQ3875.1.FDC  2020/07/14 19:05:34.480227-7 Installation1 amqzmur0  3875        5 ZX086131 amqzmur0                       OK                             OK
 AMQ3875.1.FDC  2020/07/14 19:05:34.494748-7 Installation1 amqzmur0  3875        6 ZX086131 amqzmur0                       OK                             OK
 AMQ3875.1.FDC  2020/07/14 19:05:34.508939-7 Installation1 amqzmur0  3875        7 ZX086131 amqzmur0                       OK                             OK
 AMQ3860.0.FDC  2020/07/14 19:05:34.527200-7 Installation1 amqzmuc0  3860        1 ZX085131 amqzmuc0                       zrcE_UNEXPECTED_ERROR          OK
 AMQ3860.0.FDC  2020/07/14 19:05:34.537821-7 Installation1 amqzmuc0  3860        2 ZX085131 amqzmuc0                       OK                             OK
 AMQ3860.0.FDC  2020/07/14 19:05:34.544538-7 Installation1 amqzmuc0  3860        3 ZX085131 amqzmuc0                       OK                             OK
 AMQ3860.0.FDC  2020/07/14 19:05:34.548960-7 Installation1 amqzmuc0  3860        4 ZX085131 amqzmuc0                       OK                             OK
 AMQ3860.0.FDC  2020/07/14 19:05:34.561632-7 Installation1 amqzmuc0  3860        5 ZX085131 amqzmuc0                       OK                             OK
 AMQ3860.0.FDC  2020/07/14 19:05:34.575213-7 Installation1 amqzmuc0  3860        6 ZX085131 amqzmuc0                       OK                             OK
 AMQ3860.0.FDC  2020/07/14 19:05:34.587412-7 Installation1 amqzmuc0  3860        7 ZX085131 amqzmuc0                       OK                             OK
 AMQ3860.0.FDC  2020/07/14 19:05:34.597694-7 Installation1 amqzmuc0  3860        8 ZX085131 amqzmuc0                       OK                             OK
 AMQ3860.0.FDC  2020/07/14 19:05:34.607962-7 Installation1 amqzmuc0  3860        9 ZX085131 amqzmuc0                       OK                             OK
 AMQ3860.0.FDC  2020/07/14 19:05:34.618114-7 Installation1 amqzmuc0  3860       10 ZX085131 amqzmuc0                       OK                             OK
 AMQ3860.0.FDC  2020/07/14 19:05:34.628255-7 Installation1 amqzmuc0  3860       11 ZX085131 amqzmuc0                       OK                             OK
 AMQ3860.0.FDC  2020/07/14 19:05:34.638425-7 Installation1 amqzmuc0  3860       12 ZX085131 amqzmuc0                       OK                             OK
 AMQ3860.0.FDC  2020/07/14 19:05:34.650603-7 Installation1 amqzmuc0  3860       13 ZX085131 amqzmuc0                       OK                             OK
 AMQ3860.0.FDC  2020/07/14 19:05:34.660993-7 Installation1 amqzmuc0  3860       14 ZX085131 amqzmuc0                       OK                             OK
 AMQ3860.0.FDC  2020/07/14 19:05:34.671087-7 Installation1 amqzmuc0  3860       15 ZX085131 amqzmuc0                       OK                             OK
 AMQ3860.0.FDC  2020/07/14 19:05:34.681312-7 Installation1 amqzmuc0  3860       16 ZX085131 amqzmuc0                       OK                             OK
 AMQ3860.0.FDC  2020/07/14 19:05:34.697562-7 Installation1 amqzmuc0  3860       17 ZX085131 amqzmuc0                       OK                             OK
 AMQ3860.0.FDC  2020/07/14 19:05:34.711243-7 Installation1 amqzmuc0  3860       18 ZX085131 amqzmuc0                       OK                             OK
 AMQ3860.0.FDC  2020/07/14 19:05:34.725149-7 Installation1 amqzmuc0  3860       19 ZX085131 amqzmuc0                       OK                             OK
 AMQ3860.0.FDC  2020/07/14 19:05:34.738601-7 Installation1 amqzmuc0  3860       20 ZX085131 amqzmuc0                       OK                             OK
 AMQ3860.0.FDC  2020/07/14 19:05:34.752341-7 Installation1 amqzmuc0  3860       21 ZX085131 amqzmuc0                       OK                             OK
 AMQ3860.0.FDC  2020/07/14 19:05:34.768204-7 Installation1 amqzmuc0  3860       22 ZX085131 amqzmuc0                       OK                             OK
 AMQ5683.0.FDC  2020/07/14 19:07:38.467932-7 Installation1 amqrrmfa  5683        1 XC130004 xehExceptionHandler            STOP                           OK
 AMQ5655.0.FDC  2020/07/14 19:07:38.762211-7 Installation1 amqzxma0  5655        1 ZX005025 zxcProcessChildren             zrcX_PROCESS_MISSING           OK
 AMQ5680.0.FDC  2020/07/14 19:08:26.172609-7 Installation1 amqzmur0  5680        1 ZX086131 amqzmur0                       zrcE_UNEXPECTED_ERROR          OK
 AMQ5680.0.FDC  2020/07/14 19:08:26.200308-7 Installation1 amqzmur0  5680        2 ZX086131 amqzmur0                       OK                             OK
 AMQ5680.0.FDC  2020/07/14 19:08:26.217636-7 Installation1 amqzmur0  5680        3 ZX086131 amqzmur0                       OK                             OK
 AMQ5680.0.FDC  2020/07/14 19:08:26.234832-7 Installation1 amqzmur0  5680        4 ZX086131 amqzmur0                       OK                             OK
 AMQ5680.0.FDC  2020/07/14 19:08:26.257326-7 Installation1 amqzmur0  5680        5 ZX086131 amqzmur0                       OK                             OK
 AMQ5680.0.FDC  2020/07/14 19:08:26.284681-7 Installation1 amqzmur0  5680        6 ZX086131 amqzmur0                       OK                             OK
 AMQ5680.0.FDC  2020/07/14 19:08:26.311337-7 Installation1 amqzmur0  5680        7 ZX086131 amqzmur0                       OK                             OK
 AMQ5665.0.FDC  2020/07/14 19:08:26.341323-7 Installation1 amqzmuc0  5665        1 ZX085131 amqzmuc0                       zrcE_UNEXPECTED_ERROR          OK
 AMQ5665.0.FDC  2020/07/14 19:08:26.365050-7 Installation1 amqzmuc0  5665        2 ZX085131 amqzmuc0                       OK                             OK
 AMQ5665.0.FDC  2020/07/14 19:08:26.382551-7 Installation1 amqzmuc0  5665        3 ZX085131 amqzmuc0                       OK                             OK
 AMQ5665.0.FDC  2020/07/14 19:08:26.399656-7 Installation1 amqzmuc0  5665        4 ZX085131 amqzmuc0                       OK                             OK
 AMQ5665.0.FDC  2020/07/14 19:08:26.424520-7 Installation1 amqzmuc0  5665        5 ZX085131 amqzmuc0                       OK                             OK
 AMQ5665.0.FDC  2020/07/14 19:08:26.453076-7 Installation1 amqzmuc0  5665        6 ZX085131 amqzmuc0                       OK                             OK
 AMQ5665.0.FDC  2020/07/14 19:08:26.476744-7 Installation1 amqzmuc0  5665        7 ZX085131 amqzmuc0                       OK                             OK
 AMQ5665.0.FDC  2020/07/14 19:08:26.500388-7 Installation1 amqzmuc0  5665        8 ZX085131 amqzmuc0                       OK                             OK
 AMQ5665.0.FDC  2020/07/14 19:08:26.523800-7 Installation1 amqzmuc0  5665        9 ZX085131 amqzmuc0                       OK                             OK
 AMQ5665.0.FDC  2020/07/14 19:08:26.547566-7 Installation1 amqzmuc0  5665       10 ZX085131 amqzmuc0                       OK                             OK
 AMQ5665.0.FDC  2020/07/14 19:08:26.571547-7 Installation1 amqzmuc0  5665       11 ZX085131 amqzmuc0                       OK                             OK
 AMQ5665.0.FDC  2020/07/14 19:08:26.595087-7 Installation1 amqzmuc0  5665       12 ZX085131 amqzmuc0                       OK                             OK
 AMQ5665.0.FDC  2020/07/14 19:08:26.620416-7 Installation1 amqzmuc0  5665       13 ZX085131 amqzmuc0                       OK                             OK
 AMQ5665.0.FDC  2020/07/14 19:08:26.643714-7 Installation1 amqzmuc0  5665       14 ZX085131 amqzmuc0                       OK                             OK
 AMQ5665.0.FDC  2020/07/14 19:08:26.666947-7 Installation1 amqzmuc0  5665       15 ZX085131 amqzmuc0                       OK                             OK
 AMQ5665.0.FDC  2020/07/14 19:08:26.689955-7 Installation1 amqzmuc0  5665       16 ZX085131 amqzmuc0                       OK                             OK
 AMQ5665.0.FDC  2020/07/14 19:08:26.718390-7 Installation1 amqzmuc0  5665       17 ZX085131 amqzmuc0                       OK                             OK
 AMQ5665.0.FDC  2020/07/14 19:08:26.745017-7 Installation1 amqzmuc0  5665       18 ZX085131 amqzmuc0                       OK                             OK
 AMQ5665.0.FDC  2020/07/14 19:08:26.771235-7 Installation1 amqzmuc0  5665       19 ZX085131 amqzmuc0                       OK                             OK
 AMQ5665.0.FDC  2020/07/14 19:08:26.797534-7 Installation1 amqzmuc0  5665       20 ZX085131 amqzmuc0                       OK                             OK
 AMQ5665.0.FDC  2020/07/14 19:08:26.823594-7 Installation1 amqzmuc0  5665       21 ZX085131 amqzmuc0                       OK                             OK
 AMQ5665.0.FDC  2020/07/14 19:08:26.849896-7 Installation1 amqzmuc0  5665       22 ZX085131 amqzmuc0                       OK                             OK


Quote:
I assume some of these FDC files describe why the amqrrmfa (Cluster Repository Manager) process ended abnormally?


Is there a quick way to find?
Back to top
View user's profile Send private message
hughson
PostPosted: Tue Jul 14, 2020 9:48 pm Post subject: Reply with quote

Grand Master

Joined: 09 May 2013
Posts: 1464
Location: Bay of Plenty, New Zealand

yanaK wrote:
Code:
 AMQ3884.0.FDC  2020/07/14 19:04:45.794783-7 Installation1 amqrrmfa  3884        1 XC130004 xehExceptionHandler            STOP                           OK
 AMQ5683.0.FDC  2020/07/14 19:07:38.467932-7 Installation1 amqrrmfa  5683        1 XC130004 xehExceptionHandler            STOP                           OK


Quote:
I assume some of these FDC files describe why the amqrrmfa (Cluster Repository Manager) process ended abnormally?


Is there a quick way to find?

Most people would use something like grep to find the process name in question. I have snipped your ffstsummary output to show the two lines in question.

It would seem that you have two FDCs related to the amqrrmfa process. Perhaps you can now show us the FDC header for one of those - expect that they are both the same.

Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software
Back to top
View user's profile Send private message Visit poster's website
yanaK
PostPosted: Tue Jul 14, 2020 10:01 pm Post subject: Reply with quote

Acolyte

Joined: 28 May 2020
Posts: 68

Code:


+-----------------------------------------------------------------------------+
|                                                                             |
| WebSphere MQ First Failure Symptom Report                                   |
| =========================================                                   |
|                                                                             |
| Date/Time         :- Wed July 15 2020 02:07:38 GMT                          |
| UTC Time          :- 1594778858.467932                                      |
| UTC Time Offset   :- -420 (PST)                                             |
| Host Name         :- t569                                              |
| Operating System  :- Linux 2.6.18-423.el5                                   |
| PIDS              :- 5724H7230                                              |
| LVLS              :- 7.1.0.1                                                |
| Product Long Name :- WebSphere MQ for Linux (x86-64 platform)               |
| Vendor            :- IBM                                                    |
| Installation Path :- /opt/mqm                                               |
| Installation Name :- Installation1    (1)                                   |
| Probe Id          :- XC130004                                               |
| Application Name  :- MQM                                                    |
| Component         :- xehExceptionHandler                                    |
| SCCS Info         :- lib/cs/unix/amqxerrx.c, 1.253.1.1                      |
| Line Number       :- 1472                                                   |
| Build Date        :- May 16 2012                                            |
| CMVC level        :- p710-001-120516                                        |
| Build Type        :- IKAP - (Production)                                    |
| Effective UserID  :- 3732 (mqm)                                             |
| Real UserID       :- 3732 (mqm)                                             |
| Program Name      :- amqrrmfa                                               |
| Addressing mode   :- 64-bit                                                 |
| LANG              :- en_US.UTF-8                                            |
| Process           :- 5683                                                   |
| Process(Thread)   :- 5683                                                   |
| Thread            :- 1                                                      |
| ThreadingModel    :- PosixThreads                                           |
| QueueManager      :- MQPSEA                                               |
| UserApp           :- FALSE                                                  |
| ConnId(1) IPCC    :- 77                                                     |
| ConnId(2) QM      :- 40                                                     |
| Last HQC          :- 2.5.5-17704504                                         |
| Last HSHMEMB      :- 2.11.11-299616                                         |
| Major Errorcode   :- STOP                                                   |
| Minor Errorcode   :- OK                                                     |
| Probe Type        :- HALT6109                                               |
| Probe Severity    :- 1                                                      |
| Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred.  |
| FDCSequenceNumber :- 0                                                      |
| Arith1            :- 11 (0xb)                                               |
| Comment1          :- SIGSEGV: address not mapped(0x10)                      |
|                                                                             |
+-----------------------------------------------------------------------------+
Back to top
View user's profile Send private message
hughson
PostPosted: Tue Jul 14, 2020 10:11 pm Post subject: Reply with quote

Grand Master

Joined: 09 May 2013
Posts: 1464
Location: Bay of Plenty, New Zealand

Has anything changed recently on this machine? Did this just started happening, or has this queue manager never worked?

I would say it is time to open a case/PMR with IBM and send them the same information you have shown here as well as the full FDC file.

Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software
Back to top
View user's profile Send private message Visit poster's website
yanaK
PostPosted: Tue Jul 14, 2020 10:18 pm Post subject: Reply with quote

Acolyte

Joined: 28 May 2020
Posts: 68

It used to work a day back! I know it's a full repository queue manager and the cluster (it has 2 full repo am and 2 normal queues) was load tested 2 days back.

Is there any fix that I can try? (This is a test queue manager so its okay to lose data)
Back to top
View user's profile Send private message
hughson
PostPosted: Tue Jul 14, 2020 10:23 pm Post subject: Reply with quote

Grand Master

Joined: 09 May 2013
Posts: 1464
Location: Bay of Plenty, New Zealand

yanaK wrote:
It used to work a day back!

That's good information to know. Now what about whether anything has changed on this machine in between the last time it worked and the first time it failed?

yanaK wrote:
Is there any fix that I can try? (This is a test queue manager so its okay to lose data)

I did have a search for that probe ID, and found some APARs unrelated to the amqrrmfa process (i.e. a different problem but similar symptom) but they were all errors that required a product fix which is what led me to suggest you contact IBM.

Of course, if you don't care about the queue manager you could just delete it and start again (and then tell the rest of the cluster to forget about it as well since you wont' be able to take it out the cluster safely first if you can't start the queue manager!)

Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software
Back to top
View user's profile Send private message Visit poster's website
yanaK
PostPosted: Tue Jul 14, 2020 10:35 pm Post subject: Reply with quote

Acolyte

Joined: 28 May 2020
Posts: 68

Quote:
Of course, if you don't care about the queue manager you could just delete it and start again (and then tell the rest of the cluster to forget about it as well since you wont' be able to take it out the cluster safely first if you can't start the queue manager!)


So the steps will be:

1.Remove qm from other 3 qms in the cluster.
2.Delete qm.
3.Restore configs of deleted qm.
4. Start qm?

How to do 3?
Back to top
View user's profile Send private message
hughson
PostPosted: Tue Jul 14, 2020 10:40 pm Post subject: Reply with quote

Grand Master

Joined: 09 May 2013
Posts: 1464
Location: Bay of Plenty, New Zealand

yanaK wrote:
Quote:
Of course, if you don't care about the queue manager you could just delete it and start again (and then tell the rest of the cluster to forget about it as well since you wont' be able to take it out the cluster safely first if you can't start the queue manager!)


So the steps will be:

1.Remove qm from other 3 qms in the cluster.
2.Delete qm.
3.Restore configs of deleted qm.
4. Start qm?

How to do 3?

Do you have saved configs of the deleted queue manager?
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software
Back to top
View user's profile Send private message Visit poster's website
yanaK
PostPosted: Tue Jul 14, 2020 10:44 pm Post subject: Reply with quote

Acolyte

Joined: 28 May 2020
Posts: 68

I didn't delete it yet. No I didn't save any config - can you point me to a doc to do that?
Back to top
View user's profile Send private message
yanaK
PostPosted: Tue Jul 14, 2020 10:48 pm Post subject: Reply with quote

Acolyte

Joined: 28 May 2020
Posts: 68

Can it so happen that the destination queue had so much load that the source qm (this one) crashed (and not starting up)?

I see 3 of the qlocals in the destination queue has over 50k curdepth.
I'm cleaning them up.
Back to top
View user's profile Send private message
yanaK
PostPosted: Tue Jul 14, 2020 11:50 pm Post subject: Reply with quote

Acolyte

Joined: 28 May 2020
Posts: 68

I am trying to use dmpmqcfg to backup but I get:
AMQ8146: WebSphere MQ queue manager not available
Back to top
View user's profile Send private message
hughson
PostPosted: Wed Jul 15, 2020 2:03 am Post subject: Reply with quote

Grand Master

Joined: 09 May 2013
Posts: 1464
Location: Bay of Plenty, New Zealand

yanaK wrote:
I didn't delete it yet. No I didn't save any config - can you point me to a doc to do that?

I think you have found how to do this since one of your later questions mentions dmpmqcfg, but if you cannot start the queue manager, then you cannot back up the config. If you don't want to just delete it and start again, I would reiterate that you should contact IBM to see if you can discover what the issue is and get a fix to it.
yanaK wrote:
Can it so happen that the destination queue had so much load that the source qm (this one) crashed (and not starting up)?

I see 3 of the qlocals in the destination queue has over 50k curdepth.
I'm cleaning them up.

I don't see how full queues on another queue manager can possibly cause a process on this queue manager to abnormally end.

yanaK wrote:
I am trying to use dmpmqcfg to backup but I get:
AMQ8146: WebSphere MQ queue manager not available

This is telling you that you cannot use dmqmqcfg to back up the definitions on your queue manager unless it is running.

I really would reiterate that with an issue like this you should contact IBM to get assistance.

You never did answer what has changed on this machine in the time between when the queue manager last successfully started and now?

Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software
Back to top
View user's profile Send private message Visit poster's website
yanaK
PostPosted: Wed Jul 15, 2020 7:51 am Post subject: Reply with quote

Acolyte

Joined: 28 May 2020
Posts: 68

Thanks Morag. I'll reach out to them.
Back to top
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Goto page 1, 2  Next Page 1 of 2

MQSeries.net Forum IndexGeneral IBM MQ Supportstrmqm leading to STATUS(Ending preemptively)
Jump to:



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP


Theme by Dustin Baccetti
Powered by phpBB 2001, 2002 phpBB Group

Copyright MQSeries.net. All rights reserved.