| Author |
Message
|
| nathanw |
 Posted: Fri Aug 24, 2012 6:28 am Post subject: Broker Upgrades Falling over on completion |
 |
|
Knight
Joined: 14 Jul 2004
Posts: 550
|
OK
AIX 6.1.0.0
MQ 7.0.1.8
MB 6.1.0.10
I am onsite at a client whereby we are upgrading the Brokers to V8 bu using 6.1.0.10 as a staging post.
We have upgraded broker on several servers and experiencing the following fdc error (extract)
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Fri August 24 2012 10:54:52 BST |
| UTC Time :- 1345802092.226334 |
| UTC Time Offset :- 60 (GMT) |
| Host Name :- huxd0171 |
| Operating System :- AIX 6.1 |
| PIDS :- 5724H7221 |
| LVLS :- 7.0.1.8 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- XC267011 |
| Application Name :- MQM |
| Component :- xehAsySignalMonitor |
| SCCS Info :- lib/cs/unix/amqxerrx.c, 1.242.1.3 |
| Line Number :- 2879 |
| Build Date :- Feb 24 2012 |
| CMVC level :- p701-108-120224 |
| Build Type :- IKAP - (Production) |
| Effective UserID :- 21003 (mqm) |
| Real UserID :- 21052 (mqadming) |
| Program Name :- amqzmuc0 |
| Addressing mode :- 64-bit |
| Process :- 9961506 |
| Thread :- 2 |
| UserApp :- FALSE |
| Last HQC :- 0.0.0-0 |
| Last HSHMEMB :- 0.0.0-0 |
| Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6209 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6209: An unexpected asynchronous signal (33 : |
| SIGDANGER) has been received and ignored. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 33 (0x21) |
| Arith2 :- 9961506 (0x980022) |
| Comment1 :- SIGDANGER |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
xehAsySignalMonitor
xcsFFST
MQM Trace History
{ xihCSThreadClear
-{ xcsEmptyCBM
-} xcsEmptyCBM rc=OK
} xihCSThreadClear rc=OK
{ xppInitialiseDestructorRegistrations
} xppInitialiseDestructorRegistrations rc=OK
{ xehAsySignalMonitor
-{ xcsGetEnvironmentInteger
--{ xcsGetEnvironmentString
--} xcsGetEnvironmentString rc=xecE_E_ENV_VAR_NOT_FOUND
-} xcsGetEnvironmentInteger rc=xecE_E_ENV_VAR_NOT_FOUND
-{ xcsIsEnvironment
-} xcsIsEnvironment rc=OK
-{ xppPostAsySigMonThread
-} xppPostAsySigMonThread rc=OK
Data: 0x00000021
-{ xehHandleAsySignal
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsReleaseThreadMutexSem
--} xcsReleaseThreadMutexSem rc=OK
-} xehHandleAsySignal rc=OK
-{ xcsFFST
This points towards this
http://www-01.ibm.com/support/docview.wss?uid=swg1IV19658
But the versions so not tie up
Basically once we are restarted one of the servers the system ran fine until today when the FDC above happened, again in its multitudes.
The period of time between the original upgrade and FDC issue and the current one was approx 48 hours
Any thoughts on what could be causing this would be appreciated.
_________________
Who is General Failure and why is he reading my hard drive?
Artificial Intelligence stands no chance against Natural Stupidity.
Only the User Trace Speaks The Truth  |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Aug 24, 2012 6:35 am Post subject: Re: Broker Upgrades Falling over on completion |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| nathanw wrote: |
| I am onsite at a client whereby we are upgrading the Brokers to V8 bu using 6.1.0.10 as a staging post. |
Was WMQ upgraded / changed at the same time? What maintenance has been applied to that? It's odd on the face of it that a WMB upgrade would cause a WMQ FDC.
(Nice sig by the way. Sounds familiar....)
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Aug 24, 2012 6:37 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| What's in the relevant AMQERR log at the coincident time? |
|
| Back to top |
|
|
| nathanw |
| Posted: Fri Aug 24, 2012 6:55 am Post subject: |
|
|
Knight
Joined: 14 Jul 2004
Posts: 550
|
Vitor we are upgrading AIX MQ and WMB so yes it is and the version of MQ is as posted at the start
(I happen to think that is true in the sig yes you wrote it but I stole it)
jeff I will get together the info and let you know but basically it contains a shedload( that means a lot) of 6209 errors
_________________
Who is General Failure and why is he reading my hard drive?
Artificial Intelligence stands no chance against Natural Stupidity.
Only the User Trace Speaks The Truth |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Aug 24, 2012 6:58 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| nathanw wrote: |
| it contains a shedload( that means a lot) |
I'm sure I could have figured that out... 
What is logged just before the *first* AMQ6209? |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Aug 24, 2012 7:06 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| nathanw wrote: |
| Vitor we are upgrading AIX MQ and WMB so yes it is and the version of MQ is as posted at the start |
So does the queue manager work reliably if it doesn't have a broker sitting on it, i.e. is this a WMQ upgrade issue not a WMB upgrade issue.
| nathanw wrote: |
| (I happen to think that is true in the sig yes you wrote it but I stole it) |
And you're quite welcome. Spread the Word.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
