Domino Cluster Error

HCL Domino Domino Forum
1

Hello,

I meet a problem today when I create a cluster for two domino servers R6.0.2. Both of two servers’ console have the following errors.

CLREPL> checking for modifications to cluster directory.

RTRREPL> checking RTR queue for modified databases.

RTRREPL> Retrying failed replications.

I input “Show cluster” command, both of the two servers have the following errors.

…

Server: test1 , availability: unreachable

Server: test2 , availability: unreachable

And in the test1’s cluster replication event, there is the errors

Unable to replicate from Mail\XXX.nsf to CLUSTER test2 Mail\XXX.nsf: Remote system not responding.

But ping the other server, both available. I am puzzled by it. Any help is appreciated. Thanks a lot.

Qu Yue

2

Subject: Domino Cluster Error

Hola, probaste crear un documento de conexión (connection document) para cada uno de los servers?, en estos puedes definir el nombre y la IP del servidor de destino.También asegurate que no haya puertos bloqueados por algún firewall entre los servidores.

Saludos y suerte

3

Subject: Domino Cluster Error-------(To Saludos y suerte)

Hi, Saludos

Would you like to translate your reponse to English language? Sorry that I could not understand it. Thanks again.

4

Subject: results of TRACE console command

What does the Domino Trace command report?

If you’re trying to connect to test2 from test1, enter ‘trace test2’ (best to use test2’s distinguished name rather than its common name) from the console on test1. This is much like using the trace button from a client’s port configuration dialog, but (in this case) more useful, because it reports the connection status from the perspective of the server you’re investigating. The results of the trace may isolate the problem for you.

5

Subject: RE: results of TRACE console command

Ted, thanks your response.

I traced test1 and test2, not find any clue. The following is the trace report.

trace test1

09/06/2004 08:57:58 AM Network: Determining path to server test1

09/06/2004 08:57:58 AM Network: Available Ports: TCPIP

09/06/2004 08:57:58 AM Network: Checking normal priority connection documents only…

09/06/2004 08:57:58 AM Network: Allowing wild card connection documents…

09/06/2004 08:57:58 AM Network: Enabling name service requests and probes…

09/06/2004 08:57:58 AM Network: Address found in local TCPIP names table for test1

09/06/2004 08:57:58 AM Network: Connecting to test1 over TCPIP

09/06/2004 08:57:58 AM Network: Using address ‘XX.XX.XX.XX’ for test1 on TCPIP

09/06/2004 08:57:58 AM Network: Connected to server test1

trace test2

09/06/2004 09:06:33 AM Network: Determining path to server test2

09/06/2004 09:06:33 AM Network: Available Ports: TCPIP

09/06/2004 09:06:33 AM Network: Checking normal priority connection documents only…

09/06/2004 09:06:33 AM Network: Allowing wild card connection documents…

09/06/2004 09:06:33 AM Network: Enabling name service requests and probes…

09/06/2004 09:06:33 AM Network: Address found in local TCPIP names table for test2

09/06/2004 09:06:33 AM Network: Connecting to test2 over TCPIP

09/06/2004 09:06:33 AM Network: Using address ‘test2.ll.com’ for test2 on TCPIP

09/06/2004 09:06:33 AM Network: Requesting IP Address for test2.ll.com from DNS

09/06/2004 09:06:33 AM Network: DNS returned address XX.XX.XX.XX for test2.ll.com

09/06/2004 09:06:33 AM Network: Connected to server test2.ll.com

It seems that connection is OK. But why in cluster replication event there is an error that remote system not responding. I am puzzled by it. Thanks again

Qu Yue

6

Subject: diagnostic setting passthru_loglevel=4

This one has me puzzled, too. The notes.ini setting passthru_loglevel=5 tells Domino to write more information network connection attempts to the server log; that may tell you more about why the cluster probe is failing. The output (log only, not console) looks something like this when a cluster probe or other network connection succeeds:

09/07/2004 09:21:18 AM Network: Connecting to Test2/Acme over TCPIP

09/07/2004 09:21:18 AM Network: Using address ‘10.19.19.11’ for Test2/Acme on TCPIP

09/07/2004 09:21:21 AM Network: Connected to server Test2/Acme

In your case, it may show something more interesting.