The forum will be down for maintenance over the weekend of August 18-20, 2017. The forum will be shut down on the evening (EDT) of Friday, August 18. Downtime is unknown but may be up to two days. The forum will be restarted as soon as maintenance is complete.

How should I approach this symptom in an arbiter-partner1-partner2-copy setup?

16.0.0.2419 read-only scale-out server is failing to connect over the WAN, and it produces the following I messages every 60 seconds.

The E message appears only very occasionally.

I. 04/24 12:44:38. Database "XXX" mirroring: Waited for incoming connection for 60 seconds before requesting log page, now dropping connections
I. 04/24 12:44:38. Database "XXX" mirroring:  disconnected from parent "DONORCENTRAL_primary"
I. 04/24 12:44:38. Database "XXX" mirroring:  parent reconnection process starting
E. 04/24 12:44:38. Database "XXX" mirroring:  mirror connection to server "DONORCENTRAL_primary" failed: connection already exists
I. 04/24 12:44:40. Database "XXX" mirroring:  connected to parent "DONORCENTRAL_primary"
I. 04/24 12:44:40. Database "XXX" mirroring:  synchronizing ...
I. 04/24 12:44:41. Database "XXX" mirroring:  parent reconnection process stopping

asked 25 Apr, 13:27

Breck%20Carter's gravatar image

Breck Carter
26.5k433604876
accept rate: 21%

edited 25 Apr, 13:27


So your main problem appears to be that the outgoing connection from this server to the primary can be established, but the connection going the other way cannot (either due to misconfiguration or a firewall or something else in your network blocking it). If you don't know why this is occurring, you can start by enabling -z or sa_server_option('DebuggingInformation') on both the copy node and the primary and look at the messages in the server console. They should give you a hint about what the outgoing and incoming connections are attempting to do.

I've seen the "E. 04/24 12:44:38. Database "XXX" mirroring: mirror connection to server "DONORCENTRAL_primary" failed: connection already exists" message sporadically occur when the server attempts to create a mirroring connection immediately after the last one was dropped, but internally we haven't fully cleaned up the old connection. In the cases I've seen it, this condition should clear with in a few seconds and isn't anything to worry about given what is happening when it is occurring.

I hope this helps,

Ian

permanent link

answered 25 Apr, 15:24

Ian%20McHardy's gravatar image

Ian McHardy
3.1k23353
accept rate: 39%

edited 25 Apr, 15:31

1

In this case the client reports "firewall" was both problem and solution... similar to "beer" :)

(29 Apr, 05:17) Breck Carter
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×54

question asked: 25 Apr, 13:27

question was seen: 293 times

last updated: 29 Apr, 05:22