所有文件均显示Page unavailable.清缓存无效。(已解决)


#1

点到文件下载页面时显示该错误页面。浏览文件列表正常。客户端下载正常。浏览器是Chrome。服务端版本6.1.1
清缓存无效,重启无效。
此前一直正常运行。
seahub_django_request.log日志:
2017-07-07 07:38:45,245 [ERROR] django.request:256 handle_uncaught_exception Internal Server Error: /lib/964ed056-017c-4d66-9260-5c98e2f7abce/file/software/develop/VisualGDB-5.2r8.zip
Traceback (most recent call last):
File “/www/seafile/seafile-server-6.1.1/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 “/www/seafile/seafile-server-6.1.1/seahub/seahub/auth/decorators.py”, line 27, in _wrapped_view
return view_func(request, *args, **kwargs)
File “/www/seafile/seafile-server-6.1.1/seahub/seahub/base/decorators.py”, line 74, in _decorated
return func(request, *args, **kwargs)
File “/www/seafile/seafile-server-6.1.1/seahub/seahub/views/file.py”, line 375, in view_lib_file
return _file_view(request, repo_id, path)
File “/www/seafile/seafile-server-6.1.1/seahub/seahub/views/file.py”, line 559, in _file_view
fileshare = l[0] if len(l) > 0 else None
File “/www/seafile/seafile-server-6.1.1/seahub/thirdpart/Django-1.8.18-py2.7.egg/django/db/models/query.py”, line 144, in len
self._fetch_all()
File “/www/seafile/seafile-server-6.1.1/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 “/www/seafile/seafile-server-6.1.1/seahub/thirdpart/Django-1.8.18-py2.7.egg/django/db/models/query.py”, line 238, in iterator
results = compiler.execute_sql()
File “/www/seafile/seafile-server-6.1.1/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 “/www/seafile/seafile-server-6.1.1/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 “/www/seafile/seafile-server-6.1.1/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 “/www/seafile/seafile-server-6.1.1/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 “/www/seafile/seafile-server-6.1.1/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/lib64/python2.7/site-packages/MySQLdb/cursors.py”, line 205, in execute
self.errorhandler(self, exc, value)
File “/usr/lib64/python2.7/site-packages/MySQLdb/connections.py”, line 36, in defaulterrorhandler
raise errorclass, errorvalue
OperationalError: (1054, “Unknown column ‘share_fileshare.permission’ in ‘field list’”)
2017-07-07 07:46:08,500 [WARNING] django.request:170 get_response Not Found: /sys/notificationadmin/。


#2

没有运行 6.0 - 6.1 的升级脚本吧


#3

在升级到6.1的时候就运行过了。也成功的跑了一段时间了。只是在今天突然就不行了。或者是今天才发现不行了。因为之前一直是用客户端的


#4

有没有人来给个解决办法啊。


#5

重新从备份的6.0.9升级到6.1.1,现在没问题了。应该是遗漏了6.0-6.1的升级,而只是进行了minor-upgrade.sh。这点其实应该做的更智能化一些,统一使用一个升级脚本,然后脚本来自动判断需要升级哪些东西。


#6

兄弟,你这个Sea file网页登录不了的问题最后怎么解决的呢,谢谢了


#7

时间太久记不太清楚了。
印象中此类问题可以试试停止后把/tmp里的缓存全部删掉,
不然就是我上面说的,升级的时候有些版本遗漏了。


#8

谢谢啊,兄弟。执行过fsck和gc两个命令,.cache里面是空的,重启以后还是不行,也没有升级过,不知道怎么回事