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 » MQ crash, no FDC, no reason, no trace...

Post new topic  Reply to topic Goto page Previous  1, 2
 MQ crash, no FDC, no reason, no trace... « View previous topic :: View next topic » 
Author Message
ramires
PostPosted: Mon Jun 07, 2010 1:56 am    Post subject: Reply with quote

Knight

Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
do you have the AIX levels MQ 7 requires? According this:

http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27011894

"This requires either AIX 5.3 TL6 SP4 plus APAR IZ10231 or AIX 6.1.
Please note: APAR IZ10231 is available in AIX 5.3-TechnologyLevel6-ServicePack5 (AIX 5.3 TL6-SP5, TL7, 610)."
Back to top
View user's profile Send private message
banjar1
PostPosted: Mon Jun 07, 2010 2:21 am    Post subject: Reply with quote

Acolyte

Joined: 29 Nov 2006
Posts: 54
Location: FRA
It has just happened again
I will post more after I make sure everything is up and running.
Back to top
View user's profile Send private message Send e-mail
banjar1
PostPosted: Mon Jun 07, 2010 2:27 am    Post subject: Reply with quote

Acolyte

Joined: 29 Nov 2006
Posts: 54
Location: FRA
Here is the list of 'mqm' processes running just before I killed them (channels excluded):

qlhhubfc:/var/mqm/errors$ grep -v runmqchl processes.list
UID PID PPID C STIME TTY TIME CMD
mqm 942180 4829290 0 07:43:39 - 0:06 amqzlaa0 -mQLHHUB -fip23
mqm 1163480 19402930 0 06:48:00 - 0:09 /usr/mqm/bin/runmqtrm -m QLHHUB -q INITQ.METAR
mqm 1343614 4829290 0 06:48:36 - 0:15 amqzlaa0 -mQLHHUB -fip6
mqm 3322036 4829290 0 06:47:55 - 0:00 /usr/mqm/bin/amqzfuma -m QLHHUB
mqm 3633338 4243620 0 09:46:04 - 0:00 sh -c /var/mqm/bin/trigger_publish.ksh 'TMC 24PUB.OPMET PUBLISH /var/mqm/bin/trigger_publish.ksh QLHHUB '
mqm 3915802 4829290 0 08:36:18 - 0:01 amqzlaa0 -mQLHHUB -fip37
mqm 3997766 4829290 0 08:35:32 - 0:01 amqzlaa0 -mQLHHUB -fip33
mqm 4194436 4829290 0 08:35:39 - 0:01 amqzlaa0 -mQLHHUB -fip34
mqm 4231350 1163480 0 09:45:21 - 0:00 sh -c /var/mqm/bin/trigger_publish.ksh 'TMC 24PUB.METAR PUBLISH /var/mqm/bin/trigger_publish.ksh QLHHUB '
mqm 4243620 19402930 0 06:48:00 - 0:00 /usr/mqm/bin/runmqtrm -m QLHHUB -q INITQ.OPMET
mqm 4255786 8409222 0 10:06:59 - 0:00 sleep 10
mqm 4427926 19402930 0 06:48:00 - 0:00 /usr/mqm/bin/runmqtrm -m QLHHUB -q INITQ.INOTAM
mqm 4526194 4829290 0 08:36:18 - 0:11 amqzlaa0 -mQLHHUB -fip38
mqm 4620542 4829290 3 06:48:00 - 2:09 amqzlaa0 -mQLHHUB -fip0
mqm 4689996 4829290 4 06:47:55 - 2:06 amqzmuc0 -m QLHHUB
mqm 4702232 4829290 0 06:48:00 - 0:12 amqzlaa0 -mQLHHUB -fip1
mqm 4829290 1 0 06:47:55 - 0:07 amqzxma0 -m QLHHUB
mqm 4833306 4829290 0 08:36:08 - 0:02 amqzlaa0 -mQLHHUB -fip36
mqm 4956396 13140052 0 08:38:28 pts/16 0:07 /bin/ksh /home/mqm/mqcc.ksh
mqm 5247130 4829290 1 07:50:48 - 0:12 amqzlaa0 -mQLHHUB -fip30
mqm 5320816 4231350 0 10:07:03 - 0:00 sleep 10
mqm 5644444 4829290 1 07:05:41 - 0:54 amqzlaa0 -mQLHHUB -fip16
mqm 5808218 4829290 0 07:09:26 - 0:13 amqzlaa0 -mQLHHUB -fip17
mqm 5894326 4829290 3 07:03:13 - 0:47 amqzlaa0 -mQLHHUB -fip15
mqm 6185030 4829290 0 06:48:05 - 0:00 amqzlaa0 -mQLHHUB -fip3
mqm 7000314 19402930 0 06:48:00 - 0:00 /usr/mqm/bin/runmqtrm -m QLHHUB -q INITQ.WXSATIM
mqm 7115002 4829290 0 06:47:57 - 0:01 amqzmur0 -m QLHHUB
mqm 7143676 19402930 0 06:48:00 - 0:00 /usr/mqm/bin/amqpcsea QLHHUB
mqm 7266362 9048074 0 07:27:41 - 0:00 sshd: mqm@pts/16
mqm 7274624 4427926 0 09:47:27 - 0:00 sh -c /var/mqm/bin/trigger_publish.ksh 'TMC 24PUB.INOTAM PUBLISH /var/mqm/bin/trigger_publish.ksh QLHHUB '
mqm 7299196 4829290 0 06:48:02 - 0:16 amqzlaa0 -mQLHHUB -fip2
mqm 7712786 19402930 0 06:48:00 - 0:00 /usr/mqm/bin/runmqtrm -m QLHHUB -q INITQ.UAD
mqm 8409222 7000314 0 09:51:38 - 0:00 sh -c /var/mqm/bin/trigger_publish.ksh 'TMC 24PUB.WXSATIM PUBLISH /var/mqm/bin/trigger_publish.ksh QLHHUB '
mqm 8458302 4829290 0 08:36:02 - 0:01 amqzlaa0 -mQLHHUB -fip35
mqm 8818870 19042456 0 06:48:04 - 0:08 /usr/mqm/bin/amqrmppa -m QLHHUB
mqm 8851604 26030110 0 10:06:59 - 0:00 sleep 10
mqm 10719354 19402930 0 06:48:00 - 0:00 /usr/mqm/bin/runmqtrm -m QLHHUB -q INITQ.TAF
mqm 11501788 26169388 0 10:07:01 - 0:00 sleep 10
mqm 13140052 7266362 0 07:27:41 pts/16 0:00 -ksh
mqm 14475282 4829290 0 07:53:32 - 0:11 amqzlaa0 -mQLHHUB -fip32
mqm 16687124 19402930 0 06:48:00 - 0:00 /usr/mqm/bin/runmqtrm -m QLHHUB -q INITQ.BUFR
mqm 17731834 4956396 0 10:07:04 pts/16 0:00 [sleep]
mqm 18022650 19402930 3 06:48:00 - 1:00 /usr/mqm/bin/runmqchi -m QLHHUB -q SYSTEM.CHANNEL.INITQ -r
mqm 18628838 3633338 0 10:06:59 - 0:00 sleep 10
mqm 19042456 19402930 0 06:48:00 - 0:00 /usr/mqm/bin/runmqlsr -r -m QLHHUB -t TCP -p 1414
mqm 19386470 4829290 0 06:49:40 - 0:29 amqzlaa0 -mQLHHUB -fip13
mqm 19402930 4829290 0 06:47:59 - 0:00 /usr/mqm/bin/amqzmgr0 -m QLHHUB
mqm 22765694 4829290 0 09:32:55 - 0:00 amqzlaa0 -mQLHHUB -fip39
mqm 23085210 4829290 0 06:47:59 - 0:00 /usr/mqm/bin/amqrrmfa -m QLHHUB -t2332800 -s2592000 -p2592000 -g5184000 -c3600
mqm 23232550 2179254 0 06:22:52 pts/1 0:00 -ksh
mqm 24002620 4829290 0 06:47:57 - 0:00 amqzmuf0 -m QLHHUB
mqm 24485982 19402930 0 06:48:00 - 0:00 /usr/mqm/bin/runmqtrm -m QLHHUB -q INITQ.WXSIGWX
mqm 24518674 19402930 0 06:48:00 - 0:00 /usr/mqm/bin/runmqtrm -m QLHHUB -q INITQ.OTS
mqm 25493600 7274624 0 10:06:59 - 0:00 sleep 10
mqm 26030110 10719354 0 09:45:37 - 0:00 sh -c /var/mqm/bin/trigger_publish.ksh 'TMC 24PUB.TAF PUBLISH /var/mqm/bin/trigger_publish.ksh QLHHUB '
mqm 26169388 7712786 0 09:46:38 - 0:00 sh -c /var/mqm/bin/trigger_publish.ksh 'TMC 24PUB.UAD PUBLISH /var/mqm/bin/trigger_publish.ksh QLHHUB '
mqm 26271916 4829290 0 06:47:59 - 0:00 /usr/mqm/bin/amqzdmaa -m QLHHUB


dspmq output (!!!)

QMNAME(QLHHUB) STATUS(Running)


and runmqsc:
5724-H72 (C) Copyright IBM Corp. 1994, 2009. ALL RIGHTS RESERVED.
AMQ8146: WebSphere MQ queue manager not available.

No MQSC commands read.
No commands have a syntax error.
All valid MQSC commands were processed.

Last edited by banjar1 on Mon Jun 07, 2010 3:07 am; edited 1 time in total
Back to top
View user's profile Send private message Send e-mail
banjar1
PostPosted: Mon Jun 07, 2010 3:06 am    Post subject: Reply with quote

Acolyte

Joined: 29 Nov 2006
Posts: 54
Location: FRA
ramires wrote:
do you have the AIX levels MQ 7 requires? According this:

http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27011894

"This requires either AIX 5.3 TL6 SP4 plus APAR IZ10231 or AIX 6.1.
Please note: APAR IZ10231 is available in AIX 5.3-TechnologyLevel6-ServicePack5 (AIX 5.3 TL6-SP5, TL7, 610)."


Hmmm why would you think that should affect us? We do have only TL4.
Back to top
View user's profile Send private message Send e-mail
banjar1
PostPosted: Mon Jun 07, 2010 3:42 am    Post subject: Reply with quote

Acolyte

Joined: 29 Nov 2006
Posts: 54
Location: FRA
Looks like IBM found the guilty...

and the results of our investigation (as sent to IBM):

The suggestions included in IZ66327 lead us to check some other stuff and we found out that exactly at the time when our problems with MQ started a system called CFM was distributing some files to qlhhub using 'rdist' command (it is already disabled). You may want to add this corelation to the USERS AFFECTED section of IZ66327.
Back to top
View user's profile Send private message Send e-mail
ramires
PostPosted: Mon Jun 07, 2010 11:14 am    Post subject: Reply with quote

Knight

Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
banjar1 wrote:
Hmmm why would you think that should affect us? We do have only TL4.

just because is the minimum recommended fix. If you don't have that level and call IBM support, they may request to upgrade to a supported environment.
Back to top
View user's profile Send private message
warrenJ
PostPosted: Tue Jun 08, 2010 1:31 pm    Post subject: Reply with quote

Apprentice

Joined: 11 Jan 2004
Posts: 29
Location: AUSTRALIA
mvic wrote
Quote:
There are dozens of reasons a channel can end
but in our case it crashed, no FDC's, and blocked all messages from leaving the xmitq.
IBM support said "I don't think I've ever seen a failure like this that doesn't result in a FDC being thrown."
Here's the problem http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg1IZ74889 , just one of about ½ dozen v7.0.1.0/1 PMR's we've raised.
We've just got 2 more v7 outstanding PMR's waiting to be fixed.
Back to top
View user's profile Send private message
banjar1
PostPosted: Tue Jun 08, 2010 11:43 pm    Post subject: Reply with quote

Acolyte

Joined: 29 Nov 2006
Posts: 54
Location: FRA
We are unaffected; no RFH2 headers.
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 Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » General IBM MQ Support » MQ crash, no FDC, no reason, no trace...
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.