Home » Categories » Common Errors & Troubleshooting

Primary node showing the public ip instead of lan ip when cluster is configured

Article ID: 243 | Rating: Unrated | Last Updated: Wed, Nov 21, 2018 at 6:16 AM

The cluster tab of master node shows the licensed secondary ip and not the lan ip of the slave node. This happens when the slave node is behind a NAT. 

secondary node ip

In order to correct the other node ip, run the following command

/usr/local/ezlogin/ez_queryrunner.php "update prefix_settings set value='192.168.56.112' where name='remote_ip'"

 Now the cluster tab would show the lan ip of the other node instead of the public ip

secondary-fixed

 
Posted - Wed, Nov 21, 2018 at 6:14 AM. This article has been viewed 539 times.
Filed Under: Common Errors & Troubleshooting
0 (0)
Article Rating (No Votes)
Rate this article
    Attached Files
    There are no attachments for this article.
    Related Articles RSS Feed
    usernames already exists
    Viewed 333 times since Fri, Mar 15, 2019
    sshd[902]: debug1:PAM: password authentication failed for an illegal user: Authentication failure
    Viewed 4152 times since Thu, Feb 1, 2018
    strange characters in the SSH logs recordings
    Viewed 2062 times since Thu, Jun 15, 2017
    Error: User modify failed. Cannot modify user on other node: Authentication by SSH key failed!
    Viewed 408 times since Thu, Mar 7, 2019
    Setting session time out for the webinterface
    Viewed 2598 times since Wed, Jun 14, 2017
    fatal: no matching mac found: unable to ssh due to strict cipher set for pci dss compliance on remote box
    Viewed 3908 times since Fri, Sep 1, 2017
    Error opening terminal: xterm-256color.
    Viewed 256 times since Wed, Jul 31, 2019
    Token not found in Cpanel/WHM
    Viewed 3822 times since Wed, Jun 14, 2017
    getting config from other node failed
    Viewed 417 times since Wed, Jan 9, 2019
    User modify failed Cannot modify user on this node: Authentication by ssh key failed
    Viewed 3210 times since Wed, Jun 14, 2017