Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: attempting to upgrade from an incompatible database version references nonexistent docs #1854

Closed
2 tasks done
classabbyamp opened this issue Dec 31, 2024 · 3 comments
Closed
2 tasks done
Labels
bug Something isn't working

Comments

@classabbyamp
Copy link

⚠️ This issue respects the following points: ⚠️

  • This is a bug, not a question or a configuration issue.
  • This issue is not already reported on Github (I've searched it).

Bug description

2022-08-18T17:23:16.499 ERR database version 14 is too old, please see the upgrading docs

messages like this happen if upgrading from an old-enough version of sftpgo, but it seems that the "upgrading docs" no longer exist. I can't find them on https://docs.sftpgo.com and they no longer exist in the readme, as some links scattered through this repo's issues reference.

Steps to reproduce

  1. create an sftpgo database on an old version
  2. upgrade
  3. see error message

Expected behavior

docs on upgrading exist

SFTPGo version

2.6.4

Data provider

sqlite

Installation method

Other

Configuration

any configuration

Relevant log output

No response

What are you using SFTPGo for?

Private user, home usecase (home backup/VPS)

Additional info

any installation method applies here

@classabbyamp classabbyamp added the bug Something isn't working label Dec 31, 2024
@drakkan
Copy link
Owner

drakkan commented Dec 31, 2024

Upgrading docs: https://docs.sftpgo.com/latest/data-provider/#upgrading

Thanks for your contribution to the Void package, I hope it will be maintained better in the future.

@classabbyamp
Copy link
Author

ah I missed that. Would it be possible to add that URL to the error message?


we use sftpgo on Void for a developer file store (public interface), and we don't always upgrade our infra often, so sometimes the package may lag behind a little.

I was able to update from 2.3 to 2.6 by building a container with a version of sftpgo from 2.4.x, 2.5.x, and 2.6.x, and running initprovider on each version, so I guess I figured it out correctly without the docs.

@drakkan
Copy link
Owner

drakkan commented Dec 31, 2024

ah I missed that. Would it be possible to add that URL to the error message?

The location of the documents should not change in the future, so I think it is a good idea to add the link and now that the documents are hosted on a domain we control we can easily create a redirect if needed

we use sftpgo on Void for a developer file store (public interface), and we don't always upgrade our infra often, so sometimes the package may lag behind a little.

Thanks for sharing. Glad SFTPGo is useful for Void.

You have been exposed to well known vulnerabilities, such as Terrapin, for about 1 year

https://terrapin-attack.com/
https://nvd.nist.gov/vuln/detail/cve-2023-48795

and if I remember correctly, something similar happened before the update to version 2.5.4.
From time to time I check the SFTPGo packages available here and I see that Void is constantly outdated

I was able to update from 2.3 to 2.6 by building a container with a version of sftpgo from 2.4.x, 2.5.x, and 2.6.x, and running initprovider on each version, so I guess I figured it out correctly without the docs.

drakkan added a commit that referenced this issue Dec 31, 2024
Fixes #1854

Signed-off-by: Nicola Murino <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants