At the moment, I am working on transferring user data from version 6.3.4 of the Community Edition of Seafile to version 9.0.10, which has been dockerized. I have successfully transferred the user database, and I am able to use my old server credentials to log in to the new dockerized server. However, I am not able to access any of my data on the new server.
To transfer the data, I followed these steps:
- On the old server, I located the data path at /opt/seafile-data/seafile.
- On the new server, I also located the data path at /opt/seafile/seafile-data/seafile-data.
- I identified my user repository ID as “6978bdc0-f0a9-4599-9cbe-ac7f6abae264” on the old server, and then copied it from /opt/seafile/seafile-data/seafile-data to the new server.
Despite successfully logging in to the new server, I am not able to access any of my data. Whenever I click on any library on the new docker server, I receive an error in the Seafile log file:
“2023-03-09 17:30:23 …/common/seaf-db.c(781): Failed to prepare sql SELECT o.repo_id, s.size, b.commit_id, i.name, i.update_time, i.version, i.is_encrypted, i.last_modifier, i.status FROM RepoOwner o LEFT JOIN RepoSize s ON o.repo_id = s.repo_id LEFT JOIN Branch b ON o.repo_id = b.repo_id LEFT JOIN RepoInfo i ON o.repo_id = i.repo_id WHERE owner_id=? AND o.repo_id NOT IN (SELECT v.repo_id FROM VirtualRepo v) ORDER BY i.update_time DESC, o.repo_id: Unknown column ‘i.status’ in ‘field list’”.
If anyone has any suggestions related to this issue, please let me know.