Setting system locales worked
Try running "dpkg-reconfigure locales"
Thanks,
Nawaid.
On Tuesday, May 21, 2013 10:43:06 AM UTC+1, David Schmitt wrote:
>
> On 19.05.2013 14:18, Mateusz Fiołka wrote:
> > I'm not sure if it is related to the services. It rather looks like
> > puppet related to m
Actually the umbrella bug is now.
http://projects.puppetlabs.com/issues/20522
On Mon, Sep 2, 2013 at 11:47 PM, William Van Hevelingen wrote:
> Found the bug that Jeff created
>
> http://projects.puppetlabs.com/issues/11303
>
>
> On Mon, Sep 2, 2013 at 11:42 PM, William Van Hevelingen
> wrote:
Found the bug that Jeff created
http://projects.puppetlabs.com/issues/11303
On Mon, Sep 2, 2013 at 11:42 PM, William Van Hevelingen wrote:
> I get the same error when running puppet-lint puppet 3.1.x regression?
>
> rake aborted!
> invalid byte sequence in US-ASCII
> /shadow/home/blkperl/.r
I get the same error when running puppet-lint puppet 3.1.x regression?
rake aborted!
invalid byte sequence in US-ASCII
/shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.2/lib/puppet-lint/lexer.rb:120:in
`[]'
/shadow/home/blkperl/.rvm/gems/ruby-1.9.3-p194/gems/puppet-lint-0.3.
On 19.05.2013 14:18, Mateusz Fiołka wrote:
I'm not sure if it is related to the services. It rather looks like
puppet related to me.
I'm having a similar problem on a newly created vps. When I do puppet
apply first time I get the message:
Error: Could not set 'present' on ensure: invalid byte se
I'm not sure if it is related to the services. It rather looks like puppet
related to me.
I'm having a similar problem on a newly created vps. When I do puppet apply
first time I get the message:
Error: Could not set 'present' on ensure: invalid byte sequence in US-ASCII
at 3:/root/mf-prod.pp
On Monday, February 18, 2013 11:02:05 PM UTC-6, Patrick wrote:
>
> No, but it's not related to the manifest. The manifest this resource is
> in actually hasn't changed in months. Also I can reboot the box and it goes
> away. Other boxes that aren't doing it will sometimes start doing it when
No, but it's not related to the manifest. The manifest this resource is
in actually hasn't changed in months. Also I can reboot the box and it
goes away. Other boxes that aren't doing it will sometimes start doing
it when they reboot. (at least that's the behaviour I've been observing,
but I have o
I just built a new puppet master, and whenever I run puppet on it, it
throws an error while processing a service resource:
# puppet agent -t
> Info: Retrieving plugin
> Info: Caching catalog for i-45dc2b1d
> Info: Applying configuration version 'g
> 9ea47ad19bc706a754c00f00a024309948d3ea03'
> Er