err: /Settings[top]/Settings[main]/File[/usr/local/.aqadmin/puppet/var/yaml]: Failed to retrieve current state of resource: Could not find user puppet debug: Finishing transaction 75413780 with 2 changes since i put the last version on this test server i cannot launch puppet manualy: mkdir -m 700 -p /usr/local/.aqadmin/puppet/conf/ssl; \ mkdir -m 700 -p /usr/local/.aqadmin/puppet/var/facts; \ mkdir -m 700 -p /usr/local/.aqadmin/puppet/log; \ mkdir -m 700 -p /usr/local/.aqadmin/puppet/run; \ mkdir -m 700 -p /usr/local/.aqadmin/puppet/state; \ puppetd --confdir=/usr/local/.aqadmin/puppet/conf \ --logdir=/usr/local/.aqadmin/puppet/log \ --rundir=/usr/local/.aqadmin/puppet/run \ --statedir=/usr/local/.aqadmin/puppet/state \ --vardir=/usr/local/.aqadmin/puppet/var --factsync \ --factpath=/usr/local/.aqadmin/puppet/var/facts \ --factdest=/usr/local/.aqadmin/puppet/var/facts \ --server=xxxxxxxxxxx --waitforcert 30 --test --debug it has worked from <0.24.1 but now i cannot launch the utils. I tried to use root (--user=root) but guess what, on freeBSD there is no root group so the error change to : err: /Settings[top]/Settings[main]/File[/usr/local/.aqadmin/puppet/var/yaml]: Failed to retrieve current state of resource: Could not find group root but what is the issue here, the client allways runned as root , do i missed something ? I created a dummy root group and now i got : err: Could not retrieve catalog: File[/var/puppet/facts] is already being managed Dec 23 11:26:59 puppet20 puppetmasterd[19154]: Starting Puppet server version 0.24.1 Dec 23 11:27:36 puppet20 puppetmasterd[19154]: File[/var/puppet/facts] is already being managed I am a little lost there...anything i missed ? -- Cordialement, Ghislain _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
it seems that 0.23.2 has not this error with the very same command line. -- Cordialement, Ghislain _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
On Dec 24, 2007, at 2:15 AM, ADNET Ghislain wrote:> err: > /Settings[top]/Settings[main]/File[/usr/local/.aqadmin/puppet/var/ > yaml]: > Failed to retrieve current state of resource: Could not find user > puppet > debug: Finishing transaction 75413780 with 2 changes > > since i put the last version on this test server i cannot launch > puppet > manualy: > > mkdir -m 700 -p /usr/local/.aqadmin/puppet/conf/ssl; \ > mkdir -m 700 -p /usr/local/.aqadmin/puppet/var/facts; \ > mkdir -m 700 -p /usr/local/.aqadmin/puppet/log; \ > mkdir -m 700 -p /usr/local/.aqadmin/puppet/run; \ > mkdir -m 700 -p /usr/local/.aqadmin/puppet/state; \ > puppetd --confdir=/usr/local/.aqadmin/puppet/conf \ > --logdir=/usr/local/.aqadmin/puppet/log \ > --rundir=/usr/local/.aqadmin/puppet/run \ > --statedir=/usr/local/.aqadmin/puppet/state \ > --vardir=/usr/local/.aqadmin/puppet/var --factsync \ > --factpath=/usr/local/.aqadmin/puppet/var/facts \ > --factdest=/usr/local/.aqadmin/puppet/var/facts \ > --server=xxxxxxxxxxx --waitforcert 30 --test --debug > > > it has worked from <0.24.1 but now i cannot launch the utils. I tried > to use root (--user=root) but guess what, on freeBSD there is no root > group so the error change to : > > err: > /Settings[top]/Settings[main]/File[/usr/local/.aqadmin/puppet/var/ > yaml]: > Failed to retrieve current state of resource: Could not find group > root > > > but what is the issue here, the client allways runned as root , do i > missed something ?What are your user and group set to? Run --configprint user and -- configprint group on puppetd. Are those values different than previous releases? Is this a machine that worked before, or is it a new machine?> I created a dummy root group and now i got : > > err: Could not retrieve catalog: File[/var/puppet/facts] is already > being managed > > > Dec 23 11:26:59 puppet20 puppetmasterd[19154]: Starting Puppet server > version 0.24.1 > Dec 23 11:27:36 puppet20 puppetmasterd[19154]: File[/var/puppet/facts] > is already being managedOn the server? Can you run this with --trace and post the stack trace? -- There is nothing worse than aggressive stupidity. -- Johann Wolfgang von Goethe --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
> What are your user and group set to? Run --configprint user and -- > configprint group on puppetd. > > Are those values different than previous releases? > > Is this a machine that worked before, or is it a new machine? > >this was on same server, same client, same config, same command liune. I just done a gem remove and gem install of puppet to get to the last version. After doing again a remove/reboot/reinstall it works now but i have: (root)> more /etc/puppet/fileserver.conf [facts] path /var/puppet/facts2 allow * because leaving (root)> more /etc/puppet/fileserver.conf [facts] path /var/puppet/facts allow * lead to the same error i had before. Perhaps i have a bad configuration here that was not an issue but is now ? -- Cordialement, Ghislain _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
On Jan 3, 2008, at 10:10 AM, ADNET Ghislain wrote:> >> What are your user and group set to? Run --configprint user and >> -- configprint group on puppetd. >> >> Are those values different than previous releases? >> >> Is this a machine that worked before, or is it a new machine? >> >> > this was on same server, same client, same config, same command > liune. I just done a gem remove and gem install of puppet to get > to the last version. After doing again a remove/reboot/reinstall > it works nowHrm, that''s no good.> but i have: > > (root)> more /etc/puppet/fileserver.conf > [facts] > path /var/puppet/facts2 > allow * > > > because leaving > > (root)> more /etc/puppet/fileserver.conf > [facts] > path /var/puppet/facts > allow * > > > lead to the same error i had before. Perhaps i have a bad > configuration here that was not an issue but is now ?Like I said, this is a different bug, and I''m working on it. -- To get back my youth I would do anything in the world, except take exercise, get up early, or be respectable. -- Oscar Wilde --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
ok, too bad i reinstalled several time to get it working so i lost the track of it, if the error come back i will let it stay and try to give you more infos like a trace ...etc .> Like I said, this is a different bug, and I''m working on it. >ok great :) -- Cordialement, Ghislain _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users