devices are having this issue after I pushed an update:
Failed to download application ‘registry2.resin.io/enpunto/…’ due to ‘rsync exited. code: 12 signal: null’
Devices are on multiple network so it is not an internet connection related issue.
Hi @diegosucaria
What supervisor and OS versions are your devices running? We’ve seen similar bugs in the past and fixed them in newer supervisor versions, but there might be other edge cases that still lead to a scenario like this.
In any case, you can work around the issue temporarily by disabling deltas (RESIN_SUPERVISOR_DELTA = 0 in your fleet configuration) so that devices download the image with a regular docker pull.
Glad to hear. We have a few fixes for deltas in progress that should make this errors less likely. After the devices finish the download, you can turn deltas back on - if you hit this error again please let us know so that we can do a deeper dive (it will probably involve us taking a look into what’s going on in the devices).
We are experiencing some issues with the delta server at the moment. Unfortunately this isn’t currently reflected by the status page as we don’t have a separate item for that, but we are working on getting the status page and the delta server fixed as soon as possible!
@jeff is that a development device? Do you mind if I stop your application for a bit while I’m looking into it? Do you have network bandwidth limitations (eg. cellular)?
The device is fixed now and runs the latest commit.
I updated the device to the latest Supervisor (v6.3.5). That version is more resilient when applying deltas and can better identify and recover from rsync errors like the one you were seeing. code: 2 suggests the source does not match the source used for generating the delta. This could be due to SD card corruption BTW, and the fact it’s super-slow suggests you might want to use a better card
Hi Jeff, sorry, currently the supervisor needs to be updated from our end. I’ve seen that you have a handful of 2.4.2+rev1 devices right? On those we’ve marked the supervisor to update to v6.3.5. That update will automatically happen within the next 24h (the device checks in for an update once every 24h - you can speed this up by rebooting the device and then 15 minutes after reboot a check is performed, so it should update then).
Let’s see how this above works, and if you need any other devices to be updated just let us know!