Project

General

Custom queries

Profile

Actions
Copy link

Bug #18399

closed

Failed to initialize puppet class cache, will use lazy initialization instead

Added by Sven Vogel about 8 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Puppet
Target version:
1.15.0
Difficulty:
Triaged:
Bugzilla link:
Pull request:
https://github.com/theforeman/smart-proxy/pull/512
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Hi,

after Upgrade from Foreman 1.13 (Katello 3.3) i get the following error in smartproxy log. i get the error when i take a restart the server and complete process are running. if i restart later foreman-proxy the error is gone.

Failed to initialize puppet class cache, will use lazy initialization instead

I, [2017-02-06T01:03:03.540493 ] INFO -- : Successfully initialized 'dhcp_isc'
I, [2017-02-06T01:03:03.540645 ] INFO -- : Successfully initialized 'dhcp'
I, [2017-02-06T01:03:03.540760 ] INFO -- : Successfully initialized 'puppetca'
I, [2017-02-06T01:03:03.540935 ] INFO -- : Started puppet class cache initialization
I, [2017-02-06T01:03:03.542029 ] INFO -- : Successfully initialized 'puppet_proxy_puppet_api'
I, [2017-02-06T01:03:03.542153 ] INFO -- : Successfully initialized 'puppet'
D, [2017-02-06T01:03:03.542277 ] DEBUG -- : Log buffer API initialized, available capacity: 2000/1000
I, [2017-02-06T01:03:03.542356 ] INFO -- : Successfully initialized 'logs'
E, [2017-02-06T01:03:03.642049 ] ERROR -- : Failed to initialize puppet class cache, will use lazy initialization instead
I, [2017-02-06T01:03:03.677632 ] INFO -- : WEBrick 1.3.1
I, [2017-02-06T01:03:03.677860 ] INFO -- : ruby 2.0.0 (2015-12-16) [x86_64-linux]
D, [2017-02-06T01:03:03.678172 ] DEBUG -- : TCPServer.new(0.0.0.0, 9090)
D, [2017-02-06T01:03:03.678343 ] DEBUG -- : TCPServer.new(::, 9090)
W, [2017-02-06T01:03:03.678500 ] WARN -- : TCPServer Error: Address already in use - bind(2)

any information how i get that error removed?

thanks

Sven

Files

Bildschirmfoto 2017-02-06 um 01.13.33.png View Bildschirmfoto 2017-02-06 um 01.13.33.png 149 KB Sven Vogel, 02/05/2017 07:14 PM

Added by Dmitri Dolguikh about 8 years ago

Revision a823c703 (diff)

Fixes #18399 - use warning instead when cache init fails

With a clearer message. Currently, when such an issue
occurs, users aren't clear about what they need to do
to correct the error.

Actions
Copy link

Also available in: Atom PDF