Puppet users - Aug 2007 - PuppetDatabase - collection "yes", anything in db "no"

Hi there!

I´m trying to get my PuppetmasterDB running.
Problem is, though I´m not getting any errors from the puppetmaster
there is nothing stored in the database, not even tables are created. I
tried "puppetmasterd --dbmigrate", didn´t help either.
rails.log is kinda empty too..

Thing is: it kinda works anyway, there is just nothing stored in the DB
- exported a user on host A, collected that user on host B and it worked
fine, same thing with the ssh-example from the VirtualRessources page.

Either I missunderstand the sentence "You must set the storeconfigs
configuration parameter to true to enable this functionality, and Puppet
will automatically create a database for storing configurations (using
Ruby on Rails <http://rubyonrails.org>).", especially the
"Puppet will
automatically create a database" part or there is something going wrong
here..

Or is there a .sql file or something I just didn´t find?


What I Did (TM):

- installed MySQL on same host as Puppetmaster
- created db (puppetdb)
- crated user/pass(puppetdb/puppetdb)
- granted rights
- manually added a table just to check - works

Puppetmaster configured to use that DB:
#puppet.conf
[puppetmasterd]
storeconfigs = true

[rails]
dbadapter = mysql
dbserver = localhost
dbname = puppetdb
dbuser = puppetdb
dbpassword = puppetdb
#

#rails.log
Defined connections: {}
Active connections: {}
Active connection name:
#


Thanks for taking a look!

cheers
Simon
_______________________________________________
Puppet-users mailing list
Puppet-users@madstop.com
https://mail.madstop.com/mailman/listinfo/puppet-users

On Aug 15, 2007, at 12:54 PM, Simon Mügge wrote:
> [rails]
> dbadapter = mysql
> dbserver = localhost
> dbname = puppetdb
> dbuser = puppetdb
> dbpassword = puppetdb
This information needs to be in the ''puppetmasterd'' section,
not the
rails section.  Looks like your data is being stored in an sqlite3 db  
(look in $statedir).

Any ideas where I should document this?

  --
  The Roman Rule
          The one who says it cannot be done should never interrupt the
          one who is doing it.
  ---------------------------------------------------------------------
  Luke Kanies | http://reductivelabs.com | http://madstop.com

Luke Kanies schrieb:
> On Aug 15, 2007, at 12:54 PM, Simon Mügge wrote:
>   
>> [rails]
>> dbadapter = mysql
>> dbserver = localhost
>> dbname = puppetdb
>> dbuser = puppetdb
>> dbpassword = puppetdb
>>     
>
> This information needs to be in the ''puppetmasterd''
section, not the
> rails section.  Looks like your data is being stored in an sqlite3 db  
> (look in $statedir).
>   
D`oh!
> Any ideas where I should document this?
>   
Hm, it said here 
http://reductivelabs.com/trac/puppet/wiki/ConfigurationReference that 
these params belong in the section "rails" so I thought they belong in
the section "rails"... ;)
As this is autogenerated there is no chance to quickfix this right there 
I suppose?

I think the best thing is to enhance the 
http://reductivelabs.com/trac/puppet/wiki/PuppetmasterDatabase page so 
that it includes a "how to end up with a working PuppetmasterDB"
section.
Yes, I am willing to do that and I will do it in the course of this week. ;)


And thanks a lot for the fast reply!
>   --
>   The Roman Rule
>           The one who says it cannot be done should never interrupt the
>           one who is doing it.
>   ---------------------------------------------------------------------
>   Luke Kanies | http://reductivelabs.com | http://madstop.com
>
>
> _______________________________________________
> Puppet-users mailing list
> Puppet-users@madstop.com
> https://mail.madstop.com/mailman/listinfo/puppet-users
>

On Aug 15, 2007, at 2:12 PM, Simon Mügge wrote:
> Hm, it said here
> http://reductivelabs.com/trac/puppet/wiki/ConfigurationReference that
> these params belong in the section "rails" so I thought they
belong in
> the section "rails"... ;)
Hmm.  This has come up before; I should probably just remove the  
mention of the sections, since they''re only useful for developers.

The top of that file actually describes how the sections work;  
hopefully it''s clear enough.
> As this is autogenerated there is no chance to quickfix this right  
> there
> I suppose?
It''s very easy for me to regenerate, but at the least I''d have
to
change the format of the docs, which I''m not sure I should actually do.

  --
  Man is the only animal that can remain on friendly terms with the
  victims he intends to eat until he eats them.
                  -- Samuel Butler (1835-1902)
  ---------------------------------------------------------------------
  Luke Kanies | http://reductivelabs.com | http://madstop.com

Luke Kanies schrieb:
> On Aug 15, 2007, at 2:12 PM, Simon Mügge wrote:
>
>   
>> Hm, it said here
>> http://reductivelabs.com/trac/puppet/wiki/ConfigurationReference that
>> these params belong in the section "rails" so I thought they
belong in
>> the section "rails"... ;)
>>     
>
> Hmm.  This has come up before; I should probably just remove the  
> mention of the sections, since they''re only useful for developers.
>
> The top of that file actually describes how the sections work;  
> hopefully it''s clear enough.
>   
Yeah, now that I have read that..

I think I simply overlooked that because it is in the "On the 
Command-Line" section and how to supply options to an executable is 
quite clear because of the 3 examples - so I didn´t bother to read the 
lines above I think..
Maybe that info (sections!=executables / each option avalible to every 
executable) should just be moved up one section ("general information"
whatever) so it jumps right at you (and its not related to cli at any 
rate)!?

cheers

Simon Mügge wrote:
> I think I simply overlooked that because it is in the "On the 
> Command-Line" section and how to supply options to an executable is 
> quite clear because of the 3 examples - so I didn´t bother to read the 
> lines above I think..
> Maybe that info (sections!=executables / each option avalible to every 
> executable) should just be moved up one section ("general
information"
> whatever) so it jumps right at you (and its not related to cli at any 
> rate)!?
> 
Ditto but whilst "sections != executables and each option available to
every executable" you need to be clear in other documentation/errors etc
that sometimes particular configuration options need to into particular
namespaces to turn on that functionality.  For example, saying you need
to turn on storeconfigs isn''t always a helpful error message if you
don''t know which namespace to turn it on for:

"To do blah you need to turn on storeconfigs in the [puppetmasterd]
section of your configuration..."  or something less clumsy.

Regards

James Turnbull