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 » General IBM MQ Support » AMQ8101: Unexpected Error (893)

Post new topic  Reply to topic Goto page 1, 2  Next
 AMQ8101: Unexpected Error (893) « View previous topic :: View next topic » 
Author Message
skomanduri
PostPosted: Thu Feb 28, 2002 10:45 am    Post subject: Reply with quote

Newbie

Joined: 25 Feb 2002
Posts: 6

I am using MQSeries V5.2 on Sun Solaris 8.

I am attempting to create the queue manager using CRTMQM and get the above error mentioned in the subject.

I am attaching the Error log and FDC files for reference.

Any help is greatly appreciated.

Thanks

AMQERR01.LOG output
====================================
02/28/02 11:10:19
AMQ6125: An internal MQSeries error has occurred.

EXPLANATION:
An internal error has occurred with identifier 0. 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.
-------------------------------------------------------------------------------
02/28/02 11:10:19
AMQ6184: An internal MQSeries error has occurred on queue manager
stp!queue!manager.

EXPLANATION:
An error has been detected, and the MQSeries error recording routine has been
called. The failing process is process 27112.
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.
-------------------------------------------------------------------------------
=========================================
AMQ27112.0.FDC output
=========================================
+-----------------------------------------------------------------------------+
| |
| MQSeries First Failure Symptom Report |
| ===================================== |
| |
| Date/Time :- Thursday February 28 11:10:19 MST 2002 |
| Host Name :- ttc-sun2 (SunOS 5. |
| PIDS :- 5765B75 |
| LVLS :- 520 |
| Product Long Name :- MQSeries for Sun Solaris 2 (Sparc) |
| Vendor :- IBM |
| Probe Id :- ZF048015 |
| Application Name :- MQM |
| Component :- zfu_as_searchprincipallist |
| Build Date :- Jan 15 2002 |
| CMVC level :- p520-CSD03G |
| Build Type :- IKAP - (Production) |
| UserID :- 00060021 (mqm) |
| Program Name :- crtmqm |
| Process :- 00027112 |
| Thread :- 00000001 |
| QueueManager :- stp!queue!manager |
| Major Errorcode :- krcE_UNEXPECTED_ERROR |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 2 |
| Probe Description :- AMQ6125: An internal MQSeries error has occurred. |
| |
+-----------------------------------------------------------------------------+

MQM Function Stack
zsqSPICreateQM
kpiCreateQM
apiConfigure
aocConfigure
aocCreateObject
gpiSetInitAuthority
gpiSetObjectAuthority
zfu_as_setobjectauthority
zfu_as_searchprincipallist
xcsFFST

MQM Trace History
--------{ aduLocateFileCtl
--------} aduLocateFileCtl rc=OK
--------{ adiCloseFile
--------} adiCloseFile rc=OK
--------{ aduReleaseFileCtl
--------} aduReleaseFileCtl rc=OK
-------} adhClose rc=OK
------} aoiAddEntry rc=OK
------{ aodCreate
-------{ adhCreate
--------{ aduLocateFileCtl
--------} aduLocateFileCtl rc=arcE_OBJECT_MISSING
--------{ aduAllocFileCtl

--------} aduAllocFileCtl rc=OK
--------{ aduBuildOSName
--------} aduBuildOSName rc=OK
--------{ adiCreateFile
--------} adiCreateFile rc=OK
-------} adhCreate rc=OK
-------{ adhClose
--------{ aduLocateFileCtl
--------} aduLocateFileCtl rc=OK
--------{ adiCloseFile
--------} adiCloseFile rc=OK
--------{ aduReleaseFileCtl
--------} aduReleaseFileCtl rc=OK
-------} adhClose rc=OK
------} aodCreate rc=OK
------{ gpiGrantSystemObjectAuth
------} gpiGrantSystemObjectAuth rc=OK
-----} aocPerformCreation rc=OK
-----{ aocObjectDoctor
------{ almLogIt
-------{ xlsRequestMutex
-------} xlsRequestMutex rc=OK
-------{ xlsReleaseMutex
-------} xlsReleaseMutex rc=OK
-------{ hlgWriteLogRecord
--------{ mqlpgrsp
---------{ xlsRequestMutex
---------} xlsRequestMutex rc=OK
---------{ xlsReleaseMutex
---------} xlsReleaseMutex rc=OK
--------} mqlpgrsp rc=OK
--------{ mqlpgwlg
---------{ xlsRequestMutex
---------} xlsRequestMutex rc=OK
---------{ xlsRequestMutex
---------} xlsRequestMutex rc=OK
---------{ xlsReleaseMutex
---------} xlsReleaseMutex rc=OK
---------{ xlsRequestMutex
---------} xlsRequestMutex rc=OK
---------{ xlsReleaseMutex
---------} xlsReleaseMutex rc=OK
---------{ xlsRequestMutex
---------} xlsRequestMutex rc=OK
---------{ xlsReleaseMutex
---------} xlsReleaseMutex rc=OK
---------{ xlsReleaseMutex
---------} xlsReleaseMutex rc=OK
---------{ xlsRequestMutex
---------} xlsRequestMutex rc=OK
---------{ xlsReleaseMutex
---------} xlsReleaseMutex rc=OK
--------} mqlpgwlg rc=OK
-------} hlgWriteLogRecord rc=OK

------} almLogIt rc=OK
------{ aodWrite
-------{ adhOpen
--------{ aduLocateFileCtl
--------} aduLocateFileCtl rc=arcE_OBJECT_MISSING
--------{ aduAllocFileCtl
--------} aduAllocFileCtl rc=OK
--------{ aduBuildOSName
--------} aduBuildOSName rc=OK
--------{ adiOpenFile
--------} adiOpenFile rc=OK
-------} adhOpen rc=OK
-------{ adhWrite
--------{ aduLocateFileCtl
--------} aduLocateFileCtl rc=OK
--------{ adiWriteFile
--------} adiWriteFile rc=OK
-------} adhWrite rc=OK
-------{ adhClose
--------{ aduLocateFileCtl
--------} aduLocateFileCtl rc=OK
--------{ adiCloseFile
--------} adiCloseFile rc=OK
--------{ aduReleaseFileCtl
--------} aduReleaseFileCtl rc=OK
-------} adhClose rc=OK
------} aodWrite rc=OK
-----} aocObjectDoctor rc=OK
-----{ aocCompleteCreation
------{ almLogIt
-------{ xlsRequestMutex
-------} xlsRequestMutex rc=OK
-------{ xlsReleaseMutex
-------} xlsReleaseMutex rc=OK
-------{ hlgWriteLogRecord
--------{ mqlpgrsp
---------{ xlsRequestMutex
---------} xlsRequestMutex rc=OK
---------{ xlsReleaseMutex
---------} xlsReleaseMutex rc=OK
--------} mqlpgrsp rc=OK
--------{ mqlpgwlg
---------{ xlsRequestMutex
---------} xlsRequestMutex rc=OK
---------{ xlsRequestMutex
---------} xlsRequestMutex rc=OK
---------{ xlsReleaseMutex
---------} xlsReleaseMutex rc=OK
---------{ xlsRequestMutex
---------} xlsRequestMutex rc=OK
---------{ xlsReleaseMutex
---------} xlsReleaseMutex rc=OK
---------{ xlsRequestMutex
---------} xlsRequestMutex rc=OK
---------{ xlsReleaseMutex
---------} xlsReleaseMutex rc=OK
---------{ xlsReleaseMutex
---------} xlsReleaseMutex rc=OK
---------{ xlsRequestMutex
---------} xlsRequestMutex rc=OK
---------{ xlsReleaseMutex
---------} xlsReleaseMutex rc=OK
---------{ mqlpgild
----------{ xlsRequestMutex
----------} xlsRequestMutex rc=OK
----------{ xlsReleaseMutex
----------} xlsReleaseMutex rc=OK
----------{ xlsRequestMutex
----------} xlsRequestMutex rc=OK
----------{ xlsRequestMutex
----------} xlsRequestMutex rc=OK
----------{ xlsReleaseMutex
----------} xlsReleaseMutex rc=OK
----------{ mqlpgpst
-----------{ hosPostWaitPostArea
------------{ xcsPostEventSem
------------} xcsPostEventSem rc=OK
-----------} hosPostWaitPostArea rc=OK
-----------{ hosWaitWaitPostArea
------------{ xcsWaitEventSem
------------} xcsWaitEventSem rc=OK
-----------} hosWaitWaitPostArea rc=OK
----------} mqlpgpst rc=OK
----------{ xlsReleaseMutex
----------} xlsReleaseMutex rc=OK
---------} mqlpgild rc=OK
--------} mqlpgwlg rc=OK
-------} hlgWriteLogRecord rc=OK
-------{ almReleaseSpace
--------{ hlgReleaseLogSpace
---------{ mqlpgrsp
----------{ xlsRequestMutex
----------} xlsRequestMutex rc=OK
----------{ xlsReleaseMutex
----------} xlsReleaseMutex rc=OK
---------} mqlpgrsp rc=OK
--------} hlgReleaseLogSpace rc=OK
-------} almReleaseSpace rc=OK
------} almLogIt rc=OK
-----} aocCompleteCreation rc=OK
-----{ gpiSetInitAuthority
------{ gpiSetObjectAuthority
-------{ zfp_ss_lock_service
-------} zfp_ss_lock_service rc=OK
-------{ gpiMapObjectType
-------} gpiMapObjectType rc=OK
-------{ zfp_ss_getfirst_component
Back to top
View user's profile Send private message Yahoo Messenger
mrlinux
PostPosted: Thu Feb 28, 2002 10:51 am    Post subject: Reply with quote

Grand Master

Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA

What is the parameters you are using with crtmqm ???

_________________
Jeff

IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries
Back to top
View user's profile Send private message Send e-mail
skomanduri
PostPosted: Thu Feb 28, 2002 11:50 am    Post subject: Reply with quote

Newbie

Joined: 25 Feb 2002
Posts: 6

This is the command I am trying to run
crtmqm -q -d STP.DEFAULT.XMIT.QUEUE -u SYSTEM.DEAD.LETTER.QUEUE stp.queue.manager
Back to top
View user's profile Send private message Yahoo Messenger
mrlinux
PostPosted: Thu Feb 28, 2002 12:28 pm    Post subject: Reply with quote

Grand Master

Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA

It looks like the queue manager cant find something.
do you have a valid /var/mq/mqs.ini file ????

_________________
Jeff

IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries
Back to top
View user's profile Send private message Send e-mail
skomanduri
PostPosted: Thu Feb 28, 2002 12:31 pm    Post subject: Reply with quote

Newbie

Joined: 25 Feb 2002
Posts: 6

This is what I have in the MQ file.


#********************************************************************#
#* *#
#* <START_COPYRIGHT> *#
#* Licensed Materials - Property of IBM *#
#* *#
#* 63H9336 *#
#* (C) Copyright IBM Corporation 1994, 2000 *#
#* *#
#* <END_COPYRIGHT> *#
#* *#
#********************************************************************#
#***********************************************************************#
#* Module Name: mqs.ini *#
#* Type : MQSeries Machine-wide Configuration File *#
#* Function : Define MQSeries resources for an entire machine *#
#* *#
#***********************************************************************#
#* Notes : *#
#* 1) This is the installation time default configuration *#
#* *#
#***********************************************************************#
AllQueueManagers:
#********************************************************************#
#* The path to the qmgrs directory, below which queue manager data *#
#* is stored *#
#********************************************************************#
DefaultPrefix=/var/mqm

ClientExitPath:
ExitsDefaultPath=/var/mqm/exits

LogDefaults:
LogPrimaryFiles=3
LogSecondaryFiles=2
LogFilePages=1024
LogType=CIRCULAR
LogBufferPages=17
LogDefaultPath=/var/mqm/log
Back to top
View user's profile Send private message Yahoo Messenger
mrlinux
PostPosted: Thu Feb 28, 2002 12:45 pm    Post subject: Reply with quote

Grand Master

Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA

Well that looks like a valid mqsi.ini file, I guess the next thing is

what are the permissions on
/var
/var/mqm
/var/mqm/qmgrs
/var/mqm/log

_________________
Jeff

IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries

[ This Message was edited by: mrlinux on 2002-02-28 12:45 ]
Back to top
View user's profile Send private message Send e-mail
mqonnet
PostPosted: Thu Feb 28, 2002 12:49 pm    Post subject: Reply with quote

Grand Master

Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.

Hi Skomanduri,

Looks like there is a Security issue. Who are you logged in as. If you are other than the mqm user, did you add your user id to mqm group. And to check more on this, you could use dspmqaut to check the authorizations your user id has. But it looks as if your user id does not have the appropriate authority. Did you try creating the QM using mqm.manager or someone in the mqm group.
Not quite sure, but does solaris has a principal/user concept or not.
Hope this helps.

Cheers.
Kumar

_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator
Back to top
View user's profile Send private message Send e-mail Visit poster's website
skomanduri
PostPosted: Thu Feb 28, 2002 1:04 pm    Post subject: Reply with quote

Newbie

Joined: 25 Feb 2002
Posts: 6

Thanks for the repsonse.

I am using mqm user which has the same group.

All the directories have "rwx" permissions for everyone.

The only difference is the /var/mqm/log is a link to another directory path and has the same permissions. I can create files in the directory with mqm user.
Back to top
View user's profile Send private message Yahoo Messenger
mqonnet
PostPosted: Thu Feb 28, 2002 1:23 pm    Post subject: Reply with quote

Grand Master

Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.

Hi skomanduri,
I would go with creating the QM using mqm.manager userid.
Not quite sure how you create a user and get him/her into the mqm group on Solaris. But i would carefully check this process again. But otherwise i dont see why you would not be able to create a QM.

Also advisible would be to check in Solaris manual/help to see what the filesystem error code 893 means. That could give more clue to this problem.

Cheers.
Kumar

_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator
Back to top
View user's profile Send private message Send e-mail Visit poster's website
skomanduri
PostPosted: Thu Feb 28, 2002 3:16 pm    Post subject: Reply with quote

Newbie

Joined: 25 Feb 2002
Posts: 6

Looks like there is some permission on some of the files installed.

Now when I run the crtmqm command it creates the queue manager but fails to create default objects

I am attaching the error logs

======================================
-------------------------------------------------------------------------------
02/28/02 15:54:07
AMQ6118: An internal MQSeries error has occurred (15)

EXPLANATION:
An error has been detected, and the MQSeries 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.
-------------------------------------------------------------------------------
02/28/02 15:54:07
AMQ6184: An internal MQSeries error has occurred on queue manager
STP!QUEUE!MGR.

EXPLANATION:
An error has been detected, and the MQSeries error recording routine has been
called. The failing process is process 28323.
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.
-------------------------------------------------------------------------------
==================================
FDC file
==================================
+-----------------------------------------------------------------------------+
| |
| MQSeries First Failure Symptom Report |
| ===================================== |
| |
| Date/Time :- Thursday February 28 15:54:07 MST 2002 |
| Host Name :- ttc-sun2 (SunOS 5. |
| PIDS :- 5765B75 |
| LVLS :- 520 |
| Product Long Name :- MQSeries for Sun Solaris 2 (Sparc) |
| Vendor :- IBM |
| Probe Id :- ZS086005 |
| Application Name :- MQM |
| Component :- zsllpiCreateQM |
| Build Date :- Jan 15 2002 |
| CMVC level :- p520-CSD03G |
| Build Type :- IKAP - (Production) |
| UserID :- 00000000 (UNKNOWN) |
| Program Name :- crtmqm |
| Process :- 00028323 |
| Thread :- 00000001 |
| QueueManager :- STP!QUEUE!MGR |
| Major Errorcode :- xecF_E_UNEXPECTED_RC |
| Minor Errorcode :- Unknown(15) |
| Probe Type :- MSGAMQ6118 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6118: An internal MQSeries error has occurred (15) |
| Arith1 :- 21 15 |
| |
+-----------------------------------------------------------------------------+

MQM Function Stack

MQM Trace History

Process Control Block
Back to top
View user's profile Send private message Yahoo Messenger
StefanSievert
PostPosted: Thu Feb 28, 2002 4:26 pm    Post subject: Reply with quote

Partisan

Joined: 28 Oct 2001
Posts: 333
Location: San Francisco

Hi,
this might not really help you as it does not contain a solution to your problem, but you might want to look at it anyway...
http://www.messageq.com/forums/vienna/msg_body.php3?ID=27372
Looks like it is not something specific to your installation.
Stefan

_________________
Stefan Sievert
IBM Certified * WebSphere MQ
Back to top
View user's profile Send private message
mqonnet
PostPosted: Thu Feb 28, 2002 4:26 pm    Post subject: Reply with quote

Grand Master

Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.

Hi,

As i have been pointing to from the beginning, there is something wrong with the userid which you are using. BTW which userid you were on. Were you using mqm.manager or your own userid. Is this a new installation. Did you ever try creating a qm using mqm.manager login. If that too does not work, then i guess you should get back to the IBM reps. You could as well try to figure out what is wrong with your installation and the userids.

Hope this helps.

Cheers.
Kumar

_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator
Back to top
View user's profile Send private message Send e-mail Visit poster's website
StefanSievert
PostPosted: Thu Feb 28, 2002 4:32 pm    Post subject: Reply with quote

Partisan

Joined: 28 Oct 2001
Posts: 333
Location: San Francisco

Kumar,
the very first FDC indicates that he was using the mqm userId (is that what you mean by 'mqm.manager'?):
Quote:

| UserID :- 00060021 (mqm) |

The second FDC, however, shows an unknown userId, which smells very fishy:
Quote:

| UserID :- 00000000 (UNKNOWN) |

I would suggest to remove the queue manager entry from the mqs.ini file and manually delete the complete path beyond /var/mqm/qmgrs/STP!QUEUE!MGR including all subdirectories, then try the crtmqm again. What strikes me, is that the mqs.ini file shown above does not contain an entry for the queue manager. Seems like there might also be a problem in updating this file. It should contain a stanza with the queue manager name STP.QUEUE.MGR.
I would also make sure that the MQ product is on the latest CSD level.
Stefan

_________________
Stefan Sievert
IBM Certified * MQSeries

[ This Message was edited by: StefanSievert on 2002-02-28 16:34 ]
Back to top
View user's profile Send private message
mqonnet
PostPosted: Fri Mar 01, 2002 4:41 am    Post subject: Reply with quote

Grand Master

Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.

Hi Stefan,

What i meant by mqm.manager is that the user should be logged in as mqm.manager rather than any other user who is made part of the mqm group. This would surely resolve a lot of issues of authorities and rights. Because mqm.manager is the default owner of the installation. And hence i have been stressing on the need to try and create a QM using the logon id of mqm.manager rather than any other user in the mqm group. This would the first basic test, to see if there is any pertinent problem.

How i see is, that even though this user is in the mqm group, there are restrictions on the usage(which is kinda strange). And that was the reason i was asking to check the authorities. The other alternative of course would be to recreate a new userid, and try and recreate a new QM using this userid(who is in the mqm group).

But i would strongly recommend the former approach.

As for the userid which is shown in the first FFST, not quite sure if mqm is a userid in the mqm group. Just having a userid mqm does not mean it is in the mqm group. And as for the second userid. Hmmm... This is strange. No userid. Looks like the userid was never resolved or got corrupted on its way. Cant really comment on this one. But sure it is a big mess..

Cheers
Kumar

_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator
Back to top
View user's profile Send private message Send e-mail Visit poster's website
mrlinux
PostPosted: Fri Mar 01, 2002 5:01 am    Post subject: Reply with quote

Grand Master

Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA

Well the file permissons on HPUX related to /var/mqm have the suid bit set. As far as Sun goes I dont know for sure, it's been along time since I installed on a Sun Box

_________________
Jeff

IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Goto page 1, 2  Next Page 1 of 2

MQSeries.net Forum Index » General IBM MQ Support » AMQ8101: Unexpected Error (893)
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.