Update to 6.0.2 Professional fails

So. I did the update to 6.0.2 on the pro version of seafile.

Now nginx gives me a 502 and nginx rrror log is giving me the below.

[error] 624#0: *86639 open() “/opt/seafile/seafile-server-latest/seahub/media/CACHE/css/c8340f180c0b.css” failed (2: No such file or directory)

An ls of the directory shows.
drwxrwxr-x 4 seafile nogroup 4096 Oct 17 00:34 .
drwxrwxr-x 7 seafile nogroup 4096 Oct 17 00:34 …
-rw-rw-r-- 1 seafile nogroup 5283 Oct 17 00:34 build.47e68614daea.txt
-rw-rw-r-- 1 seafile nogroup 145 Oct 17 00:34 build.d9508a510082.js
-rw-rw-r-- 1 seafile nogroup 145 Oct 17 00:34 build.js
-rw-rw-r-- 1 seafile nogroup 5283 Oct 17 00:34 build.txt
drwxrwxr-x 28 seafile nogroup 4096 Oct 17 00:34 i18n
drwxrwxr-x 2 seafile nogroup 4096 Oct 17 00:34 lib
-rw-rw-r-- 1 seafile nogroup 678015 Oct 17 00:34 main.b3772c306948.js
-rw-rw-r-- 1 seafile nogroup 678015 Oct 17 00:34 main.js
-rw-rw-r-- 1 seafile nogroup 468438 Oct 17 00:34 sysadmin-main.eab63cbc22f8.js
-rw-rw-r-- 1 seafile nogroup 468438 Oct 17 00:34 sysadmin-main.js

What do?

So I can start directly - seafile.sh start seahub.sh start. I’ll check the startup script. It must refer to the actual seafile folder instead of the symlink. This - I can handle…

So the option specifying the port number at the end of my systemd startup line is no longer necessary in 6.0.2 but worked fine in 6.0.1…

ExecStart=${seafile_dir}/seafile-server-latest/seahub.sh fast-cgi 8000 was not working but
ExecStart=${seafile_dir}/seafile-server-latest/seahub.sh fast-cgi does work.

the cache file ‘media/CACHE/css/c8340f180c0b.css’ was created when you access the front manage page first time, it was overrider when you upgraded. and the front manage page , which was cached as well, still refer the cached file.
so you should delete the cached front page in ‘/tmp’ .