| Author |
Message
|
| b001063 |
 Posted: Mon Jul 12, 2010 11:29 am Post subject: AIX UPGRADE TO 6.1 MQSeries 6.0.2.4 dspmqaut failure |
 |
|
Newbie
Joined: 12 Jul 2010
Posts: 4
|
We upgraded our AIX server from 5.3 to 6.1. MQSeries was already running as 64 bit at 6.0.2.7. Following the upgrade our monitor and queue viewing tools failed with a 2063 when they try to connect to the qmanager. We attempted to manually update the permissions using setmqauth and got "AMQ7047: An unexpected error was encountered by a command".
We ran a trace and here is the key to the problem but I dont know the answer
----} xcsWaitEventSem rc=OK
11:07:34.979458 438410.1 MessageReceived (24 bytes)
11:07:34.979468 438410.1 0x0000: 5a574741 0000177e 00000000 00000002 |ZWGA...~........|
11:07:34.979468 438410.1 0x0010: 0000080f 00000000 |........ |
11:07:34.979476 438410.1 ---} zcpReceiveOnPipe rc=OK
11:07:34.979485 438410.1 --}! ziiSendReceiveAgent rc=MQRC_SECURITY_ERROR
11:07:34.979493 438410.1 --{ zcpDeleteMessage
11:07:34.979502 438410.1 --} zcpDeleteMessage rc=OK
11:07:34.979510 438410.1 -}! ziiSPIGetObjectAuthority rc=MQRC_SECURITY_ERROR
11:07:34.979519 438410.1 }! lpiSPIGetObjectAuthority rc=MQRC_SECURITY_ERROR
11:07:34.979529 438410.1 { MQDISC
11:07:34.979540 438410.1 -{ zstMQDISC
The odd thing is that the dspmqaut and setmqaut commands work if we are accessing anyone in the mqm group, but fail for all other groups and ids.
Anyone have an idea of what is wrong?
thanks
Susan |
|
| Back to top |
|
 |
| zpat |
| Posted: Mon Jul 12, 2010 11:31 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
|
| Back to top |
|
|
| b001063 |
| Posted: Mon Jul 12, 2010 11:32 am Post subject: |
|
|
Newbie
Joined: 12 Jul 2010
Posts: 4
|
| Yes we have No answer yet. Hopeing someone out there has already experienced this and can give me the right answer. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jul 12, 2010 11:32 am Post subject: Re: AIX UPGRADE TO 6.1 MQSeries 6.0.2.4 dspmqaut failure |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| b001063 wrote: |
| The odd thing is that the dspmqaut and setmqaut commands work if we are accessing anyone in the mqm group, but fail for all other groups and ids. |
That's because those commands ignore the mqm group, which has all permissions & nothing can change that.
| b001063 wrote: |
Anyone have an idea of what is wrong?
|
The FDC file you've posted part of has the most useful (to anyone who's not IBM Support) information at the top. The ProbeId is the place to start.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| b001063 |
| Posted: Mon Jul 12, 2010 11:39 am Post subject: |
|
|
Newbie
Joined: 12 Jul 2010
Posts: 4
|
This is not creating a FDC file, however here is the top of the trace file.
Timestamp Process.Thread Trace Data
===========================================
11:07:34.929373 438410.1 Version : 6.0.2.7 Level : p600-207-090617
11:07:34.929466 438410.1 Date : 07/12/10 Time : 11:07:34
11:07:34.929526 438410.1 PID : 438410 Process : dspmqaut
11:07:34.929535 438410.1 --------------------------------
11:07:34.929544 438410.1 Trace Control Memory:
11:07:34.929554 438410.1 StrucId: XTTS
11:07:34.929563 438410.1 Options MaxFileSize UserDataSize SubpoolName
11:07:34.929574 438410.1 00000000 0 0
11:07:34.929584 438410.1 01fcffff 0 -2 PMSTAX024
11:07:34.929593 438410.1 00000000 0 0
11:07:34.929602 438410.1 00000000 0 0
11:07:34.929611 438410.1 00000000 0 0
11:07:34.929620 438410.1 00000000 0 0
11:07:34.929630 438410.1 00000000 0 0
11:07:34.929639 438410.1 00000000 0 0
11:07:34.929648 438410.1 00000000 0 0
11:07:34.929657 438410.1 00000000 0 0
11:07:34.929667 438410.1 01fcffff 0 -2 = EFFECTIVE =
11:07:34.929709 438410.1 Thread stack
11:07:34.929721 438410.1 -> MQCONN
11:07:34.929730 438410.1 -> zstMQCONN
11:07:34.929741 438410.1 -> zstMQConnect
11:07:34.929750 438410.1 -> zstInitCS
11:07:34.929760 438410.1 -> xcsInitialize
11:07:34.929769 438410.1 -> xcsGetEnvironmentString
11:07:34.929777 438410.1 -----{ xcsGetEnvironmentString
11:07:34.929791 438410.1 xcsGetEnvironmentString[AMQ_SERVICE_MODULE] = NULL
11:07:34.929800 438410.1 -----}! xcsGetEnvironmentString rc=xecE_E_ENV_VAR_NOT_FOUND
11:07:34.929808 438410.1 -----{ xcsReleaseThreadMutexSem
11:07:34.929818 438410.1 hmtx is 11000ca70
11:07:34.929827 438410.1 -----} xcsReleaseThreadMutexSem rc=OK
11:07:34.929835 438410.1 ----} xcsInitialize rc=OK
11:07:34.929845 438410.1 ----{ zutConnectConfig
11:07:34.929855 438410.1 -----{ xcsLookupNamedMemBlock
11:07:34.929865 438410.1 ------{ xcsEnumerateQuickCellBlock
11:07:34.929874 438410.1 -------{ xcsGetMem
11:07:34.929885 438410.1 component:23 function:366 length:40 options:0 *pointer:11001ddc8
11:07:34.929893 438410.1 -------} xcsGetMem rc=OK
11:07:34.929904 438410.1 ------} xcsEnumerateQuickCellBlock rc=OK
11:07:34.929913 438410.1 ------{ xcsFreeQuickCellEnumerator
11:07:34.929922 438410.1 -------{ xcsFreeMem
11:07:34.929931 438410.1 component:23 pointer:11001ddc8
11:07:34.929940 438410.1 -------} xcsFreeMem rc=OK
11:07:34.929948 438410.1 ------} xcsFreeQuickCellEnumerator rc=OK
11:07:34.929955 438410.1 -----} xcsLookupNamedMemBlock rc=OK
11:07:34.929964 438410.1 -----{ xcsGetMem
11:07:34.929974 438410.1 component:33 function:137 length:72 options:0 *pointer:11001ddc8
11:07:34.929982 438410.1 -----} xcsGetMem rc=OK
11:07:34.929991 438410.1 ----} zutConnectConfig rc=OK
11:07:34.930000 438410.1 ----{ xcsTerminate
11:07:34.930008 438410.1 -----{ xcsRequestThreadMutexSem
11:07:34.930017 438410.1 hmtx is 11000ca70
11:07:34.930025 438410.1 -----} xcsRequestThreadMutexSem rc=OK
11:07:34.930037 438410.1 -----{ xcsCacheSharedSubpool
11:07:34.930046 438410.1 ------{ xcsGetMem
11:07:34.930057 438410.1 component:24 function:487 length:3184 options:0 *pointer:110039348 |
|
| Back to top |
|
|
| zonko |
| Posted: Mon Jul 12, 2010 11:45 pm Post subject: |
|
|
Voyager
Joined: 04 Nov 2009
Posts: 78
|
| Probably a failure in the underlying security mechanism which serves up the user and group IDs and names to WMQ. |
|
| Back to top |
|
|
| b001063 |
| Posted: Tue Jul 13, 2010 5:24 am Post subject: |
|
|
Newbie
Joined: 12 Jul 2010
Posts: 4
|
following another reboot of the server everything started working normally. we may never know why this happened.
Thanks |
|
| Back to top |
|
|
|
|
