Hello, we have recently updated Seafile 7.0.7 to version 7.0.8. Since then, the synchronization seems to have stopped working on Windows machines.
The download stops synchronizing at some point. Restarting the synchronization manually leads to following error:
Download could not be set up: Transport error
or “Task is already in progress”
Unfortunately, restarting Seafile or Windows, reinstalling and deleting all synchronized libraries was not successful.
The applet.log states:
[06/17/20 18:22:33]Failed to connect to named pipe: All pipe instances are busy.
[06/17/20 18:22:33]Failed to connect to named pipe: All pipe instances are busy.
[06/17/20 18:22:33] [Rpc Client] connected to daemon
[06/17/20 18:22:33] [Rpc Client] connected to daemon
[06/17/20 18:22:35]Starting the network status detector
[06/17/20 18:22:35] [AutoUpdateManager] cancel all download tasks
06/17/20 18:22:35] [AutoUpdateManager] clean file caches db
[06/17/20 18:22:35] [AutoUpdateManager] clean file caches
[06/17/20 18:22:35]starting applet rpc service
[06/17/20 18:22:35]applet rpc service started
[06/17/20 18:22:36]Failed to connect to named pipe: All pipe instances are busy.
[06/17/20 18:22:36]Failed to connect to named pipe: All pipe instances are busy.
[06/17/20 18:22:36]Failed to connect to named pipe: All pipe instances are busy.
[06/17/20 18:22:36] [Rpc Client] connected to daemon
[06/17/20 18:22:36][06/17/20 18:22:36][Rpc Client] connected to daemon
[ext listener] listening on \.\pipe\seafile_ext_pipe_cmNocmlzdGVu
[06/17/20 18:22:42]ServerStatusService: ignore request for host "127.0.0.1
[06/17/20 18:22:42] [api] network error for http://127.0.0.1:9800/media/avatars/default.png: Connection refused
[06/17/20 19:01:40]Seafile daemon process exited normally with code 0
[06/17/20 19:01:40]failed to write to named pipe: The pipe is being closed.
[06/17/20 19:01:40]failed to send rpc call: No error
[06/17/20 19:01:40]failed to write to named pipe: The pipe is being closed.
[06/17/20 19:01:40]failed to send rpc call: No error
[06/17/20 19:01:40]failed to write to named pipe: The pipe is being closed.
The synchronization logs do not show any errors until the termination.
We’ve already disabled antivirus and firewall.
seaf-fsck did not find any corrupted librarys.
A rollback to 7.0.7 solves the problem.
What could be the reason for that? We haven’t changed anything on our setup.