Seafile Professional Server 6.3 is ready for testing! Major new group functions


#21

Tried to install went from 6.2.2 to 6.3.1 ran upgrade_6.2_6.3.sh - Seafile not starting

Which log files should I look at ?


#22

Ran

seafile-server-latest/seafile.sh start
seafile-server-latest/seahub.sh start

Logs:

gunicorn_error.log
[2018-07-03 20:37:51 +0000] [1957] [INFO] Starting gunicorn 19.8.1
[2018-07-03 20:37:51 +0000] [1957] [INFO] Listening at: http://0.0.0.0:8000 (1957)
[2018-07-03 20:37:51 +0000] [1957] [INFO] Using worker: sync
[2018-07-03 20:37:51 +0000] [1965] [INFO] Booting worker with pid: 1965
[2018-07-03 20:37:51 +0000] [1966] [INFO] Booting worker with pid: 1966
[2018-07-03 20:37:51 +0000] [1967] [INFO] Booting worker with pid: 1967
[2018-07-03 20:37:52 +0000] [1968] [INFO] Booting worker with pid: 1968
[2018-07-03 20:37:52 +0000] [1969] [INFO] Booting worker with pid: 1969

ccnet.log
[07/03/18 16:32:24] …/common/session.c(132): using config file /home/cloud/Seafile/conf/ccnet.conf
[07/03/18 16:32:24] …/common/session.c(455): socket file exists, delete it anyway
[07/03/18 16:32:24] …/common/session.c(484): Listen on /home/cloud/Seafile/ccnet/ccnet.sock for local clients
[07/03/18 16:32:24] …/common/session.c(290): Update pubinfo file
[07/03/18 16:32:25] …/common/session.c(398): Accepted a local client
[07/03/18 16:32:25] …/common/session.c(398): Accepted a local client
[07/03/18 16:32:25] …/common/session.c(398): Accepted a local client
[07/03/18 16:32:25] …/common/session.c(398): Accepted a local client
[07/03/18 16:37:51] …/common/session.c(398): Accepted a local client
[07/03/18 16:37:51] …/common/peer.c(943): Local peer down

seafile.log
[07/03/18 16:32:25] http-server.c(163): fileserver: worker_threads = 10
[07/03/18 16:32:25] http-server.c(178): fileserver: fixed_block_size = 8388608
[07/03/18 16:32:25] http-server.c(193): fileserver: web_token_expire_time = 3600
[07/03/18 16:32:25] http-server.c(208): fileserver: max_indexing_threads = 1
[07/03/18 16:32:25] http-server.c(223): fileserver: max_index_processing_threads= 3
[07/03/2018 04:32:25 PM] …/common/mq-mgr.c(54): [mq client] mq cilent is started
[07/03/2018 04:32:26 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2018 04:37:26 PM] size-sched.c(96): Repo size compute queue size is 0

controller.log
[07/03/18 16:32:24] seafile-controller.c(169): starting ccnet-server …
[07/03/18 16:32:24] seafile-controller.c(73): spawn_process: ccnet-server -F /home/cloud/Seafile/conf -c /home/cloud/Seafile/ccnet -f /home/cloud/Seafile/logs/ccnet.log -d -P /home/cloud/Seafile/pids/ccnet.pid
[07/03/18 16:32:24] seafile-controller.c(88): spawned ccnet-server, pid 1909
[07/03/18 16:32:25] seafile-controller.c(571): ccnet daemon connected.
[07/03/18 16:32:25] seafile-controller.c(201): starting seaf-server …
[07/03/18 16:32:25] seafile-controller.c(73): spawn_process: seaf-server -F /home/cloud/Seafile/conf -c /home/cloud/Seafile/ccnet -d /home/cloud/Seafile/seafile-data -l /home/cloud/Seafile/logs/seafile.log -P /home/cloud/Seafile/pids/seaf-server.pid
[07/03/18 16:32:25] seafile-controller.c(88): spawned seaf-server, pid 1914
[07/03/18 16:32:25] seafile-controller.c(544): seafdav not enabled.


#23

Hi,
i tried to upgrade our test server from 6.2.9 to 6.3 (Scientific Linux 7.5 with MariaDB 10.1). Running the script upgrade_6.2_6.3.sh gives the following error:

-------------------------------------------------------------
This script would upgrade your seafile server from 6.2 to 6.3
Press [ENTER] to contiune
-------------------------------------------------------------



Updating seafile/seahub database ...

[INFO] You are using MySQL
[INFO] updating ccnet database...
/home/seafile/seafile-pro-server-6.3.0/upgrade/db_update_helper.py:353: Warning: Table 'LDAPConfig' already exists
  cursor.execute(sql)
[ERROR] Failed to execute sql: Can't DROP 'PRIMARY'; check that column/key exists

Failed to upgrade your database

#24

Well, finally I could upgrade my databases after exchanging all occurences of

DROP primary key;

with

DROP INDEX IF EXISTS 'PRIMARY';

in ccnet.sql and seafile.sql under upgrade/sql/6.3.0/mysql


#25

@daniel.pan can this please be merged into the next version?


#26

Documentation for a few major features in 6.3.0 are released.


#27

@daniel.pan

I tried it 6.22 to 6.3 - I have problems, can’t access via browser (this is the main way we use Seafile) How can does one go back the previous version ?

IE, Crome and Firefox

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at webmaster@localhost to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.

Apache2 error log

[Tue Jul 10 13:07:28.051213 2018] [mpm_prefork:notice] [pid 10598] AH00163: Apache/2.4.7 (Ubuntu) mod_fastcgi/mod_fastcgi-SNAP-0910052141 PHP/5.5.9-1ubuntu4.11 OpenSSL/1.0.1f configured – resuming normal operations
[Tue Jul 10 13:07:28.051303 2018] [core:notice] [pid 10598] AH00094: Command line: ‘/usr/sbin/apache2’

[Tue Jul 10 13:08:36.265074 2018] [fastcgi:error] [pid 10603] [client 172.16.50.50:63192] FastCGI: comm with server “/var/www/seahub.fcgi” aborted: idle timeout (30 sec)
[Tue Jul 10 13:08:36.265168 2018] [fastcgi:error] [pid 10603] [client 172.16.50.50:63192] FastCGI: incomplete headers (0 bytes) received from server “/var/www/seahub.fcgi”
[Tue Jul 10 13:08:45.014037 2018] [fastcgi:error] [pid 10604] [client 172.16.50.50:63195] FastCGI: comm with server “/var/www/seahub.fcgi” aborted: idle timeout (30 sec)
[Tue Jul 10 13:08:45.014363 2018] [fastcgi:error] [pid 10604] [client 172.16.50.50:63195] FastCGI: incomplete headers (0 bytes) received from server “/var/www/seahub.fcgi”


#28

Did you update your apache config? Fastcgi cant be used anymore since 6.3.x see: https://manual.seafile.com/changelog/changelog-for-seafile-professional-server.html


#29

I did not and I did not realize it was necessary but I will look at your link and try to apply the updates


#30

These are just the change logs is there a document that explains the required changes in more detail

The way to run Seahub in another port is also changed. You need to modify the configuration file conf/gunicorn.conf instead of running ./seahub.sh start .
Version 6.3 also changed the database table for file comments, if you have used this feature, you need migrate old file comments using the following commends after upgrading to 6.3:
./seahub.sh python-env seahub/manage.py migrate_file_comment


#31

Have a look for the changelog for version 6.2 on that page


#32

Hi,

Will you update Pro version soon ?

Some bugs seems to be fixed with CE 6.3.2 version.

Regards