Jira (PDB-3058) Report not being stored in PuppetDB due to Unicode Error

[Wyatt Alt (JIRA)]

Title: Message Title

Wyatt Alt commented on PDB-3058   Re: Report not being stored in PuppetDB due to Unicode Error Jacky Leung I spent some time trying to reproduce your issue this morning but haven't been able to yet. Can you verify that the two queries here return counts of zero? psql -d puppetdb -c 'select count(*) from reports where metrics_json is not null' psql -d puppetdb -c 'select count(*) from reports where logs_json is not null' If either of those return nonzero counts, it means the database wasn't actually cleared on the move to 4.2.0. I think the PR linked in this ticket should fix the problem, though I can't say how quickly it'll be released. To get around this you'll need to figure out where the null byte is coming from. You might be able to enable the yaml store for reports (https://docs.puppet.com/puppet/latest/configuration.html#reports), and then once your nodes have checked in, grep through the directory for the word "binary". This will indicate where you've got binary data in the report. When I stick a null byte in one of my reports, I get data that looks like this: https://gist.github.com/wkalt/db5aa9b9d16a5ca4e9f3f873b8b4886d You may be able to grep for that base64 encoded string directly and get lucky, though I could imagine that depending on the representation. Once you find the null byte, it should be pretty easy to backtrack it to a manifest. Add Comment   This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.