Hi, I have a device on an application that will not update currently. It was tagged to a prior release and after updating it to the current one the device never updated.
I had fixed this previously by temporarily moving the device to a different application and then moving it back, however, this method did not work.
Are there any methods for forcing a device to update? I’m guessing that some sort of lock is in place that is preventing the device from updating.
Hi Duncan, there aren’t any methods to force a device to update, so let’s just see what’s causing this as it is unexpected behavior. To start with, did you try looking at the journalctl logs in the host app? What services are you running on the device? Is it possible that there is a service that declines to quit after you try stopping/restarting it? Do you see this only on a single device, or the same behavior is on any device you try to update? Once we have all of this information we can look further into it.
Thanks for the reply. From the journalctl log I’ve seen the following errors:
Mar 23 15:23:34 f653dbd 5705d701e18d[784]: (node:1) UnhandledPromiseRejectionWarning: Error: Unhealthy
Mar 23 15:23:34 f653dbd resin-supervisor[1585]: (node:1) UnhandledPromiseRejectionWarning: Error: Unhealthy
Mar 23 15:23:34 f653dbd resin-supervisor[1585]: at e.<anonymous> (/usr/src/app/dist/app.js:594:33355)
Mar 23 15:23:34 f653dbd resin-supervisor[1585]: at /usr/src/app/dist/app.js:594:32452
Mar 23 15:23:34 f653dbd resin-supervisor[1585]: at Object.next (/usr/src/app/dist/app.js:594:32557)
Mar 23 15:23:34 f653dbd resin-supervisor[1585]: at o (/usr/src/app/dist/app.js:594:31274)
Mar 23 15:23:34 f653dbd resin-supervisor[1585]: (node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, >
Mar 23 15:23:34 f653dbd 5705d701e18d[784]: at e.<anonymous> (/usr/src/app/dist/app.js:594:33355)
Mar 23 15:23:34 f653dbd 5705d701e18d[784]: at /usr/src/app/dist/app.js:594:32452
Mar 23 15:23:34 f653dbd 5705d701e18d[784]: at Object.next (/usr/src/app/dist/app.js:594:32557)
Mar 23 15:23:34 f653dbd 5705d701e18d[784]: at o (/usr/src/app/dist/app.js:594:31274)
Mar 23 15:23:34 f653dbd 5705d701e18d[784]: (node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by>
Mar 23 15:24:04 f653dbd balenad[784]: time="2020-03-23T15:24:04.002333236Z" level=warning msg="Health check for container 5705d701e18d171fbb0e09c7765ecf6291c6d67e642cfabdb334d38cd84cae8f error: context deadline e>
Mar 23 15:24:04 f653dbd balenad[784]: time="2020-03-23T15:24:04.047956736Z" level=info msg="Unhealthy container 5705d701e18d171fbb0e09c7765ecf6291c6d67e642cfabdb334d38cd84cae8f: restarting..."
Mar 23 15:25:00 f653dbd sh[3191]: No supervisor configuration found from API or required variables not set. Using arguments for image and tag.
Could any of these errors be preventing the device from updating?
The device is running a Python application that uses tkinter, there’s also a pigpio daemon that is running in the container as well.
I see this only on a single device, I was able to update another device with no issues, but this device never updated to the new image.
Hi @lowderd,
Yes, this definitely looks like an issue that could cause an issue with updating, as it appears that the Supervisor container is unhealthy. Would it be possible to provide the UUID of the device (or the full dashboard URL for it) and grant support access? We’d like to have a look if possible, to characterise the issue and clean it up for you so it can update.
If you’d prefer to keep it private, feel free to DM me, and I’ll deal with it from there!
Best regards,
Heds