@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.
Search Criteria
Package Details: seafile 9.0.11-1
Package Actions
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: | 111 |
Popularity: | 0.000000 |
First Submitted: | 2016-08-11 16:38 (UTC) |
Last Updated: | 2024-11-14 17:06 (UTC) |
Dependencies (8)
- fuse (fuse2)
- libevent (libevent-gitAUR)
- libsearpcAUR
- libwebsockets
- python-future
- sqlite (sqlite-fossilAUR)
- intltool (make)
- vala (vala-gitAUR) (make)
Required by (2)
Sources (2)
Latest Comments
« First ‹ Previous 1 .. 22 23 24 25 26 27 28 29 30 31 32 .. 47 Next › Last »
mertemba commented on 2015-03-20 11:43 (UTC)
<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).
MadMe commented on 2015-03-19 16:52 (UTC)
4.0.6-1 seems to be broken for me...
Upload works fine for me, download won't start. With the binary from 4.0.5(i guess at least so) it works fine. Now while i am writing here... i saw Varakh's Post. maybe the same problem?
vit commented on 2015-03-12 16:36 (UTC)
After upgrading to 4.0.6 there is still notification in admin interface about new server version 4.0.3 available. Am I the only one with this?
Varakh commented on 2015-03-04 19:47 (UTC)
Is download a file working for you guys? I followed the steps in the wiki and it is loading if I click on download but nothing happens.
Pinned Comments