-
Notifications
You must be signed in to change notification settings - Fork 37
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
Waiting for Node Classifier to start... #36
Comments
I too had the same issue. |
In your provisioning are you setting https_proxy environment variable? It seems when trying to contact the node classifier, it will try and use that proxy, which of course wouldn't be able to contact your local vagrant environment. https://tickets.puppetlabs.com/browse/ENTERPRISE-533 That's an issue we were running into, I moved the line that put in the proxy below the puppet provisioning and it worked fine. |
I'm having a problem as well. Looks like the code that handles the PE install is https://github.com/oscar-stack/vagrant-pe_build I can't tell what changed. We're running PE 2015.3.1. I edited the vagrant-pe_build gem to throw the installer into debug mode. Log attached. There is no proxy setting as @yzguy suggested. I did notice there are two entries for master.vagrant.vm in /etc/hosts. I wonder if that's the problem?
|
Finally tracked this down. I was using virtualbox but then switched to vmware_fusion. VM memory was not set correctly in roles.yaml. Services were not starting due to insufficient memory in the VM. The Oscar vmware_fusion template uses the incorrect syntax for setting memory in the VM. I submitted PR #48 to show the correct syntax. |
Seems like Node Classifier takes forever and then times out after starting pe-puppetdb. What check is performed to check if Node Classifier is started?
The contents of /var/log/pe-console-services/* are below:
The text was updated successfully, but these errors were encountered: