Seafile Pro Real-Time backup

I recently set up a seafile real-time backup server according to the instructions in the manual and the servers are failing to communicate. I am a novice to mid-level Linux user who is setting up the system for my small business and need help resolving my issue. Any help is very much appreciated

Both servers are running Ubuntu 18.04 LTS with seafile pro 6.3.4
I am using HTTP and both systems are on the same network now,
The production seafile is 192.168.63.190 and the backup is 192.168.63.170
I have no issues with the production server and have approximately 2 TB of data.

the seafile log from the backup server reads:
[09/19/2018 12:29:20 PM] Disconnected from daemon
[09/19/18 12:29:26] http-server.c(197): fileserver: worker_threads = 10
[09/19/18 12:29:26] http-server.c(210): fileserver: backlog = 32
[09/19/18 12:29:26] http-server.c(225): fileserver: fixed_block_size = 8388608
[09/19/18 12:29:26] http-server.c(240): fileserver: web_token_expire_time = 3600
[09/19/18 12:29:26] http-server.c(255): fileserver: max_indexing_threads = 1
[09/19/18 12:29:26] http-server.c(270): fileserver: max_index_processing_threads= 3
[09/19/2018 12:29:26 PM] …/common/mq-mgr.c(61): [mq client] mq cilent is started
[09/19/2018 12:29:26 PM] http-tx-mgr.c(2177): Sync polling timer triggered, start to fetch repo list from primary.
[09/19/2018 12:29:26 PM] http-tx-mgr.c(611): libcurl failed to GET http://192.168.63.190/seafhttp/server-sync/repo-list: Couldn’t connect to server.
[09/19/2018 12:29:27 PM] size-sched.c(103): Repo size compute queue size is 0
[09/19/2018 12:34:27 PM] size-sched.c(103): Repo size compute queue size is 0
[09/19/2018 12:39:27 PM] size-sched.c(103): Repo size compute queue size is 0
[09/19/2018 12:44:27 PM] size-sched.c(103): Repo size compute queue size is 0
[09/19/2018 12:49:27 PM] size-sched.c(103): Repo size compute queue size is 0
[09/19/2018 12:54:27 PM] size-sched.c(103): Repo size compute queue size is 0
[09/19/2018 12:59:27 PM] size-sched.c(103): Repo size compute queue size is 0
[09/19/2018 01:04:27 PM] size-sched.c(103): Repo size compute queue size is 0
[09/19/2018 01:09:27 PM] size-sched.c(103): Repo size compute queue size is 0

The corresponding seafile.log on the server reads:
[09/19/18 12:34:26] http-server.c(197): fileserver: worker_threads = 15
[09/19/18 12:34:26] http-server.c(210): fileserver: backlog = 32
[09/19/18 12:34:26] http-server.c(225): fileserver: fixed_block_size = 8388608
[09/19/18 12:34:26] http-server.c(240): fileserver: web_token_expire_time = 3600
[09/19/18 12:34:26] http-server.c(255): fileserver: max_indexing_threads = 1
[09/19/18 12:34:26] http-server.c(270): fileserver: max_index_processing_threads= 3
[09/19/18 12:34:26] …/common/mq-mgr.c(61): [mq client] mq cilent is started
[09/19/18 12:34:26] filelock-mgr.c(973): Cleaning expired file locks.
[09/19/18 12:34:26] filelock-mgr.c(1003): 0 expired file locks are unlocked.
[09/19/18 12:34:27] size-sched.c(103): Repo size compute queue size is 0
[09/19/18 12:36:18] http-tx-mgr.c(821): libcurl failed to POST http://192.168.63.170/seafhttp/server-sync/update-sync/9a81f7f6-8621-47dc-9706-2ae085009cc8: Couldn’t connect to server.
[09/19/18 12:39:27] size-sched.c(103): Repo size compute queue size is 0
[09/19/18 12:44:27] size-sched.c(103): Repo size compute queue size is 0
[09/19/18 12:46:19] http-tx-mgr.c(821): libcurl failed to POST http://192.168.63.170/seafhttp/server-sync/update-sync/27ad24e8-5c25-4632-9c7d-ca6ec4114610: Couldn’t connect to server.
[09/19/18 12:49:07] http-tx-mgr.c(821): libcurl failed to POST http://192.168.63.170/seafhttp/server-sync/update-sync/9a81f7f6-8621-47dc-9706-2ae085009cc8: Couldn’t connect to server.
[09/19/18 12:49:27] size-sched.c(103): Repo size compute queue size is 0
[09/19/18 12:50:53] http-tx-mgr.c(821): libcurl failed to POST http://192.168.63.170/seafhttp/server-sync/update-sync/27ad24e8-5c25-4632-9c7d-ca6ec4114610: Couldn’t connect to server.
[09/19/18 12:54:27] size-sched.c(103): Repo size compute queue size is 0
[09/19/18 12:55:10] http-tx-mgr.c(821): libcurl failed to POST http://192.168.63.170/seafhttp/server-sync/update-sync/27ad24e8-5c25-4632-9c7d-ca6ec4114610: Couldn’t connect to server.
[09/19/18 12:59:27] size-sched.c(103): Repo size compute queue size is 0
[09/19/18 13:02:04] http-tx-mgr.c(821): libcurl failed to POST http://192.168.63.170/seafhttp/server-sync/update-sync/9a81f7f6-8621-47dc-9706-2ae085009cc8: Couldn’t connect to server.
[09/19/18 13:04:27] size-sched.c(103): Repo size compute queue size is 0
[09/19/18 13:09:27] size-sched.c(103): Repo size compute queue size is 0
[09/19/18 13:14:27] size-sched.c(103): Repo size compute queue size is 0

Thank you!

So both servers are unable to access the other server. This is most likely a network configuration problem. You need to check your network and firewall settings. You can check if you are able to connect to the other server e.g. with wget:

wget -S http://192.168.63.190/seafhttp/server-sync/repo-list

HTH!

Thank you for your suggestions
I did not realize ubuntu has a firewall. I disabled it on both servers for testing purposes.

To clarify my setup: I am running seahub on the main server I do not use Apache on either machine.

I also researched further and I believe I should have been using port 8082 appended to the backup_url and to the primary_url.

When I issue the command: wget -S http://192.168.63.190:8082/seafhttp/server-sync/repo-list
–2018-09-20 12:59:16-- http://192.168.63.190:8082/seafhttp/server-sync/repo-list
Connecting to 192.168.63.190:8082… connected.
HTTP request sent, awaiting response…
HTTP/1.1 404 Not Found
Content-Length: 0
2018-09-20 12:59:16 ERROR 404: Not Found.

In the seafile primary server log, I see several lines similar to:
[09/20/18 12:46:11] http-tx-mgr.c(903): Failed to send update repo to backup(http://192.168.63.170:8082) side: Resource not found.

it appears from the logs that the backup server does initiate and send the request correctly
[09/20/18 12:50:04] http-tx-mgr.c(2177): Sync polling timer triggered, start to fetch repo list from primary.
[09/20/18 12:50:04] http-tx-mgr.c(1028): Failed to get repo list from primary: Resource not found.

Do I need Apache running on the backup server since seahub is not running?

Thank you!