I just have to acknowledge that I too am seeing random problems with
puppet which have advanced to "persistent problems".
In the beginning it was fine, I installed ruby from sources, then
facter and then puppet and it worked like a charm.
Then, 2 months ago I noticed that puppet was just not fun
Sorry, I forgot to mention what I AM seeing in the logs:
---> Could not call fileserver.list: #<#: execution
expired>
b.
On Aug 30, 5:56 pm, Kurt wrote:
> Hello list,
>
> In our company we use puppet to configure our ec2 instances.
> we start our servers with fresh instances debian lenny, som
On Wednesday 02 September 2009 00:49:01 Joe McDonagh wrote:
> Hi Kurt, possibly some kind of weird clash between gems and packages,
> which is fairly common in deb/ubuntu if you mix gems with os-native
> dpkg. I have the .24.8 package from the pool ftp.ubuntu.com (analogous
> to ftp.debian.com) wh
Kurt wrote:
> Hello list,
>
> In our company we use puppet to configure our ec2 instances.
> we start our servers with fresh instances debian lenny, some small and
> some large.
>
> we install puppet like this:
> apt-get -y --force-yes install ruby1.8 rubygems1.8
> gem install puppet --include-dep
