[Solved] Server Error while trying to sync big zip files

Hello,
I have setup a Seafile server on my Raspberry Pi. The sync was working fine until I tried syncing some big zip files. The windows client shows a Server error. Here are the logs:

[12/27/20 15:32:37] http-tx-mgr.c(1157): Transfer repo ‘6c0763b2’: (‘normal’, ‘fs’) → (‘normal’, ‘data’)
[12/27/20 15:32:38] http-tx-mgr.c(3355): Bad response code for PUT htt ps://xxx/seafhttp/repo/6c0763b2-34fa-4610-8a5e-f6dd3a41fe56/block/90ad76419996e5e3efbc63865a3f3ae6811bb9e7: 500.
[12/27/20 15:32:38] http-tx-mgr.c(929): libcurl failed to PUT htt ps://xxx/seafhttp/repo/6c0763b2-34fa-4610-8a5e-f6dd3a41fe56/block/c2d45612bf08eea359d0f03944bb0b29b7b7f63d: Operation was aborted by an application callback.
[12/27/20 15:32:38] http-tx-mgr.c(929): libcurl failed to PUT htt ps://xxx/seafhttp/repo/6c0763b2-34fa-4610-8a5e-f6dd3a41fe56/block/95d2ffc547992b6d3d03e2755a5deb265038d584: Operation was aborted by an application callback.
[12/27/20 15:32:38] http-tx-mgr.c(929): libcurl failed to PUT htt ps://xxx/seafhttp/repo/6c0763b2-34fa-4610-8a5e-f6dd3a41fe56/block/913d2363b2f9243f81bd99f1dc7f4049a9329b33: Operation was aborted by an application callback.
[12/27/20 15:32:38] http-tx-mgr.c(1157): Transfer repo ‘6c0763b2’: (‘normal’, ‘data’) → (‘error’, ‘finished’)
[12/27/20 15:32:38] sync-mgr.c(621): Repo ‘Backups’ sync state transition from uploading to ‘error’: ‘Server error’.
[12/27/20 15:33:08] sync-mgr.c(582): Repo ‘Backups’ sync state transition from ‘synchronized’ to ‘uploading’.
[12/27/20 15:33:08] http-tx-mgr.c(1157): Transfer repo ‘6c0763b2’: (‘normal’, ‘init’) → (‘normal’, ‘check’)
[12/27/20 15:33:08] http-tx-mgr.c(1157): Transfer repo ‘6c0763b2’: (‘normal’, ‘check’) → (‘normal’, ‘commit’)
[12/27/20 15:33:08] http-tx-mgr.c(1157): Transfer repo ‘6c0763b2’: (‘normal’, ‘commit’) → (‘normal’, ‘fs’)
[12/27/20 15:33:08] http-tx-mgr.c(1157): Transfer repo ‘6c0763b2’: (‘normal’, ‘fs’) → (‘normal’, ‘data’)
[12/27/20 15:33:09] http-tx-mgr.c(3355): Bad response code for PUT htt ps://xxx/seafhttp/repo/6c0763b2-34fa-4610-8a5e-f6dd3a41fe56/block/90ad76419996e5e3efbc63865a3f3ae6811bb9e7: 500.
[12/27/20 15:33:09] http-tx-mgr.c(929): libcurl failed to PUT htt ps://xxx/seafhttp/repo/6c0763b2-34fa-4610-8a5e-f6dd3a41fe56/block/c2d45612bf08eea359d0f03944bb0b29b7b7f63d: Operation was aborted by an application callback.
[12/27/20 15:33:09] http-tx-mgr.c(3355): Bad response code for PUT htt ps://xxx/seafhttp/repo/6c0763b2-34fa-4610-8a5e-f6dd3a41fe56/block/913d2363b2f9243f81bd99f1dc7f4049a9329b33: 500.
[12/27/20 15:33:09] http-tx-mgr.c(3355): Bad response code for PUT htt ps://xxx/seafhttp/repo/6c0763b2-34fa-4610-8a5e-f6dd3a41fe56/block/95d2ffc547992b6d3d03e2755a5deb265038d584: 500.
[12/27/20 15:33:09] http-tx-mgr.c(1157): Transfer repo ‘6c0763b2’: (‘normal’, ‘data’) → (‘error’, ‘finished’)
[12/27/20 15:33:09] sync-mgr.c(621): Repo ‘Backups’ sync state transition from uploading to ‘error’: ‘Server error’.
[12/27/20 15:33:39] sync-mgr.c(582): Repo ‘Backups’ sync state transition from ‘synchronized’ to ‘uploading’.
[12/27/20 15:33:39] http-tx-mgr.c(1157): Transfer repo ‘6c0763b2’: (‘normal’, ‘init’) → (‘normal’, ‘check’)
[12/27/20 15:33:39] http-tx-mgr.c(1157): Transfer repo ‘6c0763b2’: (‘normal’, ‘check’) → (‘normal’, ‘commit’)
[12/27/20 15:33:39] http-tx-mgr.c(1157): Transfer repo ‘6c0763b2’: (‘normal’, ‘commit’) → (‘normal’, ‘fs’)
[12/27/20 15:33:39] http-tx-mgr.c(1157): Transfer repo ‘6c0763b2’: (‘normal’, ‘fs’) → (‘normal’, ‘data’)
[12/27/20 15:33:40] http-tx-mgr.c(3355): Bad response code for PUT htt ps://xxx/seafhttp/repo/6c0763b2-34fa-4610-8a5e-f6dd3a41fe56/block/95d2ffc547992b6d3d03e2755a5deb265038d584: 500.
[12/27/20 15:33:40] http-tx-mgr.c(929): libcurl failed to PUT htt ps://xxx/seafhttp/repo/6c0763b2-34fa-4610-8a5e-f6dd3a41fe56/block/c2d45612bf08eea359d0f03944bb0b29b7b7f63d: Operation was aborted by an application callback.
[12/27/20 15:33:40] http-tx-mgr.c(929): libcurl failed to PUT htt ps://xxx/seafhttp/repo/6c0763b2-34fa-4610-8a5e-f6dd3a41fe56/block/913d2363b2f9243f81bd99f1dc7f4049a9329b33: Operation was aborted by an application callback.
[12/27/20 15:33:40] http-tx-mgr.c(3355): Bad response code for PUT htt ps://xxx/seafhttp/repo/6c0763b2-34fa-4610-8a5e-f6dd3a41fe56/block/90ad76419996e5e3efbc63865a3f3ae6811bb9e7: 500.
[12/27/20 15:33:40] http-tx-mgr.c(1157): Transfer repo ‘6c0763b2’: (‘normal’, ‘data’) → (‘error’, ‘finished’)
[12/27/20 15:33:40] sync-mgr.c(621): Repo ‘Backups’ sync state transition from uploading to ‘error’: ‘Server error’.
[12/27/20 15:34:10] sync-mgr.c(582): Repo ‘Backups’ sync state transition from ‘synchronized’ to ‘uploading’.
[12/27/20 15:34:10] http-tx-mgr.c(1157): Transfer repo ‘6c0763b2’: (‘normal’, ‘init’) → (‘normal’, ‘check’)
[12/27/20 15:34:10] http-tx-mgr.c(1157): Transfer repo ‘6c0763b2’: (‘normal’, ‘check’) → (‘normal’, ‘commit’)
[12/27/20 15:34:10] http-tx-mgr.c(1157): Transfer repo ‘6c0763b2’: (‘normal’, ‘commit’) → (‘normal’, ‘fs’)
[12/27/20 15:34:10] http-tx-mgr.c(1157): Transfer repo ‘6c0763b2’: (‘normal’, ‘fs’) → (‘normal’, ‘data’)
[12/27/20 15:34:11] http-tx-mgr.c(3355): Bad response code for PUT htt ps://xxx/seafhttp/repo/6c0763b2-34fa-4610-8a5e-f6dd3a41fe56/block/913d2363b2f9243f81bd99f1dc7f4049a9329b33: 500.
[12/27/20 15:34:11] http-tx-mgr.c(929): libcurl failed to PUT htt ps://xxx/seafhttp/repo/6c0763b2-34fa-4610-8a5e-f6dd3a41fe56/block/c2d45612bf08eea359d0f03944bb0b29b7b7f63d: Operation was aborted by an application callback.
[12/27/20 15:34:11] http-tx-mgr.c(929): libcurl failed to PUT htt ps://xxx/seafhttp/repo/6c0763b2-34fa-4610-8a5e-f6dd3a41fe56/block/95d2ffc547992b6d3d03e2755a5deb265038d584: Operation was aborted by an application callback.
[12/27/20 15:34:12] http-tx-mgr.c(929): libcurl failed to PUT htt ps://xxx/seafhttp/repo/6c0763b2-34fa-4610-8a5e-f6dd3a41fe56/block/90ad76419996e5e3efbc63865a3f3ae6811bb9e7: Operation was aborted by an application callback.
[12/27/20 15:34:12] http-tx-mgr.c(1157): Transfer repo ‘6c0763b2’: (‘normal’, ‘data’) → (‘error’, ‘finished’)
[12/27/20 15:34:12] sync-mgr.c(621): Repo ‘Backups’ sync state transition from uploading to ‘error’: ‘Server error’.

Here is my seafile.log:

[12/26/20 23:48:16] start to serve on pipe client
[12/26/20 23:48:54] start to serve on pipe client
[12/26/20 23:48:57] start to serve on pipe client
[12/26/20 23:48:59] start to serve on pipe client
[12/26/20 23:49:16] start to serve on pipe client
[12/27/20 02:47:22] …/common/block-backend-fs.c(120): Failed to write block 6d7c0934-e879-4fad-ae3b-7bd87dedd064:44afcc469b72e2521dd109af518e24061eeced25: $
[12/27/20 02:47:22] …/common/block-backend-fs.c(120): Failed to write block 6d7c0934-e879-4fad-ae3b-7bd87dedd064:e71d6610d8c2baa5c3f974b36fc99f51fa285529: $
[12/27/20 02:47:22] http-server.c(1662): Failed to write block 6d7c0934:44afcc469b72e2521dd109af518e24061eeced25.
[12/27/20 02:47:22] http-server.c(1662): Failed to write block 6d7c0934:e71d6610d8c2baa5c3f974b36fc99f51fa285529.
[12/27/20 02:47:29] …/common/block-backend-fs.c(120): Failed to write block 6d7c0934-e879-4fad-ae3b-7bd87dedd064:e71d6610d8c2baa5c3f974b36fc99f51fa285529: $
[12/27/20 02:47:29] http-server.c(1662): Failed to write block 6d7c0934:e71d6610d8c2baa5c3f974b36fc99f51fa285529.
[12/27/20 02:48:30] …/common/block-backend-fs.c(120): Failed to write block 6d7c0934-e879-4fad-ae3b-7bd87dedd064:4b152e24d3b15f1dc14589c236df80c683f20389: $
[12/27/20 02:48:30] http-server.c(1662): Failed to write block 6d7c0934:4b152e24d3b15f1dc14589c236df80c683f20389.
[12/27/20 02:49:00] …/common/block-backend-fs.c(120): Failed to write block 6d7c0934-e879-4fad-ae3b-7bd87dedd064:4b152e24d3b15f1dc14589c236df80c683f20389: $
[12/27/20 02:49:00] http-server.c(1662): Failed to write block 6d7c0934:4b152e24d3b15f1dc14589c236df80c683f20389.
[12/27/20 02:49:31] …/common/block-backend-fs.c(120): Failed to write block 6d7c0934-e879-4fad-ae3b-7bd87dedd064:4b152e24d3b15f1dc14589c236df80c683f20389: $
[12/27/20 06:34:42] http-server.c(176): fileserver: worker_threads = 10
[12/27/20 06:34:42] http-server.c(191): fileserver: fixed_block_size = 8388608
[12/27/20 06:34:42] http-server.c(206): fileserver: web_token_expire_time = 3600
[12/27/20 06:34:42] http-server.c(221): fileserver: max_indexing_threads = 1
[12/27/20 06:34:42] http-server.c(236): fileserver: max_index_processing_threads= 3
[12/27/20 06:34:42] http-server.c(258): fileserver: cluster_shared_temp_file_mode = 600
[12/27/20 06:39:24] start to serve on pipe client
[12/27/20 06:39:27] start to serve on pipe client
[12/27/20 06:39:31] start to serve on pipe client
[12/27/20 06:40:17] start to serve on pipe client
[12/27/20 06:42:54] start to serve on pipe client
[12/27/20 14:21:36] socket file exists, delete it anyway
[12/27/20 14:21:36] http-server.c(176): fileserver: worker_threads = 10
[12/27/20 14:21:36] http-server.c(191): fileserver: fixed_block_size = 8388608
[12/27/20 14:21:36] http-server.c(206): fileserver: web_token_expire_time = 3600
[12/27/20 14:21:36] http-server.c(221): fileserver: max_indexing_threads = 1
[12/27/20 14:21:36] http-server.c(236): fileserver: max_index_processing_threads= 3
[12/27/20 14:21:36] http-server.c(258): fileserver: cluster_shared_temp_file_mode = 600
[12/27/20 14:21:48] start to serve on pipe client
[12/27/20 14:22:16] start to serve on pipe client
[12/27/20 14:22:59] start to serve on pipe client
[12/27/20 14:23:51] start to serve on pipe client
[12/27/20 14:23:51] start to serve on pipe client

Syncing other files works fine. Also when I try setting the max-upload value seahub won’t start.

Found the solution, my drive wasn’t mounted correctly.