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 Index » IBM MQ Installation/Configuration Support » MQ install - clone/ Copy

Post new topic  Reply to topic
 MQ install - clone/ Copy « View previous topic :: View next topic » 
Author Message
mqrock
PostPosted: Wed Feb 23, 2011 4:15 am    Post subject: MQ install - clone/ Copy Reply with quote

Newbie

Joined: 23 Feb 2011
Posts: 3

Hello

Need your help. I have a working server where qmgrs are running fine. We needed another server at another location in a short span. We build a new linux servers ( everything is same ) and copied the /var/mqm ,/opt/mqm from working server to new server. Validation looks just fine but when I start queue manager...it starts and creashes in few seconds. I know I should not colne ..but it is the need I have and no time in had. your help is greatly appreciated.

/opt/mqm> strmqm testqmgr
WebSphere MQ queue manager 'testqmgr' starting.
102 log records accessed on queue manager 'testqmgr' during the log replay phase.
Log replay for queue manager 'testqmgr' complete.
Transaction manager state recovered for queue manager 'testqmgr'.
WebSphere MQ queue manager 'testqmgr' started.
:/opt/mqm> dspmq
QMNAME(testqmgr) STATUS(Running)
:/opt/mqm> dspmq
QMNAME(testqmgr) STATUS(Ending preemptively)

ERROR LOG:


EXPLANATION:
An internal error has occurred with identifier 20806105. This message is
issued in association with other messages.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcx.c : 768 --------------------------------------------------------
02/23/2011 05:54:04 AM - Process(13246.1) User(mqm) Program(amqzxma0)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager testqmgr.

EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 13246.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcx.c : 807 --------------------------------------------------------

FDC log:

+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Wednesday February 23 05:53:43 CST 2011 |
| Host Name :- npectlvmqm01 (Linux 2.6.16.60-0.21-default) |
| PIDS :- 5724H7210 |
| LVLS :- 6.0.2.9 |
| Product Long Name :- WebSphere MQ for Linux (x86-64 platform) |
| Vendor :- IBM |
| Probe Id :- XC337090 |
| Application Name :- MQM |
| Component :- xlsLateEventAllocation |
| SCCS Info :- lib/cs/unix/linux_2/amqxlfsx.c, 1.74.1.14 |
| Line Number :- 4862 |
| Build Date :- Mar 16 2010 |
| CMVC level :- p600-209-100316 |
| Build Type :- IKAP - (Production) |
| UserID :- 00010002 (mqm) |
| Program Name :- amqzxma0 |
| Addressing mode :- 64-bit |
| Process :- 13246 |
| Thread-Process :- 13246 |
| Thread :- 5 |
| ThreadingModel :- PosixThreads |
| ConnId(1) IPCC :- 3 |
| Last HQC :- 1.0.0-421560 |
| Last HSHMEMB :- 0.0.0-0 |
| Major Errorcode :- STOP |
| Minor Errorcode :- OK |
| Probe Type :- HALT6109 |
| Probe Severity :- 1 |
| Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| |
+-----------------------------------------------------------------------------+

MQM Function Stack
xstSubpoolSubtask
xcsWaitEventSem
xlsWaitEvent
xlsLateEventAllocation
xcsFFST

MQM Trace History
{ xppInitialiseDestructorRegistrations
} xppInitialiseDestructorRegistrations rc=OK
{ xcsInitialize
-{ xcsRequestThreadMutexSem
-} xcsRequestThreadMutexSem rc=OK
-{ xcsRequestThreadMutexSem
-} xcsRequestThreadMutexSem rc=OK
-{ xcsReleaseThreadMutexSem
-} xcsReleaseThreadMutexSem rc=OK
-{ xcsGetEnvironmentString
-} xcsGetEnvironmentString rc=xecE_E_ENV_VAR_NOT_FOUND
-{ xcsReleaseThreadMutexSem
-} xcsReleaseThreadMutexSem rc=OK
} xcsInitialize rc=OK
{ xstSubpoolSubtask
-{ xcsInitialize
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsStartPersistentTimerThread
--} xcsStartPersistentTimerThread rc=OK
--{ xcsConnectExistingSharedSubpool
---{ xcsAllocateQuickCell
---} xcsAllocateQuickCell rc=OK
---{ xlsThreadInitialization
----{ xcsAllocateQuickCell
----} xcsAllocateQuickCell rc=OK
---} xlsThreadInitialization rc=OK
---{ xcsConnectSharedMemSet
----{ xcsRequestThreadMutexSem
----} xcsRequestThreadMutexSem rc=OK
----{ xcsRequestThreadMutexSem
----} xcsRequestThreadMutexSem rc=OK
----{ xcsReleaseThreadMutexSem
----} xcsReleaseThreadMutexSem rc=OK
----{ xcsGetMem
----} xcsGetMem rc=OK
----{ xcsReleaseThreadMutexSem
----} xcsReleaseThreadMutexSem rc=OK
---} xcsConnectSharedMemSet rc=OK
--} xcsConnectExistingSharedSubpool rc=OK
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsReleaseThreadMutexSem
--} xcsReleaseThreadMutexSem rc=OK
--{ xcsGetEnvironmentString
--} xcsGetEnvironmentString rc=xecE_E_ENV_VAR_NOT_FOUND
--{ xcsReleaseThreadMutexSem
--} xcsReleaseThreadMutexSem rc=OK
-} xcsInitialize rc=OK
-{ xcsCreateEventSem
--{ xlsCreateEvent
---{ xcsAllocateQuickCell
---} xcsAllocateQuickCell rc=OK
---{ xllSpinLockInit
---} xllSpinLockInit rc=OK
--} xlsCreateEvent rc=OK
-} xcsCreateEventSem rc=OK
-{ xcsCreateEventSem
--{ xlsCreateEvent
---{ xcsAllocateQuickCell
---} xcsAllocateQuickCell rc=OK
---{ xllSpinLockInit
---} xllSpinLockInit rc=OK
--} xlsCreateEvent rc=OK
-} xcsCreateEventSem rc=OK
-{ xcsWaitEventSem
--{ xlsWaitEvent
---{ xlsLateEventAllocation
----{ xcsGetpwuid
----} xcsGetpwuid rc=OK
----{ xcsGetMem
----} xcsGetMem rc=OK
----{ xcsGetgrgid
----} xcsGetgrgid rc=Unknown(FFFF)
----{ xcsBuildDumpPtr
-----{ xcsGetMem
-----} xcsGetMem rc=OK
----} xcsBuildDumpPtr rc=OK
----{ xcsBuildDumpPtr
----} xcsBuildDumpPtr rc=OK
----{ xcsFFST
Back to top
View user's profile Send private message
exerk
PostPosted: Wed Feb 23, 2011 4:27 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

Google the Probe ID (there's a few hits) and don't post what is below the FDC header, it's only of use to the labs support people. As far as I'm concerned you got what you deserve by trying to short-cut but at least it's a salutary lesson about what you think may save time will actually end up costing you more. Far better to have done an install, saveqmgr 'back-up', and saveqmgr 'restore'.
_________________
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
View user's profile Send private message
Vitor
PostPosted: Wed Feb 23, 2011 5:37 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

exerk wrote:
Far better to have done an install, saveqmgr 'back-up', and saveqmgr 'restore'.




I'm obviously sorry it's blown up in your face, but even if your method had worked you'd have ended up with an identically named queue manager (which isn't a good idea, 2 same named queue managers in one estate), you would have probably had to rename it for business reasons (one's Dev, one's Test for instance), discovered you can't and then found that it had all the same connection & IP information cloned across and you had to edit it all manually.

Whereas using saveqmgr a few deft search & replace with the text editor of your choice and that's the connection information changed. The queue manager name problem solves itself and if you're cloning multiple machines you've got a reusable script that, once the cloning is done, could be used when you need to build an unrelated queue manager.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
mqrock
PostPosted: Wed Feb 23, 2011 6:35 am    Post subject: MQ install - clone/ Copy Reply with quote

Newbie

Joined: 23 Feb 2011
Posts: 3

You were truly correct. I agree that I should not do this ...I would strongly encourage others not to copy and expect to run. I re-ran the instal and all is well now.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Installation/Configuration Support » MQ install - clone/ Copy
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.