tompa

Looks right due to update channel is "Default", guess all later updates are on "Beta" channel? Didn't see this (Update channel) when I first asked.

Hi, according to Duplicati interface -> About -> "You are currently running Duplicati - 2.0.2.1_beta_2017-08-01" Is this correct if I'm running the latest docker?

Thanks again! Worked fine with seafile as user.

Im trying to run Seafile FSCK - https://manual.seafile.com/maintain/seafile_fsck.html But there is obvious a problem with user conflict, best way to solve this? root@server:~# docker exec -it Seafile bash root@server:/opt/haiwen/seafile-server-6.2.2# ./seaf-fsck.sh Starting seaf-fsck, please wait ... [10/10/17 12:38:20] seaf-fsck.c(155): Current user (0) is not the user for running seafile server (1000). Unable to run fsck. seaf-fsck run done Done. root@server:/opt/haiwen/seafile-server-6.2.2#

Perfect, thanks!

Thanks cmer, this sounds awesome! Could you show an example how to do this?

FYI - didn't manage to update to 6.2.2, however I did manage to recover my backup in a separate v6.1.2 server and the reinstall 6.2.2.

Ok, thanks! Seems to be running forever, doesn't seem right!? - never goes back to sqlite prompt

Thanks again ki3lich! Basic question; do I run this as two lines? sqlite3 seahub.db seafile-server-6.2.2/upgrade/sql/6.2.0/sqlite3/seahub.sql and sqlite3 usermgr.db seafile-server-6.2.2/upgrade/sql/6.2.0/sqlite3/usermgr.sql

Looks like the bug I had was in v6.2.1 - https://forum.seafile.com/t/seafile-server-6-2-0-beta-is-ready-for-testing/3941/33 Question regarding starting server 6.2.2 with data from 6.1. Is this Ok to do? 1. get my backup from 6.1 (datat and all db, .ini, .conf, etc) 2. start 6.2.2 server Will this run the upgrade script?

Thanks for your answer ki3lich! Im running sqlite, so maybe not the correct way?

Manage to start server but got other preoblems Is it possible to revert to version 6.1?

Hi, after updating today server is crashing. failed to run "ccnet-server -t" [09/23/17 12:25:19] ../common/session.c(132): using config file /opt/haiwen/conf/ccnet.conf [09/23/17 12:25:19] ../common/ccnet-db.c(142): Error exec query CREATE UNIQUE INDEX IF NOT EXISTS reference_id_index on EmailUser (reference_id): sqlite3_exec failed: table EmailUser has no column named reference_id. I didnt change any settings. Any idea? edit: full log below Installing Community Edition... Downloading & Extracting https://download.seadrive.org/seafile-server_6.2.1_x86-64.tar.gz... Using Community Edition... Installation path: /opt/haiwen/seafile-server-6.2.1 Seahub is not running Done. seafile server not running yet Done. failed to run "ccnet-server -t" [09/23/17 13:20:04] ../common/session.c(132): using config file /opt/haiwen/conf/ccnet.conf [09/23/17 13:20:04] ../common/ccnet-db.c(142): Error exec query CREATE UNIQUE INDEX IF NOT EXISTS reference_id_index on EmailUser (reference_id): sqlite3_exec failed: table EmailUser has no column named reference_id. edit2: I think Iv found the same problem here - https://forum.seafile.com/t/seafile-server-6-2-0-beta-is-ready-for-testing/3941/19 Dont know exatly how to solve within Unraid though...

Ok, that explains the update. thanks!

Any chance we could get an update to 6.1.1 - https://forum.seafile.com/t/seafile-version-6-1-1-is-ready/3118 Thanks! edit: its actually updated to 6.1.1, did I miss this or how does the update progress work?