thr3ads.net - Puppet users - [Puppet Users] Problem with storeconfigs [May 2009]

If this information is useful, please help other people find it:
Share via:

Stefano Harding

2009-May-12 17:13 UTC

[Puppet Users] Problem with storeconfigs

Hello all,

I have what is certainly a stupid problem on my part. I have setup puppet in a 
test environment and it''s been working wonderfully. I am now in the
process of
moving this to our production systems and I have rebuilt our puppetmaster 
completely from scratch using the same modules/manifests, etc. from my test 
system.

Unfortunately I am running into an issue with what I assume is storeconfigs:

I setup the puppetmaster, ran the puppet client on it, no problems.
Setup a second puppet client, no problems.
On the third client I get the following error:

debug: Calling puppetmaster.getconfig
err: Could not retrieve catalog: Exported resource Sshkey[10.10.12.14] cannot 
override local resource on node humpty.ebrary.com
warning: Not using cache on failed catalog

I read the error description on 
http://reductivelabs.com/trac/puppet/wiki/SyntaxErrors but I really
don''t
fully understand what I should be doing to resolve this. It worked fine in our 
test environment...???

I am running CentOS 5.3 on both the puppetmaster and the clients, puppet 
version puppet-0.24.8-1.el5.1 from the EPEL repository.

My puppet.conf file on my puppetmaster has the following in it for storeconfigs:

    storeconfigs = true
    dbadapter = mysql
    dbuser = puppet
    dbpassword = password
    dbserver = 127.0.0.1
    dbsocket = /var/lib/mysql/mysql.sock

I also installed the MySQL Ruby Gem as described here: 
http://reductivelabs.com/trac/puppet/wiki/UsingStoredConfiguration

On the puppetmaster I have:

gem list --local

*** LOCAL GEMS ***

actionmailer (2.1.1)
actionpack (2.1.1)
activerecord (2.1.1)
activeresource (2.1.1)
activesupport (2.1.1)
cgi_multipart_eof_fix (2.3)
daemons (1.0.7)
fastthread (1.0.1)
gem_plugin (0.2.2)
mongrel (1.0.1)
mysql (2.7)
rails (2.1.1)
rake (0.8.3)

Below is the full output of the puppet client:

puppetd -vtd
info: Loading fact sysinfo
info: Loading fact gem_passenger_version
info: Loading fact iscsi
debug: Creating default schedules
debug: Failed to load library ''ldap'' for feature
''ldap''
debug: 
/Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/lib/puppet/lib]: 
Autorequiring File[/var/lib/puppet]
debug: 
/Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/var/lib/puppet/classes.txt]:
Autorequiring File[/var/lib/puppet]
debug: 
/Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/lib/puppet/state]: 
Autorequiring File[/var/lib/puppet]
debug: 
/Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/lib/puppet/ssl]: 
Autorequiring File[/var/lib/puppet]
debug: 
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/puppet/ssl/certs]:
Autorequiring File[/var/lib/puppet/ssl]
debug: 
/Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/lib/puppet/facts]: 
Autorequiring File[/var/lib/puppet]
debug: 
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/puppet/ssl/private_keys]:
Autorequiring File[/var/lib/puppet/ssl]
debug: 
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/puppet/ssl/private_keys/humpty.ebrary.com.pem]:
Autorequiring File[/var/lib/puppet/ssl/private_keys]
debug: 
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/puppet/ssl/public_keys/humpty.ebrary.com.pem]:
Autorequiring File[/var/lib/puppet/ssl/public_keys]
debug: 
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/puppet/ssl/private]:
Autorequiring File[/var/lib/puppet/ssl]
debug: 
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/puppet/ssl/certs/humpty.ebrary.com.pem]:
Autorequiring File[/var/lib/puppet/ssl/certs]
debug: 
/Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/var/lib/puppet/state/state.yaml]:
Autorequiring File[/var/lib/puppet/state]
debug: 
/Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/etc/puppet/puppet.conf]:
Autorequiring File[/etc/puppet]
debug: 
/Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/var/log/puppet/http.log]:
Autorequiring File[/var/log/puppet]
debug: 
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/puppet/ssl/csr_humpty.ebrary.com.pem]:
Autorequiring File[/var/lib/puppet/ssl]
debug: 
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/puppet/ssl/public_keys]:
Autorequiring File[/var/lib/puppet/ssl]
debug: 
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/puppet/ssl/certs/ca.pem]:
Autorequiring File[/var/lib/puppet/ssl/certs]
debug: 
/Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/etc/puppet/namespaceauth.conf]:
Autorequiring File[/etc/puppet]
debug: Finishing transaction 23811340516160 with 0 changes
notice: Ignoring --listen on onetime run
debug: Loaded state in 0.01 seconds
debug: Puppet::Network::Client::File: defining fileserver.describe
debug: Puppet::Network::Client::File: defining fileserver.list
debug: Puppet::Network::Client::File: defining fileserver.retrieve
info: Retrieving plugins
debug: Calling fileserver.list
debug: /File[/var/lib/puppet/lib/plugins]/checksum: Initializing checksum hash
debug: /File[/var/lib/puppet/lib/plugins]: Creating checksum {mtime}Sun May 10 
10:22:45 -0700 2009
debug: Calling fileserver.describe
debug: Calling fileserver.list
debug: /File[/var/lib/puppet/lib/plugins/provider]/checksum: Initializing 
checksum hash
debug: /File[/var/lib/puppet/lib/plugins/provider]: Creating checksum 
{mtime}Sun May 10 10:22:45 -0700 2009
debug: Calling fileserver.describe
debug: Calling fileserver.list
debug: /File[/var/lib/puppet/lib/plugins/provider/sysctl]/checksum: 
Initializing checksum hash
debug: /File[/var/lib/puppet/lib/plugins/provider/sysctl]: Creating checksum 
{mtime}Sun May 10 10:22:45 -0700 2009
debug: Calling fileserver.describe
debug: Calling fileserver.list
debug: /File[/var/lib/puppet/lib/plugins/provider/sysctl/parsed.rb]/checksum: 
Initializing checksum hash
debug: /File[/var/lib/puppet/lib/plugins/provider/sysctl/parsed.rb]: Creating 
checksum {md5}f1ad6c1cd610b6fe33fcd245759c09d1
debug: Calling fileserver.describe
debug: Calling fileserver.list
debug: /File[/var/lib/puppet/lib/plugins/facter]/checksum: Initializing 
checksum hash
debug: /File[/var/lib/puppet/lib/plugins/facter]: Creating checksum {mtime}Sun 
May 10 10:22:45 -0700 2009
debug: Calling fileserver.describe
debug: Calling fileserver.list
debug: /File[/var/lib/puppet/lib/plugins/facter/sysinfo.rb]/checksum: 
Initializing checksum hash
debug: /File[/var/lib/puppet/lib/plugins/facter/sysinfo.rb]: Creating checksum 
{md5}0d5b6a92650b7041295236bee11b8dc8
debug: Calling fileserver.describe
debug: Calling fileserver.list
debug: 
/File[/var/lib/puppet/lib/plugins/facter/gem_passenger_version.rb]/checksum: 
Initializing checksum hash
debug: /File[/var/lib/puppet/lib/plugins/facter/gem_passenger_version.rb]: 
Creating checksum {md5}beb690f2fa867fa7eba1d558d2e601e1
debug: Calling fileserver.describe
debug: Calling fileserver.list
debug: /File[/var/lib/puppet/lib/plugins/facter/iscsi.rb]/checksum: 
Initializing checksum hash
debug: /File[/var/lib/puppet/lib/plugins/facter/iscsi.rb]: Creating checksum 
{md5}db4caff9c377021561ee3ba8fe461bc4
debug: Calling fileserver.describe
debug: Calling fileserver.list
debug: /File[/var/lib/puppet/lib/plugins/type]/checksum: Initializing checksum 
hash
debug: /File[/var/lib/puppet/lib/plugins/type]: Creating checksum {mtime}Sun 
May 10 10:22:45 -0700 2009
debug: Calling fileserver.describe
debug: Calling fileserver.list
debug: /File[/var/lib/puppet/lib/plugins/type/sysctl.rb]/checksum: 
Initializing checksum hash
debug: /File[/var/lib/puppet/lib/plugins/type/sysctl.rb]: Creating checksum 
{md5}65fe3deaf4e245b7a5f031dac3d73f4d
debug: Calling fileserver.describe
debug: Finishing transaction 23456254757320 with 0 changes
info: Retrieving facts
debug: Calling fileserver.list
debug: /File[/var/lib/puppet/facts]/checksum: Initializing checksum hash
debug: /File[/var/lib/puppet/facts]: Creating checksum {mtime}Sun May 10 
10:22:34 -0700 2009
debug: Calling fileserver.describe
debug: Calling fileserver.list
debug: /File[/var/lib/puppet/facts/sysinfo.rb]/checksum: Initializing checksum 
hash
debug: /File[/var/lib/puppet/facts/sysinfo.rb]: Creating checksum 
{md5}0d5b6a92650b7041295236bee11b8dc8
debug: Calling fileserver.describe
debug: Calling fileserver.list
debug: /File[/var/lib/puppet/facts/gem_passenger_version.rb]/checksum: 
Initializing checksum hash
debug: /File[/var/lib/puppet/facts/gem_passenger_version.rb]: Creating 
checksum {md5}beb690f2fa867fa7eba1d558d2e601e1
debug: Calling fileserver.describe
debug: Calling fileserver.list
debug: /File[/var/lib/puppet/facts/iscsi.rb]/checksum: Initializing checksum 
hash
debug: /File[/var/lib/puppet/facts/iscsi.rb]: Creating checksum 
{md5}db4caff9c377021561ee3ba8fe461bc4
debug: Calling fileserver.describe
debug: Finishing transaction 23456253180400 with 0 changes
info: Loading fact sysinfo
info: Loading fact gem_passenger_version
info: Loading fact iscsi
debug: Retrieved facts in 2.44 seconds
debug: Retrieving catalog
debug: Calling puppetmaster.getconfig
err: Could not retrieve catalog: Exported resource Sshkey[10.10.12.14] cannot 
override local resource on node humpty.ebrary.com
warning: Not using cache on failed catalog


Any help you can provide is greatly appreciated!

 - Stefano


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Luke Kanies

2009-May-12 21:09 UTC

head link

[Puppet Users] Re: Problem with storeconfigs

On May 12, 2009, at 12:13 PM, Stefano Harding wrote:
> Hello all,
>
> I have what is certainly a stupid problem on my part. I have setup  
> puppet in a test environment and it''s been working wonderfully. I
am
> now in the process of moving this to our production systems and I  
> have rebuilt our puppetmaster completely from scratch using the same  
> modules/manifests, etc. from my test system.
Looks like you emailed this to the old puppet-users@madstop.com list;  
you should sign on to the new google group.
>
> Unfortunately I am running into an issue with what I assume is  
> storeconfigs:
>
> I setup the puppetmaster, ran the puppet client on it, no problems.
> Setup a second puppet client, no problems.
> On the third client I get the following error:
>
> debug: Calling puppetmaster.getconfig
> err: Could not retrieve catalog: Exported resource  
> Sshkey[10.10.12.14] cannot override local resource on node  
> humpty.ebrary.com
> warning: Not using cache on failed catalog
This problem is usually a result of two hosts defining the same key.   
Look in the db for a resource whose type is sshkey and title is  
10.10.12.14.  Something like:

select * from resources where restype = "sshkey" and title =  
"10.10.12.14";

Most likely, you''ll have two in there, and you can follow the host id  
back to who''s defining them.


-- 
I don''t know the key to success, but the key to failure is trying to
please everybody. -- Bill Cosby
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Greg

2009-Jun-23 01:17 UTC

head link

[Puppet Users] Re: Problem with storeconfigs

Hi all,

I''ve come across this problem and in my case its a *slight*
difference...

Basically when I jumpstart a host on Solaris, the initial hostname is
sans
domainname. After running through puppet for the first time, puppet
decides
that the hostname includes a domain name because puppet is
responsible
for putting in a resolv.conf file (I bootstrap it using hosts files).
Heres what
I''m seeing:

Jun 23 10:59:00 client puppetd[4037]: [ID 702911 daemon.error] Could
not retrieve catalog: Exported resource Sshkey[client] cannot override
local resource on node client.domain.com
Jun 23 10:59:00 client puppetd[4037]: [ID 702911 daemon.warning] Not
using cache on failed catalog

I''m thinking I may have to bootstrap the domain into the system before
puppet
runs, which is kind of annoying, as I would like puppet to handle as
much initial
setup as possible...

Greg

On May 13, 7:09 am, Luke Kanies <l...@madstop.com>
wrote:> On May 12, 2009, at 12:13 PM, Stefano Harding wrote:
>
> > Hello all,
>
> > I have what is certainly a stupid problem on my part. I have setup  
> > puppet in a test environment and it''s been working
wonderfully. I am  
> > now in the process of moving this to our production systems and I  
> > have rebuilt our puppetmaster completely from scratch using the same  
> > modules/manifests, etc. from my test system.
>
> Looks like you emailed this to the old puppet-us...@madstop.com list;  
> you should sign on to the new google group.
>
>
>
> > Unfortunately I am running into an issue with what I assume is  
> > storeconfigs:
>
> > I setup the puppetmaster, ran the puppet client on it, no problems.
> > Setup a second puppet client, no problems.
> > On the third client I get the following error:
>
> > debug: Calling puppetmaster.getconfig
> > err: Could not retrieve catalog: Exportedresource 
> > Sshkey[10.10.12.14]cannotoverridelocalresourceon node  
> > humpty.ebrary.com
> > warning: Not using cache on failed catalog
>
> This problem is usually a result of two hosts defining the same key.  
> Look in the db for aresourcewhose type is sshkey and title is  
> 10.10.12.14.  Something like:
>
> select * from resources where restype = "sshkey" and title =  
> "10.10.12.14";
>
> Most likely, you''ll have two in there, and you can follow the host
id  
> back to who''s defining them.
>
> --
> I don''t know the key to success, but the key to failure is trying
to
> please everybody. -- Bill Cosby
> ---------------------------------------------------------------------
> Luke Kanies |http://reductivelabs.com|http://madstop.com--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Nigel Kersten

2009-Jun-23 14:18 UTC

head link

[Puppet Users] Re: Problem with storeconfigs

On Mon, Jun 22, 2009 at 6:17 PM, Greg<greg.boug@gmail.com>
wrote:>
> Hi all,
>
> I''ve come across this problem and in my case its a *slight*
> difference...
>
> Basically when I jumpstart a host on Solaris, the initial hostname is
> sans
> domainname. After running through puppet for the first time, puppet
> decides
> that the hostname includes a domain name because puppet is
> responsible
> for putting in a resolv.conf file (I bootstrap it using hosts files).
Are you completely wedded to the idea of using FQDN as your certname?

We generate GUIDs here for certnames.

I''m assuming the certname is your problem here, not the actual
hostname?
> Heres what
> I''m seeing:
>
> Jun 23 10:59:00 client puppetd[4037]: [ID 702911 daemon.error] Could
> not retrieve catalog: Exported resource Sshkey[client] cannot override
> local resource on node client.domain.com
> Jun 23 10:59:00 client puppetd[4037]: [ID 702911 daemon.warning] Not
> using cache on failed catalog
>
> I''m thinking I may have to bootstrap the domain into the system
before
> puppet
> runs, which is kind of annoying, as I would like puppet to handle as
> much initial
> setup as possible...
>
> Greg
>
> On May 13, 7:09 am, Luke Kanies <l...@madstop.com> wrote:
>> On May 12, 2009, at 12:13 PM, Stefano Harding wrote:
>>
>> > Hello all,
>>
>> > I have what is certainly a stupid problem on my part. I have setup
>> > puppet in a test environment and it''s been working
wonderfully. I am
>> > now in the process of moving this to our production systems and I
>> > have rebuilt our puppetmaster completely from scratch using the
same
>> > modules/manifests, etc. from my test system.
>>
>> Looks like you emailed this to the old puppet-us...@madstop.com list;
>> you should sign on to the new google group.
>>
>>
>>
>> > Unfortunately I am running into an issue with what I assume is
>> > storeconfigs:
>>
>> > I setup the puppetmaster, ran the puppet client on it, no
problems.
>> > Setup a second puppet client, no problems.
>> > On the third client I get the following error:
>>
>> > debug: Calling puppetmaster.getconfig
>> > err: Could not retrieve catalog: Exportedresource
>> > Sshkey[10.10.12.14]cannotoverridelocalresourceon node
>> > humpty.ebrary.com
>> > warning: Not using cache on failed catalog
>>
>> This problem is usually a result of two hosts defining the same key.
>> Look in the db for aresourcewhose type is sshkey and title is
>> 10.10.12.14.  Something like:
>>
>> select * from resources where restype = "sshkey" and title
>> "10.10.12.14";
>>
>> Most likely, you''ll have two in there, and you can follow the
host id
>> back to who''s defining them.
>>
>> --
>> I don''t know the key to success, but the key to failure is
trying to
>> please everybody. -- Bill Cosby
>> ---------------------------------------------------------------------
>> Luke Kanies |http://reductivelabs.com|http://madstop.com
> >
>


-- 
Nigel Kersten
nigelk@google.com
System Administrator
Google, Inc.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Possibly Parallel Threads

Search for more maybe matching threads

Puppet users - May 2009 - Problem with storeconfigs

[Puppet Users] Problem with storeconfigs

[Puppet Users] Re: Problem with storeconfigs

[Puppet Users] Re: Problem with storeconfigs

[Puppet Users] Re: Problem with storeconfigs

Possibly Parallel Threads