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

Package Repository - Reset / Cleanup #218

Open
andrboot opened this issue Jan 28, 2016 · 3 comments
Open

Package Repository - Reset / Cleanup #218

andrboot opened this issue Jan 28, 2016 · 3 comments

Comments

@andrboot
Copy link

Hi,
Is there a way to clean up old packages, or reset/remove the current packages downloaded in vFense?
Sitting on around 22GB of packages now, 80% of them I know are old patches, are no longer needed.

@linuxdynasty
Copy link

You can remove them, if you know which ones are no longer needed. The only issue I can see happening, is that you want to install a patch on a machine and that patch is no longer available on the vFense server.

@andrboot
Copy link
Author

Is it possible to reset the package part of the database so that it can be forced to re-download packages it needs?

@andrboot
Copy link
Author

Hi,
I have worked it out, not the best scenario but it works :).
Note - This will essentially delete all your current history for installed applications, and force your server once the clients have refreshed their apps to re-download any outstanding patches.
Essentially the following:

  1. Stop vFense.
  2. Export the rethinkdb to json files, (rethink-export)
  3. In the exported folder remove the following json files -
    . * Files.json
    • apps_per_agent.json
  4. Stop the rethinkDB.
  5. Remove/Move the rethinkdb from the current location.
  6. Remove/Move the packages folder (/opt/TopPatch/var/packages/)
  7. Start the rethinkDB.
  8. Import the cleaned up folder, e.g. rethinkdb-import -d rethinkdb_export_timedatestamp
  9. Start up vFense
  10. Manually refresh agents, or wait patiently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants