Yes, I have oauth configured.
Update documentation please :
add
pip3 install --timeout=3600 python-memcached
If seahub dont start !!
1 Like
It is caused by that you use an old memcache configuration that depends on python-memcache. The new way is
'BACKEND': 'django_pylibmc.memcached.PyLibMCCache',
The old way is
'BACKEND': ‘'django.core.cache.backends.memcached.MemcachedCache',
2 Likes
I have been saving seafile-data to a separate directory (separate hard drive) from seafile scripts in the past, but it seems to not be an option any more. Installation script (setup-seafile-mysql.py) no longer prompts user for seafile data directory location and doesn’t save the seafile data directory location to ccnet/seafile.ini. I tweaked the installation script to save seafile data to another directory, but it seems like seafile.sh and seahub.sh scripts assume the data files to be in the directory one level up. Was that intentional?
2 Likes
Just installed 7.1.3 Pro on my preproduction server and hitting it with some basic tests.
Not sure if it’s just my system or a bug, but when I go into the administration-panel and click on statistics, I get an blank page + an error message on the top saying: Please check your network connection:
Nothing important for me, but just wanted to give this feedback
In addition the administrator lost his 2fa configuration and was able to login without 2fa. I could re-enable it again and was fine there.
The one other normal user I have on the test-server still had 2fa enabled.
If you want to change the seafile-data to another place, you can use symbolic link. Support saving seafile-data to a separate directory is not necessary, so it had been removed.
Statistics work fine in my 7.1.3 Pro production instance. Could you find/provide some log entries?
I see, thanks for the reply!
Aha that is very relevant information! I tested the docker version of 7.1.3 as an upgrade, but Seafile couldn’t find the commits, so I downgraded again. I use a custom path for seafile-data in ccnet.conf, like probably many others, so that’s probably the reason it didn’t work.
It would be nice if the upgrade script would recognize this and set the symbolic link.
1 Like
I also use it. So far there is no hint in the upgrade documentation. (https://download.seafile.com/published/seafile-manual/upgrade/upgrade_notes_for_7.1.x.md)
Looks like 7.1.x is still beta.
1 Like
Note for those who need to downgrade: the gunicorn.conf configuration file will be renamed to gunicorn.conf.py during the upgrade process. This is stated in the upgrade script, but you won’t see this when using the Docker containers. So it would be nice if this would also be mentioned in the upgrade notes.
The upgrade/install instructions for 7.1 are incomplete.
The instructions to add the pip3 packages will fail if system package libmemcached-dev is missing (pylibmc will fail to build). libmemcached-dev should be added as needed package in the information above.
Unfortunately the upgrade from 7.0.5 didn’t work for me at all under Debian9:
- Installed:
apt install python3 python3-setuptools python3-pip -y
pip3 install --timeout=3600 Pillow pylibmc captcha jinja2 sqlalchemy psd-tools django-pylibmc django-simple-captcha python3-ldap
-
Followed memcache fix in Seafile server 7.1.3 is ready!.
-
Starting seafile server I get:
Apr 27 00:31:17 vm-seafile python3[2112]: 2020-04-27 00:31:17,669 [ERROR] django.request:135 handle_uncaught_exception Internal Server Er
Traceback (most recent call last):
File "/opt/seafile/seafile-server-7.1.3/seahub/thirdpart/django/core/handlers/exception.py",
response = get_response(request)
File "/opt/seafile/seafile-server-7.1.3/seahub/thirdpart/django/core/handlers/base.py", line
response = middleware_method(request)
File "/opt/seafile/seafile-server-7.1.3/seahub/thirdpart/django/middleware/locale.py", line 2
i18n_patterns_used, prefixed_default_language = is_language_prefix_patterns_used(urlconf)
File "/opt/seafile/seafile-server-7.1.3/seahub/thirdpart/django/conf/urls/i18n.py", line 29,
for url_pattern in get_resolver(urlconf).url_patterns:
File "/opt/seafile/seafile-server-7.1.3/seahub/thirdpart/django/utils/functional.py", line 35
res = instance.__dict__[self.name] = self.func(instance)
File "/opt/seafile/seafile-server-7.1.3/seahub/thirdpart/django/urls/resolvers.py", line 407,
patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module)
File "/opt/seafile/seafile-server-7.1.3/seahub/thirdpart/django/utils/functional.py", line 35
res = instance.__dict__[self.name] = self.func(instance)
File "/opt/seafile/seafile-server-7.1.3/seahub/thirdpart/django/urls/resolvers.py", line 400,
return import_module(self.urlconf_name)
File "/usr/lib/python3.5/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 986, in _gcd_import
-> rollback to 7.0.5
In short: you are using python3.5, which is not enough.
2 Likes
I tried to setup 7.1.3 on my home server running a fresh and up to date Debian 10 Buster on docker-ce.
mysql and memcached start but seafile does not start, if I enable https with letsencrypt. Having only http starts if I comment out timezone line.
Is this a known bug? Do we stick to 7.0.5 for the moment?
Thx, so time for a dist upgrade.
@saljut7 I think so, but you could check https://linuxize.com/post/how-to-install-python-3-7-on-debian-9/. For me was a possible alternative if you need to stick to debian 9. After that, you could use the update-alternatives. Here is a good example for that.
1 Like
Hi,
In the previous version (in cloud mode) it was possible for the admin to add members to a group.
Right now this is not possible anymore.
Was this a bug, or will it come back?
Can you post a screenshot? In my case, I can still add a member in “System Admin -> Groups -> A group page -> Members”
