# Force balena supervisor poll check

**URL:** <https://forums.balena.io/t/force-balena-supervisor-poll-check/26041>\
**Category:** balenaOS\
**Created:** [August 20, 2019, 7:05pm UTC](https://forums.balena.io/t/force-balena-supervisor-poll-check/26041 "2019-08-20T19:05:31Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rubenm](https://avatars.discourse-cdn.com/v4/letter/r/7bcc69/32.png) [@rubenm](https://forums.balena.io/u/rubenm)\
**Post date:** [August 20, 2019, 7:05pm UTC](https://forums.balena.io/t/force-balena-supervisor-poll-check/26041/1 "2019-08-20T19:05:31Z")

</div>

Hello,  
We are running older versions of BalenaOS (Resin OS 2.9.7+rev4) and supervisor (6.6.0), and we usually encounter an issue when the host ends up with a double container when moved across applications.  
We can workaround this by removing the existing `/tmp/resin-supervisor/<containerid>/resin-supervisor.lock` from the host. However, the change is not immediate, and we have to wait for several minutes for the change to kick in, and then the issue is fixed.

I believe this waiting period is controlled by the variable `RESIN_SUPERVISOR_POLL_INTERVAL`, which is 15 minutes by default. My question is: without changing this variable, is there a way we can shorten the waiting length for this change to apply, or is there a way to “force” supervisor to update their containers when we remove the lockfiles? Unfortunately we cannot upgrade OS for our production fleet, so I’m looking for ways to just make the app migration more manageable by us

If you require more context I can gladly help you replicate the issue so you can observe and test

Thanks in advance

---

<div class="post-metadata">

**Author:** ![\_Page](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/_page/32/22_2.png) [@\_Page](https://forums.balena.io/u/_Page)\
**Post date:** [August 20, 2019, 7:48pm UTC](https://forums.balena.io/t/force-balena-supervisor-poll-check/26041/2 "2019-08-20T19:48:23Z")

</div>

You should be able to override the lock when triggering the update and the supervisor will apply the update immediately (and without the need for the manual lock removal): [https://www.balena.io/docs/learn/deploy/release-strategy/update-locking/#overriding-the-lock](https://www.balena.io/docs/learn/deploy/release-strategy/update-locking/#overriding-the-lock)

---

<div class="post-metadata">

**Author:** ![rubenm](https://avatars.discourse-cdn.com/v4/letter/r/7bcc69/32.png) [@rubenm](https://forums.balena.io/u/rubenm)\
**Post date:** [August 20, 2019, 11:28pm UTC](https://forums.balena.io/t/force-balena-supervisor-poll-check/26041/4 "2019-08-20T23:28:59Z")

</div>

I’ll try out the solution, many thanks!