Internal Server Error after upgrade from 6.2.5 to 6.3.2

laest · July 23, 2018, 3:14pm

Hi everybody!

two days ago I upgraded my seafile community installation from version 6.2.5 to version 6.3.2. Since then, seafile client is not showing any libraries and the webinterface/seahub ist not working anymore -> Internal Server Error

To me, it looks like my NGINX configuration is not working with the new seafile server version. My nginx configuration is as follows (and worked well with version 6.2.5):

server {
   listen 80;
   server_name    my.seafile.url;
   return         301 https://$server_name$request_uri;
}

server {

   listen 443;
   ssl on;
   ssl_certificate /etc/ssl/nginx/cacert.pem;        # path to your cacert.pem
   ssl_certificate_key /etc/ssl/nginx/privkey.pem;   # path to your privkey.pem
   
   server_name listbox.dnshome.de;    
   location / {
       proxy_pass         http://127.0.0.1:8000;
       proxy_set_header   Host $host;
       proxy_set_header   X-Real-IP $remote_addr;
       proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
       proxy_set_header   X-Forwarded-Host $server_name;
       proxy_http_version 1.1; # if you use http2 or you get errors in nginx like connection refused ... HTTP/1.1
       proxy_read_timeout  1200s;

       # used for view/edit office file via Office Online Server
       client_max_body_size 0;

       access_log      /var/log/nginx/seahub.access.log;
       error_log       /var/log/nginx/seahub.error.log;
   }       
   
   location /seafhttp {
       rewrite ^/seafhttp(.*)$ $1 break;
       proxy_pass http://127.0.0.1:8082;
       client_max_body_size 0;
       proxy_http_version 1.1;
   }
   
   location /media {
       root /home/myseafileuser/seafile-server-latest/seahub;
   }
}

Since I do not use FCGI, version 6.3.2 should work as version 6.2.5 in my opinion. So I would really be thankful if you could help me fixing this problem, since going back to version 6.2.5 is not a durable solution

Thanks in advance guys

bionade24 · July 23, 2018, 3:30pm

Why do use this instead of rewrite ^ https://$http_host$request_uri? permanent; ?

Edit: If you have too much bugs, 6.3.1 is much more stable.

laest · July 23, 2018, 3:38pm

I just replaced the

return 301 https://$server_name$request_uri;

with the sudgested

rewrite ^ https://$http_host$request_uri? permanent;

Still the same error. I don’t know it the internal Server Error is a bug of 6.3.2 or just a missconfiguration thing,… i guess it is missconfig…

Even if I use the nginx config from the seafile manual 6.3.2 is not working (https://manual.seafile.com/deploy/https_with_nginx.html)

bionade24 · July 23, 2018, 3:39pm

What is the output of seahub.log and which error occurs on the browser?

laest · July 23, 2018, 3:56pm

seahub.log:

    2018-07-23 15:49:52,600 [ERROR] django.request:135 handle_uncaught_exception Internal Server Error: /api2/account/info/
Traceback (most recent call last):
  File "/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/core/handlers/exception.py", line 41, in inner
    response = get_response(request)
  File "/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/core/handlers/base.py", line 244, in _legacy_get_response
    response = middleware_method(request)
  File "/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/middleware/locale.py", line 24, in process_request
    i18n_patterns_used, prefixed_default_language = is_language_prefix_patterns_used(urlconf)
  File "/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/utils/lru_cache.py", line 100, in wrapper
    result = user_function(*args, **kwds)
  File "/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/conf/urls/i18n.py", line 29, in is_language_prefix_patterns_used
    for url_pattern in get_resolver(urlconf).url_patterns:
  File "/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/utils/functional.py", line 35, in __get__
    res = instance.__dict__[self.name] = self.func(instance)
  File "/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/urls/resolvers.py", line 405, in url_patterns
    patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module)
  File "/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/utils/functional.py", line 35, in __get__
    res = instance.__dict__[self.name] = self.func(instance)
  File "/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/urls/resolvers.py", line 398, in urlconf_module
    return import_module(self.urlconf_name)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "/home/seafile/seafile-server-6.3.2/seahub/seahub/utils/rooturl.py", line 41, in <module>
    url(r'^%s' % settings.SITE_ROOT[1:], include(settings.SITE_ROOT_URLCONF)),
  File "/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/conf/urls/__init__.py", line 50, in include
    urlconf_module = import_module(urlconf_module)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "/home/seafile/seafile-server-6.3.2/seahub/seahub/urls.py", line 12, in <module>
    from seahub.views.file import view_history_file, view_trash_file,\
  File "/home/seafile/seafile-server-6.3.2/seahub/seahub/views/file.py", line 43, in <module>
    from seahub.wopi.utils import get_wopi_dict
  File "/home/seafile/seafile-server-6.3.2/seahub/seahub/wopi/utils.py", line 7, in <module>
    import requests
  File "/home/seafile/seafile-server-6.3.2/seahub/thirdpart/requests-2.18.4-py2.7.egg/requests/__init__.py", line 90, in <module>
    from urllib3.exceptions import DependencyWarning
ImportError: cannot import name DependencyWarning

The error is that as soon as I want to open seahub through URL it says: internal server error, nothing else is displayed

bionade24 · July 23, 2018, 3:59pm

Seems not all parts of SeaFile were imported. Execute chmod -R a+rwx over the whole directory and try to update seafile to same version.

laest · July 23, 2018, 4:11pm

This is what I just did:

chmod -R a+rwx the whole seafile directory
stoped seafile and seahub
executed minor upgrade --> no change of the error
executed 6.2 to 6.3 upgrade script --> following errors during execution:

This script would upgrade your seafile server from 6.2 to 6.3
Press [ENTER] to contiune

Updating seafile/seahub database …

[INFO] You are using MySQL
[INFO] updating ccnet database…
/home/seafile/seafile-server-6.3.2/upgrade/db_update_helper.py:352: Warning: Table ‘LDAPConfig’ already exists
cursor.execute(sql)
/home/seafile/seafile-server-6.3.2/upgrade/db_update_helper.py:352: Warning: Table ‘GroupStructure’ already exists
cursor.execute(sql)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘parent_group_id’”)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[WARNING] Failed to execute sql: (1075, ‘Incorrect table definition; there can be only one auto column and it must be defined as a key’)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[WARNING] Failed to execute sql: (1075, ‘Incorrect table definition; there can be only one auto column and it must be defined as a key’)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[WARNING] Failed to execute sql: (1075, ‘Incorrect table definition; there can be only one auto column and it must be defined as a key’)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[INFO] updating seafile database…
/home/seafile/seafile-server-6.3.2/upgrade/db_update_helper.py:352: Warning: Table ‘SeafileConf’ already exists
cursor.execute(sql)
/home/seafile/seafile-server-6.3.2/upgrade/db_update_helper.py:352: Warning: Table ‘RepoInfo’ already exists
cursor.execute(sql)
[WARNING] Failed to execute sql: (1075, ‘Incorrect table definition; there can be only one auto column and it must be defined as a key’)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[WARNING] Failed to execute sql: (1075, ‘Incorrect table definition; there can be only one auto column and it must be defined as a key’)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[WARNING] Failed to execute sql: (1075, ‘Incorrect table definition; there can be only one auto column and it must be defined as a key’)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[WARNING] Failed to execute sql: (1075, ‘Incorrect table definition; there can be only one auto column and it must be defined as a key’)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[WARNING] Failed to execute sql: (1075, ‘Incorrect table definition; there can be only one auto column and it must be defined as a key’)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[WARNING] Failed to execute sql: (1075, ‘Incorrect table definition; there can be only one auto column and it must be defined as a key’)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[WARNING] Failed to execute sql: (1075, ‘Incorrect table definition; there can be only one auto column and it must be defined as a key’)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[WARNING] Failed to execute sql: (1075, ‘Incorrect table definition; there can be only one auto column and it must be defined as a key’)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[WARNING] Failed to execute sql: (1075, ‘Incorrect table definition; there can be only one auto column and it must be defined as a key’)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[WARNING] Failed to execute sql: (1075, ‘Incorrect table definition; there can be only one auto column and it must be defined as a key’)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[WARNING] Failed to execute sql: (1075, ‘Incorrect table definition; there can be only one auto column and it must be defined as a key’)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[WARNING] Failed to execute sql: (1075, ‘Incorrect table definition; there can be only one auto column and it must be defined as a key’)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[WARNING] Failed to execute sql: (1075, ‘Incorrect table definition; there can be only one auto column and it must be defined as a key’)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[WARNING] Failed to execute sql: (1075, ‘Incorrect table definition; there can be only one auto column and it must be defined as a key’)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[WARNING] Failed to execute sql: (1075, ‘Incorrect table definition; there can be only one auto column and it must be defined as a key’)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[WARNING] Failed to execute sql: (1075, ‘Incorrect table definition; there can be only one auto column and it must be defined as a key’)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[WARNING] Failed to execute sql: (1075, ‘Incorrect table definition; there can be only one auto column and it must be defined as a key’)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[WARNING] Failed to execute sql: (1075, ‘Incorrect table definition; there can be only one auto column and it must be defined as a key’)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[WARNING] Failed to execute sql: (1075, ‘Incorrect table definition; there can be only one auto column and it must be defined as a key’)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘id’”)
[INFO] updating seahub database…
[WARNING] Failed to execute sql: (1061, “Duplicate key name ‘notifications_notification_386bba5a’”)
[WARNING] Failed to execute sql: (1061, “Duplicate key name ‘institutions_institutionadmin_user_7560167c8413ff0e_uniq’”)
Done

migrating avatars …

Done

updating /home/seafile/seafile-server-latest symbolic link to /home/seafile/seafile-server-6.3.2 …

Upgraded your seafile server successfully.

bionade24 · July 23, 2018, 4:36pm

Did you the mysql table upgrade?

laest · July 23, 2018, 4:39pm

This one?

./seahub.sh python-env seahub/manage.py migrate_file_comment

If yes, I did. My upgrade procedure was as usual:

stop seafile and seahub
wget & tar new version
execute upgrade script
start seafile and seahub

bionade24 · July 23, 2018, 5:08pm

yes, but you have to upgrade it when seafile is running

laest · July 23, 2018, 5:13pm

I am not 100% sure, but I think I did run the mysql upgrade when the server is running because it gave me an error that seafile needs to be running in the first place

Anyway, I just excecuted the mysql upgrade again, this is the output:

seafile-server-6.3.2$ ./seahub.sh python-env seahub/manage.py migrate_file_comment

LC_ALL is not set in ENV, set to en_US.UTF-8

Warning: File comment has changed since version 6.3, while table `base_filecomment` is not migrated yet, please consider migrate it according to v6.3.0 release note, otherwise the file comment feature will not work correctly.
            
/home/seafile/seafile-server-6.3.2/seahub/thirdpart/requests-2.18.4-py2.7.egg/requests/__init__.py:80: RequestsDependencyWarning: urllib3 (1.9.1) or chardet (3.0.4) doesn't match a supported version!
  RequestsDependencyWarning)
Traceback (most recent call last):
  File "seahub/manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/core/management/__init__.py", line 364, in execute_from_command_line
    utility.execute()
  File "/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/core/management/__init__.py", line 356, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/core/management/base.py", line 283, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/core/management/base.py", line 327, in execute
    self.check()
  File "/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/core/management/base.py", line 359, in check
    include_deployment_checks=include_deployment_checks,
  File "/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/core/management/base.py", line 346, in _run_checks
    return checks.run_checks(**kwargs)
  File "/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/core/checks/registry.py", line 81, in run_checks
    new_errors = check(app_configs=app_configs)
  File "/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/core/checks/urls.py", line 16, in check_url_config
    return check_resolver(resolver)
  File "/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/core/checks/urls.py", line 26, in check_resolver
    return check_method()
  File "/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/urls/resolvers.py", line 254, in check
    for pattern in self.url_patterns:
  File "/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/utils/functional.py", line 35, in __get__
    res = instance.__dict__[self.name] = self.func(instance)
  File "/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/urls/resolvers.py", line 405, in url_patterns
    patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module)
  File "/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/utils/functional.py", line 35, in __get__
    res = instance.__dict__[self.name] = self.func(instance)
  File "/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/urls/resolvers.py", line 398, in urlconf_module
    return import_module(self.urlconf_name)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "/home/seafile/seafile-server-6.3.2/seahub/seahub/utils/rooturl.py", line 41, in <module>
    url(r'^%s' % settings.SITE_ROOT[1:], include(settings.SITE_ROOT_URLCONF)),
  File "/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/conf/urls/__init__.py", line 50, in include
    urlconf_module = import_module(urlconf_module)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "/home/seafile/seafile-server-6.3.2/seahub/seahub/urls.py", line 12, in <module>
    from seahub.views.file import view_history_file, view_trash_file,\
  File "/home/seafile/seafile-server-6.3.2/seahub/seahub/views/file.py", line 43, in <module>
    from seahub.wopi.utils import get_wopi_dict
  File "/home/seafile/seafile-server-6.3.2/seahub/seahub/wopi/utils.py", line 7, in <module>
    import requests
  File "/home/seafile/seafile-server-6.3.2/seahub/thirdpart/requests-2.18.4-py2.7.egg/requests/__init__.py", line 90, in <module>
    from urllib3.exceptions import DependencyWarning
ImportError: cannot import name DependencyWarning
Done.

Edit: I just managed to solve the problem. Thank you for your guidance, without that I would not have got it up an running again

All I did was doing some research about the “ImportError: cannot import name DependencyWarning” error of the mysql upgrade skript. Following thread gave me the solution https://forum.seafile.com/t/solved-upgrade-from-6-2-5-to-6-3-1-importerror-cannot-import-name-dependencywarning/6554(thanks to user klangborste for sharing the solution):

sudo apt-get remove python-pip
sudo easy_install pip
sudo pip install --upgrade urllib3
Stop Seafile
rm -rf /<tmp_dir>/seahub_cache/
Start Seafile

Now my seafile 6.3.2 installation works great again Thanks again for your help

bionade24 · July 23, 2018, 6:27pm

This would be my next advice, to reinstall urllib3,
No problem, I always help where I can!

Niclas · August 16, 2018, 1:10pm

I’ve got the same problem and tried the suggested solutions, but still fail.

In “laest”'s description is missing the part “sudo apt-get install python-pip” in step 2. Otherwise you get errors that pip cannot be found
Step 3 fails for me with error message: “Cannot fetch index base URL http://pypi.python.org/simple - Could not find any downloads that satisfy the requirement urllib3 in /usr/lib/python2.7/dist-packages – No distributions at all found for urllib3 in /usr/lib/python2.7/dist-packages – Storing complete log in /root/.pip/pip.log”
./seahub.sh python-env seahub/manage.py migrate_file_comment fails, too with a long error message, ending with: "ImportError: cannot import name DependencyWarning

Currently I’m clueless and hope you have any idea what to do.

:EDIT: No my web interfaces shows: 502 Bad Gateway - nginx

bionade24 · August 18, 2018, 9:29am

So Seahub doesn’t work. Please post your seahub.log.

Niclas · August 21, 2018, 7:35am

Ok, now it’s “Internal server error” again. Seahub was an issue since sync worked, except for the UIs in browser and client. But now even sync isn’t doing it’s job anymore, so it looks like Seafile is affected, too.

Here’s an excerpt of seahub.log:

Blockquote
2018-08-21 07:16:52,982 [ERROR] django.request:135 handle_uncaught_exception Internal Server Error: /api2/events/
Traceback (most recent call last):
File “/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/core/handlers/exception.py”, line 41, in inner
response = get_response(request)
File “/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/core/handlers/base.py”, line 244, in _legacy_get_response
response = middleware_method(request)
File “/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/middleware/locale.py”, line 24, in process_request
i18n_patterns_used, prefixed_default_language = is_language_prefix_patterns_used(urlconf)
File “/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/utils/lru_cache.py”, line 100, in wrapper
result = user_function(*args, **kwds)
File “/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/conf/urls/i18n.py”, line 29, in is_language_prefix_patterns_used
for url_pattern in get_resolver(urlconf).url_patterns:
File “/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/utils/functional.py”, line 35, in get
res = instance.dict[self.name] = self.func(instance)
File “/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/urls/resolvers.py”, line 405, in url_patterns
patterns = getattr(self.urlconf_module, “urlpatterns”, self.urlconf_module)
File “/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/utils/functional.py”, line 35, in get
res = instance.dict[self.name] = self.func(instance)
File “/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/urls/resolvers.py”, line 398, in urlconf_module
return import_module(self.urlconf_name)
File “/usr/lib/python2.7/importlib/init.py”, line 37, in import_module
import(name)
File “/home/seafile/seafile-server-6.3.2/seahub/seahub/utils/rooturl.py”, line 41, in
url(r’^%s’ % settings.SITE_ROOT[1:], include(settings.SITE_ROOT_URLCONF)),
File “/home/seafile/seafile-server-6.3.2/seahub/thirdpart/Django-1.11.13-py2.7.egg/django/conf/urls/init.py”, line 50, in include
urlconf_module = import_module(urlconf_module)
File “/usr/lib/python2.7/importlib/init.py”, line 37, in import_module
import(name)
File “/home/seafile/seafile-server-6.3.2/seahub/seahub/urls.py”, line 12, in
from seahub.views.file import view_history_file, view_trash_file,
File “/home/seafile/seafile-server-6.3.2/seahub/seahub/views/file.py”, line 43, in
from seahub.wopi.utils import get_wopi_dict
File “/home/seafile/seafile-server-6.3.2/seahub/seahub/wopi/utils.py”, line 7, in
import requests
File “/home/seafile/seafile-server-6.3.2/seahub/thirdpart/requests-2.18.4-py2.7.egg/requests/init.py”, line 90, in
from urllib3.exceptions import DependencyWarning
ImportError: cannot import name DependencyWarning

That’s the part that keeps repeating itself after the upgrade.

bionade24 · August 21, 2018, 8:48am

Try it with sudo python -m pip install --upgrade pip and then sudo python -m install urllib3

Niclas · August 21, 2018, 12:45pm

Hmm…I think I tried that already.

I’m just getting the error message: /usr/bin/python: No module named pip.main; ‘pip’ is a package and cannot be directly executed

And for the second command: /usr/bin/python: No module named installed

Niclas · August 22, 2018, 7:52am

In the meantime I renamed the seafile-server-6.3.2 directory and my backed up seafile-server-6.2.5_bak back to seafile-server-6.2.5. After that I executed the minor-script.sh and at least got my web UI back and the libraries listed in the Seafile client and browser.

But still there is an issue since the client shows: “Serverfehler” (“Server Error”) below each library and tries to upload from time to time, unsuccessfully. Via webbrowser I can access the libraries and open the files.

bionade24 · August 22, 2018, 8:42am

Can you open your python 2 console with python2 ?

Niclas · August 22, 2018, 8:44am

Yes, it says:

Python 2.7.3 (default Nov 24 2017, 21:13:24)
[GCC 4.6.3] on linux2

Seems to be outdated?!

Internal Server Error after upgrade from 6.2.5 to 6.3.2

This script would upgrade your seafile server from 6.2 to 6.3 Press [ENTER] to contiune

This script would upgrade your seafile server from 6.2 to 6.3
Press [ENTER] to contiune