[GH-ISSUE #334] Docker: No pending agent updates #215

Closed
opened 2026-03-02 02:14:34 +03:00 by kerem · 4 comments
Owner

Originally created by @gurhyj on GitHub (Mar 18, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/334

Docker: agents not updating from 1.4.7 to 1.4.9 or above inc 1.4.12. No pending action icon for any agent even if manually select update agent, via agents update. Uninstall of existing agent to 1.4.7 and install of 1.4.9 works but still did not update to 1.4.11. No Errors in debug log.

Have run prune database and remove orphaned actions.

Manually running winagent-v1.4.12 upgrades the agent.

Originally created by @gurhyj on GitHub (Mar 18, 2021). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/334 Docker: agents not updating from 1.4.7 to 1.4.9 or above inc 1.4.12. No **pending action icon** for any agent even if manually select update agent, via agents update. Uninstall of existing agent to 1.4.7 and install of 1.4.9 works but still did not update to 1.4.11. No Errors in debug log. Have run prune database and remove orphaned actions. Manually running winagent-v1.4.12 upgrades the agent.
kerem closed this issue 2026-03-02 02:14:34 +03:00
Author
Owner

@sadnub commented on GitHub (Mar 19, 2021):

Can you see if you can generate an agent update package manually? Go to Agent > Install Agent and do the generated exe. It should generate and download.

also no pending action will show if the agent is online and attempts to update. Maybe AV is catching it?

<!-- gh-comment-id:802931611 --> @sadnub commented on GitHub (Mar 19, 2021): Can you see if you can generate an agent update package manually? Go to Agent > Install Agent and do the generated exe. It should generate and download. also no pending action will show if the agent is online and attempts to update. Maybe AV is catching it?
Author
Owner

@wh1te909 commented on GitHub (Mar 19, 2021):

Just tested on a fresh docker install, not able to reproduce:

Installed agent v1.4.12 (which is an old agent atm, current is 1.4.13) and then manually did Agents > Update Agents > Select All > Update

dockerupdate1

See screenshot above, it will actually create a pending action entry for the agent even if it's online, I added this recently.
Since agent was online it immediately received the update command, did the update and then around 30 seconds later, pending action is gone cuz it was completed:

dockerupdate2

Please try a fresh docker install and let us know if issue still occurs, if so please see the new github issue template and fill it out. Thanks

<!-- gh-comment-id:803166196 --> @wh1te909 commented on GitHub (Mar 19, 2021): Just tested on a fresh docker install, not able to reproduce: Installed agent v1.4.12 (which is an old agent atm, current is 1.4.13) and then manually did Agents > Update Agents > Select All > Update ![dockerupdate1](https://user-images.githubusercontent.com/7434746/111847377-ea8d5d80-88c5-11eb-897a-4f0a1ad4f16b.PNG) See screenshot above, it will actually create a pending action entry for the agent even if it's online, I added this recently. Since agent was online it immediately received the update command, did the update and then around 30 seconds later, pending action is gone cuz it was completed: ![dockerupdate2](https://user-images.githubusercontent.com/7434746/111847510-304a2600-88c6-11eb-90c9-0e98caf1ca20.PNG) Please try a fresh docker install and let us know if issue still occurs, if so please see the new github issue template and fill it out. Thanks
Author
Owner

@gurhyj commented on GitHub (Mar 19, 2021):

Will do I was just getting the following

image

<!-- gh-comment-id:803169051 --> @gurhyj commented on GitHub (Mar 19, 2021): Will do I was just getting the following ![image](https://user-images.githubusercontent.com/66262183/111848048-0f9fc180-8902-11eb-911d-9847c3e310a1.png)
Author
Owner

@wh1te909 commented on GitHub (Mar 22, 2021):

Hi this should be fixed now in latest release 0.4.28, turns out were some issues with background tasks not working in docker. Only affected older installs though not fresh installs.

<!-- gh-comment-id:804385853 --> @wh1te909 commented on GitHub (Mar 22, 2021): Hi this should be fixed now in latest release 0.4.28, turns out were some issues with background tasks not working in docker. Only affected older installs though not fresh installs.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/tacticalrmm#215
No description provided.