Upgrade 6.1.1 - 6.1.2

Hi,
I upgraded from version 6.1.1 to 6.1.2 and after logging in, I get the message “Library does not exist”.
Is there any way I can get my libraries back?

Best regards,
Krzysztof

Hi
Post your seafile log files …

#tail seafile.log -n 50

[08/18/2017 01:14:03 PM] …/common/seaf-db.c(425): Error prepare statement SELECT r.repo_id, s.size, b.commit_id, fc.file_count FROM Repo r LEFT JOIN Branch b ON r.repo_id = b.repo_id LEFT JOIN RepoSize s ON r.repo_id = s.repo_id LEFT JOIN RepoFileCount fc ON r.repo_id = fc.repo_id WHERE r.repo_id = ? AND b.name = ‘master’: mysql_stmt_prepare failed: Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8_polish_ci,IMPLICIT) for operation ‘=’.
[08/18/2017 01:14:03 PM] seafile-session.c(382): Failed to get system default repo. Create a new one.
[08/18/2017 01:14:03 PM] …/common/seaf-db.c(425): Error prepare statement SELECT r.repo_id, s.size, b.commit_id, fc.file_count FROM Repo r LEFT JOIN Branch b ON r.repo_id = b.repo_id LEFT JOIN RepoSize s ON r.repo_id = s.repo_id LEFT JOIN RepoFileCount fc ON r.repo_id = fc.repo_id WHERE r.repo_id = ? AND b.name = ‘master’: mysql_stmt_prepare failed: Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8_polish_ci,IMPLICIT) for operation ‘=’.
[08/18/2017 01:14:03 PM] repo-op.c(626): Repo 8603f850-8a50-44b4-8bcd-98657702d934 doesn’t exist.
[08/18/2017 01:14:03 PM] seafile-session.c(345): Failed to add template file /home/haiwen/seafile-data/library-template/seafile-tutorial.doc.
[08/18/2017 01:14:50 PM] …/common/seaf-db.c(425): Error prepare statement SELECT r.repo_id, s.size, b.commit_id, fc.file_count FROM Repo r LEFT JOIN Branch b ON r.repo_id = b.repo_id LEFT JOIN RepoSize s ON r.repo_id = s.repo_id LEFT JOIN RepoFileCount fc ON r.repo_id = fc.repo_id WHERE r.repo_id = ? AND b.name = ‘master’: mysql_stmt_prepare failed: Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8_polish_ci,IMPLICIT) for operation ‘=’.
[08/18/2017 01:14:55 PM] …/common/seaf-db.c(425): Error prepare statement SELECT r.repo_id, s.size, b.commit_id, fc.file_count FROM Repo r LEFT JOIN Branch b ON r.repo_id = b.repo_id LEFT JOIN RepoSize s ON r.repo_id = s.repo_id LEFT JOIN RepoFileCount fc ON r.repo_id = fc.repo_id WHERE r.repo_id = ? AND b.name = ‘master’: mysql_stmt_prepare failed: Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8_polish_ci,IMPLICIT) for operation ‘=’.
[08/18/2017 01:15:00 PM] …/common/seaf-db.c(425): Error prepare statement SELECT r.repo_id, s.size, b.commit_id, fc.file_count FROM Repo r LEFT JOIN Branch b ON r.repo_id = b.repo_id LEFT JOIN RepoSize s ON r.repo_id = s.repo_id LEFT JOIN RepoFileCount fc ON r.repo_id = fc.repo_id WHERE r.repo_id = ? AND b.name = ‘master’: mysql_stmt_prepare failed: Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8_polish_ci,IMPLICIT) for operation ‘=’.
[08/18/2017 01:15:09 PM] …/common/seaf-db.c(425): Error prepare statement SELECT r.repo_id, s.size, b.commit_id, fc.file_count FROM Repo r LEFT JOIN Branch b ON r.repo_id = b.repo_id LEFT JOIN RepoSize s ON r.repo_id = s.repo_id LEFT JOIN RepoFileCount fc ON r.repo_id = fc.repo_id WHERE r.repo_id = ? AND b.name = ‘master’: mysql_stmt_prepare failed: Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8_polish_ci,IMPLICIT) for operation ‘=’.
[08/18/2017 01:15:18 PM] …/common/seaf-db.c(425): Error prepare statement SELECT r.repo_id, s.size, b.commit_id, fc.file_count FROM Repo r LEFT JOIN Branch b ON r.repo_id = b.repo_id LEFT JOIN RepoSize s ON r.repo_id = s.repo_id LEFT JOIN RepoFileCount fc ON r.repo_id = fc.repo_id WHERE r.repo_id = ? AND b.name = ‘master’: mysql_stmt_prepare failed: Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8_polish_ci,IMPLICIT) for operation ‘=’.

tail seahub.log -n 50

File “/home/haiwen/seafile-server-6.1.2/seahub/thirdpart/Django-1.8.18-py2.7.egg/django/db/models/base.py”, line 877, in _do_update
return filtered._update(values) > 0
File “/home/haiwen/seafile-server-6.1.2/seahub/thirdpart/Django-1.8.18-py2.7.egg/django/db/models/query.py”, line 580, in _update
return query.get_compiler(self.db).execute_sql(CURSOR)
File “/home/haiwen/seafile-server-6.1.2/seahub/thirdpart/Django-1.8.18-py2.7.egg/django/db/models/sql/compiler.py”, line 1062, in execute_sql
cursor = super(SQLUpdateCompiler, self).execute_sql(result_type)
File “/home/haiwen/seafile-server-6.1.2/seahub/thirdpart/Django-1.8.18-py2.7.egg/django/db/models/sql/compiler.py”, line 840, in execute_sql
cursor.execute(sql, params)
File “/home/haiwen/seafile-server-6.1.2/seahub/thirdpart/Django-1.8.18-py2.7.egg/django/db/backends/utils.py”, line 64, in execute
return self.cursor.execute(sql, params)
File “/home/haiwen/seafile-server-6.1.2/seahub/thirdpart/Django-1.8.18-py2.7.egg/django/db/backends/mysql/base.py”, line 129, in execute
six.reraise(utils.IntegrityError, utils.IntegrityError(*tuple(e.args)), sys.exc_info()[2])
File “/home/haiwen/seafile-server-6.1.2/seahub/thirdpart/Django-1.8.18-py2.7.egg/django/db/backends/mysql/base.py”, line 124, in execute
return self.cursor.execute(query, args)
File “/usr/lib/python2.7/dist-packages/MySQLdb/cursors.py”, line 226, in execute
self.errorhandler(self, exc, value)
File “/usr/lib/python2.7/dist-packages/MySQLdb/connections.py”, line 36, in defaulterrorhandler
raise errorvalue
IntegrityError: (1048, “Column ‘created_at’ cannot be null”)
2017-08-18 11:15:39,499 [ERROR] seahub.api2.authentication:139 authenticate_v2 error when save token v2:
Traceback (most recent call last):
File “/home/haiwen/seafile-server-6.1.2/seahub/seahub/api2/authentication.py”, line 137, in authenticate_v2
token.save()
File “/home/haiwen/seafile-server-6.1.2/seahub/seahub/api2/models.py”, line 171, in save
return super(TokenV2, self).save(*args, **kwargs)
File “/home/haiwen/seafile-server-6.1.2/seahub/thirdpart/Django-1.8.18-py2.7.egg/django/db/models/base.py”, line 734, in save
force_update=force_update, update_fields=update_fields)
File “/home/haiwen/seafile-server-6.1.2/seahub/thirdpart/Django-1.8.18-py2.7.egg/django/db/models/base.py”, line 762, in save_base
updated = self._save_table(raw, cls, force_insert, force_update, using, update_fields)
File “/home/haiwen/seafile-server-6.1.2/seahub/thirdpart/Django-1.8.18-py2.7.egg/django/db/models/base.py”, line 827, in _save_table
forced_update)
File “/home/haiwen/seafile-server-6.1.2/seahub/thirdpart/Django-1.8.18-py2.7.egg/django/db/models/base.py”, line 877, in _do_update
return filtered._update(values) > 0
File “/home/haiwen/seafile-server-6.1.2/seahub/thirdpart/Django-1.8.18-py2.7.egg/django/db/models/query.py”, line 580, in _update
return query.get_compiler(self.db).execute_sql(CURSOR)
File “/home/haiwen/seafile-server-6.1.2/seahub/thirdpart/Django-1.8.18-py2.7.egg/django/db/models/sql/compiler.py”, line 1062, in execute_sql
cursor = super(SQLUpdateCompiler, self).execute_sql(result_type)
File “/home/haiwen/seafile-server-6.1.2/seahub/thirdpart/Django-1.8.18-py2.7.egg/django/db/models/sql/compiler.py”, line 840, in execute_sql
cursor.execute(sql, params)
File “/home/haiwen/seafile-server-6.1.2/seahub/thirdpart/Django-1.8.18-py2.7.egg/django/db/backends/utils.py”, line 64, in execute
return self.cursor.execute(sql, params)
File “/home/haiwen/seafile-server-6.1.2/seahub/thirdpart/Django-1.8.18-py2.7.egg/django/db/backends/mysql/base.py”, line 129, in execute
six.reraise(utils.IntegrityError, utils.IntegrityError(*tuple(e.args)), sys.exc_info()[2])
File “/home/haiwen/seafile-server-6.1.2/seahub/thirdpart/Django-1.8.18-py2.7.egg/django/db/backends/mysql/base.py”, line 124, in execute
return self.cursor.execute(query, args)
File “/usr/lib/python2.7/dist-packages/MySQLdb/cursors.py”, line 226, in execute
self.errorhandler(self, exc, value)
File “/usr/lib/python2.7/dist-packages/MySQLdb/connections.py”, line 36, in defaulterrorhandler
raise errorvalue
IntegrityError: (1048, “Column ‘created_at’ cannot be null”)

which script did u use? minor_upgrade.sh?

cause i have the same setup & it worked for me…

you can always go back to your earlier one… just stop services & start it manually from earlier version & check again

minor_upgrade.sh . I’ve upgraded on two others servers and it worked fine.

“mysql_stmt_prepare failed: Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8_polish_ci,IMPLICIT)”

This is your error. Go fix your mysql table collations.

Thx. I’ve changed collation from utf8_polish_ci to utf8_general_ci on all seafile databases and tables, and everythink is OK.