| Author |
Message
|
| sebastianhirt |
 Posted: Fri Jun 03, 2005 5:39 am Post subject: |
 |
|
Yatiri
Joined: 07 Jun 2004
Posts: 620
Location: Germany
|
| Mr Butcher wrote: |
well, i do not care which way unless we see what we need to see. both ways work. so what?  |
Well, apart from the fact that you usually have 3 times as much output to analyze, it really does not matter. Lets not argue about it, it was just a hint, not meant to criticise your way of working.
It appears 3 times, because it is 3 'different' queue managers. You can see that when you compare the QMIDs.
As Mr Butcher mentioned before. Get your channels sorted out. That might pretty sure do the deal.
You have to use the reset Cluster command to get the definitions of your 'old/unwanted/whatever/deleted' APS2 queuemanagers out of the clusters repository.
Please be careful with the comand, and use only the QMID as identifier for the queue managers.
cheers
Sebastian |
|
| Back to top |
|
 |
| lionel35 |
| Posted: Fri Jun 03, 2005 5:55 am Post subject: |
|
|
Novice
Joined: 03 Jun 2005
Posts: 11
|
ok thank you, i will that... the error logs are :
-------------------------------------------------------------------------------
06/03/2005 14:52:43
AMQ9202: Remote host 'aps3 (172.26.234.172) (1414)' not available, retry later.
EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host 'aps3
(172.26.234.172) (1414)' was not successful. However the error may be a
transitory one and it may be possible to successfully allocate a TCP/IP
conversation later.
ACTION:
Try the connection again later. If the failure persists, record the error
values and contact your systems administrator. The return code from TCP/IP is
10061 (X'274D'). The reason for the failure may be that this host cannot reach
the destination host. It may also be possible that the listening program at
host 'aps3 (172.26.234.172) (1414)' was not running. If this is the case,
perform the relevant operations to start the TCP/IP listening program, and try
again.
----- amqccita.c : 973 --------------------------------------------------------
06/03/2005 14:52:43
AMQ9202: Remote host 'i20045168 (10.67.188.200) (1414)' not available, retry
later.
EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host 'i20045168
(10.67.188.200) (1414)' was not successful. However the error may be a
transitory one and it may be possible to successfully allocate a TCP/IP
conversation later.
ACTION:
Try the connection again later. If the failure persists, record the error
values and contact your systems administrator. The return code from TCP/IP is
10061 (X'274D'). The reason for the failure may be that this host cannot reach
the destination host. It may also be possible that the listening program at
host 'i20045168 (10.67.188.200) (1414)' was not running. If this is the case,
perform the relevant operations to start the TCP/IP listening program, and try
again.
----- amqccita.c : 973 --------------------------------------------------------
06/03/2005 14:52:44
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'TO_CRBTAPS3' ended abnormally.
ACTION:
Look at previous error messages for channel program 'TO_CRBTAPS3' in the error
files to determine the cause of the failure.
----- amqrccca.c : 769 --------------------------------------------------------
06/03/2005 14:52:44
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'TO_CRBTSAGIC1' ended abnormally.
ACTION:
Look at previous error messages for channel program 'TO_CRBTSAGIC1' in the
error files to determine the cause of the failure.
----- amqrccca.c : 769 -------------------------------------------------------- |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Fri Jun 03, 2005 6:01 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
ok, it does not look like an mq problem, but you may check the receiving end too. check also that the listener is running on the receiving end.
then i would go and check the network.
good luck
_________________
Regards, Butcher |
|
| Back to top |
|
|
| lionel35 |
| Posted: Fri Jun 03, 2005 6:10 am Post subject: |
|
|
Novice
Joined: 03 Jun 2005
Posts: 11
|
It is the same pb on aps3 (which logs are done below) and sagic1. Maybe it comes from a firewall ? I don't know...
----- amqccita.c : 973 --------------------------------------------------------
06/03/2005 21:56:41
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'TO_CRBTSAGIC1' ended abnormally.
ACTION:
Look at previous error messages for channel program 'TO_CRBTSAGIC1' in the
error files to determine the cause of the failure.
----- amqrccca.c : 883 --------------------------------------------------------
06/03/2005 21:57:40
AMQ9002: Channel 'TO_CRBTSAGIC1' is starting.
EXPLANATION:
Channel 'TO_CRBTSAGIC1' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
06/03/2005 21:57:41
AMQ9202: Remote host 'i20045168 (10.67.188.200) (1414)' not available, retry
later.
EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host 'i20045168
(10.67.188.200) (1414)' was not successful. However the error may be a
transitory one and it may be possible to successfully allocate a TCP/IP
conversation later.
ACTION:
Try the connection again later. If the failure persists, record the error
values and contact your systems administrator. The return code from TCP/IP is
10061 (X'274D'). The reason for the failure may be that this host cannot reach
the destination host. It may also be possible that the listening program at
host 'i20045168 (10.67.188.200) (1414)' was not running. If this is the case,
perform the relevant operations to start the TCP/IP listening program, and try
again.
----- amqccita.c : 973 --------------------------------------------------------
06/03/2005 21:57:41
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'TO_CRBTSAGIC1' ended abnormally.
ACTION:
Look at previous error messages for channel program 'TO_CRBTSAGIC1' in the
error files to determine the cause of the failure.
----- amqrccca.c : 883 --------------------------------------------------------
06/03/2005 21:58:40
AMQ9002: Channel 'TO_CRBTSAGIC1' is starting.
EXPLANATION:
Channel 'TO_CRBTSAGIC1' is starting.
ACTION:
None.
------------------------------------------------------------------------------- |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Fri Jun 03, 2005 6:13 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
yes, maybe firewall. its up to you to find out.
it must have been working before, because the queuemanager know each other as cluster queuemanagers.
_________________
Regards, Butcher
Last edited by Mr Butcher on Fri Jun 03, 2005 8:08 am; edited 1 time in total |
|
| Back to top |
|
|
| sjensen |
| Posted: Fri Jun 03, 2005 6:59 am Post subject: |
|
|
Centurion
Joined: 18 Dec 2003
Posts: 134
Location: London
|
Hi,
Can APS2 ping APS3 and SAGIC1
Can APS3 ping APS2 and SAGIC1
Can SAGIC1 ping APS2 and APS3?
If not you have a network issue.
Cheers
Stefan |
|
| Back to top |
|
|
| sebastianhirt |
| Posted: Mon Jun 06, 2005 12:33 am Post subject: |
|
|
Yatiri
Joined: 07 Jun 2004
Posts: 620
Location: Germany
|
Hallo,
I hope you have solved the problem in the meanwhile on your own. But if not. One more time:
In you SAGIC1 Full Repository you have 3 definitions of the same queuemanager (CRBTAPS2) with different queue manager IDs.
| Code: |
QMID(CRBTAPS2_2005-06-02_10.38.29)
QMID(CRBTAPS2_2005-06-02_10.52.57)
QMID(CRBTAPS2_2005-06-02_09.01.28) |
As long as you have not cleared this stuff up. Your channels will never go from retrying to running. You need to make your Cluster consistent 1st thing.
Your Cluster is simply 'confused'!
Find out the real Queue manager ID of CRBTAPS2, and bounce the other ones out of the Full Repository.
If you need assistance on that, let me know.
cheers
Sebastian |
|
| Back to top |
|
|
| lionel35 |
| Posted: Mon Jun 06, 2005 12:52 am Post subject: |
|
|
Novice
Joined: 03 Jun 2005
Posts: 11
|
Hi,
thank you for asking me some news 
well, i still have some pbs, and i may ask you for help in the afternoon...after i fixed some tricks... |
|
| Back to top |
|
|
| lionel35 |
| Posted: Mon Jun 06, 2005 1:48 am Post subject: |
|
|
Novice
Joined: 03 Jun 2005
Posts: 11
|
Ok,
as you said, there was a network pb, but it was not all... so i restarted all the queue managers (with the MQSeries explorer) and then it was the reverse pb :
APS2 could see QA.SAGICIC but APS3 could not anymore.
So, i restarted all the queue managers and there was no pb anymore.
Could you please explain me why it is so "umpredictable" ? |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Mon Jun 06, 2005 2:36 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
maybe there is a new problem that you have not found jet... 
these days clustering is quite "predictable" (this was not the case when clustering was new).
_________________
Regards, Butcher |
|
| Back to top |
|
|
|
|
