Sharelink Unavailable after upgrade to 6.1.2

Hello,

I have a Seafile Community edition. I upgraded from 6.0.9 to 6.1.1 to 6.1.2.

After the upgrade I have seen problems with share links.
When a guest try to access the share URL a error-message is presented:

Page unavailable
Sorry, but the requested page is unavailable due to a server hiccup.
Our engineers have been notified, so check back later.

Also when I try to create a new share link the dialog where I generate the URL are empty (just blank white space…). The dialogs for Upload or sharing with other users/groups are working as expected…

Any Ideas?..

I found this in the seahub_django_request.log:

2017-08-17 10:39:41,232 [ERROR] django.request:256 handle_uncaught_exception Internal Server Error: /d/1ab49d2bf/
Traceback (most recent call last):
  File "/home/seafile-server-6.1.2/seahub/thirdpart/Django-1.8.18-py2.7.egg/django/core/handlers/base.py", line 132, in get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/home/seafile-server-6.1.2/seahub/seahub/share/decorators.py", line 15, in _decorated
    fileshare = FileShare.objects.get_valid_file_link_by_token(token) or \
  File "/home/seafile-server-6.1.2/seahub/seahub/share/models.py", line 136, in get_valid_file_link_by_token
    return self._get_valid_file_share_by_token(token)
  File "/home/seafile-server-6.1.2/seahub/seahub/share/models.py", line 110, in _get_valid_file_share_by_token
    fs = self.get(token=token)
  File "/home/seafile-server-6.1.2/seahub/thirdpart/Django-1.8.18-py2.7.egg/django/db/models/manager.py", line 127, in manager_method
    return getattr(self.get_queryset(), name)(*args, **kwargs)
  File "/home/seafile-server-6.1.2/seahub/thirdpart/Django-1.8.18-py2.7.egg/django/db/models/query.py", line 328, in get
    num = len(clone)
  File "/home/seafile-server-6.1.2/seahub/thirdpart/Django-1.8.18-py2.7.egg/django/db/models/query.py", line 144, in __len__
    self._fetch_all()
  File "/home/seafile-server-6.1.2/seahub/thirdpart/Django-1.8.18-py2.7.egg/django/db/models/query.py", line 965, in _fetch_all
    self._result_cache = list(self.iterator())
  File "/home/seafile-server-6.1.2/seahub/thirdpart/Django-1.8.18-py2.7.egg/django/db/models/query.py", line 238, in iterator
    results = compiler.execute_sql()
  File "/home/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/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/seafile-server-6.1.2/seahub/thirdpart/Django-1.8.18-py2.7.egg/django/db/utils.py", line 98, in __exit__
    six.reraise(dj_exc_type, dj_exc_value, traceback)
  File "/home/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/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 174, in execute
    self.errorhandler(self, exc, value)
  File "/usr/lib/python2.7/dist-packages/MySQLdb/connections.py", line 36, in defaulterrorhandler
    raise errorclass, errorvalue
OperationalError: (1054, "Unknown column 'share_fileshare.permission' in 'field list'")

I also see a 500 server error in network browser networklog:
https://the_domain.com/api/v2.1/share-links/?repo_id=a37a4435-b79c-4d19-b315-e2dc286aaad8&path=%2Feja%2Fel.pdf&_=1502958728159

This occours when I try to create a share-url for the file specified.

Regards, Sam

Did you run the upgrade script correctly?

You didn’t run the upgrade scripts properly.

Read the “How to upgrade” section of the server manual.

Ah, my fault! I missed the upgrade script 6.0 to 6.1.
I have a shell-script that downloads the package and extract, stop server and run the minor-upgrade (only!) and start again… :slight_smile:
Use to run the update manually when its a major version change…
Sorry! And thanks lot for sorting it out!

//Sam