Removed delay in updater script for non-interactive runs from install scripts. (#9589)
* Add proper handling for updater script in installers. Our updater script has a built-in random delay of up to 1 hour when run non-interactively to avoid a stampede effect for reconnections to Netdata Cloud due to auto-updates. Due to an oversight in handling of updates to existing installs in the installer scripts, this delay was also occuring when the installer scripts were run non-interactively. This commit fixes that so that non-interactive runs complete without a delay. * Update checksums in documentation.
Austin S. Hemmelgarn committed
Jul 23, 2020 at 07:14 UTC
f32713e9dba0da659e6d154e61dcd13fcb3fec52
4 files changed
+4
-4
packaging/installer/kickstart-static64.sh
+1
-1
@@ -200,7 +200,7 @@ if [ -n "$ndpath" ] ; then
200
if [ -r "${ndprefix}/etc/netdata/.environment" ] ; then
201
if [ -x "${ndprefix}/usr/libexec/netdata/netdata-updater.sh" ] ; then
202
progress "Attempting to update existing install instead of creating a new one"
203
- if run ${sudo} "${ndprefix}/usr/libexec/netdata/netdata-updater.sh" ; then
203
+ if run ${sudo} "${ndprefix}/usr/libexec/netdata/netdata-updater.sh" --not-running-from-cron ; then
204
progress "Updated existing install at ${ndpath}"
205
exit 0
206
else
packaging/installer/kickstart.sh
+1
-1
@@ -298,7 +298,7 @@ if [ -n "$ndpath" ] ; then
298
if [ -r "${ndprefix}/etc/netdata/.environment" ] ; then
299
if [ -x "${ndprefix}/usr/libexec/netdata/netdata-updater.sh" ] ; then
300
progress "Attempting to update existing install instead of creating a new one"
301
- if run ${sudo} "${ndprefix}/usr/libexec/netdata/netdata-updater.sh" ; then
301
+ if run ${sudo} "${ndprefix}/usr/libexec/netdata/netdata-updater.sh" --not-running-from-cron ; then
302
progress "Updated existing install at ${ndpath}"
303
exit 0
304
else
packaging/installer/methods/kickstart-64.md
+1
-1
@@ -77,7 +77,7 @@ To use `md5sum` to verify the intregity of the `kickstart-static64.sh` script yo
77
command above, run the following:
78
79
```bash
80
-[ "f47630f78c0c5e651cb6788301d8e05c" = "$(curl -Ss https://my-netdata.io/kickstart-static64.sh | md5sum | cut -d ' ' -f 1)" ] && echo "OK, VALID" || echo "FAILED, INVALID"
80
+[ "6c3c2957caeeeb1decaf6b6178a3a3cd" = "$(curl -Ss https://my-netdata.io/kickstart-static64.sh | md5sum | cut -d ' ' -f 1)" ] && echo "OK, VALID" || echo "FAILED, INVALID"
81
```
82
83
If the script is valid, this command will return `OK, VALID`.
packaging/installer/methods/kickstart.md
+1
-1
@@ -58,7 +58,7 @@ To use `md5sum` to verify the intregity of the `kickstart.sh` script you will do
58
run the following:
59
60
```bash
61
-[ "05e3a23be90de1c2c62b2dbd8a3fb682" = "$(curl -Ss https://my-netdata.io/kickstart.sh | md5sum | cut -d ' ' -f 1)" ] && echo "OK, VALID" || echo "FAILED, INVALID"
61
+[ "86abaea95a24df12fe444c1b3e5cfa33" = "$(curl -Ss https://my-netdata.io/kickstart.sh | md5sum | cut -d ' ' -f 1)" ] && echo "OK, VALID" || echo "FAILED, INVALID"
62
```
63
64
If the script is valid, this command will return `OK, VALID`.