Seafile version 6.1.0 beta is ready for testing!

Announcement
43

no I am confused, I am not really an expert on this:

lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 8.8 (jessie)
Release: 8.8
Codename: jessie

apt-get install ffmpeg
Package ffmpeg is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

on the other hand, I found an existing package libav-tools that is supposed to be a replacement.

do I need another source for ffmpeg in sources.list (which?) or is the package libav-tools the correct one to install?

sources.list:
deb http://ftp.de.debian.org/debian/ jessie main
deb-src http://ftp.de.debian.org/debian/ jessie main

deb http://security.debian.org/ jessie/updates main
deb-src http://security.debian.org/ jessie/updates main

deb http://ftp.de.debian.org/debian/ jessie-updates main
deb-src http://ftp.de.debian.org/debian/ jessie-updates main

edit:
it seems, I need to add: deb http://ftp.de.debian.org/debian/ jessie-backports main

44

I would like to know this too. The spawned ffmpeg processes quickly fill up my Raspberry Pi’s 1GB of RAM, making it unresponsive and pretty much useless for a given timespan. I also noticed that some (all?) ffmpeg processes won’t terminate after a thumbnail was generated.

Edit: I just skimmed through seahub’s code

  • Thumbnails can be completely disabled by setting ENABLE_THUMBNAIL = False in seahub_settings.py
  • Video thumbnails will be disabled when moviepy is not installed. See here. I did not test if it works though, I disabled the thumbnails altogether for now.
45

I also ran into this problem after upgrading 6.0.10 → 6.1.0 (on a Rasbperry Pi B+ running Arch Linux ARM). The webserver is using Nginx 1.12.0.

EDIT:
Turns out ‘requests’ was needed but wasn’t installed. ‘pip2 install requests’ inside the correct environment did the trick. It’s working now!! Thanks for the help!

46

https://github.com/haiwen/seahub/commit/0d65a688920506f448a5f24c036c7d674d38472b

Thats the Feature you’re looking for :slight_smile:

2 Likes
47

Is it possible to work together on one server programs seafile and only office?

48

Yes I use both on one server. Personally I dont use the docker image, just the document server. But It should also work with docker.

49

After editing the document, it is not saved in the seafile. Is this option not implemented yet?

50

Saving documents after editing with OnlyOffice works fine here (and automatically). Except for .odt and maybe other OpenOffice-files (Onlyoffice corrupts .odt)
So yes, it is actually implemented.

51

Hmm, I installed on the virtualbox seafile 6.1.0 and only office docker-documentserver, after editing documents in only office they are not saved. What’s interesting is if i open the document again, then the changes in only office will be visible, but in the seafile itself there will be no changes in the history and if i download the file, it is also unchanged.

52

That sounds like there is a problem with the callback OnlyOffice does to update the seafile copy.

The way the callback work can cause issues if you are running services on a private network behind an Apache proxy, so have the concept of external and internal ip names\urls.

The editor page is basically a stub script which loads a script from the OnlyOffice URL (set in seahub_settings.py) so this url must be accesible from the browser. The stub script also includes a callback based on the seafile external URL (i.e. the SERVICE_URL in ccnet.conf). So the onlyoffice server must be able to also access the seafile server using this URL.The callback is sent with a link on the onlyoffice server from which the update can be loaded - so the seafile server needs to be able to access the onlyoffice URL. Finally seafile calls its own API so must also be able to access itself using its external SERVICE_URL.

So if you have a set up whereby the seafile and onlyoffice servers can only access each other by a private network IP name and have a front facing Apache mod_proxy server to proxy public ip names to the private network ip names you will experience the situation you describe with the onlyoffice caching updates be not synching them back to seafile.

1 Like
53

Hi @daniel.pan,

Is there any precise planning for 6.1 pro release ?

Regards,

Gautier

54

I am having the same issue. In the OnlyOffice server log it shows that the callback routine is (silently) generating a 501 response from the Seafile server and hence not saving the file. Looking through the Seahub log, the relevant error line appears to be:

SSLError: ("bad handshake: Error([('SSL routines', 'ssl3_get_server_certificate', 'certificate verify failed')],)",)
2017-05-30 08:50:08,926 [ERROR] django.request:256 handle_uncaught_exception Internal Server Error: /onlyoffice/editor-callback/
Traceback (most recent call last):

I’m not sure how to proceed from here. My Seafile and OnlyOffice servers are on separate subdomains with valid letsencrypt SSL certificates. I have set VERIFY_ONLYOFFICE_CERTIFICATE = False. There must be some other configuration setting that I’ve messed up but I can’t figure out which one it is.

55

By doing the following things, I made it work properly (but I have no idea which of these was the underlying cause):

  • Fresh installation of Seafile (vs upgrade from earlier version, which was itself a crossgrade from Seafile Pro)
  • Installed both Seafile and OnlyOffice (via Docker) on the same VM
  • Shared SSL certificates between Seafile and OnlyOffice
56

Yes, I got that error too - I managed to track the problem down to this step I mention in my above post: “Finally seafile calls its own API so must also be able to access itself using its external SERVICE_URL.”

This error is misleading for two reasons:

i) it is nothing to do with the OnlyOffice setup at this point (hence VERIFY_ONLYOFFICE_CERTIFICATE is irrelevant). Seafile has already received the data, and what it is doing is calling its own web API to update the file, i.e. if SERVICE_URL (in ccnet.conf or in the web admin settings) is https://seafile.mydomain what is happening here is a seafile is attempting to connect to https://seafile.mydomain/update-api/…

ii) it is not necessarily an ssl related error, this error is thrown if the SERVICE_URL is https://… and the connection fails for any reason (timeout, dns name not found etc.)

In my setup, as I have a NAT firewall and an Apache proxy, the seafile server runs on (say) http://seacloud.internal but externally is accessed as https://seafile.mydomain. (the apache proxy also handles https so the seacloud server doesn’t have to). The NAT part of this, meant that seafile.mydomain as a ip address was only accessible outside the NAT network, so when the seafile server attempts to connect to https://seafile.mydomain/upload-api/… the connection failed (workaround was to add a fake entry in hosts for seafile.mydomain to “override” the ip address to the appropriate local NAT).

So, in your broken setup, what you could have tried would be to logon to the seafile server, and use lynx (or any other browser - command line or gui depending on how your server is setup) to attempt to connect to the url specified as the seafile SERVICE_URL

57

We are upgrading the included ElasticSearch in pro version. It turns out to be not a trivial task as the search code need to be rewritten. It can be finished in this week.

We are also turn off the video thumbnail feature by default, since it caused problems in the community edition.

A beta version of pro edition will be available in the next week.

Best regards

1 Like
58

Thank you @daniel.pan for these news !
Regards

59

Can somone summarize all update tasks that came with version 5.x, 6 and 6.1?

I will extend the server manual and write some extended pages for version specific requirements to keep it cleaner.
Everything on one upgrade page is a bit long and not flexible enough.

Thanks!

60

I have documented special notes for upgrading in the changelog at the top of each major/minor version:

https://seacloud.cc/group/3/wiki/Server%20ChangeLog.md

1 Like
61

Thanks for the hint, I read that but forgot about it!

I will try to write them next week and push my commits then.

62

:heart_eyes: super upgrade specially the improved image file view, using thumbnail to view pictures, I was waiting for this option for long time, would be nice if this feature can be added also to ios and android client by showing thumbnail created by server instead of waiting to download the whole picture which will take time for high res. pictures.
Thanks for the effort and for the hard work :+1: .