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] Config, past scans etc gone after update to latest #298

Open
markdesilva opened this issue Nov 13, 2021 · 3 comments
Open

[Bug] Config, past scans etc gone after update to latest #298

markdesilva opened this issue Nov 13, 2021 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@markdesilva
Copy link

Describe the bug
Upgraded to latest 21.4.3-v2 from 21.4.0, all configs and previous scan reports, etc are gone.

Using new volume env:
--volume ./storage/postgres-db:/opt/database
--volume ./storage/openvas-plugins:/var/lib/openvas/plugins
--volume ./storage/gvm:/var/lib/gvm
--volume ./storage/ssh:/etc/ssh

To Reproduce
Steps to reproduce the behavior:

  1. Start container with new volume envs
  2. Log into gvm
  3. No data, no scan configs, no past scans etc

Expected behavior
See all scan configs, past scans, etc.

Screenshots
NA

Host Device:

  • OS: Ubuntu
  • Version: 20.04.3

Image in use:

  • Self build? No
  • Output from docker image inspect <image> :
# docker image inspect <image> 

Additional context
Add any other context about the problem here.

@markdesilva markdesilva added the bug Something isn't working label Nov 13, 2021
@markdesilva
Copy link
Author

I'm probably doing something wrong. Previously all files were linked from gvm-data. I moved the relevant directories (plugins, database, etc) to under ./storage and ran the docker and I get this error:

2021-11-13 09:16:13,807 INFO exited: postgresql (exit status 1; not expected)

Do I need to upgrade from 21.4.0 to 21.4.2 and move my way to the latest?

@markdesilva markdesilva changed the title [Bug] [Bug] Config, past scans etc gone after update to latest Nov 13, 2021
@markdesilva
Copy link
Author

Found the postgres error logs.

2021-11-13 10:15:07.249 UTC [114] FATAL: database files are incompatible with server
2021-11-13 10:15:07.249 UTC [114] DETAIL: The data directory was initialized by PostgreSQL version 12, which is not compatible with this version 13.3.

How do I upgrade the database?

Thank you.

@markdesilva
Copy link
Author

Does this still work?

docker run --tty --rm --volume gvm-data:/data --name temp securecompliance/gvm:upgrade-database

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

3 participants