Foreman » Smart Proxy

Justin Sherrill wrote:

Moving this to foreman as I do not believe this is related to katello

where is it now?

Sorry my mistake. The class import works well. Just this Error appears on startup.

This error means that proxy couldn't initialize its internal class cache on startup and will attempt it again later. Has puppet server finished starting when smart-proxy is launched? If not, this could cause the error message you are seeing.

Dmitri Dolguikh wrote:

This error means that proxy couldn't initialize its internal class cache on startup and will attempt it again later. Has puppet server finished starting when smart-proxy is launched? If not, this could cause the error message you are seeing.

I dont know how to check that exacly. Foreman-Proxy and Puppet starts at the same time and but from the logs foreman_proxy is initialized before puppet.

14.2.2017, 16:59:59 INFO Successfully initialized 'foreman_proxy'
14.2.2017, 16:59:59 INFO Successfully initialized 'tftp'
14.2.2017, 16:59:59 INFO Successfully initialized 'puppetca'
14.2.2017, 16:59:59 INFO Started puppet class cache initialization
14.2.2017, 16:59:59 INFO Successfully initialized 'puppet_proxy_puppet_api'
14.2.2017, 16:59:59 INFO Successfully initialized 'puppet'
14.2.2017, 16:59:59 INFO Successfully initialized 'logs'
14.2.2017, 16:59:59 ERROR Failed to initialize puppet class cache, will use lazy initialization instead

This is what you meen or?

Yes this error only appears on startup. i wrote this above already. after restart from proxy the error is gone.

any fixes?

It's a transient error, which is meant to catch issues with cache initialization on proxy startup. If you are getting classes back, then proxy is working ok, then this error can be ignored.