PBWebGuy
2010-Nov-04 17:16 UTC
[Puppet Users] Strange problem with StoredConfigs overwriting files with old versions
We just ran into a condition when a templatized configuration file would get replaced with something that I had no clue where it came from and the content is no where in the puppet source tree. On subsequent updates the proper file would appear. I''ve been able to consistently reproduce the problem on multiple nodes that have the same role. We discovered a discrepancy in the last modified dates of the file in question. When we ran the update the first time it would create a file with an old date. On the subsquent update it would generate it with today''s date. We figured then it was being cached. I therefore turned off stored configs and presto my issue disappeared. There appears to be a SERIOUS bug in stored configs that under certain conditions is stuffing the incorrect versions of files out on the node. Worse is that when watching the logs for the update, it shows the correct DIFF''s of the file being made and then under the covers it writes an old version of the file to the node. I''m curious if anyone has experienced anything like this before? Regards, John -- 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.
Joe McDonagh
2010-Nov-04 17:58 UTC
Re: [Puppet Users] Strange problem with StoredConfigs overwriting files with old versions
On 11/04/2010 01:16 PM, PBWebGuy wrote:> We just ran into a condition when a templatized configuration file > would get replaced with something that I had no clue where it came > from and the content is no where in the puppet source tree. On > subsequent updates the proper file would appear. I''ve been able to > consistently reproduce the problem on multiple nodes that have the > same role. > > We discovered a discrepancy in the last modified dates of the file in > question. When we ran the update the first time it would create a > file with an old date. On the subsquent update it would generate it > with today''s date. We figured then it was being cached. I therefore > turned off stored configs and presto my issue disappeared. > > There appears to be a SERIOUS bug in stored configs that under certain > conditions is stuffing the incorrect versions of files out on the > node. Worse is that when watching the logs for the update, it shows > the correct DIFF''s of the file being made and then under the covers it > writes an old version of the file to the node. > > I''m curious if anyone has experienced anything like this before? > > Regards, > > John > >Are you running the node that exports from its catalog to update the exported resource BEFORE you re run the collecting node catalog? You''ll see this fairly often with Nagios due to the $runinterval window between nodes, resulting in updated information taking something near $runinterval to update. -- Joe McDonagh AIM: YoosingYoonickz IRC: joe-mac on freenode "When the going gets weird, the weird turn pro." -- 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.
PBWebGuy
2010-Nov-05 17:23 UTC
[Puppet Users] Re: Strange problem with StoredConfigs overwriting files with old versions
Hi Joe, Thanks for you update. I eventually found that the problem wasn''t Puppet at all. As it turned out, when a new WAR file is being deployed, Tomcat will overwrite the tomcat/conf/Catalina/localhost/ ROOT.xml configuration file with the META-INF/context.xml file. This is something that I was never aware of. Regards, John On Nov 4, 1:58 pm, Joe McDonagh <joseph.e.mcdon...@gmail.com> wrote:> On 11/04/2010 01:16 PM, PBWebGuy wrote: > > > We just ran into a condition when a templatized configuration file > > would get replaced with something that I had no clue where it came > > from and the content is no where in the puppet source tree. On > > subsequent updates the proper file would appear. I''ve been able to > > consistently reproduce the problem on multiple nodes that have the > > same role. > > > We discovered a discrepancy in the last modified dates of the file in > > question. When we ran the update the first time it would create a > > file with an old date. On the subsquent update it would generate it > > with today''s date. We figured then it was being cached. I therefore > > turned off stored configs and presto my issue disappeared. > > > There appears to be a SERIOUS bug in stored configs that under certain > > conditions is stuffing the incorrect versions of files out on the > > node. Worse is that when watching the logs for the update, it shows > > the correct DIFF''s of the file being made and then under the covers it > > writes an old version of the file to the node. > > > I''m curious if anyone has experienced anything like this before? > > > Regards, > > > John > > Are you running the node that exports from its catalog to update the > exported resource BEFORE you re run the collecting node catalog? You''ll > see this fairly often with Nagios due to the $runinterval window between > nodes, resulting in updated information taking something near > $runinterval to update. > > -- > Joe McDonagh > AIM: YoosingYoonickz > IRC: joe-mac on freenode > "When the going gets weird, the weird turn pro."-- 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.