| Author |
Message
|
| jpardi |
 Posted: Mon Jul 09, 2007 8:19 am Post subject: Log not available message; but S0000000.LOG is there. |
 |
|
Newbie
Joined: 13 Oct 2004
Posts: 6
Location: Jersy City, NJ
|
This is an v5.3 Qmgr on Unix/Solaris. When I try to start the Qmgr I get the "Log not available" message, but I have a S0000000.LOG file in my /active directory.
I've read similar posts, but it seems that for the other posts, all the logs were deleted.
I did not delete these logs inadvertently; they seem to have disappeared after a reboot.
What can be done to get my Qmgr back up? I can't delete it and create a new one. |
|
| Back to top |
|
 |
| mrlinux |
| Posted: Mon Jul 09, 2007 10:02 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
How many log files do you normally have ????
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| jpardi |
| Posted: Mon Jul 09, 2007 10:20 am Post subject: |
|
|
Newbie
Joined: 13 Oct 2004
Posts: 6
Location: Jersy City, NJ
|
Three and I'm using circular logging. The log files are defined on EMC storage.
Joan |
|
| Back to top |
|
|
| mrlinux |
| Posted: Mon Jul 09, 2007 10:28 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
So do you have all 3 log files or just the one ????
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| jpardi |
| Posted: Mon Jul 09, 2007 10:50 am Post subject: |
|
|
Newbie
Joined: 13 Oct 2004
Posts: 6
Location: Jersy City, NJ
|
| I have only one now, since the machine was rebooted, and am unable to start the Qmgr. Normally, I should have three |
|
| Back to top |
|
|
| mrlinux |
| Posted: Mon Jul 09, 2007 10:51 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Well here is a method I have used
1) Create a new qmgr with the same name on a different system, with the same log settings size/number (hopefully the server has the same UID/GID)
2) tar up the log directory and move it to the broken qmgr. and untar it.
Permissions must be the same as before, IF UID and GID are the same you are ok.
3) start the qmgr.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| jpardi |
| Posted: Mon Jul 09, 2007 11:22 am Post subject: |
|
|
Newbie
Joined: 13 Oct 2004
Posts: 6
Location: Jersy City, NJ
|
Thanks for this advice.
Do I need to copy the amqalchk.fil also? I notice in a previous post, it was advised to do this.
I went ahead and created the same named Qmgr on another machine. The problem I see is that when I look at the contents of the amqalchk.fil, it has the name of the new machine there. Won't this cause a problem if I copy this file to the old machine where the broken Qmgr is?
Joan |
|
| Back to top |
|
|
| mrlinux |
| Posted: Mon Jul 09, 2007 11:28 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Its been a while, but try it first without copying in the amqalchk.fil first.
The amqalchk.fil is pointer into which log file was used last, in theory since you have clean logs this should be ok.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| jpardi |
| Posted: Mon Jul 09, 2007 12:02 pm Post subject: |
|
|
Newbie
Joined: 13 Oct 2004
Posts: 6
Location: Jersy City, NJ
|
I copied the logs, changed the permissions, but I still can't bring up my Qmgr.
Now, in additon to "Log not available", I am getting the following in my AMQERR01.LOG file:
07/09/07 15:55:36
AMQ6767: Log file /var/mqm/log/NJTIBDEV2/active/S0000000.LOG could not be
opened for use.
EXPLANATION:
Log file /var/mqm/log/NJTIBDEV2/active/S0000000.LOG could not be opened for
use. Possible reasons include the file being missing, the queue manager being
denied permission to open the file or the contents of the file being incorrect.
ACTION:
If the log file was required to start the queue manager, ensure that the log
file exists and that the queue manager is able to read from and write to it. If
the log file was required to recreate an object from its media image and you do
not have a copy of the required log file, delete the object instead of
recreating it. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jul 09, 2007 12:53 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
What happens if you copy the the amqalchk.fil file and try a restart?
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jpardi |
| Posted: Mon Jul 09, 2007 2:40 pm Post subject: |
|
|
Newbie
Joined: 13 Oct 2004
Posts: 6
Location: Jersy City, NJ
|
IBM just gave me a "cold start" procedure and it worked!
You can create a TEMP Qmgr on the same machine with the same log file characteristics. But then you have to remove recursively, the BADQMGR's directory from /var/mqm/log. (after backing it up) Then copy recursively TEMP qmgr's directory to BADQMGR. Also have to copy TEMP's amqalchk.fil to BADQMGR's /var/mqm/qmgrs/BADQMGR directory
Thank you both for the help and suggestions.
Joan |
|
| Back to top |
|
|
| Nigelg |
| Posted: Mon Jul 09, 2007 10:46 pm Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
Back to your first post...
| Quote: |
I did not delete these logs inadvertently; they seem to have disappeared after a reboot.
|
Yeah, right...
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jul 10, 2007 2:46 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Nigelg wrote: |
Back to your first post...
| Quote: |
I did not delete these logs inadvertently; they seem to have disappeared after a reboot.
|
Yeah, right... |
I did see something like that once, in LINEAR logging though... It was due to the linear log management system not being configured quite right. If this happens again, check that the logs missing did not get archived before the qmgr went down (or after).
In my case, the archiving program was missing a temp dir to copy the AMQxxxx.LOG files to.
In case those were being rolled over while determining the files to archive (no copy of them before determining files to archive) you might have archived active logs... 
But everything's running fine now... (thanks Tim -- again) 
Circular logging though.... Depending on activity and age of the file there might just be some OS maintenance sweeper that deletes old files to reclaim space? Make sure that that process never touches the MQ directories... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Nigelg |
| Posted: Tue Jul 10, 2007 5:50 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
There have been a couple of bugs where the required media or restart log extent numbers have been one more than actually required, and so users delete logs which are still needed. Obviously, as jeff says, this applies only to linear logging.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
|
|
