Skip to Content

getting config from other node failed

How to solve 'getting config from other node failed' error while installing secondary/slave?


Overview: This article helps Ezeelogin admin users to solve the error 'getting config from other node failed' encountered while installing secondary/slave.


1. Log in to the primary node and check the configuration and other file permissions.

root@primary:~# ll /usr/local/etc/ezlogin/
total 252
drwxr-xr-x 2 ezadmin ezuser 4096 May 6 16:18 ./
drwxr-xr-x 4 root root 4096 Mar 14 15:07 ../
-r--r--r-- 1 root root 4781 May 6 11:35 build.dat
-rw-r--r-- 1 root root 207949 May 6 11:35 cacert.pem
-rw-r--r-- 1 root root 559 May 6 11:35 ez.conf
-r--r--r-- 1 root ezuser 464 Mar 14 15:07 id_clkey
-r--r--r-- 1 root ezuser 96 Mar 14 15:07 id_clkey.pub
-r--r--r-- 1 root ezuser 444 Mar 14 15:07 id_key
-r--r--r-- 1 root ezuser 89 Mar 14 15:07 id_key.pub
-r--r--r-- 1 root root 4781 Mar 14 15:07 lic.dat
-rw-rw-rw- 1 root root 25 May 6 11:35 replication.conf

Create the build.dat file in the /usr/local/etc/ezlogin/ directory on the primary node if it is not already present.

root@primary:~# touch /usr/local/etc/ezlogin/build.dat

2. Check if the LoginGraceTime parameter is enabled and set to a safe value on both nodes.

root@server:~# vim /etc/ssh/sshd_config

LoginGraceTime 30

3. Check if you can manually SCP files from the primary to the secondary node and from the secondary to the primary node as well.

root@primary:~# scp file.txt root@secondary_ip:/root/

root@secondary:~# scp file.txt root@primary_ip:/root/


Related Articles:

Install slave / secondary node for high availability in jump server