Keyword search: 

Communications errors - too many IPs or network adapters

1/5/2017 9:27 AM
You can subscribe to this wiki article using an RSS feed reader.

Problem:

I have several network interface cards in my system and FRP displays several different IPs for the same server. I would like to get rid of the IPs that I do not need.

We have also seen a number of cases with web servers having dozens of IPs or adapters leading to FRP failing to connect for jobs, or adding servers, modifications etc.  Sometimes this problem is also accompanied by a messages similar to the error message seen below in the second screen shot.

Sometimes you may find communication errors in your job logs where jobs fail,  in some cases only a few IP addresses can cause communications errors that can be fixed by using these steps.

 


Example Screen shots of too many adapters, and the warning messages.

 

 

Solution:

1. In the management console upper right corner, click the settings / system settings
2. Find the box to set the external IP address of your management server,  enter the one IP address visible to all of your replication servers.  If there is no external IP use the internal IP seen by all servers.
3. Click Save.

Next you will need to make changes to the  /FileReplicationPro/etc /s2s.properties  file on each of your servers.

The s2s.properties file provides a parameter for ignoring or locking out any number of IPs that you specify. You can list the items by IP or by host name and it is a comma separated list with NO SPACES.

Before proceeding with the steps, you can save work if you have a lot of IPs by using the TIP below.

1. Stop all FRP services on all of your servers,  you will not restart the services until you have completed the steps for each server.
2. Using a text editor, edit the file ect/ s2s.properties  (attached is a sample modified file if you which to see what it should look like)  MFRP - s2s.properties
3. Add the IPs or host names to the field s2s.tcp.exclude_ips=

Be POSITIVE to remove the one address in the list that should be used by FRP for replication. 

Example s2s.tcp.exclude_ips=192.168.201.249,192.168.201.247,192.168.201.245,192.168.201.241,192.168.201.225,192.168.201.220,192.168.201.217,192.168.201.213,192.168.201.210,192.168.201.207,192.168.201.205,192.168.201.202,192.168.201.200,192.168.201.190  (as many IPs and host names as needed)

Example s2s.tcp.exclude_ips=168.100.37.3,PRODUCTION_SVR1

4. Change the following parameter from =true  to =false 

s2s.enable_auto_discovery=false

Save the file and exit.

5. Restart the Management console all three FRP... services  (FRPRep, FRPHelp, FRPMgmt) and on all other servers start only the replication service  FRPRep.

Wait a few minutes, then go to the management console  the servers should appear in the server list as online  if not wait a little longer and if still not there,  re - add them by using the IP address that should be used for replication.

You should be able to proceed normally now.

Reminder save copies of your modified s2s.properties files for when you need to upgrade or reinstall in the future so you can replace them when they have been over written by your installer.  BTW:  An upgrade or reinstall should preserve your settings in a file called s2s.properties_bck  which you can recover / rename to get your custom changes back.

 

TIP  You can go to the servers list as seen in the screen shot above,  using your mouse highlight the list of IP numbers for the first server taking note of which server the IPs belong to.   Be POSITIVE to remove the one address in the list that should be used by FRP for replication. Save the list to a .txt file with the name or IP of the server.  In that text file use a search and replace to remove all the spaces in the string of IP addresses.  Save it.  This will be the list you will copy and paste into the s2s.properties  file for that server when you edit it.

Tail logs in Windows

Tags:
Home: WIKI - Knowledge Base Index What's new: Recently changed articles