# Balena Current Release Not Installing Completely

**URL:** <https://forums.balena.io/t/balena-current-release-not-installing-completely/366185>\
**Category:** Product support\
**Created:** [December 24, 2022, 1:51am UTC](https://forums.balena.io/t/balena-current-release-not-installing-completely/366185 "2022-12-24T01:51:12Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![SMoore](https://avatars.discourse-cdn.com/v4/letter/s/c5a1d2/32.png) [@SMoore](https://forums.balena.io/u/SMoore)\
**Post date:** [December 24, 2022, 1:51am UTC](https://forums.balena.io/t/balena-current-release-not-installing-completely/366185/1 "2022-12-24T01:51:12Z")

</div>

I pinned a new “target release” on a couple of identically configured NUC’s. I have successfully performed this action many times over the last 2 years on these NUC’s.

One NUC installed perfectly & quickly. The other NUC did not, taking many hours to sort-of install with problems as detailed below.

Specifically, on the problem NUC’s Balena Dashboard:

- “current release” shows the old release
- “target release” shows the new release.
- services shows the new release (ie “target release”)

Also, two of the services “admin” and “fluent-bit” are stuck in “Installed” and never progress to “Running.”

Host OS:balenaOS 2.107.8+rev1  
Supervisor: 14.4.4

On the problem NUC, I’ve tried (with no resolution):  
-stopping all the services  
-restarting all the services  
-rebooting  
-updating to the latest supervisor and balena OS  
-re-pinning the target release multiple times

Is there some other action I could take?

Attached please find: screen shot of the Dashboard, health check, diagnostics.

Thanks,  
Sandy  
[Balena Release Incomplete 20221223 - Google Docs.pdf](https://forums.balena.io/uploads/short-url/vOkzgSBzO69c9BwUbqcI0LXCTUE.pdf) (53.5 KB)  
[Health\_check20221223\_fierce\_hill.pdf](https://forums.balena.io/uploads/short-url/cZIJPWqdFN8GRUoVL8N79Defd7X.pdf) (16.9 KB)  
[diagnostics20221223\_fierce\_Hill.pdf](https://forums.balena.io/uploads/short-url/kqNnRGGMurxYk4oz5vbk8VLlZOQ.pdf) (615.6 KB)

---

<div class="post-metadata">

**Author:** ![nitishagar](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/nitishagar/32/4967_2.png) [@nitishagar](https://forums.balena.io/u/nitishagar)\
**Post date:** [December 26, 2022, 2:15pm UTC](https://forums.balena.io/t/balena-current-release-not-installing-completely/366185/2 "2022-12-26T14:15:37Z")

</div>

Hi,

Can you check the `balena ps` to see if there are any container left over - as I can see a lot of errors relating to port binding in the logs you attached?

Specifically the port 80 bind error: `Bind for 0.0.0.0:80 failed: port is already allocated`  
Looks related to an open issue: [Port already in use, because proxy keeps binding to the wrong container IP · Issue #272 · balena-os/balena-engine · GitHub](https://github.com/balena-os/balena-engine/issues/272)

The above issue provides some of the steps as workaround. Let us know, if the above works and if we can help further debug and answer questions in the process.

Regards,  
Nitish

---

<div class="post-metadata">

**Author:** ![SMoore](https://avatars.discourse-cdn.com/v4/letter/s/c5a1d2/32.png) [@SMoore](https://forums.balena.io/u/SMoore)\
**Post date:** [December 27, 2022, 8:40pm UTC](https://forums.balena.io/t/balena-current-release-not-installing-completely/366185/4 "2022-12-27T20:40:10Z")

</div>

Hi, Nitish,  
Thanks for bringing this to my attention. I followed the steps from the previous linked issue and did not see any improvement. Perhaps I’m missing something critical?

Also Dashboard current release has not updated to target release, even though services show the target release.

Attachments are from after following the steps outlined below.

[20221227-HealthCheck-23217009bdacc06c967b41cf0ab1c97e\_checks\_2022.12.27\_19.44.54+0000.pdf](https://forums.balena.io/uploads/short-url/or4N6yAj9VTa5cgtaB4Zfrqspmw.pdf) (17.4 KB)

[20221227-Diagnostics-23217009bdacc06c967b41cf0ab1c97e\_diagnostics\_2022.12.27\_19.44.34+0000.pdf](https://forums.balena.io/uploads/short-url/e8D6JAXGJK7sbW0pcd5GBvhQ5Oy.pdf) (628 KB)

---

<div class="post-metadata">

**Author:** ![alanb128](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/alanb128/32/2839_2.png) [@alanb128](https://forums.balena.io/u/alanb128)\
**Post date:** [December 28, 2022, 1:28am UTC](https://forums.balena.io/t/balena-current-release-not-installing-completely/366185/5 "2022-12-28T01:28:06Z")

</div>

Hello Sandy, Just confirming you followed the more explicit steps in the comment further down in the linked issue, here is a direct link: [Port already in use, because proxy keeps binding to the wrong container IP · Issue #272 · balena-os/balena-engine · GitHub](https://github.com/balena-os/balena-engine/issues/272#issuecomment-940572026) ?

---

<div class="post-metadata">

**Author:** ![SMoore](https://avatars.discourse-cdn.com/v4/letter/s/c5a1d2/32.png) [@SMoore](https://forums.balena.io/u/SMoore)\
**Post date:** [December 28, 2022, 5:38pm UTC](https://forums.balena.io/t/balena-current-release-not-installing-completely/366185/6 "2022-12-28T17:38:04Z")

</div>

Alan,  
Here are the steps I followed from “Port already in use, because proxy keeps binding to the wrong container IP - Issue #272”

- `ip link delete supervisor0`
- `balena rm --force $(balena ps -aq)`
- `balena network prune -f`
- `systemctl restart balena`  
These steps & the results from following these steps are documented in my previous email.

Let me know if I should be doing other steps etc.  
Thanks,  
Sandy

---

<div class="post-metadata">

**Author:** ![alanb128](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/alanb128/32/2839_2.png) [@alanb128](https://forums.balena.io/u/alanb128)\
**Post date:** [December 30, 2022, 9:06pm UTC](https://forums.balena.io/t/balena-current-release-not-installing-completely/366185/7 "2022-12-30T21:06:32Z")

</div>

Hello Sandy, yes it looks like you followed the proper steps. We’ll take a look at the diagnostics you provided to see if we can troubleshoot further.

---

<div class="post-metadata">

**Author:** ![jaomaloy](https://avatars.discourse-cdn.com/v4/letter/j/3bc359/32.png) [@jaomaloy](https://forums.balena.io/u/jaomaloy)\
**Post date:** [January 3, 2023, 4:59am UTC](https://forums.balena.io/t/balena-current-release-not-installing-completely/366185/11 "2023-01-03T04:59:16Z")

</div>

Hi, could you try to kill the container (e.x `charger-ws_397845_553923`) and remove the app-specific bridged docker network (ie. named 123456\_blah)? Also, is this running on network mode host?

---

<div class="post-metadata">

**Author:** ![jaomaloy](https://avatars.discourse-cdn.com/v4/letter/j/3bc359/32.png) [@jaomaloy](https://forums.balena.io/u/jaomaloy)\
**Post date:** [July 27, 2023, 7:53am UTC](https://forums.balena.io/t/balena-current-release-not-installing-completely/366185/14 "2023-07-27T07:53:46Z")

</div>

Hi, did you have any updates regarding this?

---

<div class="post-metadata">

**Author:** ![SMoore](https://avatars.discourse-cdn.com/v4/letter/s/c5a1d2/32.png) [@SMoore](https://forums.balena.io/u/SMoore)\
**Post date:** [July 27, 2023, 3:27pm UTC](https://forums.balena.io/t/balena-current-release-not-installing-completely/366185/18 "2023-07-27T15:27:16Z")

</div>

Jao,  
Thanks for checking in. We have not seen a repeat of this activity.  
Sandy
