[SOLVED] Upgrade PRO 7.0.13 - PRO 7.1.4 failed: 'Failed to execute sql'

CentOS7 - upto date - no docker

Running the update according to the release notes:

[https://download.seafile.com/published/seafile-manual/upgrade/upgrade_notes_for_7.1.x.md]

Full error output:

[root@caipirinha seafile-pro-server-7.1.4]# upgrade/upgrade_7.0_7.1.sh


This script would upgrade your seafile server from 7.0 to 7.1
Press [ENTER] to contiune

ln: failed to create symbolic link ‘/opt/seafile/seafile-data/seafile-data’: File exists
Created the symlink /opt/seafile/seafile-data for /data/seafile-data.

renaming the gunicorn.conf to gunicorn.conf.py …

Done

Updating seafile/seahub database …

[INFO] You are using MySQL
[INFO] updating seahub database…
/opt/seafile/seafile-pro-server-7.1.4/seahub/thirdpart/pymysql/cursors.py:170: Warning: (1050, “Table ‘base_reposecretkey’ already exists”)
result = self._query(query)
[WARNING] Failed to execute sql: (1054, “Unknown column ‘key’ in ‘constance_config’”)
[WARNING] Failed to execute sql: (1061, “Duplicate key name ‘drafts_draft_origin_repo_id_8978ca2c’”)
/opt/seafile/seafile-pro-server-7.1.4/seahub/thirdpart/pymysql/cursors.py:170: Warning: (1050, “Table ‘file_participants_fileparticipant’ already exists”)
result = self._query(query)
/opt/seafile/seafile-pro-server-7.1.4/seahub/thirdpart/pymysql/cursors.py:170: Warning: (1050, “Table ‘repo_api_tokens’ already exists”)
result = self._query(query)
/opt/seafile/seafile-pro-server-7.1.4/seahub/thirdpart/pymysql/cursors.py:170: Warning: (1050, “Table ‘abuse_reports_abusereport’ already exists”)
result = self._query(query)
/opt/seafile/seafile-pro-server-7.1.4/seahub/thirdpart/pymysql/cursors.py:170: Warning: (1050, “Table ‘repo_share_invitation’ already exists”)
result = self._query(query)
[WARNING] Failed to execute sql: (1060, “Duplicate column name ‘headers’”)
Done

migrating avatars …

Done

updating /opt/seafile/seafile-server-latest symbolic link to /opt/seafile/seafile-pro-server-7.1.4 …


Upgraded your seafile server successfully.

[root@caipirinha seafile-pro-server-7.1.4]# rm -rf /tmp/seahub_cache
[root@caipirinha seafile-pro-server-7.1.4]# systemctl start seafile
[root@caipirinha seafile-pro-server-7.1.4]# systemctl start seahub

journal -xe:

[root@caipirinha seafile-pro-server-7.1.4]# journalctl -xe

Jun 06 16:06:36 caipirinha.dacostaclub.com seahub.sh[31831]: Seahub is started
Jun 06 16:06:36 caipirinha.dacostaclub.com seahub.sh[31831]: Done.
Jun 06 16:06:36 caipirinha.dacostaclub.com systemd[1]: Started Seafile hub.
– Subject: Unit seahub.service has finished start-up
– Defined-By: systemd
– Support: systemd-devel Info Page

– Unit seahub.service has finished starting up.

– The start-up result is done.
Jun 06 16:06:36 caipirinha.dacostaclub.com polkitd[789]: Unregistered Authentication Agent for unix-process:31825:11653532 (system bus name :1.1374, object path /org/freedeskt

When I try to login now:

Webclient is giving me:

Page unavailable
Sorry, but the requested page is unavailable due to a server hiccup.

Our engineers have been notified, so check back later.

Client on (fedora 31) laptop is showing a rotating wheel

Client on phone is showing a rotating wheel and the message:

‘The folder ‘/’ was deleted’

Although I have a backup, I am a bit nervous for my data. What can I do to get a step further in the troubleshooting?

Mads

Inspired by the lines:

ln: failed to create symbolic link ‘/opt/seafile/seafile-data/seafile-data’: File exists
Created the symlink /opt/seafile/seafile-data for /data/seafile-data.

I stopped seafile and seahub, ran:

seafile-server-latest/seaf-fsck.sh --repair

on all libraries, restarted seafile and seahub.

After that everything worked again.

Fixed…