| Author |
Message
|
| Al Pacino |
 Posted: Tue Sep 27, 2005 5:53 am Post subject: Changing location of the log |
 |
|
Centurion
Joined: 19 Aug 2005
Posts: 114
|
Hello all,
We ran into a space issue yesterday and had to move the log for the Queue Manger to a different directory. All I did was stop all the “amq” services (the QM was already failed in the Cluster admin), run the hamvmqm command moving the logs form M:\mqm and M:\mqm\log to E:\mqm and E:\mqm\log.
After that I tried to start and it would not start. Do I need to clean the somthing in the registry ? or Do I need to delete it from the cluster admin and add it again?
I am using websphere MQ 5.3 on a windows 2000 ( clusterd environment ) CSD 10
thanks
_________________
"We can't solve problems by using the same kind of thinking we used
when we created them." |
|
| Back to top |
|
 |
| wschutz |
| Posted: Tue Sep 27, 2005 6:02 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
|
| Back to top |
|
|
| Al Pacino |
| Posted: Tue Sep 27, 2005 6:15 am Post subject: |
|
|
Centurion
Joined: 19 Aug 2005
Posts: 114
|
I followed exactlly the steps provided in the links you posted. I am getting the following error every time I try to start the QM :
Error code 2 starting QM/Queue Manger WebSphere MQ service.
The service was unable to start QM/Queue Manger. The error message reported was as follows: AMQ7002: An error occured mainpulating a file.
Use WebSphere MQ Services to investigate why the service couldn't begin. If recovery for this service is active, MQ will attempt to recover.
_________________
"We can't solve problems by using the same kind of thinking we used
when we created them." |
|
| Back to top |
|
|
| Al Pacino |
| Posted: Tue Sep 27, 2005 6:23 am Post subject: |
|
|
Centurion
Joined: 19 Aug 2005
Posts: 114
|
Also, I noticed when I log under windows registery , I see the log path pointing to the old location .
_________________
"We can't solve problems by using the same kind of thinking we used
when we created them." |
|
| Back to top |
|
|
| hopsala |
| Posted: Tue Sep 27, 2005 6:27 am Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
| Al Pacino wrote: |
| Also, I noticed when I log under windows registery , I see the log path pointing to the old location . |
Well, then the problem is pretty much obvious now isn't it?
You'll have to hamvmqm the files back to their original location, or manually change the registry to solve this prob. |
|
| Back to top |
|
|
| Al Pacino |
| Posted: Tue Sep 27, 2005 6:49 am Post subject: |
|
|
Centurion
Joined: 19 Aug 2005
Posts: 114
|
After updating the registry , I started seeing the following error when trying to start the QM :
Error code 25 starting QM/Queue Manger WebSphere MQ service.
The service was unable to start QM/Queue Manger. The error message reported was as follows: AMQ7019: An error occurred while creating the directory structure for the new queue manger.
Use WebSphere MQ Services to investigate why the service couldn't begin. If recovery for this service is active, MQ will attempt to recover.
_________________
"We can't solve problems by using the same kind of thinking we used
when we created them." |
|
| Back to top |
|
|
| hopsala |
| Posted: Tue Sep 27, 2005 7:30 am Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
Well yea, that happend to me once; my advice? You have two options:
A. Delete the qm, making sure manually all dirs were removed, and recreate it from a saveqmgr backup (I hope you have one...). If you ask me this will probably be less time consuming.
B. If you feel that this is personal, and you are not willing to give up, start improvising. There is no real procedure to solving this - try using hamv to move files back, try deleting the logs and recreating them, try other things that I can't think of from where i'm sitting.
Cry Havoc, and set loose the dogs of War! |
|
| Back to top |
|
|
| Al Pacino |
| Posted: Tue Sep 27, 2005 10:25 am Post subject: |
|
|
Centurion
Joined: 19 Aug 2005
Posts: 114
|
I have update the registry to point to drive E where I moved the log but somewhere WebSphere is still looking at the M drive , here is the error I am seeing now :
AMQ6119: An internal WebSphere MQ error has occurred (rc=2: stat:
M:\mqm\qmgrs\QM\@ipcc\.
EXPLANATION:
MQ detected an unexpected error when calling the operating system. The MQ error
recording routine has been called.
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.
It shouldn't look into the M drive ,, any Idea why it is still looking there ?
_________________
"We can't solve problems by using the same kind of thinking we used
when we created them." |
|
| Back to top |
|
|
| hopsala |
| Posted: Tue Sep 27, 2005 10:29 am Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
| Al Pacino wrote: |
| M:\mqm\qmgrs\QM\@ipcc\. |
I don't know what you did, but it seems to me it's not looking for the logs at all, but for the channel table...
As previously stated, I think your qm is buggered, take a moment of silence of gentle memory for QMs-past, and create a new one (preferably with a new name, trust me on this one) |
|
| Back to top |
|
|
| Al Pacino |
| Posted: Tue Sep 27, 2005 11:59 am Post subject: |
|
|
Centurion
Joined: 19 Aug 2005
Posts: 114
|
hopsala,
thanks so much for all the help. I found the issue to do with the cluster admin. I have to delete the resource for the QM from the cluster admin b/c for some reason it was making the registry look at the old drive. I restarted the services and the QM is up and running fine and pointing to the correct log.
_________________
"We can't solve problems by using the same kind of thinking we used
when we created them." |
|
| Back to top |
|
|
| hopsala |
| Posted: Tue Sep 27, 2005 12:11 pm Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
| Good, glad to hear; but for the record, what is this "cluster admin" you speak of? Do you mean the MSCS administration console or something similar? |
|
| Back to top |
|
|
| Al Pacino |
| Posted: Tue Sep 27, 2005 12:58 pm Post subject: |
|
|
Centurion
Joined: 19 Aug 2005
Posts: 114
|
It is the MSCS administration console
_________________
"We can't solve problems by using the same kind of thinking we used
when we created them." |
|
| Back to top |
|
|
| hopsala |
| Posted: Tue Sep 27, 2005 1:13 pm Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
Ah, you're using MSCS, so THAT's the reason it didn't work - why didn't you say so in the first place?
What the manual does not say (nor does wayne's post) is that you have to issue the command "haregtyp /r" and reboot before you use hamvmqm, otherwise all hell breaks loose. See the very end of chapter 13 in System Admin Guide for (very few and inappropriate) details. Did you issue this command?
The exact same thing happened to me in the past when trying to set up mq on MSCS, I learned the solution the hard way... |
|
| Back to top |
|
|
|
|
