Seahub stuck after Upgrade to 6.3.4

server

#1

Hello!

After upgrading Seafile Community Edition from 6.3.2 to 6.3.4 (Ubuntu 16.04.6) the Seahub frontend will not start: It is stuck with a completely empty white screen with the initial loading spinner. The console says:

Failed to load resource: the server responded with a status of 404 (Not Found) (main.js, line 0) http://myurl.xx/media/assets/scripts/app/main.js

There is a main.js file, but not in a “app” folder. Here is what I have in the “scripts” folder:

-rw-rw-r-- 1 51191 Sep 15 10:52 common.21a01cba175c.js
-rw-rw-r-- 1 51191 Sep 15 10:52 common.js
drwxrwxr-x 4 4096 Sep 15 10:52 dist
-rw-rw-r-- 1 8206 Sep 15 10:52 file-tree.ef19875b8f54.js
-rw-rw-r-- 1 8206 Sep 15 10:52 file-tree.js
drwxrwxr-x 33 4096 Sep 15 10:52 i18n
drwxrwxr-x 2 4096 Sep 15 10:52 lib
-rw-rw-r-- 1 153 Sep 15 10:52 main.ee715e56433e.js
-rw-rw-r-- 1 153 Sep 15 10:52 main.js
drwxrwxr-x 3 4096 Sep 15 10:52 orgadmin-app
-rw-rw-r-- 1 162 Sep 15 10:52 orgadmin-main.77b8ddcf76c8.js
-rw-rw-r-- 1 162 Sep 15 10:52 orgadmin-main.js
-rw-rw-r-- 1 20942 Sep 15 10:52 pinyin-by-unicode.8a45c2cfbafa.js
-rw-rw-r-- 1 20942 Sep 15 10:52 pinyin-by-unicode.js
-rw-rw-r-- 1 162 Sep 15 10:52 sysadmin-main.e14c688752f6.js
-rw-rw-r-- 1 162 Sep 15 10:52 sysadmin-main.js

Just creating the folder and copying the js inside results in even more missing js files.

I cannot find anything helpful in the logs. What can I do to clear this up? Any ideas?


#2

Did you change Seahub to WSGI mode?


#3

mod_wsgi is installed and enabled in my Apache2 and I added the snippet from here https://manual.seafile.com/changelog/server-changelog.html to my apache2.conf. Is there a way to check if Seafile is running in WSGI mode?

The problem seems to be that Seahub tries to get main.js from /media/assets/scripts/app/main.js, but there is no app folder, main.js is one level up in the scripts folder.

I guess the latest server package was downloaded and installed many times, so this cannot be an error in the package right? But what else causes this? Are these JS files and paths generated in some ways?

I am hopelessly lost here. Please help!


#4

Do you enable DEBUG mode in seahub_settings.py? If so, you should remove it.


#5

Of course I turned on the DEBUG mode. I wanted to find out what goes wrong!

Indeed, I turned it off the Seahub is loading normally. I never would have thought of the debug mode caused the problem. The debug mode should be there to solve problems. Very counter-intuitive … :frowning:

I now have more errors, the raw files are not accessible anymore, on /media/ or /seafile/. This seems to be a new error. I will have to look into that and maybe write a new post here.

Thanks a lot, daniel.pan! So great to have someone to talk to, when you are seriously stuck!