Continuous syncing when outside LAN

Hi community,

first, let me note my config:

  • Seafile Server
  • on Ubuntu Server
  • behind NAT (open and forwarded port 443) with
  • dynamic DNS using
  • Apache Server Seafile configuration.

All is working fine! Inside and outside my LAN.

Nevertheless, sth. strange is happening, when i’m outside my LAN.

Only when I am connected from “the outside” my HDDs keep on working and serving, without the necessity of syncing anything.
(I noticed that first, when my wife was using Seafile abroad and my HDDs made continuous noise.)
When all clients are within the LAN, those HDDs are only serving when asked to sync differences between Server and client.
When going over WAN/Internet, they are very busy.

This can also be observed in my Apache access log:
xx.xx.xx.xx - - [14/Apr/2018:20:04:27 +0200] “GET /seafhttp/protocol-version HTTP/1.1” 200 206 “-” “Seafile/6.0.7 (Windows NT)”
xx.xx.xx.xx - - [14/Apr/2018:20:04:28 +0200] “GET /seafhttp/repo/db8eb4c0-80d0-4ff6-936d-67bd553ba23a/commit/HEAD HTTP/1.1” 200 296 “-” “Seafile/6.0.7 (Windows NT)”
xx.xx.xx.xx - - [14/Apr/2018:20:04:28 +0200] “GET /seafhttp/protocol-version HTTP/1.1” 200 363 “-” “Seafile/6.0.7 (Windows NT)”
xx.xx.xx.xx - - [14/Apr/2018:20:04:28 +0200] “GET /seafhttp/repo/70b89446-744f-4017-bc89-64e9095c6e33/commit/HEAD HTTP/1.1” 200 296 “-” “Seafile/6.0.7 (Windows NT)”
xx.xx.xx.xx - - [14/Apr/2018:20:04:33 +0200] “GET /seafhttp/protocol-version HTTP/1.1” 200 363 “-” “Seafile/6.0.7 (Windows NT)”
xx.xx.xx.xx - - [14/Apr/2018:20:04:33 +0200] “GET /seafhttp/protocol-version HTTP/1.1” 200 363 “-” “Seafile/6.0.7 (Windows NT)”
xx.xx.xx.xx - - [14/Apr/2018:20:04:33 +0200] “GET /seafhttp/repo/70b89446-744f-4017-bc89-64e9095c6e33/commit/HEAD HTTP/1.1” 200 453 “-” “Seafile/6.0.7 (Windows NT)”
xx.xx.xx.xx - - [14/Apr/2018:20:04:33 +0200] “GET /seafhttp/repo/db8eb4c0-80d0-4ff6-936d-67bd553ba23a/commit/HEAD HTTP/1.1” 200 453 “-” “Seafile/6.0.7 (Windows NT)”
xx.xx.xx.xx - - [14/Apr/2018:20:04:38 +0200] “GET /seafhttp/protocol-version HTTP/1.1” 200 206 “-” “Seafile/6.0.7 (Windows NT)”
xx.xx.xx.xx - - [14/Apr/2018:20:04:38 +0200] “GET /seafhttp/repo/db8eb4c0-80d0-4ff6-936d-67bd553ba23a/commit/HEAD HTTP/1.1” 200 296 “-” “Seafile/6.0.7 (Windows NT)”
xx.xx.xx.xx - - [14/Apr/2018:20:04:38 +0200] “GET /seafhttp/protocol-version HTTP/1.1” 200 363 “-” “Seafile/6.0.7 (Windows NT)”
xx.xx.xx.xx - - [14/Apr/2018:20:04:38 +0200] “GET /seafhttp/repo/70b89446-744f-4017-bc89-64e9095c6e33/commit/HEAD HTTP/1.1” 200 296 “-” “Seafile/6.0.7 (Windows NT)”
xx.xx.xx.xx - - [14/Apr/2018:20:04:43 +0200] “GET /seafhttp/protocol-version HTTP/1.1” 200 363 “-” “Seafile/6.0.7 (Windows NT)”
xx.xx.xx.xx - - [14/Apr/2018:20:04:43 +0200] “GET /seafhttp/protocol-version HTTP/1.1” 200 363 “-” “Seafile/6.0.7 (Windows NT)”
xx.xx.xx.xx - - [14/Apr/2018:20:04:43 +0200] “GET /seafhttp/repo/70b89446-744f-4017-bc89-64e9095c6e33/commit/HEAD HTTP/1.1” 200 453 “-” “Seafile/6.0.7 (Windows NT)”
xx.xx.xx.xx - - [14/Apr/2018:20:04:43 +0200] “GET /seafhttp/repo/db8eb4c0-80d0-4ff6-936d-67bd553ba23a/commit/HEAD HTTP/1.1” 200 453 “-” “Seafile/6.0.7 (Windows NT)”
xx.xx.xx.xx - - [14/Apr/2018:20:04:48 +0200] “GET /seafhttp/protocol-version HTTP/1.1” 200 206 “-” “Seafile/6.0.7 (Windows NT)”
xx.xx.xx.xx - - [14/Apr/2018:20:04:48 +0200] “GET /seafhttp/repo/9dfe6129-1880-4730-afb1-ae891b2f0fda/commit/HEAD HTTP/1.1” 200 296 “-” “Seafile/6.0.7 (Windows NT)”
xx.xx.xx.xx - - [14/Apr/2018:20:04:48 +0200] “GET /seafhttp/protocol-version HTTP/1.1” 200 363 “-” “Seafile/6.0.7 (Windows NT)”
xx.xx.xx.xx - - [14/Apr/2018:20:04:48 +0200] “GET /seafhttp/repo/70b89446-744f-4017-bc89-64e9095c6e33/commit/HEAD HTTP/1.1” 200 296 “-” “Seafile/6.0.7 (Windows NT)”
xx.xx.xx.xx - - [14/Apr/2018:20:04:48 +0200] “GET /seafhttp/repo/db8eb4c0-80d0-4ff6-936d-67bd553ba23a/commit/HEAD HTTP/1.1” 200 453 “-” “Seafile/6.0.7 (Windows NT)”
xx.xx.xx.xx - - [14/Apr/2018:20:04:48 +0200] “GET /seafhttp/repo/7fb53d97-218f-4dec-9683-ffc1b9c46e72/commit/HEAD HTTP/1.1” 200 453 “-” “Seafile/6.0.7 (Windows NT)”

What is going on here?
Why do client and server talk so much when going over WAN and making my HDDs spin all night long?
No sync, just traffic…

Greets
Henrik

How often the DynDNS Service is running?

Once per day.
But my IP-Adress had never changed during the last ~6 months.

Can you try to acces the server from outside with the IP and look if it’s appearing?

It appears that it’s trying exactly every 5 seconds. Do you have a sync interval set up in the external client?

Sorry for the delay!

I made some research and found out that the repo was an old repo.
Seafile continued to try to get access to another users documents folder (on windows machine). This only occured when connected via Internet (not Intranet).
I granted him temp. access.
After this I checked this setting in client menu:
“Do not unsync a library when not found on server” and watched client and server logs.

Problem solved.

But, I do not know exactly what was happening here. Very strange behaviour.

1 Like