elastic-package starts but does nothing Windows 11

[joeperuzzi]

Installing the elastic-package through go and/or running it stand-alone pre-compiled takes CPU cycles but never moves. No matter what switches are used, the executable doesn't seem to do anything but take CPU cycles. I've let this run for 20 minutes and nothing happens other than CPU usage, i've disabled all AV (running Elastic Endpoint) as it was causing the Elastic Security process to consume all the CPU and crash explorer.

Currently Running on Windows 11 Pro 10.0.22621 on an Intel i7.

[jsoriano]

Hey @joeperuzzi,

Thanks for your report! What version of elastic-package are you using?

[joeperuzzi]

I executed "go install github.com/elastic/elastic-package@latest" yesterday, the executable will not run to give me a version and the exe properties that is generated from that command does not have a version in its properties.

[jsoriano]

@joeperuzzi can you try with one of the released versions? https://github.com/elastic/elastic-package/releases

[joeperuzzi]

I tried both 0.70 and 0.71 both have the same outcome as above.

[joeperuzzi]

Just as an update, downloaded and tested v0.74.0 and the issue still exists.

[joeperuzzi]

Just as an update, downloaded and tested v0.75.0 and the issue persists

[jsoriano]

@joeperuzzi thanks. We haven't been able to reproduce it, so by now you are our only hope to catch this issue 🙂

Could you try to investigate the process with other tools, like Process Monitor, to see if you can see something else?

Would you have the chance to try to run another Go program, even if it is just a hello world, to see if it is an issue with Go runtime?

[joeperuzzi]

@jsoriano Seems to be trying to write the c:\.git file and is failing...

[joeperuzzi]

I manually created an empty.git file

[joeperuzzi]

@jsoriano I removed the .git file and created a "c:.git" folder and the command line now works:

C:\Users\peruz\Downloads\elastic-package_0.75.0_windows_amd64.tar>elastic-package.exe version
elastic-package v0.75.0 version-hash 47a2456 (build time: 2023-02-23T07:57:31-07:00)

C:\Users\peruz\Downloads\elastic-package_0.75.0_windows_amd64.tar>

[jsoriano]

Hey @joeperuzzi,

This is useful, this pointed me to the FindRepositoryRootDirectory() function. Looking to the implementation it may be looping forever in some cases in Windows. It has a finalization condition that checks if the directory name is /. This will never be satisfied on this platform.

I wonder though why it reports to be creating a file, it should be only checking its attributes, maybe this is how the implementation works in Windows.

And I wonder too why elastic-package -h ends up calling this function, it shouldn't need it.

I will take a look by now to this finalization condition.

Thanks!

[jsoriano]

@joeperuzzi could you give a try to this patch in your scenario? #1171

[jsoriano]

I have been able to reproduce the issue by running elastic-package in Windows out of a git repository. I could also confirm that #1171 fixes the issue for me. I am opening this PR for review and merge.