The auto-start script for your Linux system need also be changed.
Actually for version 6.1 or below, you can also use the WSGI mode by the above two steps. The WSGI mode is more stable in heavy load than FastCGI mode.
Switched Seahub to WSGI mode today on pro 6.1.8 for having a flawless transition to 6.2.x! Had no problem with FastCGI either but I prefer to stay with Seafile’s default. Thanks!
Everything runs smooth with WSGI, too
Good question, I’ve never thought about that, because I’m using Apache and with Apache FastCGI has never been used for Webdav.
I would assume that Webdav still uses FastCGI with Nginx. See no reasons why it should have changed. But clarification welcome!
I have upgraded my Seafile 6.1.2 → 6.2.0, everything was fine:
Updating seafile/seahub database …
[INFO] You are using SQLite3
Done
migrating avatars …
Done
updating /opt/seafile/seafile-server-latest symbolic link to /opt/seafile/seafile-server-6.2.0 …
Upgraded your seafile server successfully.
but when I have started seafile again I get this:
…/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.
failed to run “ccnet-server -t”
It looks like I am missing something… Can you help, please?
Setup a quick testserver today and all works perfectly! Exept the Video Thumbnail creation.
While being in the Gallery the ffmpeg processes keep running but only if i reload the page a new thumb creation will be triggered(and on the reloaded page i will then see the thumb that it created before)
That means in general the creation works.
Could that be a problem in regards to the keep-alive or any other kind of timeout?
-Debian 9 Stretch
Could someone kindly provide a custom user search function returning all group members for groups you are yourself a member of? I was trying hard but I sadly fail in Python debug skills.
There is a problem in sqlite upgrade, you can find ccnet/PeerMgr/usermgr.db and manually run sqls below:
sqlite3 usermgr.db
alter table LDAPUsers add column reference_id VARCHAR(255);
alter table EmailUser add column reference_id VARCHAR(255);
CREATE UNIQUE INDEX IF NOT EXISTS reference_id_index on EmailUser (reference_id);
CREATE UNIQUE INDEX IF NOT EXISTS ldapusers_reference_id_index on LDAPUsers(reference_id);
Thank you @haikuo. The database fixed, the other problem jumped in:
Starting seahub at port 8000 ...
Traceback (most recent call last):
File "/opt/seafile/seafile-server-6.2.0/seahub/thirdpart/gunicorn", line 9, in <module>
load_entry_point('gunicorn==19.4.5', 'console_scripts', 'gunicorn')()
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 542, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2569, in load_entry_point
return ep.load()
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2229, in load
return self.resolve()
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2235, in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
File "/opt/seafile/seafile-server-6.2.0/seahub/thirdpart/gunicorn-19.4.5-py2.7.egg/gunicorn/app/wsgiapp.py", line 10, in <module>
from gunicorn.app.base import Application
File "/opt/seafile/seafile-server-6.2.0/seahub/thirdpart/gunicorn-19.4.5-py2.7.egg/gunicorn/app/base.py", line 14, in <module>
from gunicorn.config import Config, get_default_config_file
File "/opt/seafile/seafile-server-6.2.0/seahub/thirdpart/gunicorn-19.4.5-py2.7.egg/gunicorn/config.py", line 17, in <module>
import ssl
File "/usr/lib/python2.7/ssl.py", line 97, in <module>
import _ssl # if we can't import it, let the error propagate
ImportError: /usr/lib/python2.7/lib-dynload/_ssl.x86_64-linux-gnu.so: symbol SSL_CTX_set_alpn_protos, version OPENSSL_1.0.2 not defined in file libssl.so.1.0.0 with link time reference
This happens only when I start Seahub with ./seahub.sh start.
No problem when started with ./seahub.sh start-fastcgi though…
Any idea?
Thank you, the SQL statements fixed the database problem for me.
Syncing with the Seafile desktop client works now and Seahub started on Debian 9 stretch (still using fcgi, though). However, Seahub fails to serve pages with “Page unavailable” after login. Now I will have to investigate where this is coming from.
Fixed my Seahub. I also had to manually apply the DB upgrade for Seahub by running the SQLite3 queries in seafile-server-6.2.0/upgrade/sql/6.2.0/sqlite/seahub.sql against seahub.db.