No such ENC (other than Hiera).
There is also no static node declaration in Puppet; that comes from
Hiera. But again, rest of the 50-odd nodes are running just fine the very
same way.
-San
On Monday, June 2, 2014 3:33:12 PM UTC+1, jcbollinger wrote:
Is there an ENC involved?
Is there a
On Thursday, June 5, 2014 5:47:44 AM UTC-5, Sans wrote:
No such ENC (other than Hiera).
There is also no static node declaration in Puppet; that comes from
Hiera. But again, rest of the 50-odd nodes are running just fine the very
same way.
The exception is being thrown by this
On Saturday, May 31, 2014 2:53:52 PM UTC-5, Sans wrote:
Good catch Ellison; I haven't noticed that but nope, nothing unusual
from facter on the affected node.
Now running puppet agent -tv with certificate cleared from both master
and agent yields these:
notice: Starting Puppet master
Good catch Ellison; I haven't noticed that but nope, nothing unusual from
facter on the affected node.
Now running puppet agent -tv with certificate cleared from both master and
agent yields these:
notice: Starting Puppet master version 2.7.23
info: access[/certificate_request]:
Hi Henrik,
I don't really use WEBrick but apache/passenger for the normal operation. I
think WEBrick is used to run puppet master in background in debug mode. Is
there a way to use apache/passenger for that?
Anyway, I'm running puppet v2.7.3 and getting the same error for one of
those nodes
On 2014-30-05 20:54, Sans wrote:
Hi Henrik,
I don't really use WEBrick but apache/passenger for the normal
operation. I think WEBrick is used to run puppet master in background in
debug mode. Is there a way to use apache/passenger for that?
Anyway, I'm running puppet v2.7.3 and getting the
On Friday, May 30, 2014 11:13:51 PM UTC+1, Henrik Lindberg wrote:
Ok, then webrick is not the cause of your problem.
Run with --trace set to get a ruby stack trace. That will help to find
what is causing the problem.
- henrik
Yes, that was the output from --trace and that's why I
It's weird, but it looks like the hostname isn't being defined, or isn't
being sent properly. See
info: Expiring the node cache of
With just a blank afterwards. Does running facter on the affected node show
anything unusual?
On Friday, May 30, 2014 3:18:58 PM UTC-7, Sans wrote:
On
I have two identical nodes - serv106 and serv107 - one of which is working
just fine but the other one failing with these error message:
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
undefined method `include?' for nil:NilClass on node
warning: Not using cache on
Hi,
this error can me pretty much anything - you're likely hitting some kind
of bug (perhaps just a lack of error handling).
Run the puppet master with the --trace flag to get more details on
what's happening specifically.
Felix
On 05/29/2014 09:57 PM, Sans wrote:
I have two identical nodes
Thanks Felix for the heads up.
Sorry for the long post. That's all I get using --trace option but I still
can't figure out what's going wrong.
notice: Starting Puppet master version 2.7.23
info: access[^/catalog/([^/]+)$]: allowing 'method' find
info: access[^/catalog/([^/]+)$]: allowing $1
On 2014-29-05 21:57, Sans wrote:
I have two identical nodes - serv106 and serv107- one of which is
working just fine but the other one failing with these error message:
err: Could not retrieve catalog from remote server: Error 400 on
SERVER: undefined method `include?' for
12 matches
Mail list logo
