Posted: Mon Jun 06, 2005 6:25 am Post subject: Corrupted SYSTEM!AUTH!DATA!QUEUE
Apprentice
Joined: 18 Aug 2004 Posts: 43
It seems like for some reason our AUTH queue is corrputed. mqm user has lost priviledge to manage the queue manager. we can only start and stop the queue manager. Situation issimilar to as if someone has issed setmqaut to remove all priviledges for mqm group.
Now, other than rebuilding thw queue manager what are the options
a. strmqm -c ( to start the queue manager to recreate system objs). After disabling the stanza from the qm.ini. This did NOT refresh the the AUTH queue.
b. The queue manager runs allright w/o Auth Services ( pretty straight forward)
Any other way to recover this to base authorizations for mqm user. We do not have amqomd output to rerun but we have the scripts to recreate the auths.
q.1 Is it possible to get SYSTEM!AUTH!DATA!QUEUE from backup and recover to that image?
q.2 clear the queue and then load messages from another queue manager using channels etc. Or dump it using amqoamd and puttin git back on this queue manager.
Any pointer/s will be highly appreciated.
Thank you in advance.
p.s. Kernel parameters r properly set per SOLARIS QB guide. MQ Version 5.3 CSD07.
mqm is not authorised via the auth queue. The system recognises the mqm userID and the auth checks are not done.
The most likely explanation is that the OS can no longer find the mqm userID or group in the passwd or group files. Check for any changes in this area in the OS by your system admin guys.
This is different than what was there before 5.2. Pre 5.2 version even kept mqm priv in the auth file. So, from your statement it looks that the problem that we had before 5.2 that mqm account could loose the auth due to bad setmqaut executed on mqm group won't ever happen. I know this was on the wish-list of many administrators.
Do you think this is the only problem that can cause
a. runmqsc to fail with 2063 even though start and endmqm works.
b. The respository manager also quits w/ 2063.
Do want to let you know that all the objects and setmqauth were executed from another user which is part of the mqm group.
Nigel,
We checked everything related to mqm user and group ( including kernel params) everything looks good. Here is the error message we get when we start the queue manager and after that we loose access to the queue manager ( runmqsc ,amqoamd - nothing works - all fail w/ 2063).
-------------------------------------------------------------------------------
06/03/05 20:45:16
AMQ9410: Repository manager started
EXPLANATION:
The repository manager started successfully.
ACTION:
None.
-------------------------------------------------------------------------------
06/03/05 20:45:16
AMQ9508: Program cannot connect to the queue manager.
EXPLANATION:
The connection attempt to queue manager 'QM.TEST' failed with reason code 2063.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrimna.c : 427 --------------------------------------------------------
06/03/05 20:45:16
AMQ9508: Program cannot connect to the queue manager.
EXPLANATION:
The connection attempt to queue manager 'QM.TEST' failed with reason code 2063.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrrmfa.c : 3164 -------------------------------------------------------
06/03/05 20:45:16
AMQ9409: Repository manager ended abnormally.
EXPLANATION:
The repository manager ended abnormally.
ACTION:
Look at previous error messages for the repository manager in the error files
to determine the cause of the failure.
----- amqrrmfa.c : 3951 -------------------------------------------------------
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