Seafile pro edition 7.0.8 is ready!

This is a maintenance release with following fixes and updates:

  • Inviter can cancel invitation after the user has accepted the invitation. The user will be set as inactive.
  • Improve organization admin panel in multi-tenancy mode
  • Add notification when a user try to leave a page during file transfer
  • Add generating internal link (smart-link) for folders
  • Add command line tool for admin to export reports
  • [fix] Fix file drag and drop in IE and Firefox
  • [fix] Add back the feature of letting user to select storage backend
  • Improve UI for file uploading, support re-upload after error
  • [fix] Fix devices login via Shibboleth not show in devices list
  • [fix] Fix zip download when user selecting a long list of files
  • [fix] Support OnlyOffice short time periodically saving (You can config it to save a file every 5 minutes)
  • Other UI fixes
5 Likes

Great! Thanks!

I tried to test that, but I failed, because I didn’t finde a “cancel” or “uninvite” button (see screenshot).


How would I do that?

Hi Daniel,
thanks for the update. I have a strange situation with the included elasticsearch server after the update to 7.0.8:

Here are my observations:

1) elasticsearch started with seafile = slow and no search

if I start seafile via systemctl there are the following errors in the elasticsearch.log:

[2019-08-26T11:43:37,326][INFO ][o.e.n.Node ] [] initializing …
[2019-08-26T11:43:38,331][ERROR][o.e.b.Bootstrap ] Exception
java.lang.IllegalStateException: failed to obtain node locks, tried [[/home/seafile/pro-data/search/data/elasticsearch]] with lock id [0]; maybe these locations are not writable or multiple nodes were started without increasing [node.max_local_storage_nodes] (was [1])?
at org.elasticsearch.env.NodeEnvironment.(NodeEnvironment.java:265) ~[elasticsearch-5.6.13.jar:5.6.13]
at org.elasticsearch.node.Node.(Node.java:265) ~[elasticsearch-5.6.13.jar:5.6.13]

Also the cpu and memory usage is near 100% and seafile is responding very slowly.

2) seafile without file indexing = fast but no search

If I disable INDEX FILE in the seafevents.conf seafile is running like it should. Except that the search field is still visible but does not delivery and results.
In 6.x the search field disappered if I dissabled the file indexing. It seems this is not the case in 7.0.x., right?

3) elasticsearch started manually = search but no seafile

if I stop seafile and seahub and start the elasticsearch server manually I can update the search index without problems. Seafile is not running.

seafile@…:~/seafile-pro-server-7.0.8/pro/elasticsearch/bin$ ./elasticsearch
[2019-08-26T11:41:17,316][INFO ][o.e.n.Node ] [lCLpIG3] starting …
[2019-08-26T11:41:18,631][INFO ][o.e.t.TransportService ] [lCLpIG3] publish_address {127.0.0.1:9300}, bound_addresses {[::1]:9300}, {127.0.0.1:9300}

seafile@…:~/seafile-pro-server-7.0.8/pro$ ./pro.py search --update
Index updated, statistic report:

08/26/2019 11:42:30 [INFO] seafes:165 start_index_local: [commit read] 11
08/26/2019 11:42:30 [INFO] seafes:166 start_index_local: [dir read] 11
08/26/2019 11:42:30 [INFO] seafes:167 start_index_local: [file read] 11
08/26/2019 11:42:30 [INFO] seafes:168 start_index_local: [block read] 11

here is the relevant part of my seafevents.conf

[INDEX FILES]
enabled = true
interval = 10m
highlight = fvh
index_office_pdf = true

Can anybody confirm this behaviour?
Best regards
Christoph

Unfortunately, SQLAlchemy wasn’t updated, so this behavior is back: Seafile pro edition 7.0.7 is ready!

EDIT: Or maybe you planned to upgrade it? I can see a 1.3.7.dist-info folder but it seems it’s not used as the 1.1.3 egg version is still there?

Will replace the version again with a newer one (didn’t seen any issues with version 1.1.8 since release of Seafile Pro 7.0.7) as stated here: Seafile pro edition 7.0.7 is ready!

I have seen the same behaviour (at least for 1)). It seems there are orphaned Java processes somewhere. Stopped seafile, killed the process and it’s back to normal for me.

Hi @christophdb @daniel.pan

HI, I tested with my DEV environment on 7.08

after systemctl service startup

i had some logs in elasticsearch.log

[2019-08-26T21:33:44,433][INFO ][o.e.n.Node               ] [] initializing ...
[2019-08-26T21:33:44,544][INFO ][o.e.e.NodeEnvironment    ] [phVjOFG] using [1] data paths, mounts [[/ (/dev/mapper/cchumvmtmp3--vg-root)]], net usable_space [1.6gb], net total_space [7.3gb], spins? [possibly], types [ext4]
[2019-08-26T21:33:44,545][INFO ][o.e.e.NodeEnvironment    ] [phVjOFG] heap size [1007.3mb], compressed ordinary object pointers [true]
[2019-08-26T21:33:44,579][INFO ][o.e.n.Node               ] node name [phVjOFG] derived from node ID [phVjOFGSRSyBtbuv1UK2Mw]; set [node.name] to override
[2019-08-26T21:33:44,579][INFO ][o.e.n.Node               ] version[5.6.13], pid[29711], build[4d5320b/2018-10-30T19:05:08.237Z], OS[Linux/4.9.0-9-amd64/amd64], JVM[Oracle Corporation/OpenJDK 64-Bit Server VM/1.8.0_222/25.222-b10]
[2019-08-26T21:33:44,579][INFO ][o.e.n.Node               ] JVM arguments [-Xms512m, -Xmx1g, -XX:-AssumeMP, -XX:+UseConcMarkSweepGC, -XX:CMSInitiatingOccupancyFraction=75, -XX:+UseCMSInitiatingOccupancyOnly, -XX:+AlwaysPreTouch, -Xss1m, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djna.nosys=true, -Djdk.io.permissionsUseCanonicalPath=true, -Dio.netty.noUnsafe=true, -Dio.netty.noKeySetOptimization=true, -Dio.netty.recycler.maxCapacityPerThread=0, -Dlog4j.shutdownHookEnabled=false, -Dlog4j2.disable.jmx=true, -Dlog4j.skipJansi=true, -XX:+HeapDumpOnOutOfMemoryError, -Des.path.home=/home/cc/seafile/seafile-pro-server-7.0.8/pro/elasticsearch]
[2019-08-26T21:33:45,710][INFO ][o.e.p.PluginsService     ] [phVjOFG] loaded module [aggs-matrix-stats]
[2019-08-26T21:33:45,710][INFO ][o.e.p.PluginsService     ] [phVjOFG] loaded module [ingest-common]
[2019-08-26T21:33:45,711][INFO ][o.e.p.PluginsService     ] [phVjOFG] loaded module [lang-expression]
[2019-08-26T21:33:45,711][INFO ][o.e.p.PluginsService     ] [phVjOFG] loaded module [lang-groovy]
[2019-08-26T21:33:45,711][INFO ][o.e.p.PluginsService     ] [phVjOFG] loaded module [lang-mustache]
[2019-08-26T21:33:45,712][INFO ][o.e.p.PluginsService     ] [phVjOFG] loaded module [lang-painless]
[2019-08-26T21:33:45,712][INFO ][o.e.p.PluginsService     ] [phVjOFG] loaded module [parent-join]
[2019-08-26T21:33:45,712][INFO ][o.e.p.PluginsService     ] [phVjOFG] loaded module [percolator]
[2019-08-26T21:33:45,712][INFO ][o.e.p.PluginsService     ] [phVjOFG] loaded module [reindex]
[2019-08-26T21:33:45,712][INFO ][o.e.p.PluginsService     ] [phVjOFG] loaded module [transport-netty3]
[2019-08-26T21:33:45,712][INFO ][o.e.p.PluginsService     ] [phVjOFG] loaded module [transport-netty4]
[2019-08-26T21:33:45,713][INFO ][o.e.p.PluginsService     ] [phVjOFG] loaded plugin [analysis-ik]
[2019-08-26T21:33:47,488][INFO ][o.e.d.DiscoveryModule    ] [phVjOFG] using discovery type [zen]
[2019-08-26T21:33:48,022][INFO ][o.e.n.Node               ] initialized
[2019-08-26T21:33:48,022][INFO ][o.e.n.Node               ] [phVjOFG] starting ...
[2019-08-26T21:33:48,147][INFO ][o.e.t.TransportService   ] [phVjOFG] publish_address {127.0.0.1:9300}, bound_addresses {127.0.0.1:9300}
[2019-08-26T21:33:48,157][WARN ][o.e.b.BootstrapChecks    ] [phVjOFG] initial heap size [536870912] not equal to maximum heap size [1073741824]; this can cause resize pauses and prevents mlockall from locking the entire heap
[2019-08-26T21:33:48,158][WARN ][o.e.b.BootstrapChecks    ] [phVjOFG] max file descriptors [4096] for elasticsearch process is too low, increase to at least [65536]
[2019-08-26T21:33:48,158][WARN ][o.e.b.BootstrapChecks    ] [phVjOFG] max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
[2019-08-26T21:33:51,210][INFO ][o.e.c.s.ClusterService   ] [phVjOFG] new_master {phVjOFG}{phVjOFGSRSyBtbuv1UK2Mw}{N2b5iucwQfuAsjMGEJFWyQ}{127.0.0.1}{127.0.0.1:9300}, reason: zen-disco-elected-as-master ([0] nodes joined)
[2019-08-26T21:33:51,238][INFO ][o.e.h.n.Netty4HttpServerTransport] [phVjOFG] publish_address {127.0.0.1:9200}, bound_addresses {127.0.0.1:9200}
[2019-08-26T21:33:51,238][INFO ][o.e.n.Node               ] [phVjOFG] started
[2019-08-26T21:33:51,273][INFO ][o.w.a.d.Monitor          ] try load config from /home/cc/seafile/seafile-pro-server-7.0.8/pro/elasticsearch/config/analysis-ik/IKAnalyzer.cfg.xml
[2019-08-26T21:33:51,276][INFO ][o.w.a.d.Monitor          ] try load config from /home/cc/seafile/seafile-pro-server-7.0.8/pro/elasticsearch/plugins/analysis-ik/config/IKAnalyzer.cfg.xml
[2019-08-26T21:33:51,695][INFO ][o.e.g.GatewayService     ] [phVjOFG] recovered [2] indices into cluster_state
[2019-08-26T21:33:52,745][INFO ][o.e.c.r.a.AllocationService] [phVjOFG] Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[repofiles][4]] ...]).

Particularly WARN logs

[2019-08-26T21:33:48,157][WARN ][o.e.b.BootstrapChecks    ] [phVjOFG] initial heap size [536870912] not equal to maximum heap size [1073741824]; this can cause resize pauses and prevents mlockall from locking the entire heap
[2019-08-26T21:33:48,158][WARN ][o.e.b.BootstrapChecks    ] [phVjOFG] max file descriptors [4096] for elasticsearch process is too low, increase to at least [65536]
[2019-08-26T21:33:48,158][WARN ][o.e.b.BootstrapChecks    ] [phVjOFG] max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
[2019-08-26T21:33:51,210][INFO ][o.e.c.s.ClusterService   ] [phVjOFG] new_master 

But seafile looks normal and search is working (i can search from files newly indexed)

index.log is normal

08/26/2019 21:43:56 [INFO] seafes:135 clear_deleted_repo: 0 repos need to be deleted.
08/26/2019 21:43:56 [INFO] seafes:139 clear_deleted_repo: deleted repo has been cleared
08/26/2019 21:43:56 [INFO] seafes:164 start_index_local:

Index updated, statistic report:

    08/26/2019 21:43:56 [INFO] seafes:165 start_index_local: [commit read] 4
    08/26/2019 21:43:56 [INFO] seafes:166 start_index_local: [dir read]    53
    08/26/2019 21:43:56 [INFO] seafes:167 start_index_local: [file read]   50
    08/26/2019 21:43:56 [INFO] seafes:168 start_index_local: [block read]  48

I can cancel the operation here and it works fine.
You can try clearing the browser cache.
And you need to move your mouse over the corresponding invitation record to see the cancel button.

@daniel.pan Please also update the changelog.

I am sooo sorry. The browser cache…

The document for OnlyOffice is updated:

https://download.seafile.com/published/seafile-manual/deploy/only_office.md

like this but Error, where should I add code?thanks

Error prompt


{
“services”: {
“CoAuthoring”: {
“autoAssembly”: {
“enable”: true,
“interval”: “5m”
}
“sql”: {
“dbHost”: “localhost”,
“dbName”: “onlyoffice”,
“dbUser”: “onlyoffice”,
“dbPass”: “onlyoffice”
},
“redis”: {
“host”: “localhost”
},
“token”: {
“enable”: {
“request”: {
“inbox”: false,
“outbox”: false
},
“browser”: false
},
“inbox”: {
“header”: “Authorization”
},
“outbox”: {
“header”: “Authorization”
}
},
“secret”: {
“inbox”: {
“string”: “secret”
},
“outbox”: {
“string”: “secret”
},
“session”: {
“string”: “secret”
}
}
}
},
“rabbitmq”: {
“url”: “amqp://guest:guest@localhost”
}
}

@daniel.pan Could you please add 7.0.8 to the changelog? :slight_smile:
https://manual.seafile.com/changelog/changelog-for-seafile-professional-server.html

1 Like

The site has changed the link to the manual.
https://download.seafile.com/published/seafile-manual/changelog/changelog-for-seafile-professional-server.md

Why does the old manual not contain any link/reference about the new location then?

Why did the url have to change? U no care about search cache? :smile:

BTW, the new location (Seafile Wiki I guess) for the manual is horribly slow in comparison to git book.

Menu scrolling does not work on mobile devices.
Not production ready in my eyes. :frowning:

1 Like

The “old” manual contains a reference to the new location. It is just not super obvious. Check here: https://manual.seafile.com/

I disagree, this is not super nice. But this is more an transitional problem.

1 Like

Hello,
Is it possible to have the properties of a folder in the web interface.

This allows to know the number of files and subfolder of a directory for example.