I'm still not convinced this is a broken fact. I ran it in --trace with
"memoryfree" which definitely doesn't build a MySQL connection, and this
is the output:
[jg4461@radius-jg4461 ~]$ facter -p --debug --trace memoryfree
Found no suitable resolves of 1 for ec2_metadata
value for ec2_metadata
Try facter -p —debug or even facter -p —debug —trace to identify the broken
fact which does the mysql connection.
hth,
Martin
On 29 May 2015, at 13:51, Jonathan Gazeley
wrote:
> Yes, I tried running facter -p and it produces the same error. The same error
> also crops up when puppet or mcol
Yes, I tried running facter -p and it produces the same error. The same
error also crops up when puppet or mcollective execute facter too.
Thanks,
Jonathan
On 29/05/15 12:25, Martin Alfke wrote:
Have you tried running facter -p
This will also pull the pluginsynced facts.
(I am unsure which v
Have you tried running facter -p
This will also pull the pluginsynced facts.
(I am unsure which version has puppet facter)
On 29 May 2015, at 11:21, Jonathan Gazeley
wrote:
> Hi folks,
>
> Since upgrading to Puppet 3.8.1 my Facter (2.4.4) has been throwing this
> error every run:
>
> [jg44
Hi folks,
Since upgrading to Puppet 3.8.1 my Facter (2.4.4) has been throwing this
error every run:
[jg4461@webdev-ispms ~]$ facter
ERROR 2002 (HY000): Can't connect to local MySQL server through socket
'/var/lib/mysql/mysql.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server th
