Skip to content
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

Kibana Windows build is stuck on "Running bin/kibana to trigger the optimizer" #19633

Closed
azasypkin opened this issue Jun 1, 2018 · 7 comments · Fixed by #73154
Closed

Kibana Windows build is stuck on "Running bin/kibana to trigger the optimizer" #19633

azasypkin opened this issue Jun 1, 2018 · 7 comments · Fixed by #73154
Labels
bug Fixes for quality problems that affect the customer experience build Team:Operations Team label for Operations Team

Comments

@azasypkin
Copy link
Member

azasypkin commented Jun 1, 2018

Just tried to build Kibana on Windows 10 and the build never ends, it's stuck on "Running bin/kibana to trigger the optimizer" (30+ mins). Tried on VM and real hardware.

Here is stdout and ls .\build\kibana\optimize\bundles\

/cc @jbudz

@azasypkin azasypkin added bug Fixes for quality problems that affect the customer experience Team:Operations Team label for Operations Team labels Jun 1, 2018
@epixa epixa added the build label Jun 1, 2018
@azasypkin azasypkin changed the title Kibana Windows build stuck on "Running bin/kibana to trigger the optimizer" Kibana Windows build is stuck on "Running bin/kibana to trigger the optimizer" Jun 1, 2018
@tylersmalley
Copy link
Contributor

So far I have not been able to reproduce this, though we are other similar reports with plugin installation.

@azasypkin
Copy link
Member Author

Interesting, wondering if "shell" matters, I've got the same results for built-in cmd shell and PowerShell.

@bradvido
Copy link

bradvido commented Jun 5, 2018

I'm seeing the same problem with Windows Server 2016
#19678

@liza-mae
Copy link
Contributor

liza-mae commented Aug 3, 2018

Seeing the problem on Windows Server 2016 VM also. I waited over an hour, before I issued a control-c.

@tylersmalley
Copy link
Contributor

It appears this issue is due to the process not ending when calling kill https://github.com/elastic/kibana/blob/master/src/utils/watch_stdio_for_line.js#L55

@laosandegudai
Copy link

I met the same problem in windows 10.

@brezaie
Copy link

brezaie commented Mar 11, 2019

I am facing the same issue on Windows Server 2016 when installing the Search Guard plugin. Interestingly, when installing the plugin on Windows 10, everything is all right, but the issue occurs on Windows Server 2016.
Elastic version: 6.5.4

Any solutions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience build Team:Operations Team label for Operations Team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants