This is mostly a heads up / warning to those looking to upgrade to 7.1.3 at this time.
I did this upgrade earlier today , and the seahub service would not start. I read forum posts and tried the things in there but nothing I found helped. I looked in the log files and again nothing useful in there. I then tried restoring my database from backup and repointing the seafile-server-latest symbolic link back to 7.0.5 , but when I tried to start the server it fussed about the gunicorn.conf file being missing. I eventually just rolled back the entire system by recovering from backup. It may be that if I’d have had convenient access to gunicorn.conf without having to recover the entire vhdx file that this system is in would have fixed my problem. But either way - before you attempt this upgrade I would suggest that you
(a) make a tar or other file-level backup of your system that you can access (my are of the entire machine running on HyperV - or were, I’ll augmenting that going forward).
(b) specifically make sure you have that gunicorn.conf file before you do anything
This issue cost me a bunch of time today mostly because this release hasn’t matured enough in the forums to have a list of common failures and fixes.
Please plan accordingly as this was not as smooth of an upgrade as past Seafile upgrades have been for me.
My thanks to the Seafile developers is none the less - my appreciation for your product is still very high - thank you very much for the free software!