Package Details: seafile 9.0.13-1

Git Clone URL: https://aur.archlinux.org/seafile.git (read-only, click to copy)
Package Base: seafile
Description: An online file storage and collaboration tool
Upstream URL: https://github.com/haiwen/seafile
Licenses: GPL2
Conflicts: seafile-server
Provides: seafile-client-cli
Submitter: eolianoe
Maintainer: Joffrey
Last Packager: Joffrey
Votes: 110
Popularity: 0.000000
First Submitted: 2016-08-11 16:38 (UTC)
Last Updated: 2025-04-04 12:14 (UTC)

Pinned Comments

Latest Comments

« First ‹ Previous 1 .. 22 23 24 25 26 27 28 29 30 31 32 .. 47 Next › Last »

<deleted-account> commented on 2015-03-20 12:12 (UTC)

@jellysheep: Thanks for the information about seaf-server not responding. Unfortunately I do not know why, but I suspect there is something wrong with the way this package builds seafile (though I currently do not know what). Also, I found your github issue about this and using seafile-admin is not a faulty way to start seafile. This is the way the manual states[1] you should start self-compiled seafile server instances (not from the binary distribution). In any case, you may want to reopen that issue, I shall investigate further. [1] http://manual.seafile.com/build_seafile/server.html

mertemba commented on 2015-03-20 11:47 (UTC)

Apparently the seafile fileserver (listening on port 8082) does not respond at all. With the binary package downloadable on seafile.com this is not the case. Any ideas?

mertemba commented on 2015-03-20 11:43 (UTC)

@MadMe, @calrama: Sorry for any confusions. Apparently I misread the Seafile wiki. I downloaded the binary distribution files from seafile.com, therefore I had the scripts in the filesystem. Thank you for clarifying that. Apart from that, I have the same problem as before, and as Varakh and MadMe have, that downloads don't start. @calrama: nginx seems not to be the problem, as without fastcgi it does not work either.

<deleted-account> commented on 2015-03-20 11:42 (UTC)

The problem as far as I've been able to trace it is that for some reason nginx no longer communicates correctly with seahub in fastcgi. The error is a timeout and looks like this: {TIMESTAMP} [error] 376#0: *939 upstream timed out (110: Connection timed out) while reading response header from upstream, client: {CLIENT_IP}, server: {SERVER_HOSTNAME}, request: "GET /repo/{REPO_ID}/files/?p=/{REQUESTED_FILE} HTTP/1.1", upstream: "fastcgi://127.0.0.1:8000", host: "{SERVER_HOSTNAME}", referrer: "https://{SERVER_HOSTNAME}/repo/{REPO_ID}/"

<deleted-account> commented on 2015-03-20 11:16 (UTC)

@jellysheep: I've been trying to figure this out for a while now and that does not work. Firstly, both scripts have the layout of the binary distribution hardcoded and need to be patched to work with a site-wide installation. While that is done easily enough it does not change anything regarding the ability to download files in the seahub web interface. Normal library syncing in a client works with both these two scripts and with seafile-admin, but downloading a single file in the seahub web interface works with neither. @MadMe: They are not installed by default, because they are redundant and would also need to be patched (see my reply to jellysheep). @vit: I've never had any admin notifications in seafile, so I cannot help you there, unfortunately.

MadMe commented on 2015-03-20 11:10 (UTC)

@jellysheep (btw cool name) these files aren't there for me...do you maybe have an old version of seahub? I will try to copy the files from the source when I'm back home.. maybe it will work...

mertemba commented on 2015-03-20 08:42 (UTC)

@MadMe: If you installed seafile in [...]/example.org/seafile-server, first stop seafile-server@.service, then in a terminal switch to user seafile (e.g. 'sudo -u seafile -s /bin/sh') and execute the following commands: $ [...]/example.org/seafile-server/seafile.sh start $ [...]/example.org/seafile-server/seahub.sh start (or seahub.sh start-fastcgi, if you want to use fastcgi). That way seafile and downloads work fine for me.

MadMe commented on 2015-03-19 21:24 (UTC)

@jellysheep how can i do this? i find seafile.sh and seahub.sh only in package after makepkg... but i have no clue how to use them in the right way :-(

mertemba commented on 2015-03-19 17:05 (UTC)

@MadMe: Please try to start seafile and seahub via seafile.sh and seahub.sh. For me it did not work with the binary seafile-admin provided with this package (downloads did not start either).

« First ‹ Previous 1 .. 22 23 24 25 26 27 28 29 30 31 32 .. 47 Next › Last »