mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 15:05:57 +03:00
[GH-ISSUE #1234] Linux agents not updating automatically #760
Labels
No labels
In Process
bug
bug
dev-triage
documentation
duplicate
enhancement
fixed
good first issue
help wanted
integration
invalid
pull-request
question
requires agent update
security
ui tweak
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tacticalrmm#760
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @LPJon on GitHub (Aug 2, 2022).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1234
Server Info (please complete the following information):
Installation Method:
Agent Info (please complete the following information):
Describe the bug
Quite Simply I have now gone through two updates of the TacticalRMM server and no linux agents are automatically updating
To Reproduce
Steps to reproduce the behavior:
Expected behavior
They update just as the windows agent do and are automatically installed upon connection to TacticalRMM
Screenshots
If applicable, add screenshots to help explain your problem.
N/A
Additional context
Add any other context about the problem here.
@silversword411 commented on GitHub (Aug 2, 2022):
Are you code signed?
Because if you're not, that is absolutely correct...linux agents will not automatically update.
@wh1te909 commented on GitHub (Aug 2, 2022):
@silversword411 he is code signed. @LPJon any errors in
/var/log/tacticalagent.log@LPJon commented on GitHub (Aug 2, 2022):
This is all that is in the log of the XCP-ng (CentOS 8 Based) agent:
This is from a FreePBX (CentOS7 Based) agent:
@wh1te909 commented on GitHub (Aug 2, 2022):
As the root user, please edit
/etc/systemd/system/tacticalagent.serviceand find the line that looks like thisand change it to this
then
Then in the web UI please try triggering a manual agent update cycle from Agents > Update Agents and tail the same log file to see if any errors there and if so please post them (make sure to redact tokens/domains etc)
@LPJon commented on GitHub (Aug 2, 2022):
I'm not seeing any thing that looks like an error but here is the log anyway:
@wh1te909 commented on GitHub (Aug 2, 2022):
Just realized you're already on the latest agent version lol (2.2.1) even in your first post. So looks like it did work?
@LPJon commented on GitHub (Aug 2, 2022):
I manually updated those agents by hand just a few hours ago. I don't have any agents that are the previous v2.1.2 now. I can try a downgrade test later and see what the results are but I'm in the states and right now it's 2:16am so I will give it a try later today if you like?
@wh1te909 commented on GitHub (Aug 2, 2022):
sounds good yea if you could manually downgrade on an agent with debug logging then let the rmm try to update it let's see what it logs
@LPJon commented on GitHub (Aug 2, 2022):
Will do....I keep track of the linux agents just for this purpose. I also do the same with meshcentral agents. Just seems to make this process easier.
@LPJon commented on GitHub (Aug 2, 2022):
Okay now I am confused. It immediately updated without issues and the log looks just as before. I guess this isn't an issue.....maybe I installed the agent wrong the first time. When the agent is installed with the Script from TacticalRMM does it set any specific permissions on the binary file other than making it executable?
@wh1te909 commented on GitHub (Aug 4, 2022):
nope no special perms. yea weird idk maybe there were network issues or something causing download to fail. i'll close this for now but if it happens again please re-open and provide the logs thanks.