[GH-ISSUE #550] Agents do not auto-update #2293

Closed
opened 2026-03-14 03:26:46 +03:00 by kerem · 8 comments
Owner

Originally created by @tedtms on GitHub (Jun 1, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/550

Server Info:

  • OS: Ubuntu 20.04
  • Browser: Firefox
  • RMM Version: v0.6.9

Installation Method:

  • Standard
  • Docker

Agent Info:

  • Agent version: v1.4.13
  • Agent OS: Win 10 (various)

Describe the bug
Agents never automatically update. All have continuous pending actions to update the agent, which never execute. Due time comes around, nothing happens, then the due time advances. Additionally, nothing happens when executing a manual update via Agents > Update Agents

To Reproduce
Update the server installation and then check pending actions on the agents.

Expected behavior
Agents should auto-update when the due time occurs.

Additional context
RMM installation exists behind an nginx reverse proxy on another machine which is handling the certs and required me to set TlsOffload in the meshcentral configuration. I'm also using an external Postgres database.

Originally created by @tedtms on GitHub (Jun 1, 2021). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/550 **Server Info:** - OS: Ubuntu 20.04 - Browser: Firefox - RMM Version: v0.6.9 **Installation Method:** - [X] Standard - [ ] Docker **Agent Info:** - Agent version: v1.4.13 - Agent OS: Win 10 (various) **Describe the bug** Agents never automatically update. All have continuous pending actions to update the agent, which never execute. Due time comes around, nothing happens, then the due time advances. Additionally, nothing happens when executing a manual update via Agents > Update Agents **To Reproduce** Update the server installation and then check pending actions on the agents. **Expected behavior** Agents should auto-update when the due time occurs. **Additional context** RMM installation exists behind an nginx reverse proxy on another machine which is handling the certs and required me to set `TlsOffload` in the meshcentral configuration. I'm also using an external Postgres database.
kerem 2026-03-14 03:26:46 +03:00
  • closed this issue
  • added the
    question
    label
Author
Owner

@wh1te909 commented on GitHub (Jun 1, 2021):

it's probably AV, please see https://github.com/wh1te909/tacticalrmm/issues/485 and follow instructions there

<!-- gh-comment-id:852467115 --> @wh1te909 commented on GitHub (Jun 1, 2021): it's probably AV, please see https://github.com/wh1te909/tacticalrmm/issues/485 and follow instructions there
Author
Owner

@tedtms commented on GitHub (Jun 3, 2021):

So, I confirmed that all exceptions are entered correctly, and for testing purposes I even disabled AV. However, auto-update still doesn't execute. Logs never appear under C:\Windows\Temp\tacticalrmmXXXX

Following the thread on #485, I ran the manual update command, resulting in the following log:

2021-06-03 11:13:11.853   Log opened. (Time zone: UTC-04:00)
2021-06-03 11:13:11.853   Setup version: Inno Setup version 6.1.2
2021-06-03 11:13:11.853   Original Setup EXE: C:\Users\tsadler\Desktop\winagent-v1.5.7.exe
2021-06-03 11:13:11.853   Setup command line: /SL5="$608CA,3479240,824832,C:\Users\tsadler\Desktop\winagent-v1.5.7.exe" /SPAWNWND=$708BE /NOTIFYWND=$C0944 /VERYSILENT /LOG=agentupdate.txt
2021-06-03 11:13:11.853   Compatibility mode: Yes (DetectorsAppHealth Installer)
2021-06-03 11:13:11.853   Windows version: 10.0.19042  (NT platform: Yes)
2021-06-03 11:13:11.853   64-bit Windows: Yes
2021-06-03 11:13:11.853   Processor architecture: x64
2021-06-03 11:13:11.853   User privileges: Administrative
2021-06-03 11:13:11.853   Administrative install mode: Yes
2021-06-03 11:13:11.853   Install mode root key: HKEY_LOCAL_MACHINE
2021-06-03 11:13:11.853   64-bit install mode: No
2021-06-03 11:13:11.860   Created temporary directory: C:\Users\tsadler\AppData\Local\Temp\is-UVF2J.tmp
2021-06-03 11:13:14.044   Stop tacticalagent: 0
2021-06-03 11:13:16.342   Stop tacticalrpc: 0
2021-06-03 11:13:16.667   taskkill: 128
2021-06-03 11:13:17.090   Starting the installation process.
2021-06-03 11:13:17.090   Directory for uninstall files: C:\Program Files\TacticalAgent
2021-06-03 11:13:17.090   Will append to existing uninstall log: C:\Program Files\TacticalAgent\unins000.dat
2021-06-03 11:13:17.105   -- File entry --
2021-06-03 11:13:17.105   Dest filename: C:\Program Files\TacticalAgent\unins000.exe
2021-06-03 11:13:17.105   Time stamp of our file: 2021-06-03 11:13:11.490
2021-06-03 11:13:17.105   Dest file exists.
2021-06-03 11:13:17.105   Time stamp of existing file: 2021-04-26 10:30:53.864
2021-06-03 11:13:17.105   Version of our file: 51.1052.0.0
2021-06-03 11:13:17.121   Version of existing file: 51.1052.0.0
2021-06-03 11:13:17.121   Installing the file.
2021-06-03 11:13:17.121   Leaving temporary file in place for now.
2021-06-03 11:13:17.121   -- File entry --
2021-06-03 11:13:17.121   Dest filename: C:\Program Files\TacticalAgent\tacticalrmm.exe
2021-06-03 11:13:17.121   Time stamp of our file: 2021-05-28 21:59:30.000
2021-06-03 11:13:17.121   Dest file exists.
2021-06-03 11:13:17.121   Time stamp of existing file: 2021-03-18 22:09:58.000
2021-06-03 11:13:17.121   Installing the file.
2021-06-03 11:13:17.501   Successfully installed the file.
2021-06-03 11:13:17.501   -- File entry --
2021-06-03 11:13:17.501   Dest filename: C:\Program Files\TacticalAgent\nssm.exe
2021-06-03 11:13:17.501   Time stamp of our file: 2021-04-24 01:16:28.000
2021-06-03 11:13:17.501   Dest file exists.
2021-06-03 11:13:17.501   Time stamp of existing file: 2020-12-15 02:27:00.000
2021-06-03 11:13:17.501   Version of our file: 2.24.101.101
2021-06-03 11:13:17.501   Version of existing file: 2.24.101.101
2021-06-03 11:13:17.501   Same version. Skipping.
2021-06-03 11:13:17.501   -- Icon entry --
2021-06-03 11:13:17.501   Dest filename: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Tactical RMM Agent.lnk
2021-06-03 11:13:17.501   Creating the icon.
2021-06-03 11:13:17.622   Successfully created the icon.
2021-06-03 11:13:17.638   Saving uninstall information.
2021-06-03 11:13:17.638   Renaming uninstaller.
2021-06-03 11:13:17.638   Deleting uninstall key left over from previous administrative 32-bit install.
2021-06-03 11:13:17.638   Creating new uninstall key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\{0D34D278-5FAF-4159-A4A0-4E2D2C08139D}_is1
2021-06-03 11:13:17.638   Writing uninstall key values.
2021-06-03 11:13:17.638   Detected previous non administrative install? No
2021-06-03 11:13:17.638   Detected previous administrative 64-bit install? No
2021-06-03 11:13:17.638   Installation process succeeded.
2021-06-03 11:13:17.638   Need to restart Windows? No
2021-06-03 11:13:17.654   Deinitializing Setup.

And the agent was successfully updated. I have another machine that I can test on with AV disabled... do you have any other ideas what might be causing the auto-updates to fail?

<!-- gh-comment-id:853949207 --> @tedtms commented on GitHub (Jun 3, 2021): So, I confirmed that all exceptions are entered correctly, and for testing purposes I even disabled AV. However, auto-update still doesn't execute. Logs never appear under C:\Windows\Temp\tacticalrmmXXXX Following the thread on #485, I ran the manual update command, resulting in the following log: ``` 2021-06-03 11:13:11.853 Log opened. (Time zone: UTC-04:00) 2021-06-03 11:13:11.853 Setup version: Inno Setup version 6.1.2 2021-06-03 11:13:11.853 Original Setup EXE: C:\Users\tsadler\Desktop\winagent-v1.5.7.exe 2021-06-03 11:13:11.853 Setup command line: /SL5="$608CA,3479240,824832,C:\Users\tsadler\Desktop\winagent-v1.5.7.exe" /SPAWNWND=$708BE /NOTIFYWND=$C0944 /VERYSILENT /LOG=agentupdate.txt 2021-06-03 11:13:11.853 Compatibility mode: Yes (DetectorsAppHealth Installer) 2021-06-03 11:13:11.853 Windows version: 10.0.19042 (NT platform: Yes) 2021-06-03 11:13:11.853 64-bit Windows: Yes 2021-06-03 11:13:11.853 Processor architecture: x64 2021-06-03 11:13:11.853 User privileges: Administrative 2021-06-03 11:13:11.853 Administrative install mode: Yes 2021-06-03 11:13:11.853 Install mode root key: HKEY_LOCAL_MACHINE 2021-06-03 11:13:11.853 64-bit install mode: No 2021-06-03 11:13:11.860 Created temporary directory: C:\Users\tsadler\AppData\Local\Temp\is-UVF2J.tmp 2021-06-03 11:13:14.044 Stop tacticalagent: 0 2021-06-03 11:13:16.342 Stop tacticalrpc: 0 2021-06-03 11:13:16.667 taskkill: 128 2021-06-03 11:13:17.090 Starting the installation process. 2021-06-03 11:13:17.090 Directory for uninstall files: C:\Program Files\TacticalAgent 2021-06-03 11:13:17.090 Will append to existing uninstall log: C:\Program Files\TacticalAgent\unins000.dat 2021-06-03 11:13:17.105 -- File entry -- 2021-06-03 11:13:17.105 Dest filename: C:\Program Files\TacticalAgent\unins000.exe 2021-06-03 11:13:17.105 Time stamp of our file: 2021-06-03 11:13:11.490 2021-06-03 11:13:17.105 Dest file exists. 2021-06-03 11:13:17.105 Time stamp of existing file: 2021-04-26 10:30:53.864 2021-06-03 11:13:17.105 Version of our file: 51.1052.0.0 2021-06-03 11:13:17.121 Version of existing file: 51.1052.0.0 2021-06-03 11:13:17.121 Installing the file. 2021-06-03 11:13:17.121 Leaving temporary file in place for now. 2021-06-03 11:13:17.121 -- File entry -- 2021-06-03 11:13:17.121 Dest filename: C:\Program Files\TacticalAgent\tacticalrmm.exe 2021-06-03 11:13:17.121 Time stamp of our file: 2021-05-28 21:59:30.000 2021-06-03 11:13:17.121 Dest file exists. 2021-06-03 11:13:17.121 Time stamp of existing file: 2021-03-18 22:09:58.000 2021-06-03 11:13:17.121 Installing the file. 2021-06-03 11:13:17.501 Successfully installed the file. 2021-06-03 11:13:17.501 -- File entry -- 2021-06-03 11:13:17.501 Dest filename: C:\Program Files\TacticalAgent\nssm.exe 2021-06-03 11:13:17.501 Time stamp of our file: 2021-04-24 01:16:28.000 2021-06-03 11:13:17.501 Dest file exists. 2021-06-03 11:13:17.501 Time stamp of existing file: 2020-12-15 02:27:00.000 2021-06-03 11:13:17.501 Version of our file: 2.24.101.101 2021-06-03 11:13:17.501 Version of existing file: 2.24.101.101 2021-06-03 11:13:17.501 Same version. Skipping. 2021-06-03 11:13:17.501 -- Icon entry -- 2021-06-03 11:13:17.501 Dest filename: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Tactical RMM Agent.lnk 2021-06-03 11:13:17.501 Creating the icon. 2021-06-03 11:13:17.622 Successfully created the icon. 2021-06-03 11:13:17.638 Saving uninstall information. 2021-06-03 11:13:17.638 Renaming uninstaller. 2021-06-03 11:13:17.638 Deleting uninstall key left over from previous administrative 32-bit install. 2021-06-03 11:13:17.638 Creating new uninstall key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\{0D34D278-5FAF-4159-A4A0-4E2D2C08139D}_is1 2021-06-03 11:13:17.638 Writing uninstall key values. 2021-06-03 11:13:17.638 Detected previous non administrative install? No 2021-06-03 11:13:17.638 Detected previous administrative 64-bit install? No 2021-06-03 11:13:17.638 Installation process succeeded. 2021-06-03 11:13:17.638 Need to restart Windows? No 2021-06-03 11:13:17.654 Deinitializing Setup. ``` And the agent was successfully updated. I have another machine that I can test on with AV disabled... do you have any other ideas what might be causing the auto-updates to fail?
Author
Owner

@silversword411 commented on GitHub (Jun 8, 2021):

We were troubleshooting some win7x32 agent upgrade issues last night. We:

  1. Stop Tactical RPC service
  2. From admin command prompt ran "C:\Program Files\TacticalAgent\tacticalrmm.exe" -m rpc -log debug -logto stdout
  3. Agent | Update Agent | manually ran upgrade.

In the command we found

2021-06-08_154820 - agent upgrade debug2

Something was locking up the file, he's going to tweak the upgrade code to try and fix that. There was one that had 3 stuck agent upgrade's running in task manager. On the win7 I've seen MS Security Essentials not release file locks after scanning the file, not sure if that was it or not.

See if you find any other issues with that process.

<!-- gh-comment-id:857069238 --> @silversword411 commented on GitHub (Jun 8, 2021): We were troubleshooting some win7x32 agent upgrade issues last night. We: 1. Stop `Tactical RPC` service 2. From admin command prompt ran `"C:\Program Files\TacticalAgent\tacticalrmm.exe" -m rpc -log debug -logto stdout` 3. Agent | Update Agent | manually ran upgrade. In the command we found ![2021-06-08_154820 - agent upgrade debug2](https://user-images.githubusercontent.com/13395348/121248393-636ed680-c871-11eb-82ca-0f53abeeb6e9.png) Something was locking up the file, he's going to tweak the upgrade code to try and fix that. There was one that had 3 stuck agent upgrade's running in task manager. On the win7 I've seen MS Security Essentials not release file locks after scanning the file, not sure if that was it or not. See if you find any other issues with that process.
Author
Owner

@tedtms commented on GitHub (Jun 9, 2021):

@silversword411 On two machines, I disabled the service and ran tacticalrmm.exe in rpc mode with debug outputting to terminal using the command shown. However, when I manually update the agents in the RMM web interface, the debug output never provides anything. It's as if the agent is failing to receive the update command.

<!-- gh-comment-id:857632159 --> @tedtms commented on GitHub (Jun 9, 2021): @silversword411 On two machines, I disabled the service and ran tacticalrmm.exe in rpc mode with debug outputting to terminal using the command shown. However, when I manually update the agents in the RMM web interface, the debug output never provides anything. It's as if the agent is failing to receive the update command.
Author
Owner

@silversword411 commented on GitHub (Jun 9, 2021):

That sounds like networking/offline agent. Does the agent show as online from the admin interface?

<!-- gh-comment-id:857639520 --> @silversword411 commented on GitHub (Jun 9, 2021): That sounds like networking/offline agent. Does the agent show as online from the admin interface?
Author
Owner

@tedtms commented on GitHub (Jun 9, 2021):

Yep, the agent is online. However, in testing, various features of the RMM are hit-or-miss. For example, I can't remotely reboot the client using the right click actions menu, but I can browse the filesystem and execute remote terminal commands.

<!-- gh-comment-id:857642562 --> @tedtms commented on GitHub (Jun 9, 2021): Yep, the agent is online. However, in testing, various features of the RMM are hit-or-miss. For example, I can't remotely reboot the client using the right click actions menu, but I can browse the filesystem and execute remote terminal commands.
Author
Owner

@silversword411 commented on GitHub (Jun 9, 2021):

browse files system and remote terminal are mesh, not TRMM.

You tried the right-click menu of the individual agent | Agent Recovery and done # 2,3?

What are the dates of these?

2021-06-09_104258 - brave_Tactical_RMM_-_Brave

2021-06-09_104316 - brave_Tactical_RMM_-_Brave

<!-- gh-comment-id:857757201 --> @silversword411 commented on GitHub (Jun 9, 2021): browse files system and remote terminal are mesh, not TRMM. You tried the right-click menu of the individual agent | Agent Recovery and done # 2,3? What are the dates of these? ![2021-06-09_104258 - brave_Tactical_RMM_-_Brave](https://user-images.githubusercontent.com/13395348/121376473-8f409980-c90f-11eb-97d2-6a0f5c2c3c44.png) ![2021-06-09_104316 - brave_Tactical_RMM_-_Brave](https://user-images.githubusercontent.com/13395348/121376481-91a2f380-c90f-11eb-8925-26879216a461.png)
Author
Owner

@tedtms commented on GitHub (Jul 10, 2021):

Sorry for the delay on getting back to this -- I examined my system again and discovered that all of my mesh agents appear to be working but the RMM agents are not.

Unfortunately, I think Tactical (while a great project!) is not really a good fit for my environment anymore. But thanks for the help, and for building such a cool tool for the MSP community!

<!-- gh-comment-id:877559320 --> @tedtms commented on GitHub (Jul 10, 2021): Sorry for the delay on getting back to this -- I examined my system again and discovered that all of my mesh agents appear to be working but the RMM agents are not. Unfortunately, I think Tactical (while a great project!) is not really a good fit for my environment anymore. But thanks for the help, and for building such a cool tool for the MSP community!
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#2293
No description provided.