DR: Cannot connect to secondary server - After secondary server restart
Posted in 2020
Tiago Santos's Informix 14 HDR secondary could not connect to the primary after a restart (Windows, error 10060, dbaccess error 908). Eric Vercelletto, Art Kagel and others suggested checking the network, port and trust settings. Changing sqlhosts protocols from onsoctcp to olsoctcp, matching NETTYPE, restored connection and replication.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Topics: High Availability & Replication, Storage & Space Management, Stored Procedures & SPL, Logging & Checkpoints
Hello, Everything was working well, but after restart my secundary Informix 14 Server, the replication stopped working. I don't know why, because i don't have network problems. I'm getting the following log on the secondary server: 11:23:25 Started 1 B-tree scanners. 11:23:25 B-tree scanner threshold set at 5000. 11:23:25 B-tree scanner range scan size set to -1. 11:23:25 B-tree scanner ALICE mode set to 6. 11:23:25 B-tree scanner index compression level set to med. 11:23:25 Physical Recovery Started at Page (2:136869). 11:23:25 Physical Recovery Complete: 7 Pages Examined, 2 Pages Restored. 11:23:25 DR: Trying to connect to primary server = ol_unifato 11:23:27 DR: Cannot connect to primary server 11:23:27 DR: Turned off on secondary server 11:23:27 Dataskip is now OFF for all dbspaces 11:23:27 Restartable Restore has been ENABLED 11:23:27 Recovery Mode 11:24:25 Booting Language <spl> from module <> 11:24:25 Loading Module <SPLNULL> On primary: 10:48:38 System Error: Wait on network event fai led 10:48:38 Socket: 2756, Mask: 16, Error: 10060 10:49:50 System Error: Wait on network event fai led 10:49:50 Socket: 2660, Mask: 16, Error: 10060 10:51:49 DR: Cannot connect to secondary server 10:53:09 Checkpoint Completed: duration was 0 seconds. 10:53:09 Mon Nov 9 - loguniq 129, logpos 0x671018, timestamp: 0x3185c343 Interval: 5469 10:53:09 Maximum server connections 65 10:53:09 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 648, Llog used 56 10:57:42 DR: Cannot connect to secondary server 10:58:13 Checkpoint Completed: duration was 0 seconds. I already restart the secondary server again, but the replication din't start. What i can do to solve de problem, preferably without start the primary. Thank you all, Tiago Santos ------------------------------ Tiago Santos ------------------------------ #Informix
Tiago
It seems that you connection between secondary and primary has problems, and this is a major reason for the secondary not be working fine
Did you test accessing the primary from the secondary using dbaccess (on the same port as the HDR connection) ?
Hello, Tiago. Make sure you are starting your secondary server using TCP alias, not SHM. It should work. HTH Alexandre Marini Obter o Outlook para Android
From error number I guessed this must be Windows. Errno 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. So something IS going wrong apparently on network level. Firewall maybe? ------------------------------ Andreas Legner ------------------------------
Hi Eric,
Effectively, I am also not getting access using dbaccess either. Your right.
I'm getting 908: Attempt to connect to database server failed.
Firewall is off on both server. I can correctly ping both machines.
sqlhosts file is ok...
I don't know what is happening.
Thanks,
------------------------------
Tiago Santos
------------------------------
Hello Alexandre, Sorry about this, but what do you mean with SHM? Thanks, ------------------------------ Tiago Santos ------------------------------
Tiago: It looks like the two systems are not trusting each other. Check your /etc/hosts.equiv or the $INFORMIXDIR/hosts.equiv or whatever file you have listed in the REMOTE_SERVER_CFG parameter if anything. The servers must be trusted to each other. Art Art S. Kagel, President and Principal Consultant ASK Database Management www.askdbmgt.com Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves.
Tiago : Second step : check if you can reach the port number (if it is open) with telnet or any other tools Third step: if yes, try connection to this alias and check the primary's Informix log file: check that the server/user are authenticated. If not, you would see errors -951 or -952
If it is a trust thing you should see an error in the target onstat –m
Cheers
Paul
Thank you all,
With your help i think i've discovered de problem
After change de protocol from
onsoctcp
to
olsoctcp
on sqlhosts file, finally i could establish a connection with dbaccess from the secondary do the primary.
After i change the protocol on the other lines (ol, dr, and lo services on sqlhosts), about secondary service and restart de secundary server, the replication began to work again.
I take a lock on onconfig files, and i saw that the company that configured my server, set the NETTYPE parameter whith
olsoctcp
,1,150,NET (on a Windows OS), and they configured sqlhosts file with
onsoctcp.
But now that every thing seems to be working again (with
olsoctcp)
, on a Windows OS, would be better
olsoctcp
or
onsoctcp.
Note: my Windows ODBC clients are configured with:
onsoctcp.
Thanks again for you comments,
------------------------------
Tiago Santos
------------------------------