Internal Server Error after Upgrade to 11.0.12 CE

Seafile Server
1

Hello everyone

Ubuntu 20.04, Python 3.8.1, Seafile with MySQL DB, NGINX as Reverse Proxy

I tried to upgrade to 11.0.12 from 10.0.1. I ran the prerequisites mentioned in the upgrade guide and started the Upgrade script.

It went through, only with the Warning

  • [WARNING] Failed to execute sql: (1054, “Unknown column ‘domain’ in ‘org_saml_config’”)

(Im not running anything fancy, no LDAP, no SAML, so I think the warning can be ignored?)

But after the update I just get “Internal Server Error”, both on the Webpage, as well as on the Seafile Client. Seafile logs also indicate no error.

  • Seahub.log is empty (I deleted once to clear it, nothing has been written to it since)

  • Seafile.log (last 9 lines)
    2024-10-11 23:13:18 seafile-session.c(102): fileserver: max_indexing_threads = 1
    2024-10-11 23:13:18 …/common/seaf-utils.c(359): Use database Mysql
    2024-10-11 23:13:18 http-server.c(195): fileserver: worker_threads = 10
    2024-10-11 23:13:18 http-server.c(217): fileserver: cluster_shared_temp_file_mode = 600
    2024-10-11 23:13:18 socket file exists, delete it anyway
    2024-10-11 23:13:21 start to serve on pipe client
    2024-10-11 23:13:21 start to serve on pipe client
    2024-10-11 23:13:21 start to serve on pipe client
    2024-10-11 23:13:29 start to serve on pipe client

I also checked the Upgrade FAQs, the only similar entry is for an upgrade to Ver. 10 which mentions something regarding Django Python Caching, but since it was already working on Ver. 10 I would say that this settings is already correct.

CACHES = {
    'default': {
        'BACKEND': 'django_pylibmc.memcached.PyLibMCCache',
        'LOCATION': '127.0.0.1:11211',
    },
    'locmem': {
        'BACKEND': 'django.core.cache.backends.locmem.LocMemCache',
    },
}
COMPRESS_CACHE_BACKEND = 'locmem'

Is there anything else I can check or does someone maybe have any idea what went wrong with the upgrade?
Just let me know if you need more info on config :v:

2

The MySQL error has been seen before. Does this post help at all?

3

Hi

Thanks! Haven’t stumbled upon this post, but then again, I didn’t look particularly for that warning.

Running mysql Ver 15.1 Distrib 10.3.39-MariaDB.

I did the steps there and now the tables looks like this which should be the same as in the other post:

image
image1184×338 13.9 KB

But I still get the internal Server error. Would it make sense to rerun the upgrade AFTER correcting the DB? (I could revert to a snapshot)

4

Yes, I would roll back to v.10 if it is convenient to do so.

If I remember correctly the upgrade from 10 to 11 was a bit “tweaky” (at least in my case). Secondly, the MySQL issue was only a Warning and I do not recall that it was service-affecting. In any event, in my opinion, it’s best not to leave those holes to fester and possibly create problems later.

Back to the upgrade: The biggest step in preparation involved the dependencies:

sudo apt-get update
sudo apt-get install -y python3 python3-dev python3-setuptools python3-pip libmysqlclient-dev ldap-utils libldap2-dev
sudo apt-get install -y memcached libmemcached-dev
sudo pip3 install --timeout=3600 django==3.2.* future==0.18.* mysqlclient==2.1.*
pymysql pillow==10.0.* pylibmc captcha==0.4 markupsafe==2.0.1 jinja2 sqlalchemy==2.0.18
psd-tools django-pylibmc django_simple_captcha==0.5.* djangosaml2==1.5.* pysaml2==7.2.* pycryptodome==3.16.* cffi==1.15.1 lxml python-ldap==3.4.3

Since you might be “peeling an onion” here, can you take a look at Mitch’s post and run down the list of items to check in the upgrade process? Daniel Pan also lists the “official” dependencies here.

As a side bar, assuming you revert to v.10.0.1, I simply do not know if it is safe to do the whole upgrade to 11.0.12 in one fell swoop. I am in the habit of doing Seafile upgrades incrementally. I will have to leave the issue of a large jump to another commenter or post on this forum.

I hope this helps. Good luck!

5

Alright I did a rollback and fixed the table beforehand. I had the files for 11.0.5 from an earlier try still on the server and did the upgrade with that but I still get get the Internal Server error. Also after doing a minor upgrade with 11.0.12 afterwards didn’t change that.

I think I have all the dependencies matched as mentioned in the upgrade guide as well. I might try to update my Ubuntu from 20.04 to 22.04 first and then try it with Seafile again, maybe the newer Python helps. :sweat_smile:

6

Success! :wink:

I upgraded to Ubuntu 22.04. It threw out most of the Python packages but I installed all the prerequisite Python packages from the upgrade guide, incl. ‘django_pylibmc’, which was still missing afterwards.

But now its working with 11.0.12. So I assume I may have had some strange state with Python before…

(Also switched to Nginx as ReverseProxy from apache2 while I was at it because of the Django CSRF Stuff :smiley:)

7

For future reference, and future readers, where do you feel the biggest turning point was? Any sense of what the key takeaways are in this upgrade?

Glad to hear you’re up and running again.

8

Honestly I can’t pinpoint it 100%. As I said I think it was probably the state of the Python installation on the machine, maybe along with other OS-dependencies (although 20.04 should be supported for Seaf 11).