For the sake of the list archives, Jelle found the permissions on
/var/lib/puppet/yaml/foreman were root:root, while they should be
puppet:puppet so that the ENC (which runs under the puppet user) can write.
The error above referred to the exit code of the ENC script being 1
rather than 0, so it was something inside that going wrong.
···
On 30/11/12 16:02, Jelle B. wrote: > Having been in the process for the last week of seting up a Puppet 3 > enviroment with foreman rather then puppet-dashboard to day I ran into > an issue I can lead back to the ENC execution but not to what i am > missing :( > Below the output from teh puppetmaster which seems to be most helpfull. > > it is a pretty "follow the manual" setup so the node.rb is the one > mentioned on the side without much rework. > > Anyone have any idea where I went wrong or what i over looked ? > > > Nov 30 16:47:50 puppetmaster puppet-master[1657]: > (//unbound.nmdn.lan/Puppet) Unable to fetch my node definition, but the > agent run will continue: > Nov 30 16:47:50 puppetmaster puppet-master[1657]: > (//unbound.nmdn.lan/Puppet) Error 400 on SERVER: Connection: close#015 > Nov 30 16:47:50 puppetmaster puppet-master[1657]: > (//unbound.nmdn.lan/Puppet) Content-Type: text/plain#015 > Nov 30 16:47:50 puppetmaster puppet-master[1657]: > (//unbound.nmdn.lan/Puppet) Date: Fri, 30 Nov 2012 15:47:47 GMT#015 > Nov 30 16:47:50 puppetmaster puppet-master[1657]: > (//unbound.nmdn.lan/Puppet) Server: WEBrick/1.3.1 > (Ruby/1.8.7/2010-08-16) OpenSSL/0.9.8o#015 > Nov 30 16:47:50 puppetmaster puppet-master[1657]: > (//unbound.nmdn.lan/Puppet) Content-Length: 204#015 > Nov 30 16:47:50 puppetmaster puppet-master[1657]: > (//unbound.nmdn.lan/Puppet) #015 > Nov 30 16:47:50 puppetmaster puppet-master[1657]: > (//unbound.nmdn.lan/Puppet) Failed to find unbound.nmdn.lan via exec: > Execution of '/etc/puppet/node.rb unbound.nmdn.lan' returned 1: ---–
Dominic Cleal
Red Hat Engineering
