The Collector is Not Upgrading Itself

  • 7020681
  • 04-Feb-2016
  • 30-Aug-2017

Environment

Reload 5

Situation

The server was upgraded but the collectors have not.

Resolution

There is an upgrade cycle where the collector checks for an upgrade on the Reload server when a job begins.

When the Reload server is upgraded it dumps the upgrade rpm in

/reload/[POprofile]/gre_data/sync/gre_data/proc/upgrade

When a backup job runs the collector uses rsync to check for an rpm upgrade file. If it does it transfers the rpm to

/opt/beginfinite/reload/upgrade

If successful the collector upgrades itself, then corrupts of the rpm on the Reload server so it can’t upgrade again. The Reload server will check the rpm for corruption and if it is, deletes the corrupt rpm since the upgrade has been completed.

Things to check are:

  • Does the upgrade directory exist
  • Is the rpm is there and uncorrupted
  • Can the collector rsync to the server and download the upgrade

Additional Information

This article was originally published in the GWAVA knowledgebase as article ID 2722.