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 » Need help with error when trying to create copy of MQ server

Post new topic  Reply to topic Goto page 1, 2  Next
 Need help with error when trying to create copy of MQ server « View previous topic :: View next topic » 
Author Message
sroach76
PostPosted: Thu Jan 04, 2007 7:42 am    Post subject: Need help with error when trying to create copy of MQ server Reply with quote

Novice

Joined: 11 Sep 2006
Posts: 15

I am trying to setup a secondary server exactly like our primary server with its MQ configuration. This is on AIX 5.2 and MQ 5.3 CSD7. I installed MQ 5.3 and copied over the /var/mqm, /usr/mqm and /home/mqm filesystems on the secondary server. MQver returns the same results for both servers and I see all the queues and qmgrs in the directories. But when I run dspmqm -s I get this error on the new server:

$ dspmq -s
QMNAME(%3)%4STATUS(Ended unexpectedly)
QMNAME(%3)%4STATUS(Ended unexpectedly)

I have confirmed the mqs.ini is exactly the same as the primary. What am I missing? Hopefully I don't have to recreate all the qmgrs and queues on the secondary server. Thanks for any help you can provide.
Back to top
View user's profile Send private message
bbburson
PostPosted: Thu Jan 04, 2007 7:46 am    Post subject: Reply with quote

Partisan

Joined: 06 Jan 2004
Posts: 378
Location: Nowhere near a queue manager

Find all copies of amq.cat on the old server and make sure they are in the same place(s) with the permisions on the new one.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Thu Jan 04, 2007 7:48 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Shouldn't you be using a real HACMP solution?
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
sroach76
PostPosted: Thu Jan 04, 2007 8:21 am    Post subject: Reply with quote

Novice

Joined: 11 Sep 2006
Posts: 15

Thanks, it looks like it might be a file permission issue. I have been told HACMP is too expensive for this project. The replication will be between two servers about 5000 miles away from each other so we are trying a WAN replication product to replicate the MQ messages. We thought about an MQ Cluster but the application guys don't want to make too many changes to the production environment.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Thu Jan 04, 2007 8:41 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

If you were running WMQ v6 you could use the "backup" queue manager options to solve this.

I would not expect a WAN replication product to be completely troublefree. In general, you can't take a consistent backup of a queue manager while it is running - and so doing file level replication is not going to be consistent either.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
sroach76
PostPosted: Thu Jan 04, 2007 9:32 am    Post subject: Reply with quote

Novice

Joined: 11 Sep 2006
Posts: 15

All of the file permissions are now correct and in sync and I don't see any differences from the amq.cat files. I still get this error:

dspmq -s
QMNAME(%3)%4STATUS(Ended unexpectedly)
QMNAME(%3)%4STATUS(Ended unexpectedly)

Any other ideas what could be wrong?
Back to top
View user's profile Send private message
mvic
PostPosted: Thu Jan 04, 2007 12:56 pm    Post subject: Reply with quote

Jedi

Joined: 09 Mar 2004
Posts: 2080

sroach76 wrote:
Any other ideas what could be wrong?

Debug this by running the program under control of the system trace utility "truss". The trace output from that tool will show what files are being loaded, and which can't be found. Compare with the trace output from the successful run on the other machine. Almost certainly there are symlinks or other files you're missing.

Some suggestions - intended to be helpful
1. do a proper install of MQ on the 2nd machine - this will ensure you get all the files in the right places (it's making extra work for you to plan the system the way that's described above - and the extra work will be required each time you update or apply maintenance)
2. it's highly recommended to be at a much more recent CSD than 7. That is a very old level of code now.
3. If you're intending using this secondary queue manager as a hot-failover system in the style of HACMP, but without using real HACMP, then sorry but this scheme is unlikely to work predictably in production. Jeff has said it, and I'm agreeing with him here.

What exactly are the requirements for this 2nd system?
Back to top
View user's profile Send private message
HubertKleinmanns
PostPosted: Thu Jan 04, 2007 11:29 pm    Post subject: Reply with quote

Shaman

Joined: 24 Feb 2004
Posts: 732
Location: Germany

Was the original QMgr running, when you copied the files?

I would not recommend, to clone an installation of MQ by copying the files in /usr/mqm - why did you not install with installp?

Then stop the original QMgr and copy the following files and directories from one system to another:

/var/mqm/mqs.ini
/var/mqm/log/<your_qmgr>
/var/mqm/qmgrs/<your_qmgr>

The QMgr should not be active, because otherwise the files in /var/mqm/log/<your_qmgr> and /var/mqm/qmgrs/<your_qmgr> may become out of sync.
_________________
Regards
Hubert
Back to top
View user's profile Send private message Visit poster's website
sroach76
PostPosted: Fri Jan 05, 2007 12:24 pm    Post subject: Reply with quote

Novice

Joined: 11 Sep 2006
Posts: 15

Thanks for the good replies guys. I have installed MQ 5.3 and CSD7 manually to the secondary server. I then stopped the MQ on the primary and was able to replicate the /var/mqm filesystem between the systems. Once this was done I have been able to startup the qmgrs on the secondary server. I also used the runmqlsr -t tcp -p 1414 -m QMGRNAME to startup the listener for one of the qmgrs. I am trying to run a basic test on the server of just putting a test message in a queue and then getting the message. I am trying to run this on the secondary server with MQ installed. I have tried:
amqsputc QUEUE QMGR_NAME. But I always get MQCONN ended with reason code 2058. Do I need to set the MQSSERVER value from this server when I run the amqput on the server itself? Thanks

To answer some of the other questions out there, we have recommended to our application team that they upgrade from CSD7 and they are investigating the changes now. I know HACMP is the best solution but have been told that is not an option due to cost. We are testing to see how a file level replication works. I know this might open up issues with the state of messages as the primary server crashed but at least if they have not been processed yet by MQ they should be on the secondary. Right now there is no failover so we are trying to improve things.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Fri Jan 05, 2007 4:46 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

You always need to supply a client connection channel definition when attempting to create a client connection.

Using MQSERVER is the simplest way to do this for applications that can use that environment variable.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
sroach76
PostPosted: Sun Jan 07, 2007 5:24 pm    Post subject: Reply with quote

Novice

Joined: 11 Sep 2006
Posts: 15

Thanks for the reply about the client connection. Can you provide any insight to what I am missing regarding the client connection configuration?

I am running on AIX with two queue mgrs. Both are started and one listener is on 1414, the other on 1415. I am logged into the server and have tried setting the MQSERVER variable different ways. I am not sure what to use for the CHANNEL value so I tried:

export MQSERVER=SYSTEM.DEF.SVRCONN/TCP/'localhost(1414)'
export MQSERVER=CHAN1/TCP/'localhost(1414)'

And I tried port 1415 as well. When I try the put I get this message:

mqm$ amqsputc KBC!APPL!WEI!Q9 WEIAOA
Sample AMQSPUT0 start
target queue is KBC!APPL!WEI!Q9
MQOPEN ended with reason code 2085
unable to open queue for output
Sample AMQSPUT0 end

The queue mgr and queue names are correct and the variable MQSERVER is getting set. What am I missing? Thanks guys.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Sun Jan 07, 2007 5:30 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

I think you didn't look up what 2085 meant.

You're connecting just fine, the problem occurs when the code tryies to MQOPEN the queue.

Make sure you have properly quoted your queue name to avoid any shell interpolation issues, and make sure you have put the queue name in the right place, and not in the place the qmgr name should go.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
HubertKleinmanns
PostPosted: Mon Jan 08, 2007 4:52 am    Post subject: Reply with quote

Shaman

Joined: 24 Feb 2004
Posts: 732
Location: Germany

sroach76,

a '!' sign is not a valid character for queue names. You have to specify the queue name as shown in (e. g.) runmqsc.

I guess, your queue name is KBC.APPL.WEI.Q9, which is stored in the filesystem in a directory called KBC!APPL!WEI!Q9. You must use the queue name - not the directory name.
_________________
Regards
Hubert
Back to top
View user's profile Send private message Visit poster's website
Vitor
PostPosted: Mon Jan 08, 2007 4:57 am    Post subject: Reply with quote

Grand High Poobah

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

sroach76 wrote:
I know this might open up issues with the state of messages as the primary server crashed but at least if they have not been processed yet by MQ they should be on the secondary.


Depends on the last time you took the primary down to copy the files across - as per previous comments on copying files from a running queue manager and why that doesn't work out too well.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
sroach76
PostPosted: Mon Jan 08, 2007 5:53 am    Post subject: Reply with quote

Novice

Joined: 11 Sep 2006
Posts: 15

Thanks for the tips. I was finally able to put and get a message on the server. I think it was an issue with the '!' I tried another queue named TEST and everything worked fine.

I hear what you are saying about file replication probably won't work but I want to test it just so I can be sure. I have tried putting a message in the TEST queue on the primary server and am replication the entire /var/mqm filesystem. But when I add this message manually with the amqsputc command I do not see the /var/mqm/qmgr/NAME/queues/TEST/q file change at all. The file size does not change and I do not see any difference in the q file. Is there somewhere else where the actual message is stored that I am missing or is this the main problem with trying to do file replication of MQ?
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page 1, 2  Next Page 1 of 2

MQSeries.net Forum Index » IBM MQ Installation/Configuration Support » Need help with error when trying to create copy of MQ server
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.