James Turnbull wrote:
> * User type now manages password age
>
> We’ve add a new feature to user providers manages_password_age, along
> with the new properties password_min_age and password_max_age to the
> user type. These represent password minimum and maximum age in days.
> The useradd and use
And we're back with another exiting release in the 2.6.x branch - 2.6.2.
The first release candidate is now available.
2.6.2 is a maintenance release in the 2.6.x branch and it contains bug
fixes, maintenance and a small number of features (see Release Notes below).
We've include release notes b
http://projects.puppetlabs.com/issues/4904
Can Felix & Rob update the ticket with your use cases and requests?
Thanks
John
On 1 October 2010 09:01, John Warburton wrote:
> I'll file a bug
>
>
> On 1 October 2010 05:01, Nigel Kersten wrote:
>
>> On Thu, Sep 30, 2010 at 11:13 AM, Rob McBroom
This is not working (no username/password prompt when directing my
browser to the site). How do I troubleshoot this (where are the
access logs, etc...?)
On Thu, Sep 30, 2010 at 2:00 PM, Igal Koshevoy wrote:
> On Thu, Sep 30, 2010 at 3:58 AM, Tim Lank wrote:
>> puppet-users:
>>
>> I've got pupp
Felix Frank writes:
> On 09/30/2010 02:36 PM, Jeff wrote:
>
>> I'd love to use puppet as a tool to manage cron jobs across the
>> enterprise. Ideally, I'd like to chuck our expensive enterprise scheduling
>> package.
Yeah, that isn't going to happen, unless you use essentially zero of the
feature
I'll file a bug
On 1 October 2010 05:01, Nigel Kersten wrote:
> On Thu, Sep 30, 2010 at 11:13 AM, Rob McBroom
> wrote:
> > On Sep 30, 2010, at 12:37 PM, Nigel Kersten wrote:
> >
> >>> I noticed similar behaviour in Linux, with catastrophic results.
> >>> Ensure => present apparently always mean
Greg Haase wrote:
Are you aware of any documentation that clearly explains how this
collect/export functionality works?
Exporting and collecting resources relies on stored configuration[1]
being enabled on your Puppet Master. You should ensure that the database
is configured and working befor
Stephen,
Ah the David Schmitt nagios module. This is what I based my work on. I used
it as a model.
Are you aware of any documentation that clearly explains how this
collect/export functionality works?
Greg
On 9/30/10 3:31 PM, "Steven Wagner" wrote:
> Hi Greg,
>
> I'm on my phone at the mo
Hi Greg,
I'm on my phone at the moment so I don't have the exact link handy, but there
is a module on GitHub that works. I tinkered with it a lot in my old setup but
found most of my problems were due to not really understanding how the
collect/export functionality worked.
This is my favorite
Greetings,
I am working on getting Nagios implemented with Puppet so that when I add a
node to Puppet a Nagios configuration file is generated.
I can get nagios installed and configured on the server and the client with
no problems. Yet getting the client configuration file on to the server is
On Thu, Sep 30, 2010 at 11:13 AM, Rob McBroom wrote:
> On Sep 30, 2010, at 12:37 PM, Nigel Kersten wrote:
>
>>> I noticed similar behaviour in Linux, with catastrophic results.
>>> Ensure => present apparently always means "in fstab, but not mounted",
>>> which not only doesn't make much sense to
On Sep 30, 2010, at 12:37 PM, Nigel Kersten wrote:
>> I noticed similar behaviour in Linux, with catastrophic results.
>> Ensure => present apparently always means "in fstab, but not mounted",
>> which not only doesn't make much sense to me, but led me to never use
>> any ensure setting besides "m
On Thu, Sep 30, 2010 at 3:58 AM, Tim Lank wrote:
> puppet-users:
>
> I've got puppet-dashboard 1.0.3-3 setup using the rpm from here:
> http://yum.puppetlabs.com/base/
>
> Everything seems to work fine using the instructions from here:
> http://github.com/reductivelabs/puppet-dashboard
>
> I'm try
On Thu, 30 Sep 2010 03:58:29 -0700, Tim Lank wrote:
>
> puppet-users:
>
> I've got puppet-dashboard 1.0.3-3 setup using the rpm from here:
> http://yum.puppetlabs.com/base/
>
> Everything seems to work fine using the instructions from here:
> http://github.com/reductivelabs/puppet-dashboard
>
>
On Thu, Sep 30, 2010 at 1:31 AM, Felix Frank
wrote:
> On 09/30/2010 08:57 AM, John Warburton wrote:
>> Hi All
>>
>> I am not sure if I am doing this right, or just meeting some Solaris
>> specific thing that hasn't been catered for.
>>
>> Solaris 10, with puppet 0.25.5, and trying to manage /tmp.
On Thu, Sep 30, 2010 at 8:46 AM, D.N. van der Meijden
wrote:
> Here's the init script:
>
> (by the way, I changed the service to rsyslog [in the zabbix manifest
> file] and this works like a charm. So the service action works in
> puppet...)
>
> #! /bin/sh
> PATH=/bin:/usr/bin:/sbin:/usr/sbin:/etc
On Thu, Sep 30, 2010 at 6:20 AM, Daniel Maher wrote:
> I removed /var/lib/puppet/ssl/certs/.pem , then ran
> puppetd with --waitforcert . Unfortunately, when i run a
> puppetca --list --all , is not listed, even though there
> is very clearly a request pem in /var/lib/puppet/ssl/certificate_requ
Here's the init script:
(by the way, I changed the service to rsyslog [in the zabbix manifest
file] and this works like a charm. So the service action works in
puppet...)
#! /bin/sh
PATH=/bin:/usr/bin:/sbin:/usr/sbin:/etc/zabbix:/etc/zabbix/bin:/etc/
zabbix/sbin
DAEMON=/etc/zabbix/sbin/zabbix_age
Hi,
I previously had a similar problem trying to start a ruby app using
bundler that I eventually found to be caused by the non existence of the
$HOME environment variable, adding this using:
environment => "HOME=/home/user" to the exec command fixed it.
Could there be an environment differe
Can you post the init script?
Is it possible it's a PATH problem inside the script? Something that
works under your environment, but not under the user puppet is running
as?
On Thu, Sep 30, 2010 at 8:16 AM, D.N. van der Meijden
wrote:
> My bad!! I understand the puppet command now...
>
> clien
My bad!! I understand the puppet command now...
client:/tmp# puppet --verbose --debug --trace test.pp
debug: file /sbin/chkconfig does not exist
debug: file /usr/sbin/svcadm does not exist
debug: file /sbin/rc-update does not exist
debug: Creating default schedules
debug: Service[zabbix_agent](pro
My bad! Just checked out the puppet command :-s
Ok, output on my client is now:
client:/tmp# puppet --verbose --debug --trace test.pp
debug: file /sbin/chkconfig does not exist
debug: file /usr/sbin/svcadm does not exist
debug: file /sbin/rc-update does not exist
debug: Creating default schedules
>From what I understand using "puppet apply" will make no attempt to
contact the puppet master and so is useful for testing, but all your
Puppet config files must be local. The file you are applying should be
in CWD, or you can just:
puppet apply [options] /wherever/test.pp
As for your error outp
No problem Luke, thanks for helping me out here.
Since I'm still a puppet n00b, where should I place the test.pp? On
the host I presume (I tried /etc/puppet/manifests/test.pp) ?
test.pp:
class test {
service { "rsyslog":
name => "rsyslog",
enable=> true,
ensure=>
Please e-mail me off list if you're looking for a contract->perm
position in LA, close to LAX near Boeing and the other defense
companies. The role is fairly senior and involves mostly Linux and Unix
systems. Puppet experience is a win, also is OpenBSD for
routing/firewalling. More details to b
My apologies, I thought you were saying it starts but were unaware of
the exit code.
I'm now unsure... You could try run this:
puppet apply --verbose --debug --trace --summarize test.pp
where test.pp is the simplest form of your service as possible, and
see if you get anything useful, although I
Hi Luke,
As mentioned it works manually:
'client:~# /etc/init.d/zabbix_agent start ; echo $?
Starting Zabbix agent: zabbix_agentd
0
By the way, this specific client is a lenny 5.05
On 30 sep, 16:28, "luke.bigum" wrote:
> As Nigel indicated, the exit code for your init script is not what
> p
As Nigel indicated, the exit code for your init script is not what
puppet expects, it is not a file permission problem.
As Nigel suggested, shut down your service then run this:
/etc/init.d/zabbix_agent start ; echo $?
And tell us what number is printed on the screen. If it prints 1, that
would
Thanks for the quick reply Nigel.
I understand that the puppet is reporting back the exit status, but
what I don't understand is why it keeps failing when trying to start
via puppet.
All files are available on the client, permissions are ok and starting
the daemon manually works without problems.
On Thu, Sep 30, 2010 at 6:42 AM, D.N. van der Meijden
wrote:
> I'm trying to get a service running, but I keep getting the following
> error message:
> "err: //Node[debiannode]/zabbix/Service[zabbix_agent]/ensure: change
> from stopped to running failed: Could not start Service[zabbix_agent]:
> Ex
I'm trying to get a service running, but I keep getting the following
error message:
"err: //Node[debiannode]/zabbix/Service[zabbix_agent]/ensure: change
from stopped to running failed: Could not start Service[zabbix_agent]:
Execution of '/etc/init.d/zabbix_agent start' returned 1: at /etc/
puppet
On Wed, Sep 29, 2010 at 9:22 PM, Jeff McCune wrote:
> On Sat, Sep 25, 2010 at 2:45 PM, Nigel Kersten
> wrote:
>> What implications of introducing a new syntactical element are there?
>
> Yet another inconsistency and confusion for newbies.
>
> With that said, I think the benefits _far_ outweigh
On 09/29/2010 03:31 PM, Radek wrote:
maybe this will help:
minute => "2-57/5",
Lovely, thank you.
--
Daniel Maher
"The Internet is completely over." -- Prince
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send em
2010/9/30 Héctor Rivas Gándara :
>>> We have simple inheritance in our external node classifier like this:
>>> We only allow one level, and includes cannot include other includes.
>>> Parameters specified in a node yaml override the same parameter in an
>>> include yaml.
>>> Oh, and we have a defau
Hello,
We recently re-deployed puppet certificates in our environment. I
removed and regenerated the certificates for all of the clients save for
one : the puppetmaster server itself.
As one might expect, when i run puppetd --test on the puppetmaster
server, i get :
err: Could not request
>> We have simple inheritance in our external node classifier like this:
>> We only allow one level, and includes cannot include other includes.
>> Parameters specified in a node yaml override the same parameter in an
>> include yaml.
>> Oh, and we have a default node that all of this is appended t
Thanks for clearing this up!
On 27 sep, 17:27, Richard Crowley wrote:
> > With very few exceptions (that are all made for time savings so you
> > can ignore them safely) all resources (what you were calling phases)
> > must explicitly declare their dependencies on other resources using
> > before
On 09/30/2010 02:36 PM, Jeff wrote:
> Hi Puppeteers,
>
> I'd love to use puppet as a tool to manage cron jobs across the
> enterprise. Ideally, I'd like to chuck our expensive enterprise
> scheduling package. To do that, I need to get job failure
> notifications to the network operations center. C
Hi Puppeteers,
I'd love to use puppet as a tool to manage cron jobs across the
enterprise. Ideally, I'd like to chuck our expensive enterprise
scheduling package. To do that, I need to get job failure
notifications to the network operations center. Can someone suggest a
way I can accomplish that?
puppet-users:
I've got puppet-dashboard 1.0.3-3 setup using the rpm from here:
http://yum.puppetlabs.com/base/
Everything seems to work fine using the instructions from here:
http://github.com/reductivelabs/puppet-dashboard
I'm trying to setup basic security with the .htaccess file described
in
> We have simple inheritance in our external node classifier like this:
Actually, yaml itself allows the definition of Relational Trees
(http://en.wikipedia.org/wiki/YAML#Relational_trees) that allow you to
do something like:
- &linux
name: linux
parameters:
one_parameter: "value1"
ot
(Sorry, long post, and .. I'm replying via copy & paste from Google Groups)
On Wed, 15 Sep 2010 19:59:35 -0700 (PDT), Patrick wrote:
>Sounds like a job for Augeas or puppet-concat. I think puppet_concat =
>would be a better fit.
>Augeas: http://docs.puppetlabs.com/references/stable/type.html#aug
On 30 September 2010 05:26, Nigel Kersten wrote:
>
> We should be shipping the correct config.ru for you in the 2.6.x
> Debian packages. Did that not work?
Hi Nigel,
Yes, I got the new config.ru file with the Debian package, my mistake
was starting off with the Lenny packages then trying to sele
On 09/30/2010 08:57 AM, John Warburton wrote:
> Hi All
>
> I am not sure if I am doing this right, or just meeting some Solaris
> specific thing that hasn't been catered for.
>
> Solaris 10, with puppet 0.25.5, and trying to manage /tmp. Note that /tmp
> can't be remounted on a live system (
> ht
On Sep 29, 2010, at 3:45 PM, Christian wrote:
> /usr/sbin/puppetd:159:in `require': No such file to load -- puppet/
> application/puppetd (LoadError)
>from /usr/sbin/puppetd:159
>
> What went wrong here? Is there a bug in the rpm? Or do i have to set a
> path somewhere?
It seems you hav
Doug,
This was already fixed, but there was no official release since then.
You can either -
1. wait until a new version is released.. probably in 10 days to two weeks
time frame.
2. use the nightly snapshot, or directly from github (
http://theforeman.org/projects/foreman/wiki/Installation_instru
46 matches
Mail list logo
