Clearly there is abug in the app, it should not create millions of lines but if there is a connection error a popup or something should indicate that it’s not working.
How do I find the root cause of the connection error ?
The issue you’re encountering, characterized by the pipe client failed to connect to server: Connection refused error, indicates that the SeaDrive GUI applet is unable to communicate with the background service (the daemon). On macOS SeaDrive 3.x, the “daemon” is implemented as a Finder File Provider extension.
Here are a few steps to troubleshoot and resolve this:
Manually Trigger the Extension: In SeaDrive 3.x, the background service often remains dormant until macOS is explicitly told to activate it. Open Finder and click on the SeaDrive entry in the left sidebar (under “Locations”). This action usually “wakes up” the daemon part and establishes the connection.
System Restart: Because the background service is managed by the macOS File Provider framework, it can sometimes enter a stuck state that only a system reboot can clear.
Reset Client Preferences: If the connection continues to fail, there might be a corruption in the local configuration. You can try resetting it by running the following command in your Terminal (note that you will need to re-add your account afterwards):
Check for Path Length Issues: In some cases, if your macOS username or the installation path is exceptionally long, the internal Unix socket used for communication might fail to initialize due to system character limits.
If none of the above works, try removing the account within the app and adding it again, as this forces the system to re-register the File Provider domain.
I keep getting these error messages as well in 3.0.24.
And only a system restart temporarily fixes it (for me). It feels like a bug and looks like an issue on MacOS side. Not sure if there is something that can be done about it.
I have another issue that I am not sure if it’s related to this. I will open another post about it.
It seems that when Seadrive starts it produces the error messages
failed to send rpc call: Broken pipe
failed to get sync errors: Transport Error
and then on first file action on the server it produces constangtly this error message block
failed to send rpc call: Broken pipe
pipe client failed to connect to server: Connection refused
Call searpc from disconnected client
Call searpc from disconnected client
Call searpc from disconnected client
Call searpc from disconnected client
Call searpc from disconnected client
Call searpc from disconnected client
The “Broken pipe” and “Connection refused” errors indicate that the SeaDrive GUI is unable to communicate with the background File Provider extension (the daemon), likely because the extension has crashed or entered a stuck state.
To help diagnose and resolve this, you can try the following steps:
Check for Crash Reports: Open the macOS Console.app and look under Crash Reports for any entries related to SeaDrive or its File Provider extension. These reports can provide specific details on why the process is failing.
Enable Debug Logging: To capture the exact moment of failure, you can start SeaDrive from the Terminal with debug logging enabled: