01-31-2018, 02:35 PM
Hi BrendonKoz,
The fix for this was a patch rollout, not a point release. Therefore, if it fails one day, it'll self-remedy the next - so no worries. I built NEMS to be reliable and self-correcting.
To be sure, just type: sudo nems-update
If you see errors, let me know. If you don't, just follow the next step (Press "Save" on NEMS SST in this case, then restart either the Nagios service or reboot the NEMS Server).
Note that unlike nems-quickfix, nems-update shows the output of the update - hence why I say, you can do that if in doubt. Though if you already ran nems-quickfix and all is well, it is entirely redundant to run nems-update. :p
Let us know how it goes.
The fix for this was a patch rollout, not a point release. Therefore, if it fails one day, it'll self-remedy the next - so no worries. I built NEMS to be reliable and self-correcting.
To be sure, just type: sudo nems-update
If you see errors, let me know. If you don't, just follow the next step (Press "Save" on NEMS SST in this case, then restart either the Nagios service or reboot the NEMS Server).
Note that unlike nems-quickfix, nems-update shows the output of the update - hence why I say, you can do that if in doubt. Though if you already ran nems-quickfix and all is well, it is entirely redundant to run nems-update. :p
Let us know how it goes.
Robbie Ferguson // The Bald Nerd
Did I help you out? Appreciate what I do? Please consider saying thanks:
Did I help you out? Appreciate what I do? Please consider saying thanks:
- Throw something in the tip jar: https://donate.category5.tv
- Support Category5 TV on Patreon: https://patreon.com/category5
- Support NEMS Linux on Patreon: https://patreon.com/nems