Mysql error in seafile server

I am getting this error when trying to create a shared link. Any ideas and this repeats in the log for a bit.

Traceback (most recent call last):
 File "/home/todd/seafile-server-7.1.5/seahub/thirdpart/django/core/handlers/exception.py", line 41, in inner
response = get_response(request)
 File "/home/todd/seafile-server-7.1.5/seahub/thirdpart/django/core/handlers/base.py", line 249, in _legacy_get_response
response = self._get_response(request)
File "/home/todd/seafile-server-7.1.5/seahub/thirdpart/django/core/handlers/base.py", line 187, in _get_response
response = self.process_exception_by_middleware(e, request)
File "/home/todd/seafile-server-7.1.5/seahub/thirdpart/django/core/handlers/base.py", line 185, in _get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/home/todd/seafile-server-7.1.5/seahub/thirdpart/django/views/decorators/csrf.py", line 58, in wrapped_view
return view_func(*args, **kwargs)
File "/home/todd/seafile-server-7.1.5/seahub/thirdpart/django/views/generic/base.py", line 68, in view
return self.dispatch(request, *args, **kwargs)
File "/home/todd/seafile-server-7.1.5/seahub/thirdpart/rest_framework/views.py", line 505, in dispatch
response = self.handle_exception(exc)
File "/home/todd/seafile-server-7.1.5/seahub/thirdpart/rest_framework/views.py", line 465, in handle_exception
self.raise_uncaught_exception(exc)
File "/home/todd/seafile-server-7.1.5/seahub/thirdpart/rest_framework/views.py", line 476, in raise_uncaught_exception
raise exc
File "/home/todd/seafile-server-7.1.5/seahub/thirdpart/rest_framework/views.py", line 502, in dispatch
response = handler(request, *args, **kwargs)
File "/home/todd/seafile-server-7.1.5/seahub/seahub/api2/endpoints/share_links.py", line 393, in post
fs = FileShare.objects.create_dir_link(username, repo_id, path,
File "/home/todd/seafile-server-7.1.5/seahub/seahub/share/models.py", line 156, in create_dir_link
return self._add_file_share(username, repo_id, path, 'd', password,
File "/home/todd/seafile-server-7.1.5/seahub/seahub/share/models.py", line 98, in _add_file_share
fs = super(FileShareManager, self).create(
File "/home/todd/seafile-server-7.1.5/seahub/thirdpart/django/db/models/manager.py", line 85, in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)
File "/home/todd/seafile-server-7.1.5/seahub/thirdpart/django/db/models/query.py", line 394, in create
obj.save(force_insert=True, using=self.db)
File "/home/todd/seafile-server-7.1.5/seahub/thirdpart/django/db/models/base.py", line 807, in save
self.save_base(using=using, force_insert=force_insert,
File "/home/todd/seafile-server-7.1.5/seahub/thirdpart/django/db/models/base.py", line 838, in save_base
updated = self._save_table(raw, cls, force_insert, force_update, using, update_fields)
File "/home/todd/seafile-server-7.1.5/seahub/thirdpart/django/db/models/base.py", line 924, in _save_table
result = self._do_insert(cls._base_manager, using, fields, update_pk, raw)
File "/home/todd/seafile-server-7.1.5/seahub/thirdpart/django/db/models/base.py", line 962, in _do_insert
return manager._insert([self], fields=fields, return_id=update_pk,
File "/home/todd/seafile-server-7.1.5/seahub/thirdpart/django/db/models/manager.py", line 85, in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)
File "/home/todd/seafile-server-7.1.5/seahub/thirdpart/django/db/models/query.py", line 1079, in _insert
return query.get_compiler(using=using).execute_sql(return_id)
File "/home/todd/seafile-server-7.1.5/seahub/thirdpart/pymysql/connections.py", line 676, in _read_packet
packet.raise_for_error()
File "/home/todd/seafile-server-7.1.5/seahub/thirdpart/pymysql/protocol.py", line 223, in raise_for_error
err.raise_mysql_exception(self._data)
File "/home/todd/seafile-server-7.1.5/seahub/thirdpart/pymysql/err.py", line 107, in raise_mysql_exception
raise errorclass(errno, errval)
django.db.utils.DataError: (1406, "Data too long for column 'token' at row 1")

So in case anyone else ever has this I went to seahub-db share_fileshare table and increased the token from varchar(10) to 100. Might be able to go lower but wanted to make sure it worked.

Then there could be more issues. This issue (either) means you haven’t run all migration scripts in the past (or there was a flaw in the upgrade scripts).