Fathom Replication database broker port

Posted by James Palmer on 14-Mar-2016 12:32

OE 10.2B08 on Win 2012 R2

I'm configuring replication on a couple of servers that are firewalled to the hilt. I've found where most of the port settings are, but one has me flummoxed. 

The Fathom Replication Server cannot connect to the database broker on 10.4.49.231 at the port -17466.

What determines this port number? I'd like to find the appropriate range to open up. 

Thanks. 

OpenEdge RDBMS - Forum

All Replies

Posted by marcv on 14-Mar-2016 13:00

Not sure if  you already gave this a look: knowledgebase.progress.com/.../P51588

It says it pertains to all supported OS configurations.

Posted by Libor Laubacher on 14-Mar-2016 15:33

And should be equal to -S of the target DB.

Posted by James Palmer on 14-Mar-2016 17:14

I seem to have three sets of ports I need to open. There is the minport maxport block. Then there is the agent port. 48000 sort of range, but there is a port around 17000 I can't account for that it's looking for. I'll post the full log file tomorrow but it's very odd.

Sent from my Windows Phone

Posted by Libor Laubacher on 14-Mar-2016 18:59

You need to open exactly the ports as MarcV pointed out above.

listener-minport/listener-maxport (see target.repl.properties) and -S your target database listens on (this should match  port= under [control-agent.agentX] section of source.repl.properties).

Posted by James Palmer on 15-Mar-2016 03:53

Ok so here's the source DB log file extract as promised:

[2016/03/14@16:54:23.169+0000] P-2672       T-6244  I RPLS   21: (-----) Connection timeout for host 10.4.49.231 port 4391 transport TCP.

[2016/03/14@16:55:05.177+0000] P-2672       T-6244  I RPLS   21: (-----) Connection timeout for host 10.4.49.231 port 4391 transport TCP.

[2016/03/14@16:55:47.174+0000] P-2672       T-6244  I RPLS   21: (-----) Connection timeout for host 10.4.49.231 port 4391 transport TCP.

[2016/03/14@16:56:29.179+0000] P-2672       T-6244  I RPLS   21: (-----) Connection timeout for host 10.4.49.231 port 4391 transport TCP.

[2016/03/14@16:57:11.171+0000] P-2672       T-6244  I RPLS   21: (-----) Connection timeout for host 10.4.49.231 port 4391 transport TCP.

[2016/03/14@16:57:53.178+0000] P-2672       T-6244  I RPLS   21: (-----) Connection timeout for host 10.4.49.231 port 4391 transport TCP.

[2016/03/14@16:58:35.171+0000] P-2672       T-6244  I RPLS   21: (-----) Connection timeout for host 10.4.49.231 port 4391 transport TCP.

[2016/03/14@16:59:17.176+0000] P-2672       T-6244  I RPLS   21: (-----) Connection timeout for host 10.4.49.231 port 4391 transport TCP.

[2016/03/14@16:59:59.175+0000] P-2672       T-6244  I RPLS   21: (-----) Connection timeout for host 10.4.49.231 port 4391 transport TCP.

[2016/03/14@17:00:41.177+0000] P-2672       T-6244  I RPLS   21: (-----) Connection timeout for host 10.4.49.231 port 4391 transport TCP.

[2016/03/14@17:05:42.283+0000] P-2672       T-6244  I RPLS   21: (11240) The Replication Server will continue Agent connection attempts for an additional 21 Hr 16 Min 6 Sec.

[2016/03/14@17:05:42.283+0000] P-2672       T-6244  I RPLS   21: (10842) Connecting to Fathom Replication Agent l_idx_pts.

[2016/03/14@17:06:47.311+0000] P-2672       T-6244  I RPLS   21: (10496) The Fathom Replication Agent l_idx_pts cannot be contacted by the database broker on host 10.4.49.231, port 48010.

[2016/03/14@17:06:47.311+0000] P-2672       T-6244  I RPLS   21: (10397) The connection attempt to the Fathom Replication Agent l_idx_pts failed.

[2016/03/14@17:11:48.416+0000] P-2672       T-6244  I RPLS   21: (11240) The Replication Server will continue Agent connection attempts for an additional 21 Hr 10 Min 0 Sec.

[2016/03/14@17:11:48.416+0000] P-2672       T-6244  I RPLS   21: (10842) Connecting to Fathom Replication Agent l_idx_pts.

[2016/03/14@17:12:53.482+0000] P-2672       T-6244  I RPLS   21: (10496) The Fathom Replication Agent l_idx_pts cannot be contacted by the database broker on host 10.4.49.231, port 48010.

[2016/03/14@17:12:53.482+0000] P-2672       T-6244  I RPLS   21: (10397) The connection attempt to the Fathom Replication Agent l_idx_pts failed.

[2016/03/14@17:17:54.091+0000] P-2672       T-6244  I RPLS   21: (11240) The Replication Server will continue Agent connection attempts for an additional 21 Hr 3 Min 54 Sec.

[2016/03/14@17:17:54.091+0000] P-2672       T-6244  I RPLS   21: (10842) Connecting to Fathom Replication Agent l_idx_pts.

[2016/03/14@17:18:59.290+0000] P-2672       T-6244  I RPLS   21: (10496) The Fathom Replication Agent l_idx_pts cannot be contacted by the database broker on host 10.4.49.231, port 48010.

[2016/03/14@17:18:59.290+0000] P-2672       T-6244  I RPLS   21: (10397) The connection attempt to the Fathom Replication Agent l_idx_pts failed.

[2016/03/14@17:24:00.396+0000] P-2672       T-6244  I RPLS   21: (11240) The Replication Server will continue Agent connection attempts for an additional 20 Hr 57 Min 48 Sec.

[2016/03/14@17:24:00.396+0000] P-2672       T-6244  I RPLS   21: (10842) Connecting to Fathom Replication Agent l_idx_pts.

[2016/03/14@17:24:42.397+0000] P-2672       T-6244  I RPLS   21: (-----) Connection timeout for host 10.4.49.231 port 48010 transport TCP.

[2016/03/14@17:25:32.399+0000] P-2672       T-6244  I RPLS   21: (-----) Connection timeout for host 10.4.49.231 port 48010 transport TCP.

[2016/03/14@17:26:22.400+0000] P-2672       T-6244  I RPLS   21: (-----) Connection timeout for host 10.4.49.231 port 48010 transport TCP.

[2016/03/14@17:27:12.401+0000] P-2672       T-6244  I RPLS   21: (-----) Connection timeout for host 10.4.49.231 port 48010 transport TCP.

[2016/03/14@17:28:02.405+0000] P-2672       T-6244  I RPLS   21: (-----) Connection timeout for host 10.4.49.231 port 48010 transport TCP.

[2016/03/14@17:28:52.402+0000] P-2672       T-6244  I RPLS   21: (-----) Connection timeout for host 10.4.49.231 port 48010 transport TCP.

[2016/03/14@17:29:42.407+0000] P-2672       T-6244  I RPLS   21: (-----) Connection timeout for host 10.4.49.231 port 48010 transport TCP.

[2016/03/14@17:30:32.410+0000] P-2672       T-6244  I RPLS   21: (-----) Connection timeout for host 10.4.49.231 port 48010 transport TCP.

[2016/03/14@17:30:40.410+0000] P-2672       T-6244  I RPLS   21: (10396) The Fathom Replication Server cannot connect to the database broker on 10.4.49.231 at the port -17526.

[2016/03/14@17:30:40.410+0000] P-2672       T-6244  I RPLS   21: (10397) The connection attempt to the Fathom Replication Agent l_idx_pts failed.

4391 is the minport/maxport range, 48010 is the agent setting. That's all fine and I understand. It's the 17526 I don't understand and it won't work without that port open.

What concerns me is that it's different for a couple of the other databases we are replicating (this is a multi-db environment), and I'm worried it might change on DB restart, hence needing to know where it comes from so I can cater for the range.

Posted by Libor Laubacher on 15-Mar-2016 04:05

>  It's the 17526 I don't understand and it won't work without that port open.

-17526 is just an integer overflow, it should have said 48010

Posted by Libor Laubacher on 15-Mar-2016 04:06

I mean -17256 = 48010 in this case.

Posted by James Palmer on 15-Mar-2016 04:15

Oh right... duuuh! Silly me. Right I'll try taking those 17k range ports back out again and see what happens. :)

Posted by George Potemkin on 15-Mar-2016 04:29

> -17526 is just an integer overflow, it should have said 48010

In fact it's a bug of promsgs file:
%LThe Fathom Replication Agent is listening on port %l. (10394)
%LThe Fathom Replication Server is listening on port %l. (10395)
%LThe Fathom Replication Server cannot connect to the database broker on %s at the port %d. (10396)

Message 10396 uses the "%d" tag instead of the "%l"

Hex editor can "fix" the bug. ;-)

Just in case: the similar issues:

10.0A 13/12/2003 %LThe Fathom Replication Server cannot connect to the database broker on %s at the port %d. (10396)
10.0B 05/08/2004 This process has been made ready using port %d to be used by the attachable Debugger. (11826)
10.2B 14/12/2009 %LA remote client was unable to connect to server %d using port %d - please check the port. (12451)
10.2B 14/12/2009 %LServer %d has %d unresolved pending connections(s). Please check port %d. (12454)

Posted by James Palmer on 15-Mar-2016 04:46

Thanks George. Is it fixed in 11.6? If not I'll raise it as a bug.

Posted by George Potemkin on 15-Mar-2016 05:04

No, it's not fixed in 11.6.

BTW, I has made an Excel file with all messages extracted from promsgs file and combined with the information from $DLC/prohelp/msgdata

ftp.progress-tech.ru/.../promsgs.dump.11.6.xlsx

For example, you can check all messages with the text that contains "port %d" (or "port %l").

Posted by James Palmer on 15-Mar-2016 05:07

Thanks George - helpful indeed!

Posted by James Palmer on 15-Mar-2016 05:11

Case raised: 00341689

Posted by James Palmer on 23-Mar-2016 08:52

This is fixed in 11.7

This thread is closed