Re: [Puppet Users] Odd (fatal) error noted in logs

2013-10-02 Thread jcbollinger
On Tuesday, October 1, 2013 1:57:43 PM UTC-5, Ayers, Mike wrote: > > > From: puppet...@googlegroups.com [mailto:puppet- > > us...@googlegroups.com ] On Behalf Of Peter Berghold > > > What does "Could not prefetch package provider 'apt': invalid byte > > sequence in US-ASCII" mean exactly? Th

Re: [Puppet Users] Odd (fatal) error noted in logs

2013-10-01 Thread Simon Oakes
I also have been experiencing this same issue since puppet version 3.3.0-1 (latest) as well as with RC2 in the devel repo. With the previous version of 3.2.4-1 this behaviour was not present. After doing some testing/research the other day, I found that if you force locales to en_US.UTF-8 before y

Re: [Puppet Users] Odd (fatal) error noted in logs

2013-10-01 Thread David Schmitt
Actually, the ruby code for the apt provider is UTF-8 (most probably it has the BOM at the beginning). Puppet will ONLY run under an UTF-8 using locale. This is thanks to the "Great Idea[tm]" of the ruby interpreter that only allows source code in the locale of the running process. Regards, Da

Re: [Puppet Users] Odd (fatal) error noted in logs

2013-10-01 Thread Peter Berghold
Now I'm really confused... I use emacs and vi exclusively and neither of those should be US-ASCII. This leads me to wonder which file. Is it the provider itself or ??? On Tue, Oct 1, 2013 at 2:57 PM, Ayers, Mike wrote: > > From: puppet-users@googlegroups.com [mailto:puppet- > > us...@googlegro

RE: [Puppet Users] Odd (fatal) error noted in logs

2013-10-01 Thread Ayers, Mike
> From: puppet-users@googlegroups.com [mailto:puppet- > us...@googlegroups.com] On Behalf Of Peter Berghold > What does "Could not prefetch package provider 'apt': invalid byte > sequence in US-ASCII" mean exactly? This started showing up in the logs > of some of my servers... If a file