Upload error files greater than 10kb

We have a private seafile that has worked very well till yesterday. Now we have a problem to upload any file greater than 10kb (in the past we have uploaded files more than 10 mb). We can upload many files of 9kb without any problem.
We have tried to investigate any log file in our server without results.
all libraries seem consistent (fschk) and the space available is enough to upload any file.
Any idea?
SEafile version 6.0.6
thanks
oriano

Can you give us some more information?

  • Are you trying to upload via the webui, or via syncing?
  • Are you getting any kind of error? If so, what is the error?
  • What flavor and version of Linux are you running?
  • Do you have Apache or NGinx installed?
  • Have there been any upgrades or updates done on the server since it last worked?
1 Like

more information:
Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial
4.4.0-66-generic
total used free shared buff/cache available
Mem: 1982 455 96 17 1430 1271
Swap: 6143 141 6002

Filesystem Size Used Avail Use% Mounted on
udev 972M 0 972M 0% /dev
tmpfs 199M 21M 178M 11% /run
/dev/mapper/SEAFILE–vg-root 486G 53G 409G 12% /
tmpfs 992M 0 992M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 992M 0 992M 0% /sys/fs/cgroup
/dev/sda1 472M 162M 286M 37% /boot
tmpfs 199M 0 199M 0% /run/user/1000

root@SEAFILE:~# nginx -v
nginx version: nginx/1.10.3 (Ubuntu)

Hi

  • Are you trying to upload via the webui, or via syncing?
    both
    Are you getting any kind of error? If so, what is the error?
    In webUI "Unknow Error"
    in windows client “Server Error”
  • What flavor and version of Linux are you running?
    ubuntu 16.04 con kernel 4.4.0-66
  • Do you have Apache or NGinx installed?
    NGinx
  • Have there been any upgrades or updates done on the server since it last worked?
    Yes we have found an automatic update on 29 March related to the openssl. (current version 1.0.2G-1 ubuntu 4.11)

Can you try to upload a file greater than 10 kb and then post the results of the log files of both the server and client here?

In the client we haven’t any log and in the server there are a lot of log files?
which logs do you need?

Thx

Both the server and the client have 3 basic logs. The client has the following three logs: (You can find them by right clicking the Seafile client and then clicking “Open Logs Folder”.

applet.log
ccnet.log
seafile.log

The server has these three basic logs, located in your Server folder under logs.

controller.log
ccnet.log
seafile.log

Try an upload of a file larger than 10k and note the time it failed. Then, go to that time slot in each file and post the results for each here. That should give us some clues as to what is going on.

APPLET.LOG
[04/04/18 15:24:45]starting ccnet: ("-c", “C:/Users/XXX.YYY/ccnet”)
[04/04/18 15:24:46]trying to connect to ccnet daemon…

[04/04/18 15:24:46]connected to ccnet daemon

[04/04/18 15:24:46]starting seaf-daemon: ("-c", “C:/Users/XXX.YYY/ccnet”, “-d”, “D:/seafile/Seafile/seafile-data”, “-w”, “D:/seafile/Seafile”)
[04/04/18 15:24:47][Rpc Client] connected to daemon
[04/04/18 15:24:47][Rpc Client] connected to daemon
[04/04/18 15:24:47][MessageListener] connected to daemon
[04/04/18 15:24:49]Starting the network status detector
[04/04/18 15:24:49][Rpc Client] connected to daemon
[04/04/18 15:24:50]setGeometry: Unable to set geometry 510x583+2573+243 on QWidgetWindow/‘MainWindowClassWindow’. Resulting geometry: 510x728+2573+243 (frame: 9, 38, 9, 9, custom margin: 0, 0, 0, 0, minimum size: 320x583, maximum size: 16777215x16777215).
[04/04/18 15:24:50][Rpc Client] connected to daemon

CCNET.log
[04/04/18 15:24:45] ccnet-daemon.c(193): starting ccnet client 6.1.3
[04/04/18 15:24:45] ccnet-daemon.c(195): ccnet source code version 5b9f64c2438517e1c95b28678097419542d1d084
[04/04/18 15:24:46] …/common/session.c(132): using config file C:/Users/oriano.sita/ccnet\ccnet.conf
[04/04/18 15:24:46] …/common/session.c(418): Listen on 127.0.0.1 13419
[04/04/18 15:24:46] …/common/session.c(290): Update pubinfo file
[04/04/18 15:24:46] …/common/session.c(398): Accepted a local client
[04/04/18 15:24:47] …/common/session.c(398): Accepted a local client
[04/04/18 15:24:47] …/common/session.c(398): Accepted a local client
[04/04/18 15:24:47] …/common/session.c(398): Accepted a local client
[04/04/18 15:24:47] …/common/session.c(398): Accepted a local client
[04/04/18 15:24:47] …/common/session.c(398): Accepted a local client
[04/04/18 15:24:47] …/common/peer.c(943): Local peer down
[04/04/18 15:24:47] …/common/peer.c(943): Local peer down
[04/04/18 15:24:47] …/common/session.c(398): Accepted a local client
[04/04/18 15:24:47] …/common/session.c(398): Accepted a local client
[04/04/18 15:24:47] …/common/session.c(398): Accepted a local client
[04/04/18 15:24:49] …/common/session.c(398): Accepted a local client
[04/04/18 15:24:49] …/common/session.c(398): Accepted a local client
[04/04/18 15:24:50] …/common/session.c(398): Accepted a local client
[04/04/18 15:24:50] …/common/session.c(398): Accepted a local client

seafile.log
[04/04/18 15:48:10] seaf-daemon.c(558): starting seafile client 6.1.3
[04/04/18 15:48:10] seaf-daemon.c(560): seafile source code version 5fc440fe04370308d8dd9de4b1c63a388da68278
[04/04/18 15:48:10] …/common/mq-mgr.c(60): [mq client] mq cilent is started
[04/04/18 15:48:10] …/common/mq-mgr.c(106): [mq mgr] publish to heartbeat mq: seafile.heartbeat
[04/04/18 15:48:47] sync-mgr.c(702): Repo ‘test’ sync state transition from ‘synchronized’ to ‘uploading’.
[04/04/18 15:48:47] http-tx-mgr.c(3423): Upload with HTTP sync protocol version 1.
[04/04/18 15:48:47] http-tx-mgr.c(1132): Transfer repo ‘3b68abd5’: (‘normal’, ‘init’) --> (‘normal’, ‘check’)
[04/04/18 15:48:47] http-tx-mgr.c(1132): Transfer repo ‘3b68abd5’: (‘normal’, ‘check’) --> (‘normal’, ‘commit’)
[04/04/18 15:48:47] http-tx-mgr.c(1132): Transfer repo ‘3b68abd5’: (‘normal’, ‘commit’) --> (‘normal’, ‘fs’)
[04/04/18 15:48:47] http-tx-mgr.c(1132): Transfer repo ‘3b68abd5’: (‘normal’, ‘fs’) --> (‘normal’, ‘data’)
[04/04/18 15:48:47] http-tx-mgr.c(3155): Bad response code for PUT https://XXX.YYY.ZZZ/seafhttp/repo/3b68abd5-b6e0-4446-9c8b-028fc8a19a81/block/913d1e53aa442946710bd8749f6e20e2ba3f6de6: 500.
[04/04/18 15:48:47] http-tx-mgr.c(1132): Transfer repo ‘3b68abd5’: (‘normal’, ‘data’) --> (‘error’, ‘finished’)
[04/04/18 15:48:47] sync-mgr.c(764): Repo ‘test’ sync state transition from uploading to ‘error’: ‘Error occured in upload.’.

Ok… You are getting an error 500, which is a server error. Can you post the seafile server logs for the same time slot?

evaluating the logs on the server we haven’t found any problem and any action related to the upload file operation.
excluding the seafile server we have investigated in detail the flow of the data and we have found the problen in our reverse proxy.
Now Seafile works again.
Many thanks for your support .

No problem… Glad to see it’s working again.