yah, no worries. I’m not in a hurry, data is getting sent to the cloud, so this isn’t causing me issue.
thanks for a great product.
b
1 Like
Hello briansheets,
I’m happy to report that this issue should not cause you any more problems with the latest Shake OS v0.21.2 update.
The system now properly handles 172.17... subnets.
Thank you again for notifying us about this!
ok, still having the issue, any action required on my part?
You can check whether the System Version displayed on rs.local/ is 0.21.2.
If not, it means that the automatic update has not yet reached your Shake. To manually update it, all you need to do is reboot the Shake and it will self-update.
If the issue persists after that, please download the new logs and send them to us. We’ll review them and see what’s going on.
Thank you.
can I get the version from the shell?
nm, found the upgrade.log,
2026 084 14:28:31: Checking for software updates…
2026 084 14:28:31: Updating rsh-SW-updater
2026 084 14:28:37: Shake-OS is up to date (ver 0.21)
2026 084 14:28:38: Installing ver 0.21.2 of the R-Shake system…
2026 084 14:28:39: Patch level 2 for ver 0.21 is already installed, nothing to do, exiting …
2026 084 14:28:39: Upgrade to version 22 failed, not continuing
2026 084 14:28:39: Updating Docker image registry.gitlab.com/rshake-public/rsh-fe-config:v21.2
2026 084 14:28:49: Updating Docker image registry.gitlab.com/rshake-public/rsh-data-producer
2026 084 14:28:55: Updating Docker image registry.gitlab.com/rshake-public/rsh-data-consumer
2026 084 14:29:00: Software updates complete.
Yes, you can also see it from the shell as you have done.
It appears your Shake is already updated to v0.21.2, so could you please tar the entire /opt/log/ folder and send the resulting file?
Thank you.
log.tgz (206.0 KB)
Hello, and thank you for the logs!
I’ve sent you an email at your forum address with more details and further steps, so we can continue there.
Thank you again.
A post was split to a new topic: No connection to Shake?