Can someone please help me out with this issue?
On Thu, Feb 7, 2013 at 6:39 PM, Rakesh Kathpal wrote:
> Please see.. if you can help me out in this issue...
>
> Appreciate your efforts..
>
> -- Forwarded message --
> From: Rakesh Kathpal
> Date: Thu, Feb 7, 2013 at 4:48 PM
> Sub
Hi,
Version of puppet master - 3.0.2
Version of puppet client- 3.0.2
I have declared in [master] section.
On Saturday, February 9, 2013 7:59:06 AM UTC+5:30, denmat wrote:
>
> Hi,
>
> Couple of questions:
> What version of puppet?
> What section of the puppet conf do you have those opt
+1 for packaging natively (deb, rpm, etc) and using the Puppet "package"
resource to deliver/install it. Life will be much better this way ;)
On Sun, Feb 10, 2013 at 2:18 PM, Jakov Sosic wrote:
> On 02/10/2013 11:09 PM, Andreas Hilboll wrote:
>
>> Hi,
>>
>> I would like to install Piwik [*], wh
On 02/10/2013 11:09 PM, Andreas Hilboll wrote:
Hi,
I would like to install Piwik [*], which is a PHP webstatistics package,
on some of my nodes, using Puppet. The underlying servers are running
Debian Squeeze. Piwik is distributed as a .zip or .tar.gz file, which is
available at their website. T
Hi,
I would like to install Piwik [*], which is a PHP webstatistics package,
on some of my nodes, using Puppet. The underlying servers are running
Debian Squeeze. Piwik is distributed as a .zip or .tar.gz file, which is
available at their website. They provide a constant URL always pointing
to the
http://lists.fedoraproject.org/pipermail/devel/2013-January/176011.html
https://fedorahosted.org/formulas/wiki/WikiStart
Hmm, difficult to tell. Perhaps someone here know more.
Best
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscri
- Original Message -
> From: "Ellison Marks"
> To: puppet-users@googlegroups.com
> Sent: Sunday, February 10, 2013 10:05:25 PM
> Subject: [Puppet Users] Re: warnings for those shifting from puppet kick to
> mcollective
>
> We use mco puppet runall 1 (our master is slightly anemic) in a
We use mco puppet runall 1 (our master is slightly anemic) in an every hour
cron job. We have few enough hosts that they can all run within the hour.
It's not quite as nice as the commander, as the commander would start
running them all immediately after the last one was done, but it works for
Looks like that was actually the problem. Searched google and came across
the fix. Had to change the type of the messages column to mediumtext and
the pending jobs started finishing. Did this by:
alter table report_logs change column message message VARCHAR(65536);
Just in case someone runs
Thanks Steven, I uploaded my code
to https://github.com/roadtest/plm-accounts and I will study your code in
the mean time.
cheers,
carl
On Sunday, February 10, 2013 12:07:15 AM UTC-5, Steven wrote:
>
> I'm not noticing the problem, but maybe it would help to see some other
> code.
> I just
On Sun, Feb 10, 2013 at 9:32 AM, Keith Burdis wrote:
> Have you looked at using hiera [1] for your configuration? It is very good
> for cascading defaults with more specific config at the top of the hierarchy
> and the least specific at the bottom. It is part of Puppet 3 and an add on
> for 2.7.
Thanks for pointing me to the log location. Looks like this might be the
cause of the problem:
--
..snip
2013-02-10T10:40:35-0800: [Worker(delayed_job.3 host:ssfpcond01 pid:25048)]
Report.create_from_yaml_file failed with ActiveRecord::StatementInvalid:
*Mysql::Error:
Data too long for column
Are you having the problem after running 'puppet agent --test' a few times
or it just happens without any manual run ?
I was having the same problem some days ago, in my case because I was
running 'puppet agent --test', more specifically the --show_diff that is
used in --test was automatically
Have you looked at using hiera [1] for your configuration? It is very good
for cascading defaults with more specific config at the top of the
hierarchy and the least specific at the bottom. It is part of Puppet 3 and
an add on for 2.7.
- Keith
[1]
http://www.devco.net/archives/2011/06/05/hiera_
On 2/6/2013 1:18 PM, Moses Mendoza wrote:
On Tue, Feb 5, 2013 at 1:15 AM, wrote:
I'm having trouble getting puppet dashboard (1.2.21) to run on apache.
i installed puppetmaster-passenger and puppet-dashboard package. It didn't
create user puppet-dashboard automatically as stated in the instal
Bryan Berry gave a talk at FOSDEM a couple of days ago about
integration testing for infrastructure
(https://speakerdeck.com/bryanwb/dont-shrug-integration-testing-for-infrastructure-with-ruby-frameworks).
He talked about a tool that's
come out of the Chef community called Test Kitchen, and pointed
Try looking in /usr/share/puppet-dashboard/log/.
Did you update the dashboard or puppet master recently? I have ran into
similar problems after updates, since I run the dashboard on a different
port than the external_nodes script uses. The DASHBOARD_URL in
/usr/share/puppet-dashboard/bin/extern
17 matches
Mail list logo