Forum: CFEngine Help
Subject: insert_type: file: delays of many hours
Author: davidlee
Link to topic: https://cfengine.com/forum/read.php?3,24674,24674#msg-24674
(cfengine community 3.1.4; RHEL 5.6 on about 20 systems.)
Most of our cfengine file-editing uses default insert_type ("literal") for its
insertion operations. Things generally work fine; our changes to master
cfengine configuration and data take effect on clients some 5-10 minutes
afterwards.
But we have one place (and want to have a few more) where we use insert_type of
"file". This is usually only triggered at system-installation time, so we
never really see it in day-to-day action. But occasionally we alter its master
template file, which should cause it to perform its action on the target file
on the client machines.
Yesterday, I altered the template file, and was surprised to see that nothing
happened on any client. So on a sample client I manually ran "cf-agent -KI",
and that triggered the expected repair of the target file to be done on that
client. Strange: why did it only work when run manually? I waited another 15
minutes and did the same on another client. Again, that triggered the promise
into action on that client. Strange again.
Went home for the night. Came back in this morning. Lo and behold, overnight
the client systems had, eventually over several hours, correctly updated
themselves.
But why the delay of up to five hours? Might there be some sort of hidden,
undocumented expireafter/ifelapsed stuff happening under insert_type of "file"?
(If this is a version 3.1.4 issue, note that we are trapped on 3.1.4 by a
serious cfengine segfault bug (839) preventing us from upgrading...)
_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
https://cfengine.org/mailman/listinfo/help-cfengine
