Upgrade Seafile 11 to Seafile 12 fails

Seafile Server
1

Hi,

i want to upgrade my Seafile Server 11 Community Edition to Version 12.

But on Upgrading i run into following problems:

[21:14h][root@Seafile][:/opt/seafile/seafile-server-latest/upgrade]$ ./upgrade_11.0_12.0.sh

This script would upgrade your seafile server from 11.0 to 12.0
Press [ENTER] to contiune

Updating seafile/seahub database …

[INFO] You are using MySQL
[INFO] updating seafile database…
[INFO] updating seahub database…
[INFO] updating seafevents database…
[WARNING] Failed to execute sql: (1146, “Table ‘seahub-db.UserActivity’ doesn’t exist”)
[WARNING] Failed to execute sql: (1146, “Table ‘seahub-db.Activity’ doesn’t exist”)
[WARNING] Failed to execute sql: (1146, “Table ‘seahub-db.UserActivity’ doesn’t exist”)
[WARNING] Failed to execute sql: (1146, “Table ‘seahub-db.UserActivity’ doesn’t exist”)
[WARNING] Failed to execute sql: (1146, “Table ‘seahub-db.FileHistory’ doesn’t exist”)
[WARNING] Failed to execute sql: (1146, “Table ‘seahub-db.FileAudit’ doesn’t exist”)
[WARNING] Failed to execute sql: (1146, “Table ‘seahub-db.FileUpdate’ doesn’t exist”)
[WARNING] Failed to execute sql: (1146, “Table ‘seahub-db.PermAudit’ doesn’t exist”)
Done

migrating avatars …

Done

Later i receive this Problem, too:

[21:19h][root@Seafile][:/opt/seafile/seafile-server-latest]$ ./seahub.sh start

Cannot find JWT_PRIVATE_KEY value from environment, try to read .env file.
LC_ALL is not set in ENV, set to en_US.UTF-8
Starting seahub at port 8000 …

It’s the first time you start the seafile server. Now let’s create the admin account

What is the email for the admin account?
[ admin email ]

Seafile Server starts, and Seahub Server start also.

I see Login Webinterface, but on logging in, i receive an Website Error.

i would appreciate any ideas which help me tu upgrade my Seafile Server to Version 12 CE successfully.

thanks in advance
sourcedoctor

2

Did you create the conf/.env file?

# template

TIME_ZONE=UTC
JWT_PRIVATE_KEY=xxx
SEAFILE_SERVER_PROTOCOL=https
SEAFILE_SERVER_HOSTNAME=seafile.example.com
SEAFILE_MYSQL_DB_HOST=db # your MySQL host
SEAFILE_MYSQL_DB_PORT=3306
SEAFILE_MYSQL_DB_USER=seafile
SEAFILE_MYSQL_DB_PASSWORD=<your MySQL password>
SEAFILE_MYSQL_DB_CCNET_DB_NAME=ccnet_db
SEAFILE_MYSQL_DB_SEAFILE_DB_NAME=seafile_db
SEAFILE_MYSQL_DB_SEAHUB_DB_NAME=seahub_db

See Upgrade in Seafile Manual.

3

Hi,

yes .env File has been created in conf directory.
I’ve also set all parameter matching to my environment.
But it seems not to be found for some reason

4

Going back to the top, are you actually missing the database tables cited in the warning messages?

What version of Seafile CE 11 are you upgrading? Are you upgrading the latest version of Seafile CE 11?

-Thanks

5

i upgrade from
Seafile CE 11.0.13

6

Read the log files and see what happens when you start the server

7

i do not have some logs … where are they?
How can i see them?

all i have is a logger configuration in seahub_settings.py in conf directory, but i do not find something where access, and problems are logged to:

LOGGING = {
‘version’: 1,
‘disable_existing_loggers’: True,
‘formatters’: {
‘verbose’: {
‘format’: ‘%(process)-5d %(thread)d %(name)-50s %(levelname)-8s %(message)s’
},
‘standard’: {
‘format’: ‘%(asctime)s [%(levelname)s] %(name)s:%(lineno)s %(funcName)s %(message)s’
},
‘simple’: {
‘format’: ‘[%(asctime)s] %(name)s %(levelname)s %(message)s’,
‘datefmt’: ‘%d/%b/%Y %H:%M:%S’
},
},
‘filters’: {
‘require_debug_false’: {
‘()’: ‘django.utils.log.RequireDebugFalse’,
},
‘require_debug_true’: {
‘()’: ‘django.utils.log.RequireDebugTrue’,
},
},
‘handlers’: {
‘console’: {
‘filters’: [‘require_debug_true’],
‘class’: ‘logging.StreamHandler’,
‘formatter’: ‘simple’
},
‘syslog’: {
‘class’: ‘logging.handlers.SysLogHandler’,
‘address’: ‘/dev/log’,
‘formatter’: ‘standard’
},
},
‘loggers’: {
# root logger
# All logs printed by Seahub and any third party libraries will be handled by this logger.
‘’: {
‘handlers’: [‘console’, ‘syslog’],
‘level’: ‘DEBUG’, # Logs when log level is higher than info. Level can be any one of DEBUG, INFO, WARNING, ERROR, CRITICAL.
‘disabled’: False
},
# This logger recorded logs printed by Django Framework. For example, when you see 5xx page error, you should check the logs recorded by this logger.
‘django.request’: {
‘handlers’: [‘console’, ‘syslog’],
‘level’: ‘DEBUG’,
‘propagate’: False,
},
},
}

8

Do you have the missing databases?

9

They are usually stored in the logs folder

11

ah, ok

found it

for some Reason seafevents Configuration failed, so everything which depends on this configuration didn’t happens.

This causes Upgrade Problems to Version 12.

Thanks for the help