| Author |
Message
|
| Boomn4x4 |
 Posted: Thu Feb 16, 2012 9:28 am Post subject: Tracking down an AMQ8135 error |
 |
|
Disciple
Joined: 28 Nov 2011
Posts: 172
|
I have a Perl script that monitors the queue depth. The script executes an MQSC to display the status "display qstatus(myq) monitor", I parse the results looking for CURDEPTH.
The script is supposed to run every 60 seconds (using Xymon).
For some reason, the script runs fine, then about 38 seconds later, it seems that the script runs again, this time getting a AMQ8135 - Not Authorized error.... 22 seconds later, the script runs again just fine. Are there some logs somewhere that will tell me what exactly is happening? I looked in /var/mqm/errors, but don't see anything recent. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Feb 16, 2012 9:42 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
The next step of this I presume?
There should be something in the queue manager logs; if not you can enable security events on the queue manager & see what's being refused.
I would guess that sometimes when you start a new command shell (assuming you're sticking with the method indicated in your previous thread) the user credentials are not being inherited by the new shell and hence it's being refused by the queue manager.
Like I said, cumbersome. PCF is much more controllable.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Boomn4x4 |
| Posted: Thu Feb 16, 2012 10:14 am Post subject: |
|
|
Disciple
Joined: 28 Nov 2011
Posts: 172
|
| Vitor wrote: |
The next step of this I presume?
There should be something in the queue manager logs; if not you can enable security events on the queue manager & see what's being refused.
I would guess that sometimes when you start a new command shell (assuming you're sticking with the method indicated in your previous thread) the user credentials are not being inherited by the new shell and hence it's being refused by the queue manager.
Like I said, cumbersome. PCF is much more controllable. |
Once Authority events (I assume that is what you are refering to as i don't see 'security' events) are enabled, where are those events posted to so that I can see them?
I will be looking into PCF |
|
| Back to top |
|
|
| Boomn4x4 |
| Posted: Thu Feb 16, 2012 10:19 am Post subject: |
|
|
Disciple
Joined: 28 Nov 2011
Posts: 172
|
Found the messages, but I'm not sure I'm understanding the data?
| Code: |
00000 07 00 00 00 24 00 00 00--01 00 00 00 2C 00 00 00 |....$.......,...|
00010 01 00 00 00 01 00 00 00--01 00 00 00 F3 07 00 00 |............�...|
00020 05 00 00 00 04 00 00 00--44 00 00 00 DF 07 00 00 |........D...�...|
00030 00 00 00 00 30 00 00 00--51 4D 4D 58 42 53 43 53 |....0...QMMXBSCS|
00040 20 20 20 20 20 20 20 20--20 20 20 20 20 20 20 20 | |
00050 20 20 20 20 20 20 20 20--20 20 20 20 20 20 20 20 | |
00060 20 20 20 20 20 20 20 20--03 00 00 00 10 00 00 00 | ........|
00070 FC 03 00 00 01 00 00 00--04 00 00 00 20 00 00 00 |�........... ...|
00080 D1 0B 00 00 00 00 00 00--0C 00 00 00 72 6F 6F 74 |� ...... ...root|
00090 20 20 20 20 20 20 20 20--03 00 00 00 10 00 00 00 | ........|
000A0 01 00 00 00 06 00 00 00--04 00 00 00 30 00 00 00 |............0...|
000B0 D0 0B 00 00 00 00 00 00--1C 00 00 00 72 75 6E 6D |� ...... ...runm|
000C0 71 73 63 20 20 20 20 20--20 20 20 20 20 20 20 20 |qsc |
000D0 20 20 20 20 20 20 20 20-- | |
|
|
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Feb 16, 2012 10:40 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Where did you find this (message)??
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Boomn4x4 |
| Posted: Thu Feb 16, 2012 10:47 am Post subject: |
|
|
Disciple
Joined: 28 Nov 2011
Posts: 172
|
| bruce2359 wrote: |
| Where did you find this (message)?? |
SYSTEM.ADMIN.QMGR.EVENT |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Feb 16, 2012 10:53 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Boomn4x4 wrote: |
[code]00010 01 00 00 00 01 00 00 00--01 00 00 00 F3 07 00 00 |
Intel platform.
R/C x'07f3' = MQRC_NOT_AUTHORIZED
I'm looking further...
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Feb 16, 2012 11:00 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Please post the complete message - including the MQMD.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Feb 16, 2012 11:05 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Boomn4x4 wrote: |
| Once Authority events (I assume that is what you are refering to as i don't see 'security' events) are enabled |
My bad. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Boomn4x4 |
| Posted: Thu Feb 16, 2012 11:09 am Post subject: |
|
|
Disciple
Joined: 28 Nov 2011
Posts: 172
|
| bruce2359 wrote: |
| Please post the complete message - including the MQMD. |
I'm not sure I know exactly what you are asking for but:
Message Identifier:
Message Identifier Bytes:
| Code: |
00000 41 4D 51 20 51 4D 4D 58--42 53 43 53 20 20 20 20 |AMQ QMMXBSCS |
00010 88 AB 32 4F 42 87 22 20-- |.�2OB." | |
Data length = 216
Format = MQEvent
Coded Character Identifier= 1208
Encoding - 546
Message Data = $
The Data itself is complete above. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Feb 16, 2012 11:11 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Boomn4x4 wrote: |
| Found the messages, but I'm not sure I'm understanding the data? |
The layout's in the APR. If I'm reading it correctly (late in the day & either too little or too much caffine is in my blood for the size of font) then it's saying that user root is not authorised to perform the operation. On the assumption you're not running this script as a super user this seems to reinforce my theory the new shell is not inheriting the permissions correctly.
But it sounds a little dangerous if command shells spawned from script sometimes run as root so that could be rubbish.
Look it up & count the bytes in a larger font. Or use the event support pac to interpret it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Boomn4x4 |
| Posted: Thu Feb 16, 2012 12:13 pm Post subject: |
|
|
Disciple
Joined: 28 Nov 2011
Posts: 172
|
| Vitor wrote: |
| . On the assumption you're not running this script as a super user this seems to reinforce my theory the new shell is not inheriting the permissions correctly. |
That was enough for me to find the problem, thanks.
Some how, two instances of my monitor were running, one as root.... One of them was sending the correct alert, one of them running as root was erroring out.
I should have picked up on this right away when I noticed that the script was supposed to be running every 60 second, but the alerts were changing twice every 60 seconds. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Feb 16, 2012 12:22 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Boomn4x4 wrote: |
I should have picked up on this right away when I noticed that the script was supposed to be running every 60 second, but the alerts were changing twice every 60 seconds.
| Boomn4x4 wrote: |
| Not Authorized error.... 22 seconds later, |
|
Ah, I miss the good-old days of 22 second half-minutes of 30 seconds each.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
|
|
