Hi,
On 01/26/2012 08:14 PM, Jo Rhett wrote:
> One thing about a well-written piece of generic code is that it can be used
> in many environments. A lot of my modules do things like "do I have an
> external interface or am I behind the firewall?" and do different things
> based on those answers.
On 01/25/2012 04:40 PM, Christopher Wood wrote:
> Unfortunately I am unable to reproduce this except outside the target
> virtualized environment, currently unavailable due to resource concerns.
>
> So far courier-imap and courier-pop restart as they should elsewhere.
I recommend puppet agent --
Thanks Brice, using mod_rpaf fixed the issue! I've also realized why
puppet SHOULD NOT rely on the X-Forwarded-For for determining source
information to authorize API access. As soon as I had it working with
mod_rpaf I performed an API request with a hostname different than the
actual machine:
mal
Hi everyone,
I am using puppet 2.7.9 and ruby 1.8.7 on debian box. I don't a lot of
modules right now: just one module that create user + dotfile + ssh key and
compiled catalog takes around 70s do I have to worry is that big.
Does the compiled time scale with the module number? Do I have to make
Hi,
the code below will work, but it will not magically transfer file
contents as seen on host A to the master and from there to host B.
Any state you wish puppt to maintain you have to make known to puppet.
If you want puppet to pickup and process any piece of information from
an agent, you wil
Hi,
On 01/21/2012 08:02 PM, bhagyesh wrote:
> info: Applying configuration version '1327172288'
> notice: /Stage[main]/Networking::Resolver/File[/tmp/resolv.conf]/
> ensure: created
> debug: Finishing transaction 23673547908420
so it worked, didn't it?
Why did you reinstall your master? o_O
--
Hi John,
thanks for coming up with such elaborate ideas, your input to this group
adds a lot of meat to many discussions.
I can agree with a lot of what you wrote, barring the following remarks:
On 01/26/2012 06:00 PM, jcbollinger wrote:
> Modules provide definitions of resources that they own.
Hi,
On 01/24/2012 11:50 PM, Bryan Beaudreault wrote:
> I have a special init.d script that can
> handle this, but want to define the service multiple times in a puppet
> class.
I assume your new initscript declares a different Provides: tag than the
stock memcached initscript, yes?
Whatever this
Hello,
On Fri, Jan 27, 2012 at 15:20, Felix Frank
wrote:
> how I see need for
> explicit module dependencies and a system that can automatically
> download required modules from the forge. I can see this supplementing
> your idea of constraints nicely, but without it, downloading modules
> could
On 26/01/12 17:48, jcbollinger wrote:
> In particular, it is useful to recognize that dependencies are not just on a
> particular resource generally -- rather, they are on a particular resource
> having certain specific properties.
Yes.
Also: currently in Puppet one cannot say anything about a re
Hi,
On 01/27/2012 02:52 PM, Walter Heck wrote:
> There's something else we need to think about here. Some modules have
> a soft/conditional requirement for other modules. What I mean is that
> if you don't use certain parts of a module, you don't need the module
> that that part of the code refers
On Jan 26, 1:42 pm, Christopher Wood
wrote:
> On Thu, Jan 26, 2012 at 06:32:49PM +, Dan White wrote:
> > I am relatively new to both Puppet and ssh-keys,
> > but is it possible for the PuppetMaster to generate all the keys rather
> > that each client creating their own ?
>
> This might be one
On Jan 27, 7:20 am, Felix Frank
wrote:
> Hi John,
>
> thanks for coming up with such elaborate ideas, your input to this group
> adds a lot of meat to many discussions.
>
> I can agree with a lot of what you wrote, barring the following remarks:
>
> On 01/26/2012 06:00 PM, jcbollinger wrote:
>
>
Hi all,
I just upgraded a client with puppet 2.7.9 to 2.7.10 and now the
authorized_keys started to loop
notice: /Stage[main]/Authorizedkey::UserX/
Authorizedkey::Manage[userx_dss_domainx_test]/
Ssh_authorized_key[userx_dss_domainx_test]/options: options changed
'no-port-forwarding,no-agent-forwa
On Jan 26, 8:56 am, jimbob palmer wrote:
> Say you have a RHEL6 environment. You have some packages you want
> installed, these rely on a yumrepo. That yumrepo relies on an rpm-gpg key
> being installed.
>
> Now you get some RHEL5 boxes to add to the network. Your yumrepo RHEL6.2
> with a depend
Hi everyone,
I am trying to setup puppet-dashboard when trying to use the "rake
RAILS_ENV=production db:migrate" I have the following error:
# rake RAILS_ENV=production db:migrate
NOTE: Gem.source_index is deprecated, use Specification. It will be removed
on or after 2011-11-01.
Gem.source_index
On Jan 27, 4:02 am, Antidot SAS wrote:
> Hi everyone,
>
> I am using puppet 2.7.9 and ruby 1.8.7 on debian box. I don't a lot of
> modules right now: just one module that create user + dotfile + ssh key and
> compiled catalog takes around 70s do I have to worry is that big.
That's pretty exces
On Fri, Jan 27, 2012 at 10:27 AM, rvlinden
wrote:
> Hi all,
>
> I just upgraded a client with puppet 2.7.9 to 2.7.10 and now the
> authorized_keys started to loop
>
> notice: /Stage[main]/Authorizedkey::UserX/
> Authorizedkey::Manage[userx_dss_domainx_test]/
> Ssh_authorized_key[userx_dss_domainx_
Hi,
On 01/27/2012 04:22 PM, jcbollinger wrote:
> From a usability perspective, I think this is a far better proposal
> than anything else on the table:
I've thought of another plus. Even though the design proposal adds to
the DSL (and complexity is generally to be avoided), it does so in a
manner
Thanks
I run puppet on RHEL5 with Ruby 1.8.7
On Jan 27, 4:56 pm, Nan Liu wrote:
> On Fri, Jan 27, 2012 at 10:27 AM, rvlinden
>
>
>
>
>
> wrote:
> > Hi all,
>
> > I just upgraded a client with puppet 2.7.9 to 2.7.10 and now the
> > authorized_keys started to loop
>
> > notice: /Stage[main]/Autho
Hey thx for the answer...
the puppetmaster is an old Poweredge SC1425 with 2 Go of RAM and 4 CPU
(Intel Xeon 2.8Ghz)
Regarding the catalog it is playing a lot with hash tables... Trying to
figure out a way to show it to you... Attachment could be a way?
On Fri, Jan 27, 2012 at 4:55 PM, jcboll
On Fri, 2012-01-27 at 11:02 +0100, Antidot SAS wrote:
> Hi everyone,
>
>
>
>
> I am using puppet 2.7.9 and ruby 1.8.7 on debian box. I don't a lot of
> modules right now: just one module that create user + dotfile + ssh
> key and compiled catalog takes around 70s do I have to worry is that
> bi
70s sounds does sound a bit high for managing only three resources,
but more info is required before I can really answer your question.
How did you install Puppet? (OS packages, gem?)
What OS are you running, and can you provide some info about the
Hardware?
Also, if you have a sample of the mani
Hello, I'm new to puppet and am getting a puppet server setup with
puppet dashboard. I have the puppet server and puppet dashboard
(Apache/Passenger) setup and working well with 60+ test nodes working
as expected. Only problem is that I have this one error in the logs
which I can't figure out.
Jan
Hi,
First I would like to start of with a quote from
http://projects.puppetlabs.com/projects/puppet/wiki/Module_Ssh_Auth_Patterns.
"ssh::auth is currently in an unstable release. Please test it, and
report bugs and feature requests on the Puppet users mailing list. Based
on the results of peop
Since several weeks, both yum.puppetlabs.com and
downloads.puppetlabs.com are unreachable from some connections. This
is showing every time I check for updates in the repository.
It seems that there is a problem in routing. See:
traceroute to yum.puppetlabs.com (96.126.116.126), 30 hops max, 40
by
I am experiencing a curious event, and wondering if others have seen
this... As well, I have a question related to it.
Today, I noticed my puppet summary report from Foreman this morning,
that 60 of my 160 hosts all stopped reporting at nearly the exact same
time, and have not since restarted.
On Jan 27, 8:01 am, Felix Frank
wrote:
> Hi,
>
> On 01/27/2012 02:52 PM, Walter Heck wrote:
>
> > There's something else we need to think about here. Some modules have
> > a soft/conditional requirement for other modules. What I mean is that
> > if you don't use certain parts of a module, you do
Here are the info you wanted:
OS: Debian squeeze
Puppet: installed from gem version 2.7.9
As I sayed the hardware is an old Poweredge SC1425 with 4 Xeon 2,8 Ghz with
2 Go of Memory
Apparently the code is preety ugly since the compiled time is big, I have
just share the code:
https://github.com/jm
What the heck does this mean?
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
undefined method `fact_merge' for nil:NilClass
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
Only seems to be happening on one host in particular...
On Jan 27, 7:58 am, Nick wrote:
> On 26/01/12 17:48, jcbollinger wrote:
>
> > In particular, it is useful to recognize that dependencies are not just on a
> > particular resource generally -- rather, they are on a particular resource
> > having certain specific properties.
>
> Yes.
>
> Also: cur
On Fri, Jan 27, 2012 at 7:49 AM, Antidot SAS wrote:
> Hi everyone,
>
>
> I am trying to setup puppet-dashboard when trying to use the "rake
> RAILS_ENV=production db:migrate" I have the following error:
> # rake RAILS_ENV=production db:migrate
> NOTE: Gem.source_index is deprecated, use Specificat
On Fri, Jan 27, 2012 at 2:59 AM, Erwin wrote:
> Since several weeks, both yum.puppetlabs.com and
> downloads.puppetlabs.com are unreachable from some connections. This
> is showing every time I check for updates in the repository.
>
> It seems that there is a problem in routing. See:
> traceroute
Hi,
Puppet's sister project, MCollective would do it. An alternative would be
something like Rundeck.
Den
On 28/01/2012, at 3:52, Kyle Mallory wrote:
> I am experiencing a curious event, and wondering if others have seen this...
> As well, I have a question related to it.
>
> Today, I notice
While you're logging into every host to install mcollective, there are some
other things to think about (that are easily puppetizeable):
-remote syslogging, so that lots of logs don't cause application hosts to clot
-file system monitoring for your hosts, so you get an alert before things fill
u
Thread back from the dead 5 months later :)
Nan, using your code example, I get this with PE 2.0.1:
err: Could not retrieve catalog from remote server: Error 400 on
SERVER: Could not match ${ldapclient::params::fileroot}/${name},
at /etc/puppetlabs/puppet/modules/ldapclient/manifests/config.pp:3
On Jan 27, 11:10 am, Antidot SAS wrote:
> Here are the info you wanted:
> OS: Debian squeeze
> Puppet: installed from gem version 2.7.9
> As I sayed the hardware is an old Poweredge SC1425 with 4 Xeon 2,8 Ghz with
> 2 Go of Memory
>
> Apparently the code is preety ugly since the compiled time is
Downforeveryone... says the service is up. I can confirm this with a
traceroute from a VPS on another network (on which yum can check the
repository).
On my network bot URLs (which point to the same IP/server) still
cannot be reached. I tried several machines, but all can't reach this
server. And i
On Jan 27, 4:34 pm, jblaine wrote:
> Thread back from the dead 5 months later :)
>
> Nan, using your code example, I get this with PE 2.0.1:
>
> err: Could not retrieve catalog from remote server: Error 400 on
> SERVER: Could not match ${ldapclient::params::fileroot}/${name},
> at /etc/puppetlab
John, I've no doubt the code is trash. I'm struggling through what I
consider to be an extremely obtuse declarative language. Thank
you for the advice.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
h
I think you are missing double quotes around:
${ldapclient::params::fileroot}/${name}
Sent from my iPhone
On Jan 27, 2012, at 17:35, jblaine wrote:
Thread back from the dead 5 months later :)
Nan, using your code example, I get this with PE 2.0.1:
err: Could not retrieve catalog from remote s
Indeed.
Trashing the entire defined resource idea 30 mins ago, and
simply trying:
class ldapclient::config {
case $sys_sshortai {
'RH6': {
file { '/etc/openldap/ldap.conf':
mode => '444',
source => "${ldapclient::params::fileroot}/${nam
At first, I fired the command:
puppet node_aws bootstrap --image ami-0166b168 --keyname Test_Server --
type t1.micro --group default --login root --keyfile /aws_key_pair/
Test_Server.pem
I got the error as:
notice: Creating new instance ...
notice: Creating new instance ... Done
notice: Creating t
I found this bug in Redmine that sounds like it could be your problem.
http://projects.puppetlabs.com/issues/3234
It looks like a long standing issue, but that Nick L is possibly on to a
solution. Could you review the ticket to see if this is what is affecting
you and if so post your newest info i
The errors are good at locating the source of your issues:
err: /Stage[main]/Ldapclient::Config/File[/etc/nslcd.conf]: Could not evaluate:
Could not retrieve information from environment production source(s)
puppet:///modules/ldapclient/files/RH6/ldapclient::config at
/etc/puppetlabs/puppet/modu
On Fri, Jan 27, 2012 at 3:17 PM, jblaine wrote:
> Indeed.
>
> Trashing the entire defined resource idea 30 mins ago, and
> simply trying:
>
> class ldapclient::config {
> case $sys_sshortai {
> 'RH6': {
> file { '/etc/openldap/ldap.conf':
> mode => '444',
>
Den and Gary, thanks for the replies.
I am trying to re-use the title (as I understand it). Can I not do that?
Do I have to type the name of the file as the title and also at the
end of my source => "${ldapclient::params::fileroot}/...", ?
Gary, I've removed '/files' as part of ${ldapclient::
47 matches
Mail list logo
