Custom Facts not Storing
Hi! I have about a dozen custom facts, which until relatively recently were all being stored fine in PuppetDB. I use a curl command from one of my servers to retrieve the whole facts database and produce a simple webpage detailing these over my server estate (~150 linux servers)
About a month ago I noticed that some of these were reporting some of the facts incorrectly. When I log on to these servers and check using 'facter -p' the facts are reporting correctly, yet from the remote server the facts are simply not present. One example is a very simple ...
On a node with missing facts, can you add a notify { "factname = $factname": } to its manifest to see if the master receives the fact value at all?
hi - thanks for the reply. sorry, but i'll need a bit of handholding here.. do you mean notify { "factname = $factname": } explicitly, or for my simple example, notify { "mysql_version = $mysql_version ...(more)
Great. Thanks. mysql_version =... indicates that the master does not in fact bind a value to $mysql_version. Your custom fact is not transmitted correctly. Try enabling debug output on the agent ...(more)
if i run puppet agent -t on the affected node, i see this: Notice: mysql_version = 5.6.12 Notice: /Stage[main]/Main/Node[brpdecl01]/Notify[mysql_version = 5.6.12]/message ...(more)
ok, this is getting weirder. starting puppet with 'puppet agent -t' causes the fact to be correctly reported to the master. starting it with our usual way (service puppet start ...(more)