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

Waiting for Node Classifier to start... #36

Open
benhocker opened this issue Dec 31, 2014 · 4 comments
Open

Waiting for Node Classifier to start... #36

benhocker opened this issue Dec 31, 2014 · 4 comments

Comments

@benhocker
Copy link

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?

==> master: Notice: /Stage[main]/Puppet_enterprise::Puppetdb::Service/Service[pe-puppetdb]/ensure: ensure changed 'stopped' to 'running'
==> master: Notice: Finished catalog run in 3.06 seconds
==> master: 
==> master: Loaded plugins: fastestmirror, security
==> master: Cleaning repos: puppet-enterprise-installer
==> master: Cleaning up Everything
==> master: Cleaning up list of fastest mirrors
==> master: PuppetDB configured.
==> master: Waiting for Node Classifier to start...
==> master: !!! WARNING: The node classifier could not be reached; please check the logs in '/var/log/pe-console-services/' for more information.

The contents of /var/log/pe-console-services/* are below:

[root@master pe-console-services]# tail -20 pe-console-services-daemon.log 
07:46:48,324 |-INFO in LogbackRequestLog - Will use configuration file [/etc/puppetlabs/console-services/request-logging.xml]
07:46:48,336 |-INFO in ch.qos.logback.access.joran.action.ConfigurationAction - debug attribute not set
07:46:48,337 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.FileAppender]
07:46:48,337 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [FILE]
07:46:48,337 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.access.PatternLayoutEncoder] for [encoder] property
07:46:48,355 |-INFO in ch.qos.logback.core.FileAppender[FILE] - File property is set to [/var/log/pe-console-services/console-services-access.log]
07:46:48,356 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [FILE] to null
07:46:48,356 |-INFO in ch.qos.logback.access.joran.action.ConfigurationAction - End of configuration.
07:46:48,356 |-INFO in ch.qos.logback.access.joran.JoranConfigurator@2b00d44c - Registering current configuration as safe fallback point

07:46:48,780 |-INFO in LogbackRequestLog - Will use configuration file [/etc/puppetlabs/console-services/request-logging.xml]
07:46:48,781 |-INFO in ch.qos.logback.access.joran.action.ConfigurationAction - debug attribute not set
07:46:48,781 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.FileAppender]
07:46:48,781 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [FILE]
07:46:48,785 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.access.PatternLayoutEncoder] for [encoder] property
07:46:48,786 |-INFO in ch.qos.logback.core.FileAppender[FILE] - File property is set to [/var/log/pe-console-services/console-services-access.log]
07:46:48,786 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [FILE] to null
07:46:48,786 |-INFO in ch.qos.logback.access.joran.action.ConfigurationAction - End of configuration.
07:46:48,786 |-INFO in ch.qos.logback.access.joran.JoranConfigurator@4b160f29 - Registering current configuration as safe fallback point

[root@master pe-console-services]# tail -20 console-services.log 
2014-12-31 07:46:49,125 INFO  [o.e.j.s.ServerConnector] Started ServerConnector@71f61516{HTTP/1.1}{127.0.0.1:4430}
2014-12-31 07:46:49,149 INFO  [o.e.j.s.ServerConnector] Started ServerConnector@18d2543e{SSL-HTTP/1.1}{0.0.0.0:4431}
2014-12-31 07:46:49,309 INFO  [m.database] creating migration table 'schema_migrations'
2014-12-31 07:46:49,331 INFO  [m.core] Starting migrations
2014-12-31 07:46:49,687 INFO  [m.core] Running up for [20140903132700 20140903153000 20141024111137]
2014-12-31 07:46:49,687 INFO  [m.core] Up 20140903132700-initial-scheme
2014-12-31 07:46:49,778 INFO  [m.core] Up 20140903153000-backup-activity-events
2014-12-31 07:46:49,788 INFO  [m.core] Up 20141024111137-drop-commit-uniqueness
2014-12-31 07:46:49,795 INFO  [m.core] Ending migrations
2014-12-31 07:46:49,836 INFO  [o.e.j.s.h.ContextHandler] Started o.e.j.s.ServletContextHandler@4e57af8b{/activity-api,null,AVAILABLE}
2014-12-31 07:46:49,870 INFO  [p.c.class-updater] Requesting environment list from "https://master:8140/v2.0/environments"
2014-12-31 07:46:52,255 INFO  [p.c.class-updater] 200 response received for request for environments from "https://master:8140/v2.0/environments"
2014-12-31 07:46:52,264 INFO  [p.c.class-updater] Requesting classes in production from "https://master:8140/production/resource_types/*"
2014-12-31 07:47:00,244 INFO  [p.c.class-updater] 200 response received for request for classes in production from "https://master:8140/production/resource_types/*"
2014-12-31 07:47:03,225 INFO  [p.c.class-updater] Synchronized 105 classes from the Puppet Master in 13 seconds
2014-12-31 08:01:50,012 INFO  [p.c.class-updater] Requesting environment list from "https://master:8140/v2.0/environments"
2014-12-31 08:01:53,699 INFO  [p.c.class-updater] 200 response received for request for environments from "https://master:8140/v2.0/environments"
2014-12-31 08:01:53,733 INFO  [p.c.class-updater] Requesting classes in production from "https://master:8140/production/resource_types/*"
2014-12-31 08:02:01,889 INFO  [p.c.class-updater] 200 response received for request for classes in production from "https://master:8140/production/resource_types/*"
2014-12-31 08:02:03,937 INFO  [p.c.class-updater] Synchronized 105 classes from the Puppet Master in 14 seconds
[root@master pe-console-services]# tail -20 console-services-access.log 
master - - - 31/Dec/2014:08:03:34 -0800 "GET /rbac-api/v1/users HTTP/1.1" 200 421
master - - - 31/Dec/2014:08:03:35 -0800 "POST /rbac-api/v1/users/42bf351c-f9ec-40af-84ad-e976fec7f4bd/password/reset HTTP/1.1" 201 851
master - - - 31/Dec/2014:08:03:37 -0800 "POST /rbac-api/v1/auth/reset HTTP/1.1" 200 2
master - - - 31/Dec/2014:08:03:54 -0800 "POST /classifier-api/v1/classified/nodes/master HTTP/1.1" 200 123
master - - - 31/Dec/2014:08:04:01 -0800 "POST /classifier-api/v1/classified/nodes/master HTTP/1.1" 200 123
master - - - 31/Dec/2014:08:04:32 -0800 "POST /classifier-api/v1/classified/nodes/master HTTP/1.1" 200 123
master - - - 31/Dec/2014:08:04:49 -0800 "POST /classifier-api/v1/classified/nodes/master HTTP/1.1" 200 123
master - - - 31/Dec/2014:08:05:06 -0800 "POST /classifier-api/v1/classified/nodes/master HTTP/1.1" 200 123
master - - - 31/Dec/2014:08:05:13 -0800 "POST /classifier-api/v1/classified/nodes/master HTTP/1.1" 200 123
@pearcec
Copy link

pearcec commented Mar 27, 2015

I too had the same issue.

@yzguy
Copy link

yzguy commented Nov 16, 2015

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.

@mmarseglia
Copy link

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.
pe-install.txt

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?

[vagrant@master vagrant]$ cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 master.vagrant.vm master
10.20.1.3 master.vagrant.vm master

@mmarseglia
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants