Seafhttp error 500 in Seadrive

Hello,
I’m a relatively new seafile user. I have the pro version installed in a docker, and it’s been working great. I do have an issue though where the seadrive client shows an “Internal server error” shortly after starting seadrive. This error never goes away.

This is what I see in the log:

[07/08/20 21:53:03] Bad response code for GET https://my.domain.org/seafhttp/accessible-repos/?repo_id=eb458afe-eee2-47a8-bf79-9cdb9941afb0: 500.
[07/08/20 21:53:33] Bad response code for GET https://my.domain.org/seafhttp/accessible-repos/?repo_id=eb458afe-eee2-47a8-bf79-9cdb9941afb0: 500.
[07/08/20 21:54:03] Bad response code for GET https://my.domain.org/seafhttp/accessible-repos/?repo_id=eb458afe-eee2-47a8-bf79-9cdb9941afb0: 500.
[07/08/20 21:54:33] Bad response code for GET https://my.domain.org/seafhttp/accessible-repos/?repo_id=eb458afe-eee2-47a8-bf79-9cdb9941afb0: 500.
[07/08/20 21:55:03] Bad response code for GET https://my.domain.org/seafhttp/accessible-repos/?repo_id=eb458afe-eee2-47a8-bf79-9cdb9941afb0: 500.

I’m using NGINX Proxy Manager as my reverse proxy and I set up seafile as a proxy host, so basically the reverse proxy communicates with seafile via http but with the domain using https. I am trying to find out the reason I am getting this 500 error, but can’t dial it in. Does anyone have any experience with this and can offer some advice?

Note: All functions seem to work, I can upload and download files. The only issue I “might” have is that it isn’t detecting my file changes and updating them to the server sometimes and I have to restart seadrive. Maybe this issue is related? I don’t seem to have this issue when connected on the LAN using the http address, only when routing through the https reverse proxy.

I can now confirm that I am having this issue without using the reverse proxy as well. I connected using the internal address but still get the error, as well as intermittent sync issues.

I am getting this error in my seafile sever log as well:

[07/10/2020 10:28:00 PM] pipe client failed to connect to server: Connection refused
[07/10/2020 10:28:00 PM] …/common/seaf-utils.c(324): Named pipe client failed to connect.
[07/10/2020 10:28:00 PM] quota-mgr.c(934): Failed to alloc rpc client.
[07/10/2020 10:28:02 PM] pipe client failed to connect to server: Connection refused
[07/10/2020 10:28:02 PM] …/common/seaf-utils.c(324): Named pipe client failed to connect.
[07/10/2020 10:28:02 PM] quota-mgr.c(934): Failed to alloc rpc client.
[07/10/2020 10:28:27 PM] pipe client failed to connect to server: Connection refused
[07/10/2020 10:28:27 PM] …/common/seaf-utils.c(324): Named pipe client failed to connect.
[07/10/2020 10:28:57 PM] pipe client failed to connect to server: Connection refused
[07/10/2020 10:28:57 PM] …/common/seaf-utils.c(324): Named pipe client failed to connect.
[07/10/2020 10:29:02 PM] pipe client failed to connect to server: Connection refused
[07/10/2020 10:29:02 PM] …/common/seaf-utils.c(324): Named pipe client failed to connect.
[07/10/2020 10:29:02 PM] quota-mgr.c(934): Failed to alloc rpc client.
[07/10/2020 10:29:27 PM] pipe client failed to connect to server: Connection refused
[07/10/2020 10:29:27 PM] …/common/seaf-utils.c(324): Named pipe client failed to connect.

Can anyone point me in the right direction on this?

You should check server seafile.log for errors.

Hi Jonathan, thank you very much for your response. I have been pulling my hair out trying to solve this issue. I looked in my seafile server.log and it is filled with the following errors:

[07/13/2020 10:05:30 PM] …/common/seaf-utils.c(324): Named pipe client failed to connect.
[07/13/2020 10:05:30 PM] quota-mgr.c(934): Failed to alloc rpc client.
[07/13/2020 10:05:54 PM] pipe client failed to connect to server: Connection refused
[07/13/2020 10:05:54 PM] …/common/seaf-utils.c(324): Named pipe client failed to connect.
[07/13/2020 10:06:24 PM] pipe client failed to connect to server: Connection refused
[07/13/2020 10:06:24 PM] …/common/seaf-utils.c(324): Named pipe client failed to connect.
[07/13/2020 10:06:30 PM] pipe client failed to connect to server: Connection refused
[07/13/2020 10:06:30 PM] …/common/seaf-utils.c(324): Named pipe client failed to connect.
[07/13/2020 10:06:30 PM] quota-mgr.c(934): Failed to alloc rpc client.
[07/13/2020 10:06:54 PM] pipe client failed to connect to server: Connection refused
[07/13/2020 10:06:54 PM] …/common/seaf-utils.c(324): Named pipe client failed to connect.
[07/13/2020 10:07:24 PM] pipe client failed to connect to server: Connection refused
[07/13/2020 10:07:24 PM] …/common/seaf-utils.c(324): Named pipe client failed to connect.
[07/13/2020 10:07:30 PM] pipe client failed to connect to server: Connection refused
[07/13/2020 10:07:30 PM] …/common/seaf-utils.c(324): Named pipe client failed to connect.
[07/13/2020 10:07:30 PM] quota-mgr.c(934): Failed to alloc rpc client.
[07/13/2020 10:07:54 PM] pipe client failed to connect to server: Connection refused
[07/13/2020 10:07:54 PM] …/common/seaf-utils.c(324): Named pipe client failed to connect.
[07/13/2020 10:08:00 PM] pipe client failed to connect to server: Connection refused
[07/13/2020 10:08:00 PM] …/common/seaf-utils.c(324): Named pipe client failed to connect.
[07/13/2020 10:08:19 PM] filelock-mgr.c(973): Cleaning expired file locks.
[07/13/2020 10:08:24 PM] pipe client failed to connect to server: Connection refused
[07/13/2020 10:08:24 PM] …/common/seaf-utils.c(324): Named pipe client failed to connect.
[07/13/2020 10:08:26 PM] pipe client failed to connect to server: Connection refused
[07/13/2020 10:08:26 PM] …/common/seaf-utils.c(324): Named pipe client failed to connect.
[07/13/2020 10:08:26 PM] quota-mgr.c(934): Failed to alloc rpc client.
[07/13/2020 10:08:30 PM] pipe client failed to connect to server: Connection refused
[07/13/2020 10:08:30 PM] …/common/seaf-utils.c(324): Named pipe client failed to connect.
[07/13/2020 10:08:30 PM] quota-mgr.c(934): Failed to alloc rpc client.
[07/13/2020 10:08:54 PM] pipe client failed to connect to server: Connection refused
[07/13/2020 10:08:54 PM] …/common/seaf-utils.c(324): Named pipe client failed to connect.
[07/13/2020 10:09:24 PM] pipe client failed to connect to server: Connection refused
[07/13/2020 10:09:24 PM] …/common/seaf-utils.c(324): Named pipe client failed to connect.
[07/13/2020 10:09:30 PM] pipe client failed to connect to server: Connection refused
[07/13/2020 10:09:30 PM] …/common/seaf-utils.c(324): Named pipe client failed to connect.

Do these mean anything to you? Are they related to my problem?

It seems ccnet-server has crashed or some issues. You can try to restart your server. If problem persists, you should try latest server version.

Thanks Jonathan, restarting seemed to have helped, I also upgraded to Seadrive 2.0.4. My server is already version 7.1.4 so no update needed there. I guess now I will just monitor it to see if ccnet crashes again. Sorry I didn’t try this before, I spent so much time thinking it was a client sided issue I didn’t even think to restart the server itself.