|
|
@@ -115,6 +115,15 @@ To upgrade VMRay: You should be able to safely run this at any time (still, foll
|
|
|
## Handling Failed Upgrades
|
|
|
If the upgrade fails, check `/usr/local/src/vmray-x.y.z/install.log` to find the reason. After fixing, delete the tarballs, zips, and directories for vmray and extended-kvm from `/usr/local/src/` on the vmray servers, and then rerun the state.
|
|
|
|
|
|
+## Permissions after upgrade
|
|
|
+
|
|
|
+Sometimes after upgrades we get an error. A triangle with an exclamation point will display in the new analysis. If you hover over this symbol, an error message will appear, such as "Post processing error Error during post processing: report_engine_result.json not found (possible crash).". This has usually been due to permissions issues.
|
|
|
+
|
|
|
+To fix, run from the salt master:
|
|
|
+```
|
|
|
+salt vmray\* cmd.run 'find /opt/vmray -type f -exec chmod g+r,o+r {} \;; find /opt/vmray -type d -exec chmod g+rx,o+rx {} \;; chown -R vmray:vmray /opt/vmray; find /opt/vmray -perm 0777 -type f -exec chmod 755 {} \;'
|
|
|
+```
|
|
|
+
|
|
|
## Backups
|
|
|
|
|
|
A script `/usr/local/bin/xdr-vmray-backups.sh` backs the system up to a bucket named `xdr-<ENV>-vmray-backups`. The bucket has folders for the server name. For server nodes, the script uses the VMRay distribution's backup script. For workers and combined servers, ISO's are backed up to /iso and vm images are backed up into the vms subfolder.
|
Fred Damstra [afs macbook]