-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Fleet / Agent] Agent is stuck on Enrolling, goes Offline, nothing in Activity Details and little in agent log #21601
Comments
Pinging @elastic/ingest-management (Team:Ingest Management) |
@ph we decided this was not working, after you had to leave the zoom chat. just fyi. |
@EricDavisX @blakerouse did we have a theory of what was causing this? |
@ph At the moment, I do not have any ideas on why this would be happening. Waiting for newest snapshot to do some of my own testing. |
QA reported that (I think with the same build) that Win 10 x64 was working - its possible I have the machine in a bad state. But it may end up pushing me to do some more upgrade tests to ensure the desired path for moving from 7.9.x to 7.10.x is working |
And the snapshot for today may not be out, we might try to find a way to make progress instead of waiting, unless we have other high priority items to do (which we may)! |
I find that Win 10 works for me, and my win 7 with a full wipe and revert to a known good clean state still fails as noted. So it may be a distinct problem for some reason. And Win 10 is having different problems with Endpoint, to be logged separately |
I can confirm that I still see this on the same Win 7 image, with the 7.10 BC1 build. |
I am consistently running into this when running Kibana from source (main branch) on my Mac. I'm encountering this using 7.10 and 8.0 snapshot builds of agent and when using either Here are my agent logs, note that the first
|
Summarizing discoveries made with @neptunian @nchaulet @blakerouse async:
@neptunian will put up a PR with changes on Kibana side so that we can test and confirm the fix. |
@EricDavisX I believe this is fixed from the work made by @neptunian is that correct, looking at the latest report from qa this looks ok. |
I don't know if this made it into 7.10 BC2 - who can confirm (apart from testing). We can just keep testing and wait till BC3 to be sure, if needed |
I tested with BC2 today and was able to confirm the fix. The release tracking issue https://github.com/elastic/dev/issues/1496 also shows that the fixes made BC2. |
Bug Conversion: Below 02 Testcases already exists for this ticket: |
Testing with the latest 8.0 snapshot of Kibana and Agent that were compiled today, details below:
hash of agent is: af3cda3c from today’s *just finished build artifacts here
https://snapshots.elastic.co/8.0.0-af3cda3c/downloads/beats/elastic-agent/elastic-agent-8.0.0-SNAPSHOT-windows-x86_64.zip
tested on a known good Win7 x64 instance on the Endgame VPN, vSphere cluster, we can share access if this isn't reproducible in other Windows vms. And I can try one or two more tomorrow too, to help.
installed in cloud staging:
Kibana info is$ git show -s 6f983728d7f8c2cf065a6d5099157a5cfdc3cd08
Date: Tue Oct 6 09:46:56 2020 +0300
host was installed with the new Agent 'install' subcommand, and it seems to show it is trying... but very little is in the Agent log.
.\elastic-agent.exe install -f --kibana-url https://abcddd43ea44262a3e3b7013402bdc7.us-central1.gcp.foundit.no:443 --enrollment-token abcQTV9uUUJNZ2pkU2tObWlEQTM6N0xxaWFNbWxRLUdEeXJFSzVfTGZaQQ==
using the default policy with nothing else in it.
the log file only had:
elastic-agent-json.log
we were debugging a few issues and actually saw a strange 'file lock' type error when we had rebooted the machine just prior (but it was a hard shut down, when it was hung in an shutting-down state... so maybe that particular message doesn't relate)
screenshots
The text was updated successfully, but these errors were encountered: