Seahub.sh not starting after upgrade 6.2.12 to 6.3.7

[NOnooSS]

Hello,

I have upgrade my Seafilepro 6.2.12 to 6.3.7 and seahub.sh is not starting.

When i change “daemon = False” in guinicorn.conf file, i have those errors messages

Traceback`` (most recent call last):, File "/seafile/seafile-pro-server-6.3.7/seahub/thirdpart/gunicorn", line 9, in <module>, load_entry_point('gunicorn==19.8.1', 'console_scripts', 'gunicorn')(), File "/seafile/seafile-pro-server-6.3.7/seahub/thirdpart/gunicorn-19.8.1-py2.7.egg/gunicorn/app/wsgiapp.py", line 61, in run, WSGIApplication("%(prog)s [OPTIONS] [APP_MODULE]").run(), File "/seafile/seafile-pro-server-6.3.7/seahub/thirdpart/gunicorn-19.8.1-py2.7.egg/gunicorn/app/base.py", line 223, in run, super(Application, self).run(), File "/seafile/seafile-pro-server-6.3.7/seahub/thirdpart/gunicorn-19.8.1-py2.7.egg/gunicorn/app/base.py", line 72, in run, Arbiter(self).run(), File "/seafile/seafile-pro-server-6.3.7/seahub/thirdpart/gunicorn-19.8.1-py2.7.egg/gunicorn/arbiter.py", line 60, in __init__, self.setup(app), File "/seafile/seafile-pro-server-6.3.7/seahub/thirdpart/gunicorn-19.8.1-py2.7.egg/gunicorn/arbiter.py", line 120, in setup, self.app.wsgi(), File "/seafile/seafile-pro-server-6.3.7/seahub/thirdpart/gunicorn-19.8.1-py2.7.egg/gunicorn/app/base.py", line 67, in wsgi, self.callable = self.load(), File "/seafile/seafile-pro-server-6.3.7/seahub/thirdpart/gunicorn-19.8.1-py2.7.egg/gunicorn/app/wsgiapp.py", line 52, in load, return self.load_wsgiapp(), File "/seafile/seafile-pro-server-6.3.7/seahub/thirdpart/gunicorn-19.8.1-py2.7.egg/gunicorn/app/wsgiapp.py", line 41, in load_wsgiapp, return util.import_app(self.app_uri), File "/seafile/seafile-pro-server-6.3.7/seahub/thirdpart/gunicorn-19.8.1-py2.7.egg/gunicorn/util.py", line 350, in import_app, __import__(module), File "/seafile/seafile-pro-server-6.3.7/seahub/seahub/wsgi.py", line 25, in <module>, application = get_wsgi_application(), File "/seafile/seafile-pro-server-6.3.7/seahub/thirdpart/django/core/wsgi.py", line 13, in get_wsgi_application, django.setup(set_prefix=False), File "/seafile/seafile-pro-server-6.3.7/seahub/thirdpart/django/__init__.py", line 27, in setup, apps.populate(settings.INSTALLED_APPS), File "/seafile/seafile-pro-server-6.3.7/seahub/thirdpart/django/apps/registry.py", line 108, in populate, app_config.import_models(), File "/seafile/seafile-pro-server-6.3.7/seahub/thirdpart/django/apps/config.py", line 202, in import_models, self.models_module = import_module(models_module_name), File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module, __import__(name), File "/seafile/seafile-pro-server-6.3.7/seahub/seahub/base/models.py", line 13, in <module>, from seahub.group.models import GroupMessage, File "/seafile/seafile-pro-server-6.3.7/seahub/seahub/group/models.py", line 13, in <module>, from seahub.profile.models import Profile, File "/seafile/seafile-pro-server-6.3.7/seahub/seahub/profile/models.py", line 206, in <module>, from .utils import refresh_cache, File "/seafile/seafile-pro-server-6.3.7/seahub/seahub/profile/utils.py", line 8, in <module>, from seahub.utils import normalize_cache_key, File "/seafile/seafile-pro-server-6.3.7/seahub/seahub/utils/__init__.py", line 1187, in <module>, seafevents_api.init(EVENTS_CONFIG_FILE), File "/seafile/seafile-pro-server-6.3.7/pro/python/seafevents/seafevents_api.py", line 9, in init, load_config(config_file), File "/seafile/seafile-pro-server-6.3.7/pro/python/seafevents/app/config.py", line 27, in load_config, appconfig.seaf_session_cls = init_db_session_class(appconfig.seaf_conf_path, db = 'seafile'), File "/seafile/seafile-pro-server-6.3.7/pro/python/seafevents/db.py", line 111, in init_db_session_class, engine = create_engine_from_conf(config_file, db), File "/seafile/seafile-pro-server-6.3.7/pro/python/seafevents/db.py", line 52, in create_engine_from_conf, backend = config.get(db_sec, 'type'), File "/usr/lib/python2.7/ConfigParser.py", line 607, in get, raise NoSectionError(section), ConfigParser.NoSectionError: No section: 'database',`

Should i try to upgrade again ? Do i need to change something in vhost file ?
Im not using fastcgi and using docker.

In my seafile.conf file, i have :

[database]
type=sqlite3
path=/seafile/pro-data/seafevents.db
[fileserver]
port=8082

Set maximum upload file size to 200M.

max_upload_size=800

Set maximum download directory size to 200M.

max_download_dir_size=10000

Config : nginx 1.13.5 / Debian Linux 9

Thanks in advance

[oliver-la]

There's no indication on seafile removing sqlite3 support. Their documentation also states that they won't disclose how to migrate to MySQL in the pro edition. (WHY?)

However, I found this note https://manual.seafile.com/deploy/upgrade_notes.html:

Seahub does not start
In case Seahub does not start after the upgrade, install python-requests.

sudo apt-get install python-requests

It indeed is missing in my image. I'll test this tomorrow (in 16 hours or so). Hopefully it's only because of that and not a configuration issue.

[oliver-la]

After adding the dependency and appending this config to conf/seafile.conf, seahub starts but is unable to respond to any API calls. (generic server error, yes I'll definitely debug that... /s)

[database]
type=sqlite3
path=/seafile/pro-data/seafevents.db

Since I don't use Seafile anymore anyway, I won't look further into this. Feel free to post a fix.
Most likely they broke something in their software and forgot to mention anything about it... Not even the debug messages are helpful.