Ah ok I see, I thought as a test to manage the puppet client first
would be a good thing,
thank your for your answer, then I will go with something like ntp for
a test.
cu
stefanero
On 24 Mrz., 04:16, Denmat wrote:
> Hi,
>
> If you try to restart the client during the update, won't that confus
On Tue, Mar 22, 2011 at 10:40 PM, Cody Robertson wrote:
> On 03/22/2011 04:32 PM, Ohad Levy wrote:
>
>
>
> On Tue, Mar 22, 2011 at 10:28 PM, Cody Robertson wrote:
>
>> On 03/22/2011 04:23 PM, Ohad Levy wrote:
>>
>>
>> On Tue, Mar 22, 2011 at 10:04 PM, Eduardo S. Scarpellini <
>> scarpell...@gma
Hi,
On 03/23/2011 07:13 PM, Peter Gillard-Moss wrote:
> Hi,
>
> I have an interesting problem with groups and users.
>
> Our puppet configuration is nice and modular so each application we wish
> to install has its own class. For some applications we want to add
> existing users, created in ano
On 03/23/2011 11:49 PM, Michel wrote:
> Hello;
>
> Is there any documentation on how to perform a puppet upgrade? I
> download the tarball and extracted it to my copied puppetmaster
> server. Right now I have all the node definitions working, but any
> modules are not working.
> (not even a simp
> It's not at all clear to me what this is supposed to do. Perhaps you want to
> class App3 {
> include App1::with_app3_support
> }
>
> and
>
> class App3::with_app3_support inherits App3 {
> User["app1user"] { groups +> [ "app3users" ] }
> }
Grr. That's what you get for over-paraphrasing ;-
I need to adjust the runinterval for example, because 30min is way to
often when you change something once a month.
Therefor I would have to update the puppet.conf file , and then give
the client a restart to take its new config.
Well I did another test,
took out puppet.conf from the service defin
On Mar 24, 6:33 am, stefanero wrote:
> I need to adjust the runinterval for example, because 30min is way to
> often when you change something once a month.
Naturally you do need to choose a run interval that is appropriate for
your situation. Do remember, however, that Puppet is about more th
So set up new node, ran on the client
puppetd --server puppetmaster --waitforcert 60 --test
on the puppetmaster itself I ran
puppetca --list
saw the hostname
and then ran:
puppetca --sign hostname.domain.com
and on the puppet node itself I went back and ran puppetd -tv
and get the following
I was fighting with this issue today. Try to use FQDN in 'server' directive.
On 24.03.2011 16:50, Mike Franon wrote:
So set up new node, ran on the client
puppetd --server puppetmaster --waitforcert 60 --test
on the puppetmaster itself I ran
puppetca --list
saw the hostname
and then ran:
p
Hi all,
I've noticed that puppet-dashboard takes a lot of time to refresh some
webs, but today, I've started to remove some old nodes and it takes
more than 10 minutes to remove one.
The host hasn't a really high load:
[root@puppet01 ~]# uptime
16:54:31 up 14 days, 5:17, 1 user, load average
On 24 Mar 2011, at 16:57, Arnau Bria wrote:
> Hi all,
>
> I've noticed that puppet-dashboard takes a lot of time to refresh some
> webs, but today, I've started to remove some old nodes and it takes
> more than 10 minutes to remove one.
>
> The host hasn't a really high load:
>
> [root@puppet0
On Thu, 24 Mar 2011 17:06:33 +0100
Stefan Goethals wrote:
> Dashboard removes the reports for nodes one by one...
> This can take a long time with many reports.
>
> Solutions :
> - Delete reports in the db with a delete statement.
> - run the cleanup rake task for reports as explained on the gith
Thanks,
Do you mean on the puppetmaster?
On Thu, Mar 24, 2011 at 11:22 AM, Sergey Zhuga wrote:
> I was fighting with this issue today. Try to use FQDN in 'server' directive.
>
> On 24.03.2011 16:50, Mike Franon wrote:
>>
>> So set up new node, ran on the client
>>
>> puppetd --server puppetmas
Hi John,
thnx you for an answer. I think cron might be a good option.
Stefanero
On 24 Mrz., 14:03, jcbollinger wrote:
> On Mar 24, 6:33 am, stefanero wrote:
>
> > I need to adjust the runinterval for example, because 30min is way to
> > often when you change something once a month.
>
> Natural
On Mar 24, 2011, at 9:06 AM, Stefan Goethals wrote:
> Dashboard removes the reports for nodes one by one...
> This can take a long time with many reports.
If this is true (and I have no reason to doubt it), it's Very Bad. I've filed
it as a bug:
http://projects.puppetlabs.com/issues/6828
If t
Yes, I'm experiencing the exact same problem when hitting the destroy
button. Mysql and ruby1.8 are eating all resources.
In my test env I had the agent runinterval set to 600 seconds to get lots of
reports and stress the server a little. When I tried to take the node out of
service by hitting 'DE
There were a few very important changes we forgot to highlight in the
Dashboard v1.1.0rc1 release notes.
1. Reports will need to be converted to a new schematized format when
upgrading (#5459). Rather than just storing reports as serialized
YAML in the database as is currently done in v1.0.4, th
This rc addresses an issue when using Dashboard 1.1.0rc1 with Puppet
2.6.7rc1 when the Puppet master would have both storedconfigs, and the
inventory service enabled.
Bug #6791 - Fact lookup for a single node from Dashboard fails when
using storeconfigs
This is because the active_re
Hi again,
I'm cleaning my DB (which was 15GB) following:
https://github.com/puppetlabs/puppet-dashboard
I did:
rake RAILS_ENV=production reports:prune upto=1 unit=wk
rake RAILS_ENV=development reports:prune upto=1 unit=wk
(It has been running for about 3 months)
and after:
rake RAILS_ENV=pr
hello guys,
I am trying to incorporate run stages into my puppet setup. I've been
working with this for a few days and I haven't quite got the hang of
it yet...
When I attempt my puppet run this is the error I see:
[root@chromews21 ~]# puppet
This release addresses issues with the Puppet 2.6.x series and adds the
Inventory Service.
Inventory Service:
The inventory service is a way to track facts for all nodes.
Preliminary documentation can be found here[1], which will be
finalized by the time 2.6.7 is released.
[1]
https://g
On 03/24/2011 06:32 PM, Arnau Bria wrote:
Hi again,
I'm cleaning my DB (which was 15GB) following:
https://github.com/puppetlabs/puppet-dashboard
I did:
rake RAILS_ENV=production reports:prune upto=1 unit=wk
rake RAILS_ENV=development reports:prune upto=1 unit=wk
(It has been running for abo
disregard, didn't know I needed 2.6.7rc1 cheers
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegro
Hello all,
Backstop Solutions Group is looking for a Linux System Administrator to work in
our downtown Chicago office running our production environment along with some
dev and QA space. We're buzzword compliant (SaaS products, some Ruby on Rails,
etc), pretty DevOps-y (getting more so all th
On Fri, Mar 25, 2011 at 9:36 AM, Tim Dunphy wrote:
> hello guys,
>
> I am trying to incorporate run stages into my puppet setup. I've been
> working with this for a few days and I haven't quite got the hang of
> it yet...
>
>
> When I attempt my puppet run this is the error I see:
>
> --
I would suggest using Passenger. I am using CentOS 5.5 and the setup
is as follows:
Configure EPEL yum repository http://dev.antoinesolutions.com/epel-repository
for the RPM installer, or you can manually create an epel.repo file
in /etc/yum.repos.d
After the EPEL yum repo is set up run:
yum -y in
On 03/24/2011 06:49 PM, Cody Robertson wrote:
On 03/24/2011 06:32 PM, Arnau Bria wrote:
Hi again,
I'm cleaning my DB (which was 15GB) following:
https://github.com/puppetlabs/puppet-dashboard
I did:
rake RAILS_ENV=production reports:prune upto=1 unit=wk
rake RAILS_ENV=development reports:pru
Hi Cody,
Thanks for both replies!
tomorrow morning I'll take a look to links.
Cheers,
Arnau
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, sen
On Thu, Mar 24, 2011 at 5:10 PM, Thomas S Hatch wrote:
>
> These accelerated releases are going to keep us on our toes!
>
>
This is the downside of monthly releases, particularly when we have an
extra, out of cycle release like we did for 2.6.6.
If there's anything we can do in the Puppet commun
On Thu, Mar 24, 2011 at 5:42 PM, Nigel Kersten wrote:
>
>
> On Thu, Mar 24, 2011 at 5:10 PM, Thomas S Hatch wrote:
>
>>
>> These accelerated releases are going to keep us on our toes!
>>
>>
> This is the downside of monthly releases, particularly when we have an
> extra, out of cycle release like
Jacob Helwig wrote:
> This release addresses issues with the Puppet 2.6.x series and adds
> the Inventory Service.
For those using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople.org/repo/puppet/
Packages for EL 4 - 6 and Fedora 13 - 15 are available for test
On 25 March 2011 11:42, Nigel Kersten wrote:
> On Thu, Mar 24, 2011 at 5:10 PM, Thomas S Hatch wrote:
>
>> These accelerated releases are going to keep us on our toes!
>>
> This is the downside of monthly releases, particularly when we have an
> extra, out of cycle release like we did for 2.6.6.
* hai wu [2011-03-20]:
> I am interested in the details using cucumber-puppet to verify catalog
> compilation. Could you please elaborate on it?
I setup a catalog policy that applies to all catalogs, by specifying a
scenario for each of our servers like so:
@node
Given a node spec
Apologies - I haven't had time to test the release candidates. This is a
kicker for us, as I want to start using the new features from the dashboard
& inventory in 2.6.7
https://projects.puppetlabs.com/issues/6845
John
--
You received this message because you are subscribed to the Google Groups
34 matches
Mail list logo
