mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 15:05:57 +03:00
[GH-ISSUE #124] On Clients - tacticalrmm - Not Installed #72
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#72
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 @KenGrant on GitHub (Oct 1, 2020).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/124
On the clients tacticalrmm.exe reports:
Agent : not installed
Check Runner : Not Installed
Salt minion : running
Mesh Agent : running
Tactical RMM website shows Agent Overdue.
Build appeared to go normally just the agent won't run.
Windows 10 - Two PC attempted.
@wh1te909 commented on GitHub (Oct 1, 2020):
uninstall the agent from the RMM (right click > remove agent).
On the agent, open cmd as admin first, cd to the directory of the exe (this way when it prints the error message the window won't close so you can see it). Pass
--log DEBUGto the executable and install it again. It will show the error message.@KenGrant commented on GitHub (Oct 1, 2020):
Thanks you for the swift reply:
I have tried - C:\Program Files\TacticalAgent>tacticalrmm.exe --log DEBUG
It just open the Tactical RMM box with the first messages.
I am going to try a manual install tomorrow as you suggest in the Downloadable Install of the Agent. I'll update findings...
Many thanks - I am very keen to try to get this working- It looks so promising.
@wh1te909 commented on GitHub (Oct 1, 2020):
sorry, i meant pass it to the installer executable
if you're using the generated EXE, something like this
rmm-client-site-server.exe --log DEBUGwith manual method
will keep ticket open till we get it working :)
@KenGrant commented on GitHub (Oct 2, 2020):
Hi
I have run this now and have seen at the bottom of the process:
2020-10-02 09:45:57,913 - installer - install - 363 - DEBUG - {'detail': 'Invalid token.'}
2020-10-02 09:46:02,916 - installer - install - 374 - ERROR - Unable to register salt with the RMM
2020-10-02 09:46:02,924 - installer - install - 375 - ERROR - Installation failed
Can I mention a couple of issues I experienced during install:-
The three subdomains do not appear to have entered into the hosts file despite accepting the offer add adding them by the install.
In my domains DNS settings I was not abbe to add the root domain xxx.net to the TXT entry _acme-challenge.xxx.net - the website kept deleting xxx.net suffix. However, it did pass the verification and so I presumed OK - maybe not?
For Info I have setup a fresh Google VM for this test.
I can access the RMM (token working for Auth) - RDP working but nothing reported under tasks, patching etc. Also agent initially says it working and then goes orange and then red.
I have had a look at salt on the server and I see this message (subsititued PC name) :
Authentication request from "PCNAME"
[INFO ] Authentication failed from host "PCNAME" the key is in pending and needs to be accepted with salt-key -a PCNAME
Running this - salt-key -a PCNAME (tried on a previous VM) doesn't help. Gets accepted but makes no difference to the agent or RMM website.
Hope this helps with a diagnosis of the issue.
@KenGrant commented on GitHub (Oct 2, 2020):
Just to mention, I can transfer the domain I am using to a different nameserver if you think that would help?
@wh1te909 commented on GitHub (Oct 2, 2020):
domain is fine no need to touch that
sounds like the install script didn't properly install salt based on the errors you posted
i've never tested it on google cloud
can you let me know exactly the VM instance size OS ram etc that you created and i'll spin one up and test a fresh install
@KenGrant commented on GitHub (Oct 2, 2020):
Many thanks for sticking with this - much appreciated.
Google VM Info:
Machine type
e2-medium (2 vCPUs, 4 GB memory)
ubuntu-2004-focal-v20200917
Description
Canonical, Ubuntu, 20.04 LTS, amd64 focal image built on 2020-09-17, supports Shielded VM features
Location
asia (Asia Pacific), eu (European Union), us (United States)
Zone
europe-west2-c
Not sure if it's relevant but the last boot time on RMM for all PC's that I have setup is showing as 51 Years ago -(Oct-01-2020 - 16:29 | 51 years ago)?
Thanks
@wh1te909 commented on GitHub (Oct 2, 2020):
great thanks i'll spin one up and see where the salt install went wrong
yea the boot time showing that is normal since the agent didn't finish installing so alot of info is missing and most things won't work
@Omnicef commented on GitHub (Oct 2, 2020):
I can add to this. I also have a site where almost all clients show the
invalid token info. (All but one I believe).
On Fri, Oct 2, 2020 at 10:09 AM wh1te909 notifications@github.com wrote:
--
Anthony Fenech
909-992-2031
Anthony@Synergy-Computer.com
@wh1te909 commented on GitHub (Oct 3, 2020):
@KenGrant screenshot above of the instance I created.
You only need to enter
_acme-challengefor the TXT record, not the full domain, so your dns manager was properly deleting it for you.I updated the install script to handle hosts files that don't have 127.0.1.1
I then ran it on my google cloud VM and all worked, agents working too.
Please delete the VM and start from scratch using the latest install.sh script.
Also, on the agents, run the following from an elevated command prompt please
Wait a minute or 2 then please make sure the following 3 folders do NOT exist:
If they do then forcefully delete them.
Then from the new RMM generate an exe and try the install again and let me know.
@KenGrant commented on GitHub (Oct 5, 2020):
Hi
I have done a complete VM re-install & cleaned the client as you instructed. Unfortunately the same issue has occurred- the clients Salt log file contains:-
2020-10-05 09:25:17,688 [salt.minion :1075][ERROR ][9312] Minion unable to successfully connect to a Salt Master.
Can you let know where you would like info from?
Thanks
@wh1te909 commented on GitHub (Oct 5, 2020):
did you open up ports 4505 and 4506 TCP in google cloud firewall and on the VM's firewall?
@KenGrant commented on GitHub (Oct 5, 2020):
You're correct - I had setup TAGS with I forgot to add to the VM network for 4505 & 6.
I have added them and restarted VM & Salt on Client -I now get (on client) :
2020-10-05 10:37:27,627 [salt.crypt :798 ][ERROR ][2604] The Salt Master has cached the public key for this node, this salt minion will wait for 10 seconds before attempting to re-authenticate
Do I need to re-install Client only or complete re-install for both?
Thanks
@wh1te909 commented on GitHub (Oct 5, 2020):
just uninstall and re-install the agent same instructions as before
also remove the agents from the RMM (right click on agent > remove agent)
it will say spin for a while and then say unable to contact etc just click yes, that will properly clean up the salt master's keys
also that error is normal, as long as there are only a few of them in the log file. it should stop printing that error to the log file once the salt key is accepting during install. heading to bed will follow up when i wake up in a few hours
@KenGrant commented on GitHub (Oct 5, 2020):
That's great - will try this now and let you know.
Thanks
@KenGrant commented on GitHub (Oct 5, 2020):
We have lift off!! 👍
Going to trial now - wondering about AV & Web protection. Any thoughts webroot etc?
Also, tried to add a new RMM user - didn't work, I guess because no Google Authenticator yet for this?
Many thanks for all your help.
@dinger1986 commented on GitHub (Oct 5, 2020):
Great!
When you add a new user then right click on the user and click Reset Two-Factor Auth, this will then set this up.
@KenGrant commented on GitHub (Oct 5, 2020):
Thanks - dinger1986
Is there an AV conversation anywhere - I am super excited about this project?
@dinger1986 commented on GitHub (Oct 5, 2020):
There has been chat on discord, I personally (Im not involved in the project) would like to see even defender integrated a bit which should be doable with event viewer (having said that any AV etc should be able to be manged with event viewer and log files etc)
@KenGrant commented on GitHub (Oct 5, 2020):
Thanks - early days for me - I'll keep a close watch on developments.