J
James Palmer
Guest
Still having trouble with Replication with a client. I'll try and explain. OE 10.2B08. Windows. This has been an ongoing issue for a while. Struggling to get anywhere with Tech Support as well. Had another instance of problems just now. Client rebooted the target. This comes up perfectly well and the agents are listening. But the repl servers are "Performing Failure Recovery". If I Terminate Server all you get is a line in the log file indicating that the administrator account logged in and out, but no action, and the repl server does NOT terminate. If I repeat the action the process terminating the server hangs itself up, and if I kill it the DB shuts down due to a latch being held. I can't disconnect it using proshut. At the point the target server was rebooted we get this in the source logs: [2017/05/15@16:54:16.178+0100] P-6108 T-7148 I RPLS 26: (9407) Connection failure for host 192.168.16.238 port 4400 transport TCP. [2017/05/15@16:54:16.178+0100] P-6108 T-7148 I RPLS 26: (11713) A communications error -4008 in rpCOM_RecvMsg. [2017/05/15@16:54:16.178+0100] P-6108 T-7148 I RPLS 26: (-----) Diagnostic Dump of RPCommInfo_t - TCP/IP Receive Error [2017/05/15@16:54:16.178+0100] P-6108 T-7148 I RPLS 26: (-----) 0000: d8a0 0102 0000 0000 0000 0000 3011 0000 8abb 0000 8abb 0000 0200 0000 4400 0000 [2017/05/15@16:54:16.178+0100] P-6108 T-7148 I RPLS 26: (-----) 0020: c3e1 0300 fb6c 0000 0000 0000 efce 1959 0000 0000 3c41 0000 0100 0000 1900 0000 [2017/05/15@16:54:16.178+0100] P-6108 T-7148 I RPLS 26: (-----) 0040: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 [2017/05/15@16:54:16.178+0100] P-6108 T-7148 I RPLS 26: (-----) 0060: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 [2017/05/15@16:54:16.178+0100] P-6108 T-7148 I RPLS 26: (-----) 0080: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 [2017/05/15@16:54:16.178+0100] P-6108 T-7148 I RPLS 26: (-----) 00a0: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 [2017/05/15@16:54:16.178+0100] P-6108 T-7148 I RPLS 26: (-----) 00c0: 0000 0000 0000 0000 0000 0000 3139 322e 3136 382e 3136 2e32 3338 0000 0000 0000 [2017/05/15@16:54:16.178+0100] P-6108 T-7148 I RPLS 26: (-----) 00e0: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 [2017/05/15@16:54:16.178+0100] P-6108 T-7148 I RPLS 26: (-----) 0100: 0000 0000 0000 0000 0000 0000 3139 322e 3136 382e 3136 2e32 3338 0000 0000 0000 [2017/05/15@16:54:16.178+0100] P-6108 T-7148 I RPLS 26: (-----) 0120: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 [2017/05/15@16:54:16.178+0100] P-6108 T-7148 I RPLS 26: (-----) 0140: 0000 0000 0000 0000 0000 0000 [2017/05/15@16:54:16.180+0100] P-6108 T-7148 I RPLS 26: (10492) A communications error -157 occurred in function rpNLS_PollListener while receiving a message. [2017/05/15@16:54:16.180+0100] P-6108 T-7148 I RPLS 26: (10661) The Fathom Replication Server is beginning recovery for agent l_idx_audit. [2017/05/15@16:54:16.180+0100] P-6108 T-7148 I RPLS 26: (10842) Connecting to Fathom Replication Agent l_idx_audit. We've advised the client to reboot the source, but it's not an ideal solution as they are 24/7.
Continue reading...
Continue reading...