This message was deleted.

Looks like one of your facts might have some sort of unicode value the fact parser doesn’t like, so it ends up breaking the plan where it’s trying to get facts from the node.

Is there a way to determine which fact it is and how to fix it?

Maybe take a look at the output of

facter -p

and see if anything looks funky

I did that. Puppet runs fine with no errors and nothing funky when I run

factor -p

\u0000

, which is the null byte, is also un-storable by Postgres as it uses that value to mark the end of a string. So, PuppetDB also fails to store any fact that includes it.

You could possibly try running

puppet task run facts --nodes <http://puppetcompiler-prod.com|puppetcompiler-prod.com>

, not sure if you’ll get more info or not

Could also try the following on the node that is failing:

facter -p --json | grep -a $'\u0000'