Hello, I am running seafile on docker within my proxmox server and recently had to migrate this over to a new proxmox server and rebuilt it. Everything works just find, however, now the SeaDrive does not seem to be functioning correctly anymore on either of my personal linux machines.
I looked at the seadrive-gui.log
and get the following;
[09/01/2022 09:11:42 AM] loaded 1 accounts
[09/01/2022 09:11:42 AM] starting applet rpc service
[09/01/2022 09:11:42 AM] socket file exists, delete it anyway
[09/01/2022 09:11:42 AM] applet rpc service started
[09/01/2022 09:11:42 AM] seadrive gui started
[09/01/2022 09:11:42 AM] starting seadrive daemon: seadrive "-d" "/home/vnc/.seadrive/data" "-l" "/home/vnc/.seadrive/logs/seadrive.log" "-f" "/home/vnc/SeaDrive"
[09/01/2022 09:11:42 AM] Name com.canonical.AppMenu.Registrar does not exist on the session bus
[09/01/2022 09:11:45 AM] Unable to get config value download_limit: Config not exists
[09/01/2022 09:11:45 AM] Unable to get config value upload_limit: Config not exists
[09/01/2022 09:11:45 AM] Switched to account seafile.example_com USERNAME 3f35046
[09/01/2022 09:11:46 AM] Switched to account seafile.example_com USERNAME 3f35046
[09/01/2022 09:14:00 AM] Unable to get config value download_limit: Config not exists
[09/01/2022 09:14:00 AM] Unable to get config value upload_limit: Config not exists
When I do launch SeaDrive, some folders are not loading, all of Local & 2 sub-folders within My-Libraries. I tried to delete my account, then uninstall it with apt purge seadrive-daemon seadrive-gui
, and finally reinstalled. However, I am still having the same issue.
I also attempted to set it up without the GUI and used the following commands as shown in the documentation;
curl -d "username=USERNAME&password=PASSWORD" -H "X-SEAFILE-OTP: 2FA" seafile.example_com/api2/auth-token/
#result
{"token":"TOKEN-STRING"}
vim ~/seadrive.conf
#START OF CONFIG FILE
[account]
server = seafile.example_com
username = USERNAME
token = TOKEN-STRING
is_pro = false
[general]
client_name = popOS-Desktop
[cache]
size_limit = 10GB
clean_cache_interval = 10
#END OF CONFIG FILE
seadrive -c ~/seadrive.conf -f -d ~/.seadrive/data -l ~/.seadrive/logs/seadrive.log /home/vnc/SeaDrive
I was able to connect correctly, however, I am still having issues with not all of my folders loading.
I also run the Seafile client on my computers and that works beautify, it responds almost instantaneously so I feel like my Seafile set up is working correctly.
Any advice? Thanks!
You have to check seadrive.log for errors.
Sorry for the delay, its been a busy couple of days. Below is the seadrive.log
output
$ tail -n 20 .seadrive/logs/seadrive.log
[09/01/22 21:42:16] http-tx-mgr.c(4358): Bad response code for GET https_seafile.example.com/seafhttp/repo/8871de0a-7325-417c-9f21-b1aa2a4798a6/fs-id-list/?server-head=9bf0873b1f761a047a578729ff993b7f1c2e81ea&dir-only=1: 500.
[09/01/22 21:42:16] http-tx-mgr.c(5043): Failed to get fs id list for repo 8871de0a on server https_seafile.example.com.
[09/01/22 21:42:16] http-tx-mgr.c(1128): Transfer repo '8871de0a': ('normal', 'fs') --> ('error', 'finished')
[09/01/22 21:42:16] sync-mgr.c(648): Repo 'Local' sync state transition from downloading to 'error': 'Error occured in download.'.
[09/01/22 21:42:16] http-tx-mgr.c(4358): Bad response code for GET https_seafile.example.com/seafhttp/repo/80c37b83-9fa1-489d-b814-2ad0935e21cf/fs-id-list/?server-head=c0848f8ec3de1babc01d12a84984236bc4ab71ae&dir-only=1: 500.
[09/01/22 21:42:16] http-tx-mgr.c(5043): Failed to get fs id list for repo 80c37b83 on server https_seafile.example.com.
[09/01/22 21:42:16] http-tx-mgr.c(1128): Transfer repo '80c37b83': ('normal', 'fs') --> ('error', 'finished')
[09/01/22 21:42:16] sync-mgr.c(648): Repo '1 - Folder ABC' sync state transition from downloading to 'error': 'Error occured in download.'.
[09/01/22 21:42:17] sync-mgr.c(1670): Cloning repo 1 - Folder ABC(80c37b83-9fa1-489d-b814-2ad0935e21cf).
[09/01/22 21:42:17] sync-mgr.c(615): Repo '1 - Folder ABC' sync state transition from 'synchronized' to 'downloading'.
[09/01/22 21:42:17] sync-mgr.c(1670): Cloning repo Folder-123(7b1af5a2-fd6f-4c26-8f33-b470bb2256e6).
[09/01/22 21:42:17] http-tx-mgr.c(5015): Download with HTTP sync protocol version 2.
[09/01/22 21:42:17] sync-mgr.c(615): Repo 'Folder-123' sync state transition from 'synchronized' to 'downloading'.
[09/01/22 21:42:17] sync-mgr.c(1670): Cloning repo Local(8871de0a-7325-417c-9f21-b1aa2a4798a6).
[09/01/22 21:42:17] http-tx-mgr.c(1128): Transfer repo '80c37b83': ('normal', 'init') --> ('normal', 'check')
[09/01/22 21:42:17] http-tx-mgr.c(5015): Download with HTTP sync protocol version 2.
[09/01/22 21:42:17] sync-mgr.c(615): Repo 'Local' sync state transition from 'synchronized' to 'downloading'.
[09/01/22 21:42:17] http-tx-mgr.c(5015): Download with HTTP sync protocol version 2.
[09/01/22 21:42:17] http-tx-mgr.c(1128): Transfer repo '8871de0a': ('normal', 'init') --> ('normal', 'check')
[09/01/22 21:42:17] http-tx-mgr.c(1128): Transfer repo '7b1af5a2': ('normal', 'init') --> ('normal', 'check')
The library 80c37b83-9fa1-489d-b814-2ad0935e21cf may be corrupted. You can run seaf-fsck on the server to check this library.
You can also check seafile.log on the server to see any error related to this library.
I was able to check the log file and ran the command within the docker container. When I ran the command ./seaf-fsck.sh
, it returned with a lot of my repos being damaged and a few returned as “Failed to inflate”. In the case of 80c37b83-9fa1-489d-b814-2ad0935e21cf
it returned as “Failed to inflate” and being damaged.
Based on the docs on Seafile FSCK, I see that there is a repair option but I dont see it mention anything about a repo/library being damaged or failed to inflate. Would the command ./seaf-fsck.sh -r 80c37b83-9fa1-489d-b814-2ad0935e21cf
correct these issues? I think in my case because there seems to be a decent amount of library’s that are returning with issues I should probably run ./seaf-fsck.sh --repair
to cover all of the library’s.
Below are the results of seafile.log
:
root@a6f44921a90d:/opt/seafile/seafile-server-9.0.7# tail -n 20 /shared/seafile/logs/seafile.log
2022-09-02 08:30:32 Failed to inflate.
2022-09-02 08:30:32 ../common/fs-mgr.c(1707): Failed to decompress dir object 1e9b49f99e64098236960355ae8600f851da2fcf.
2022-09-02 08:30:32 ../common/diff-simple.c(134): Failed to find dir 8871de0a-7325-417c-9f21-b1aa2a4798a6:1e9b49f99e64098236960355ae8600f851da2fcf.
2022-09-02 08:30:32 http-server.c(1495): Failed to diff remote and master head for repo 8871de0a.
2022-09-06 07:45:51 Failed to inflate.
2022-09-06 07:45:51 ../common/fs-mgr.c(1707): Failed to decompress dir object 1e9b49f99e64098236960355ae8600f851da2fcf.
2022-09-06 07:45:51 ../common/diff-simple.c(134): Failed to find dir 8871de0a-7325-417c-9f21-b1aa2a4798a6:1e9b49f99e64098236960355ae8600f851da2fcf.
2022-09-06 07:45:51 http-server.c(1495): Failed to diff remote and master head for repo 8871de0a.
2022-09-06 19:08:38 Failed to inflate.
2022-09-06 19:08:38 ../common/fs-mgr.c(1707): Failed to decompress dir object 1e9b49f99e64098236960355ae8600f851da2fcf.
2022-09-06 19:08:38 ../common/diff-simple.c(134): Failed to find dir 8871de0a-7325-417c-9f21-b1aa2a4798a6:1e9b49f99e64098236960355ae8600f851da2fcf.
2022-09-06 19:08:38 http-server.c(1495): Failed to diff remote and master head for repo 8871de0a.
2022-09-07 08:36:21 Failed to inflate.
2022-09-07 08:36:21 ../common/fs-mgr.c(1707): Failed to decompress dir object 1e9b49f99e64098236960355ae8600f851da2fcf.
2022-09-07 08:36:21 ../common/diff-simple.c(134): Failed to find dir 8871de0a-7325-417c-9f21-b1aa2a4798a6:1e9b49f99e64098236960355ae8600f851da2fcf.
2022-09-07 08:36:21 http-server.c(1495): Failed to diff remote and master head for repo 8871de0a.
2022-09-08 08:09:01 Failed to inflate.
2022-09-08 08:09:01 ../common/fs-mgr.c(1707): Failed to decompress dir object 1e9b49f99e64098236960355ae8600f851da2fcf.
2022-09-08 08:09:01 ../common/diff-simple.c(134): Failed to find dir 8871de0a-7325-417c-9f21-b1aa2a4798a6:1e9b49f99e64098236960355ae8600f851da2fcf.
2022-09-08 08:09:01 http-server.c(1495): Failed to diff remote and master head for repo 8871de0a.
What do you think?
Okay so I ran ./seaf-fsck.sh --repair
and let that run, once it was done I ran ./seaf-fsck.sh
to see if there was any issues that was still persistent, luckily there were no issues. I then ran SeaDrive and have no more issues.
Big thanks to Jonathan for the help!!