Puppet users - Jun 2008 - Question on Storeconfig timestamps in mysql

Hi,

I am working on setting auditing at my site.  For facts storeconfig 
works wonderfully and updates the fact_values timestamp everytime a fact 
changes, but for resources it does not seem to update the time stamp 
(e.g. I updated a file, the new file was copied to the client, but 
nothing showed with a new timestamp in the database).  Is this because I 
do not understand what is suppose to happen or a bug?  It would be great 
if the time stamps were updated because then I will have a history of 
changes made to the client.  Thanks in advance.

cheers,

ski

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

On Jun 11, 2008, at 4:27 PM, Ski Kacoroski wrote:
>
> Hi,
>
> I am working on setting auditing at my site.  For facts storeconfig
> works wonderfully and updates the fact_values timestamp everytime a  
> fact
> changes, but for resources it does not seem to update the time stamp
> (e.g. I updated a file, the new file was copied to the client, but
> nothing showed with a new timestamp in the database).  Is this  
> because I
> do not understand what is suppose to happen or a bug?  It would be  
> great
> if the time stamps were updated because then I will have a history of
> changes made to the client.  Thanks in advance.

As far as I understand it, the timestamps should definitely be  
updated, so this sounds like a bug.

Are other people seeing this behaviour?

-- 
You only have to be open minded if you''re wrong.
---------------------------------------------------------------------
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
-~----------~----~----~----~------~----~------~--~---

I also noticed that I am getting multiple entries for the same fact in 
the fact_names table (e.g. I have 6 entries for macosx_productversion). 
  Shouldn''t I just have one entry?  I am wondering if this is because I
had lots of machines all hitting the database within 50 seconds (the 
updated_at times range from 13:00:07 to 13:00:56).  Would it be ok to 
update all the tables so the records just use one of the fact names?

cheers,

ski

Luke Kanies wrote:
> On Jun 11, 2008, at 4:27 PM, Ski Kacoroski wrote:
> 
>> Hi,
>>
>> I am working on setting auditing at my site.  For facts storeconfig
>> works wonderfully and updates the fact_values timestamp everytime a  
>> fact
>> changes, but for resources it does not seem to update the time stamp
>> (e.g. I updated a file, the new file was copied to the client, but
>> nothing showed with a new timestamp in the database).  Is this  
>> because I
>> do not understand what is suppose to happen or a bug?  It would be  
>> great
>> if the time stamps were updated because then I will have a history of
>> changes made to the client.  Thanks in advance.
> 
> 
> As far as I understand it, the timestamps should definitely be  
> updated, so this sounds like a bug.
> 
> Are other people seeing this behaviour?
> 
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

On Jun 12, 2008, at 10:26 AM, Ski Kacoroski wrote:
> I also noticed that I am getting multiple entries for the same fact in
> the fact_names table (e.g. I have 6 entries for  
> macosx_productversion).
>  Shouldn''t I just have one entry?  I am wondering if this is
because I
> had lots of machines all hitting the database within 50 seconds (the
> updated_at times range from 13:00:07 to 13:00:56).  Would it be ok to
> update all the tables so the records just use one of the fact names?

Hmm, I am pretty sure the fact names should be normalized, so yeah,  
that seems like a problem, and it probably is a race condition, like  
you''re thinking (assuming you have more than six hosts; otherwise, it  
might just be a normalization issue).

It should be fine to update the tables.

-- 
I do not feel obliged to believe that the same God who has endowed us
with sense, reason, and intellect has intended us to forgo their use.
     -- Galileo Galilei
---------------------------------------------------------------------
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
-~----------~----~----~----~------~----~------~--~---