[Puppet Users] Re: Importing environmental variables from file via exec

[Przemek]

John, Thank You for excellent explanation!
Wrapping it all up into a single Exec works. Moreover now I understand how 
to puppet execute shell commands. 
Wrapping is now only way to deploy postgresql database in my environment.

Best Regards 

W dniu środa, 17 lipca 2013 09:56:34 UTC+2 użytkownik Przemek napisał:
>
> Hi Puppet Community,
>
> I prepare manifests and modules to deploy stuff that I need on agent. 
> During building postgres database I have to export some environmental UNIX 
> variables stored in "some_file.conf".
> Standard procedure to do this is simply run command:
>
> root@hostname:/path_to_config_file# . some_file.conf
>>
>
> and after this I see all exported variables ("env" command in terminal).
>
> Now when I trying do the same thing in puppet exec but variables wont 
> export (no error feedback from agent on debug mode).
> Puppet code:
>
> exec {"enviroments":
>> command => '/bin/sh -c ". some_file.conf"',
>> path => ["/bin", "/usr/bin","/path_to_config_file"],
>> cwd => "/path_to_config_file",
>> refreshonly => false,
>> require => File["/path_to_config_file/some_file.conf"],
>> }
>>
>
> Puppet version: 3.1.1
> Distributor ID:Debian
> Description:Debian GNU/Linux 6.0.7 (squeeze)
> Release:6.0.7
> Codename:squeeze
>
> I will be very grateful for any help, clues or tips that lead me to 
> resolve this problem.
> P.S
> Sorry for my grammar and poor English.
>
> Best Regards
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Attention!!! Puppet pe-activemq not Starting

[Ripunjay Godhani]

getting error change from stopped to running failed: Could not start
Service[pe-activemq]: Execution of '/sbin/service pe-activemq start'
returned 1: at
/opt/puppet/share/puppet/modules/pe_mcollective/manifests/activemq.pp:25

also while doing

how to start  pe-activemq


Regards,
Ripunjay

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: 3.2.2 on CentOS 6.3, and "Did not receive certificate"

[Yaniv Kaul]

On Thursday, July 18, 2013 12:32:22 AM UTC+3, jcbollinger wrote:

>
>
> On Wednesday, July 17, 2013 12:25:18 PM UTC-5, Yaniv Kaul wrote:
>>
>>
>> How do I verify if multiple copies are installed?
>>
>
>
> I would suggest using the 'find' command on the master to look for files 
> and directories named 'puppet'.  Make sure all the results belong to the 
> same Puppet install.  In your case you might pass their full names to "rpm 
> -q -f" to verify that they all come from one or another of your installed 
> RPMs.  I don't know whether Forrie installed from RPM; if not, then that 
> part of it will need to be different for him.
>
>  
>
>> I'm using Foreman to manage the puppet master on the same host, but I 
>> don't think it has caused any issues. I don't think #1 above is what 
>> happened to me - I've tried with a completely new client.
>> I must emphasize that apart from the CA's certificate, I'm not seeing 
>> anything under 'puppet cert --list --all'.
>> Is there any debug flag I can enable to provide debug output on the 
>> master for the signing process?
>>
>>
> If you are running the master as a standalone daemon (i.e. using its 
> built-in "webrick" server) then you should be able to start it as
>
> puppet master --debug
>
> to enable debug logging.  If you are running the master under Passenger, 
> then you may be able to turn on debug logging by modifying your config.rufile 
> to pass the --debug option to the master.
>
>
> John
>
>
I've added debug to my config.ru and suddenly everything works - clients 
happily register. 
I'm not sure if I should be happy or sad, keep the debug or remove it...
Y. 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] puppet activemq not starting

[Ripunjay Godhani]

getting error change from stopped to running failed: Could not start
Service[pe-activemq]: Execution of '/sbin/service pe-activemq start'
returned 1: at
/opt/puppet/share/puppet/modules/pe_mcollective/manifests/activemq.pp:25

also while doing

how to start  pe-activemq


Regards,
Ripunjay

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: err: Could not request certificate when I run "puppet device"

[Piotr Jasiulewicz]

Hi,

have you solved the problem? Having the same issue.

Cheers,
Piotr

W dniu piątek, 17 maja 2013 15:04:22 UTC+1 użytkownik srivatsa rao napisał:
>
> Hello Gav and Meiji,
> I tried all the above.. still it doesn't solve my issue any further 
> suggestion? 
>
> my output when I run "puppet device --verbose"
>
> # puppet device --verbose
> info: starting applying configuration to sw1 at telnet://10.0.0.1/
> info: Creating a new SSL key for sw1
> err: Could not request certificate: Could not write 
> /var/opt/lib/pe-puppet/devices/sw1/ssl/private_keys/sw1.pem to 
> privatekeydir: Permission denied - 
> /var/opt/lib/pe-puppet/devices/sw1/ssl/private_keys/sw1.pem
> info: Creating a new SSL key for sw1
> err: Could not request certificate: Could not write 
> /var/opt/lib/pe-puppet/devices/sw1/ssl/private_keys/sw1.pem to 
> privatekeydir: Permission denied - 
> /var/opt/lib/pe-puppet/devices/sw1/ssl/private_keys/sw1.pem
> info: Creating a new SSL key for sw1
> err: Could not request certificate: Could not write 
> /var/opt/lib/pe-puppet/devices/sw1/ssl/private_keys/sw1.pem to 
> privatekeydir: Permission denied - 
> /var/opt/lib/pe-puppet/devices/sw1/ssl/private_keys/sw1.pem
> .
> .
> .
> .
>
> Thanks,
> Vatsa
>
> On Monday, 5 November 2012 13:17:05 UTC-8, Gavin Williams wrote:
>>
>> Try changing the file owner/group to match what you're running puppet 
>> as... 
>>
>> Gav
>>
>> On 5 November 2012 20:51, meiji wang  wrote:
>>
>>> Although I change the mode to 0777, Puppet forces the mode to 0750
>>>
>>> debug: /File[/var/opt/lib/pe-puppet/devices/certname/state]: 
>>> Autorequiring File[/var/opt/lib/pe-puppet/devices/certname]
>>> debug: /File[/var/opt/lib/pe-puppet/devices/certname/clientbucket]/mode: 
>>> mode changed '0777' to '0750'
>>> debug: /File[/var/opt/lib/pe-puppet/devices/certname/ssl]/mode: mode 
>>> changed '0777' to '0771'
>>> debug: /File[/var/opt/lib/pe-puppet/devices/certname/ssl/private]/mode: 
>>> mode changed '0777' to '0750'
>>> debug: /File[/var/opt/lib/pe-puppet/devices/certname/state]/mode: mode 
>>> changed '0777' to '1755'
>>> debug: 
>>> /File[/var/opt/lib/pe-puppet/devices/certname/ssl/private_keys]/mode: mode 
>>> changed '0777' to '0750'
>>> debug: /File[/var/opt/lib/pe-puppet/devices/certname/client_yaml]/mode: 
>>> mode changed '0777' to '0750'
>>> debug: /File[/var/opt/lib/pe-puppet/devices/certname/client_data]/mode: 
>>> mode changed '0777' to '0750'
>>> info: Creating a new SSL key for certname
>>> ..
>>> err: Could not request certificate: Could not write 
>>> /var/opt/lib/pe-puppet/devices/certname/ssl/private_keys/certname.pem to 
>>> privatekeydir: Permission denied - 
>>> /var/opt/lib/pe-puppet/devices/certname/ssl/private_keys/certname.pem
>>>
>>>
>>> then Puppet throws error message..
>>>
>>> Meiji
>>>
>>>
>>> On Monday, November 5, 2012 8:18:03 AM UTC-8, meiji wang wrote:

 1.   I get the following error when I run “puppet device’

 err: Could not request certificate: Could not write 
 /var/opt/lib/pe-puppet/**devices/certname/ssl/private_**keys/certname.pem 
 to privatekeydir: Permission denied - /var/opt/lib/pe-puppet/**
 devices/certname/ssl/private_**keys/certname.pem

 Any thought?


 Thanks,

>>>  -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Puppet Users" group.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msg/puppet-users/-/CEDQ4q9o5uEJ.
>>> To post to this group, send email to puppet...@googlegroups.com.
>>> To unsubscribe from this group, send email to 
>>> puppet-users...@googlegroups.com.
>>> For more options, visit this group at 
>>> http://groups.google.com/group/puppet-users?hl=en.
>>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Welcome Cloudsmith to Puppet Labs!

[Nikola Petrov]

Glad to hear this is coming. I am currently not using Geppetto for speed
considerations but I think that tools are lacking and Cloudsmith can
really change that!

-- 
Nikola

On Wed, Jul 17, 2013 at 07:05:53PM -0700, Nigel Kersten wrote:
> Some of you will already be familiar with Cloudsmith products such as
> Geppetto, an IDE for Puppet modules, and some of you may be familiar with
> the excellent work Cloudsmith folks like Henrik have done in areas like the
> Puppet core parser.
> 
> We've been working together for a while now, and today we're thrilled to
> announce the acquisition of Cloudsmith into the Puppet Labs family.
> 
> 
> There is more about the acquisition on our blog:
> https://puppetlabs.com/blog/cloudsmith-joins-puppet-labs/
> 
> For more info about the Puppet Module IDE Geppetto:
> 
> 
> Geppetto: A Puppet IDE (blog)
> http://bit.ly/12VlbCf
> 
> Geppetto 3.0 Overview (video)
> http://bit.ly/12wsqR8
> 
> Geppetto, A Puppet IDE and Your Favorite Backseat Driver (podcast)
> http://bit.ly/12Kz0SW
> 
> 
> 
> cheers,
> 
> Nigel Kersten
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to puppet-users+unsubscr...@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.
> For more options, visit https://groups.google.com/groups/opt_out.
> 
> 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] About Facter via YAML and mcollective

[Fabrice Bacchella]

I'm looking at
http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/FactsFacterYAML

If my understanding is right, just using this class can be dangerous because if 
puppet is run with a --tags that dooesn't match it, it will not be run. But 
some fact can be changer any way (fqdn, ssh tokens, …)

How guys do you ensure it will always be updated ?

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Choosing provider by properties?

[jcbollinger]

On Wednesday, July 17, 2013 1:29:20 PM UTC-5, Jakov Sosic wrote:
>
> Hi, 
>
> is it possible to choose the provider based on property? 
>
> For example, I'm trying to develop two different providers for same type 
> of resource. If i use path location on the local filesystem I want 
> provider "local" to be chosen, and if I use link property, then I want 
> provider "remote" to be chosen. 
>
> For example, this definition should chose provider 'local': 
>
> resource { 'a': 
>   path => '/some/local/disk.iso', 
> } 
>
>
> And this definition should chose provider 'remote': 
>
> resource { 'a': 
>   link => 'http://example.com/disk.iso', 
> } 
>
> Is this possible without manually specifying "provider => remote"? 
>
>

Not to my knowledge, no.

This is not the correct provider paradigm.  The provider for a given 
resource type used on a given node, if not specified explicitly, is 
supposed to be chosen based on the characteristics of the node, not of the 
resource.  You seem to be artificially separating your provider into two 
pieces.  My recommendation would be to create one provider whose behavior 
varies according to the resource's properties, instead of trying to make 
the choice between different providers depend on resource properties.

 

>
> Also, second question. It would be great if puppet could raise error in 
> case when both conflicting properties are set. For example this should 
> yeild an error: 
>
> resource { 'a': 
>   path => '/some/local/disk.iso', 
>   link => 'http://example.com/disk.iso', 
> } 
>
> Is this possible? 
>


I think you can use the property validation hook to accomplish this.  It is 
focused on validating individual properties, and there is no guarantee of 
which property will be validated first, but all you really need is to raise 
/ check a flag an the resource instance as part of the validation of each 
of those properties.  You raise an ArgumentError if the validation code for 
either property finds that the flag is already raised.  See 
http://docs.puppetlabs.com/guides/custom_types.html for general details on 
the property validation hook.


>
> If these questions are more suitable to puppet-dev list, I will post 
> them there. Thank you guys. 
>


No, puppet-dev is for discussion of the development of Puppet itself, not 
for questions about its use.  "Development" of Puppet manifests is a usage 
issue with respect to the Puppet program. 


John

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: err: Could not request certificate when I run "puppet device"

[srivatsa rao]

Hey,
I tried a Lotta things. Nothing seemed to work so I bought up a new VM and 
carefully installed puppet following steps on website and things started to 
work.

But I always had a doubt that I did not have the config file right or once its 
wrong the changes does not take effect, just my guess. Try with config file if 
it doesn't work just resort to re-install.

Vatsa

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Puppet agent process get stuck

[jcbollinger]

On Wednesday, July 17, 2013 12:00:13 PM UTC-5, yannig rousseau wrote:
>
> Hi, 
>
> 3 days ago, we had a production issue where the puppetmaster became 
> unreachable for 20 minute.
> All of the puppet clients which tried to connect at this time are now 
> failing :  "Run of Puppet configuration client already in progress; 
> skipping"
>
> Further investigation show that the puppet agent process is still running 
> on all of this clients 3 days later. I tried to kille the process on a 
> machine, and puppet service came back to normal for this machine.
>
> Is there a way to kill the process on all of the client ?
>


Puppet does not provide a built-in mechanism for this.  There is a variety 
of tools that could do it, but you would have to had already set them up.

 

> Is there a way to specify a timeout on the process ? This would permit to 
> discard the process without human action
>


Again, Puppet does not provide this as a built-in feature, but it should be 
possible to add external instrumentation to make it happen.  That would 
probably be facilitated by launching the agent periodically via a scheduler 
(such as cron) instead of running it in daemon mode.


John

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Permission problem on puppet master

[jcbollinger]

On Wednesday, July 17, 2013 10:17:50 AM UTC-5, Piotr Jasiulewicz wrote:
>
> Hi John
>
>
> there is no SELinux on this system. Issue still is an issue.. :/
>
>>
>>

Count me a bit dubious of that claim.  It's quite hard to find a Linux 
these days that does not at least have SELinux in the kernel.  But maybe 
you built a LFS system for yourself, or something.

If Puppet is anywhere in the ballpark with respect to characterizing the 
problem, then then it is some kind of failure writing a new file to an 
existing directory to which discretionary access controls permit access.  I 
already enumerated most of the variations on that theme that I could think 
of, but here's an amended summary:

   - blockage by SELinux 
   - filesystem mounted read-only
   - remote filesystem, with access blocked at the protocol level
   - (new) virtual machine, with access blocked by the virtualization layer
   - (new) filesystem is full

If none of those seem to apply then you may be able to get a clue as to 
what's happening by running the master under strace.


John

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Permission problem on puppet master

[Piotr Jasiulewicz]

Hi,

well resolved by changing the puppet version. There is no selinux on ubuntu 
by default.


Thanks,
Piotr

W dniu czwartek, 18 lipca 2013 14:31:00 UTC+1 użytkownik jcbollinger 
napisał:
>
>
>
> On Wednesday, July 17, 2013 10:17:50 AM UTC-5, Piotr Jasiulewicz wrote:
>>
>> Hi John
>>
>>
>> there is no SELinux on this system. Issue still is an issue.. :/
>>
>>>
>>>
>
> Count me a bit dubious of that claim.  It's quite hard to find a Linux 
> these days that does not at least have SELinux in the kernel.  But maybe 
> you built a LFS system for yourself, or something.
>
> If Puppet is anywhere in the ballpark with respect to characterizing the 
> problem, then then it is some kind of failure writing a new file to an 
> existing directory to which discretionary access controls permit access.  I 
> already enumerated most of the variations on that theme that I could think 
> of, but here's an amended summary:
>
>- blockage by SELinux 
>- filesystem mounted read-only
>- remote filesystem, with access blocked at the protocol level
>- (new) virtual machine, with access blocked by the virtualization 
>layer
>- (new) filesystem is full
>
> If none of those seem to apply then you may be able to get a clue as to 
> what's happening by running the master under strace.
>
>
> John
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Installing MSI failed with errror: The network name cannot be found.

[tinu]

Im trying to install the SCOMAgent.msi on Windows Server 2008 R2 with 
puppet version 2.7.19

I try this code and get the error "change from absent to present failed: 
Failed to install: The network name cannot be found.":

package {'System Center Operations Manager 2007 R2 Agent':
ensure=> installed,
provider => 'msi',
source=> 'C:\Install\MOMAgent.msi',
}


if I use a command line like 'msiexec /i C:\Install\MOMAgent.msi' the scom 
agent will be installed.

Can anyone help me?

Thanx tinu

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Puppet agent process get stuck

[yannig rousseau]

I managed to kill all of the stuck process with a simple ssh loop in a 
script. Nevertheless, that's not very cool to proceed so...

Don't you think it would be a good option to implement a timeout in the 
puppet agent ? If the connection / catalog application is too long (this 
treshold could be set with a specific argument), the puppet agent discard 
the action and request the puppet master again... 
Or is it too complicated to implement safely ?

Yannig

On Thursday, July 18, 2013 3:11:46 PM UTC+2, jcbollinger wrote:
>
>
>
> On Wednesday, July 17, 2013 12:00:13 PM UTC-5, yannig rousseau wrote:
>>
>> Hi, 
>>
>> 3 days ago, we had a production issue where the puppetmaster became 
>> unreachable for 20 minute.
>> All of the puppet clients which tried to connect at this time are now 
>> failing :  "Run of Puppet configuration client already in progress; 
>> skipping"
>>
>> Further investigation show that the puppet agent process is still running 
>> on all of this clients 3 days later. I tried to kille the process on a 
>> machine, and puppet service came back to normal for this machine.
>>
>> Is there a way to kill the process on all of the client ?
>>
>
>
> Puppet does not provide a built-in mechanism for this.  There is a variety 
> of tools that could do it, but you would have to had already set them up.
>
>  
>
>> Is there a way to specify a timeout on the process ? This would permit to 
>> discard the process without human action
>>
>
>
> Again, Puppet does not provide this as a built-in feature, but it should 
> be possible to add external instrumentation to make it happen.  That would 
> probably be facilitated by launching the agent periodically via a scheduler 
> (such as cron) instead of running it in daemon mode.
>
>
> John
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Perform action when exported resources change

[George Brown]

Hello,

I am trying to work out how to have one server perform an action when a new 
host is added.

Specifically it needs to execute a command containing the hostname of the 
new node in order to accept a license. My questions are as follows

1) As I hostname is available as a fact is there a easy way to export this 
rather than having an exec perform /bin/hostname?

2) When the resource is updated is their a way to show only the updated 
contents? 

Please let me know if I'm going the wrong way and if there's a better way 
to do this

Many thanks
George

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: 3.2.2 on CentOS 6.3, and "Did not receive certificate"

[jcbollinger]

On Wednesday, July 17, 2013 5:31:47 PM UTC-5, Forrie wrote:
>
> I do not have separate Puppet installs.  At the moment, it's been 
> installed via the Gem, so the master and agent are coming from the same 
> code, running on the original host (it was not rebuilt).   It is running 
> under Passenger/Apache, presently.
>
>
Then I'm sorry, I can't follow this.  The description of the problem is 
either too inconsistent or too fragmented.

Fresh installs of Puppet are not known to exhibit the problem you describe, 
so the issue must have arisen through the upgrade.  Since you're using gem, 
perhaps you have a compatibility problem among the set of gems currently 
installed.  Or back to basics: you DID restart apache/passenger after 
upgrading the master, right?

If I am to have any hope of being able to do anything further for you, 
however, then I need a detailed timeline of what was done to Puppet on your 
site, starting from "everything is running great on Puppet 2.7 / CentOS 5" 
(or whatever), including which systems were (re)built, what OS and Puppet 
versions were used, and what problems were observed on which systems.


John

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Choosing provider by properties?

[Jakov Sosic]

On 07/18/2013 03:07 PM, jcbollinger wrote:

> Not to my knowledge, no.
> 
> This is not the correct provider paradigm.  The provider for a given
> resource type used on a given node, if not specified explicitly, is
> supposed to be chosen based on the characteristics of the node, not of
> the resource.  You seem to be artificially separating your provider into
> two pieces.  My recommendation would be to create one provider whose
> behavior varies according to the resource's properties, instead of
> trying to make the choice between different providers depend on resource
> properties.

Thing I'm trying to accomplish is to enable the 'cobblerdistro' provider
to be able to add new distro to cobbler either via 'cobbler distro add'
or 'cobbler import'.

Those two commands work very differently, and although a result of both
is a 'distro' (in cobbler terms), they are quite different.

So, I was thinking maybe to develop separate providers, and the one that
is called depends on the params/properties set.


> I think you can use the property validation hook to accomplish this.  It
> is focused on validating individual properties, and there is no
> guarantee of which property will be validated first, but all you really
> need is to raise / check a flag an the resource instance as part of the
> validation of each of those properties.  You raise an ArgumentError if
> the validation code for either property finds that the flag is already
> raised.  See http://docs.puppetlabs.com/guides/custom_types.html for
> general details on the property validation hook.

OK, I will try that.


> No, puppet-dev is for discussion of the development of Puppet itself,
> not for questions about its use.  "Development" of Puppet manifests is a
> usage issue with respect to the Puppet program.

Although this is a provider discussion and not pure manifest... that's
why I asked.


Thank you jcbollinger!

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Installing MSI failed with errror: The network name cannot be found.

[Rob Reynolds]

Hello,

Can you run puppet apply --debug *themanifestname.pp*
*
*
and submit your output here (minus any sensitive data)?

Thanks!

--
Rob Reynolds
Developer, Puppet Labs

*Join us at PuppetConf 2013, August 22-23 in San Francisco - *
http://bit.ly/pupconf13*
**Register now and take advantage of the Final Countdown discount - save
15%!*


On Thu, Jul 18, 2013 at 7:20 AM, tinu  wrote:

> Im trying to install the SCOMAgent.msi on Windows Server 2008 R2 with
> puppet version 2.7.19
>
> I try this code and get the error "change from absent to present failed:
> Failed to install: The network name cannot be found.":
>
> package {'System Center Operations Manager 2007 R2 Agent':
> ensure=> installed,
> provider => 'msi',
> source=> 'C:\Install\MOMAgent.msi',
> }
>
>
> if I use a command line like 'msiexec /i C:\Install\MOMAgent.msi' the scom
> agent will be installed.
>
> Can anyone help me?
>
> Thanx tinu
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] PuppetMaster LB on top of OCFS2

[Jakov Sosic]

Hi,

I'm trying to design a solution that will encompass load balancing
puppet master.

I have two nodes, and idea is to connect them with DRBD, put some
cluster aware filesystem (OCFS2 or GFS2), and just link /etc/puppet and
/var/lib/puppet on both nodes to cluster FS.

Accessing to the masters would be load balanced by round-robin DNS.

Would this work? Is there any problem that both masters are using the
same directories? Any possibility of data corruption or potential
race-conditions?

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Transfer inventory and filebucket changes to consolidated dashboard server

[GregC]

I have a dashboard server sitting in my development lan and am able to pull 
inventory and file bucket information from my development Puppet Master 
server to the dashboard.

I would like to be able to pull the facter inventory and filebucket from my 
Production Puppet Master server into the development dashboard server, that 
way I have one view for all my systems.

There are firewall rules that need to be opened from Production to 
Development.

 Can someone tell me which ports I need opened to make this happen? I 
assume the following:

22
8140
80

If anyone an implementation i'd be interested in hearing your approach. I 
currently transfer all my production puppet runs to my development 
dashboard server and import those reports in each night.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] (announcement) Geppetto 3.2.0 Released

[Henrik Lindberg]

Hi,
Geppetto 3.2.0 was just pushed to the download and update site.

In brief:
* Support for Puppet 3.2, including --parser future (iteration, lambdas)
* Direct Publishing to the Forge
* Improved Editing of Modulefile / module meta data.
* Based on (compatible with) Eclipse Kepler
* Bug Fixes

Release Notes: https://github.com/cloudsmith/geppetto/wiki/Release-Notes

To get the new version, do a check for updates in your Geppetto, or 
download a fresh copy from here: 
http://cloudsmith.github.io/geppetto/download.html


Enjoy
Henrik

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: PuppetMaster LB on top of OCFS2

[GregC]

Load balancing will work without issue, there is a good suggestion on using 
round robin DNS in Chapter 4 of Pro Puppet page 116.

On Thursday, July 18, 2013 1:00:34 PM UTC-4, Jakov Sosic wrote:
>
> Hi, 
>
> I'm trying to design a solution that will encompass load balancing 
> puppet master. 
>
> I have two nodes, and idea is to connect them with DRBD, put some 
> cluster aware filesystem (OCFS2 or GFS2), and just link /etc/puppet and 
> /var/lib/puppet on both nodes to cluster FS. 
>
> Accessing to the masters would be load balanced by round-robin DNS. 
>
> Would this work? Is there any problem that both masters are using the 
> same directories? Any possibility of data corruption or potential 
> race-conditions? 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Unable to use Cloud Provisioner

[shivaraj mathrubai]

Thanks Justin, but I already have installed guid, any other thoughts ?

I was following the steps provided here 
http://docs.puppetlabs.com/guides/cloud_pack_getting_started.html

It says the below : Do you know which exact file I should add the PATH on a 
CentOS ? how to add it ?

After installing it, you must add the lib directory of the module to your 
$RUBYLIB. Add the following to your .profile file (replacing 
/etc/puppet/modules with the directory from the install command, if 
necessary), then run source ~/.profile to re-load it in the current shell:

export RUBYLIB=/etc/puppet/modules/cloud_provisioner/lib:$RUBYLIB


On Thursday, 18 July 2013 00:21:52 UTC+1, shivaraj mathrubai wrote:
>
>
> Hi Guys, 
>
> I'm unable to load the module cloud provisioner, when I try to run 
> node_aws it gives me the below errors:
>
> Error: Could not autoload puppet/face/node_aws/list_keynames: no such file 
> to load -- guid
> Error: Could not parse application options: Could not autoload 
> puppet/face/node_aws/list_keynames: no such file to load -- guid
>
> And when I see the help list I can see the below message:
>
> ! node! Subcommand unavailable due to error. Check error logs.
>   ! node_aws! Subcommand unavailable due to error. Check error 
> logs.
>
> I'm using Puppet 3.2.3 and Ruby 1.9.2
>
> Any hint to fix this ?
>
> Thanks in advance !
>
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] puppet activemq not starting

[R.I.Pienaar]

- Original Message -
> From: "Ripunjay Godhani" 
> To: puppet-users@googlegroups.com
> Sent: Thursday, July 18, 2013 9:42:11 AM
> Subject: [Puppet Users] puppet activemq not starting
> 
> getting error change from stopped to running failed: Could not start
> Service[pe-activemq]: Execution of '/sbin/service pe-activemq start'
> returned 1: at
> /opt/puppet/share/puppet/modules/pe_mcollective/manifests/activemq.pp:25
> 
> also while doing
> 
> how to start  pe-activemq

what happens when you run this command by hand? "service pe-activemq start"
do you get any errors or anything like that?

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] RabbitMQ module won't start stomp

[David Griffith]

Can I get some help getting the RabbitMQ module provide a stomp server 
talking to MCollective on an Ubuntu system?  It was working a few days ago, 
but I found that I cannot reproduce this on a new set of machines -- 
RabbitMQ will not provide stomp services  I have tried the official 
puppetlabs/rabbitmq module and the git version from yesterday and from 
today.  Nothing works.  My site.pp file looks like this:

node 'testserver.foo.com' {
  $rabbitmq_plugins = [ 'amqp_client', 'rabbitmq_stomp' ]

  class { 'rabbitmq::server':
config => '[ {rabbit_stomp, [{tcp_listeners, [6163]} ]} ].',
  }

  rabbitmq_plugin {'rabbitmq_stomp':
ensure => present,
require => Class['rabbitmq::service'],
provider => 'rabbitmqplugins',
  }
}

This is what I was told in #pup...@freenode.net to use.  Version 2.1.0 of 
the module results in this complaint:

  Error: 
  /Stage[main]//Node[testserver.foo.com]/Rabbitmq_plugin[rabbitmq_stomp]: 
  Could not evaluate: Execution of '/usr/sbin/rabbitmq-plugins list -E' 
  returned 1: erlexec: HOME must be set

Using the bleeding edge from 
https://githib.com/puppetlabs/puppetlabs-rabbitmq yields this:

Error: Could not retrieve catalog from remote server: Error 400 on 
SERVER: Puppet::Parser::AST::Resource failed with error ArgumentError: 
Could not find declared class rabbitmq::server at 
/etc/puppet/manifests/site.pp:9 on node testserver.foo.com
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

Using the Master from yesterday (9eadc4274b5a70fd55d036b0365f63e90325d5a7), 
which I was told WOULD work yields this:

Error: /Stage[main]/Rabbitmq/Rabbitmq_plugin[rabbitmq_management]: Could 
not evaluate: Execution of '/usr/sbin/rabbitmq-plugins list -E' returned 
1: erlexec: HOME must be set

Notice: /Stage[main]/Rabbitmq::Service/Service[rabbitmq-server]: 
Dependency Rabbitmq_plugin[rabbitmq_management] has failures: true
Warning: /Stage[main]/Rabbitmq::Service/Service[rabbitmq-server]: 
Skipping because of failed dependencies
Notice: /Stage[main]/Rabbitmq/Anchor[rabbitmq::end]: Dependency 
Rabbitmq_plugin[rabbitmq_management] has failures: true
Warning: /Stage[main]/Rabbitmq/Anchor[rabbitmq::end]: Skipping because 
of failed dependencies
Notice: /Stage[main]/Rabbitmq::Install::Rabbitmqadmin/Exec[Download 
rabbitmqadmin]: Dependency Rabbitmq_plugin[rabbitmq_management] has 
failures: true
Warning: /Stage[main]/Rabbitmq::Install::Rabbitmqadmin/Exec[Download 
rabbitmqadmin]: Skipping because of failed dependencies
Notice: 
/Stage[main]/Rabbitmq::Install::Rabbitmqadmin/File[/usr/local/bin/rabbitmqadmin]:
 

Dependency Rabbitmq_plugin[rabbitmq_management] has failures: true
Warning: 
/Stage[main]/Rabbitmq::Install::Rabbitmqadmin/File[/usr/local/bin/rabbitmqadmin]:
 

Skipping because of failed dependencies
Notice: 
/Stage[main]//Node[testserver.foo.com]/Rabbitmq_plugin[rabbitmq_stomp]: 
Dependency Rabbitmq_plugin[rabbitmq_management] has failures: true
Warning: 
/Stage[main]//Node[testserver.foo.com]/Rabbitmq_plugin[rabbitmq_stomp]: 
Skipping because of failed dependencies
Notice: Finished catalog run in 0.83 seconds

What can I do to get this working?

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Package install error

[Mark Hatch]

Here is my manifest...

package { 'tractor blade':
provider => 'rpm',
ensure   => present,
source   => 
'puppet:///modules/mpsvfx/tractor-blade-1.7_1191418-linuxFC12_gcc44icc121.x86_64.rpm',
name => 
'tractor-blade-1.7_1191418-linuxFC12_gcc44icc121.x86_64.rpm',
}


Here is where that file is...

...modules/mpsvfx/files/tractor-blade-1.7_1191418-linuxFC12_gcc44icc121.x86_64.rpm

Here is the error I get...

Error: Execution of '/bin/rpm -i 
puppet:///modules/mpsvfx/tractor-blade-1.7_1191418-linuxFC12_gcc44icc121.x86_64.rpm'
 
returned 1: error: open of 
puppet:///modules/mpsvfx/tractor-blade-1.7_1191418-linuxFC12_gcc44icc121.x86_64.rpm
 
failed: No such file or directory

Anybody know what I am doing wrong?

Thanks.
Mark

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: 3.2.2 on CentOS 6.3, and "Did not receive certificate"

[Forrie]

I upgraded our Puppet master to 3.x a while ago, after the file access 
issues (allow_ip, etc.) were fixed.I didn't actually test connection of 
a new client until this past week - where the others are running 2.x agent 
code and working.

Here are the gems I have presently:

builder (3.2.2)
daemon_controller (1.1.4)
facter (1.7.2)
fastthread (1.0.7)
fcgi (0.9.1)
ffi (1.9.0)
hiera (1.2.1)
json (1.8.0)
json_pure (1.8.0)
libvirt-ruby (1.0.2)
passenger (4.0.8)
puppet (3.2.3)
puppet-lint (0.3.2)
puppet-module (0.3.4)
rack (1.5.2)
rack-protection (1.5.0)
rake (10.1.0)
rgen (0.6.5)
rubygems-update (2.0.5)
sinatra (1.4.3)
sqlite3 (1.3.7)
sqlite3-ruby (1.3.3)
stomp (1.2.10)
tilt (1.4.1)
tzinfo (1.0.1)
zonefile (1.04)

Now, I could re-install the Puppet 3.x code and see if that resolves the 
problem.   I need to be very careful, as I have many 2.x agents that still 
require the Puppet master running -- so, if I uninstall the gem, then check 
to see if the directory and /usr/local/bin copies are removed, reinstall 
and re-run the master and see what happens.

I presume /var/lib/puppet doesn't need to be touched in this case, as it's 
local data.

Yes, of course the master that's running Puppet under Passenger (4.0.8) has 
been restarted multiple times, in the effort to continue debugging this.   
Though, I note the post above that mentions adding debug to config.ru - 
which I'm puzzled by. I suppose I could back-out the Passenger process 
altogether and run a standard Puppet master and see if the problem 
persists, also.

Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: 3.2.2 on CentOS 6.3, and "Did not receive certificate"

[Forrie]

Actually, with the improvements to Puppet 3.x, I wonder if it's really 
necessary to run Puppet under Passenger anymore... we have less than 100 
hosts, but that could change.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: PuppetMaster LB on top of OCFS2

[Jakov Sosic]

On 07/18/2013 08:29 PM, GregC wrote:

Load balancing will work without issue, there is a good suggestion on
using round robin DNS in Chapter 4 of Pro Puppet page 116.


Yeah but I am little suspicious about two masters sharing 
/var/lib/puppet ... could that cause troubles?




--
Jakov Sosic
www.srce.unizg.hr

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppetlabs Apt module: dependency cycle

[Alon Nisser]

Using  ```puppetlabs/apt``` in a puppet provisioner for vagrant.  the 
module is installed in puppet/modules and I'm getting a strange Dependency 
cycle error.
the code in the manifest file:

# Run apt-get update when anything beneath /etc/apt/ changes
#taken from 
https://blog.kumina.nl/2010/11/puppet-tipstricks-running-apt-get-update-only-when-needed/
exec { "apt-get update":
command => "/usr/bin/apt-get update",
onlyif => "/bin/sh -c '[ ! -f /var/cache/apt/pkgcache.bin ] || 
/usr/bin/find /etc/apt/* -cnewer /var/cache/apt/pkgcache.bin | /bin/grep . 
> /dev/null'",
}

package {

["build-essential","apache2","git","python","python-dev","python-setuptools", 
"python-pip"]:
ensure => present,
require => Exec["apt-get update"],
}

class { 'apt':

}
include apt

apt::builddep { ["python-imaging","python-lxml"]:
require => Class['apt'] 
 }

class {'nodejs':

}
include nodejs

package {"less":
ensure => present,
provider => 'npm',
require => Package['npm'],

}

I actually noticed similiar questions 
[here](http://stackoverflow.com/questions/13568748/dependency-cycle-with-apt-source)
 
and 
[here](http://stackoverflow.com/questions/15384733/puppet-issue-with-aptsource-and-stages),
 
but not with a satisfying answer.
The error message:

←[0;37mdebug: /Stage[main]//Package[python-virtualenv]/require: 
requires Package
[python-pip]←[0m
←[0;37mdebug: /Stage[main]//Package[python-virtualenv]/require: 
requires Package
[python-setuptools]←[0m
←[0;37mdebug: /Stage[main]/Apt/File[configure-apt-proxy]/notify: 
subscribes to E
xec[apt_update]←[0m
←[0;37mdebug: /Stage[main]/Apt/Anchor[apt::update]/require: requires 
Class[Apt::
Update]←[0m
←[0;37mdebug: /Stage[main]/Apt/File[sources.list.d]/notify: subscribes 
to Exec[a
pt_update]←[0m
←[0;37mdebug: /Stage[main]//Package[python-pip]/require: requires 
Exec[apt-get u
pdate]←[0m
←[0;37mdebug: 
/Stage[main]//Apt::Builddep[python-lxml]/Exec[apt-builddep-python-
lxml]/notify: subscribes to Exec[apt_update]←[0m
←[0;37mdebug: /Stage[main]//Package[apache2]/require: requires 
Exec[apt-get upda
te]←[0m
←[0;37mdebug: /Stage[main]//Package[python-dev]/require: requires 
Exec[apt-get u
pdate]←[0m
←[0;37mdebug: /Stage[main]/Nodejs/Package[npm]/require: requires 
Anchor[nodejs::
repo]←[0m
←[0;37mdebug: /Stage[main]/Nodejs/Package[nodejs]/require: requires 
Anchor[nodej
s::repo]←[0m
←[0;37mdebug: /Stage[main]//Package[python]/require: requires 
Exec[apt-get updat
e]←[0m
←[0;37mdebug: /Stage[main]//Package[build-essential]/require: requires 
Exec[apt-
get update]←[0m
←[0;37mdebug: /Stage[main]//Apt::Builddep[python-imaging]/require: 
requires Clas
s[Apt]←[0m
←[0;37mdebug: /Stage[main]//Package[git]/require: requires Exec[apt-get 
update]←
[0m
←[0;37mdebug: /Stage[main]//Package[less]/require: requires 
Package[npm]←[0m
←[0;37mdebug: /Stage[main]//Package[sphinx]/require: requires 
Package[python-pip
]←[0m
←[0;37mdebug: 
/Stage[main]//Apt::Builddep[python-imaging]/Anchor[apt::builddep::
python-imaging]/require: requires Class[Apt::Update]←[0m
←[0;37mdebug: /Stage[main]//Package[python-setuptools]/require: 
requires Exec[ap
t-get update]←[0m
←[0;37mdebug: /Stage[main]/Apt/File[sources.list]/notify: subscribes to 
Exec[apt
_update]←[0m
←[0;37mdebug: 
/Stage[main]//Apt::Builddep[python-imaging]/Exec[apt-builddep-pyth
on-imaging]/notify: subscribes to Exec[apt_update]←[0m
←[0;37mdebug: 
/Stage[main]//Apt::Builddep[python-lxml]/Anchor[apt::builddep::pyt
hon-lxml]/require: requires Class[Apt::Update]←[0m
←[0;37mdebug: /Stage[main]//Apt::Builddep[python-lxml]/require: 
requires Class[A
pt]←[0m
←[1;35merr: Could not apply complete catalog: Found 1 dependency cycle:
(Anchor[apt::update] => Class[Apt] => Apt::Builddep[python-lxml] => 
Exec[apt-bui
lddep-python-lxml] => Exec[apt_update] => Class[Apt::Update] => 
Anchor[apt::upda
te])
Try the '--graph' option and opening the resulting '.dot' file in 
OmniGraffle or
 GraphViz←[0m

any known workaound? solution?

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: PuppetMaster LB on top of OCFS2

[Cory Stoker]

On Thu, Jul 18, 2013 at 1:53 PM, Jakov Sosic  wrote:

> On 07/18/2013 08:29 PM, GregC wrote:
>
>> Load balancing will work without issue, there is a good suggestion on
>> using round robin DNS in Chapter 4 of Pro Puppet page 116.
>>
>
> Yeah but I am little suspicious about two masters sharing /var/lib/puppet
> ... could that cause troubles?
>
>
We have puppetmasters that share /var/lib/puppet/ssl via NFS.  This works
great.  Just make sure you do not have 2 active CA servers at the same
time.  The only shared stuff for the puppetmasters in /var/lib/puppet is
the SSL stuff.  We also share the /etc/puppet/environments for code.  We
use this setup to scale to tens of thousands of puppet clients.

HTH

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Puppetlabs Apt module: dependency cycle

[jcbollinger]

On Thursday, July 18, 2013 3:38:25 PM UTC-5, Alon Nisser wrote:
>
> Using  ```puppetlabs/apt``` in a puppet provisioner for vagrant.  the 
> module is installed in puppet/modules and I'm getting a strange Dependency 
> cycle error.
> the code in the manifest file:
>
> # Run apt-get update when anything beneath /etc/apt/ changes
> #taken from 
> https://blog.kumina.nl/2010/11/puppet-tipstricks-running-apt-get-update-only-when-needed/
> exec { "apt-get update":
> command => "/usr/bin/apt-get update",
> onlyif => "/bin/sh -c '[ ! -f /var/cache/apt/pkgcache.bin ] || 
> /usr/bin/find /etc/apt/* -cnewer /var/cache/apt/pkgcache.bin | /bin/grep . 
> > /dev/null'",
> }
> 
> package {
> 
> ["build-essential","apache2","git","python","python-dev","python-setuptools", 
> "python-pip"]:
> ensure => present,
> require => Exec["apt-get update"],
> }
>
> class { 'apt':
> 
> }
> include apt
> 
> apt::builddep { ["python-imaging","python-lxml"]:
> require => Class['apt'] 
>  }
> 
> class {'nodejs':
> 
> }
> include nodejs
> 
> package {"less":
> ensure => present,
> provider => 'npm',
> require => Package['npm'],
> 
> }
>
> I actually noticed similiar questions [here](
> http://stackoverflow.com/questions/13568748/dependency-cycle-with-apt-source) 
> and [here](
> http://stackoverflow.com/questions/15384733/puppet-issue-with-aptsource-and-stages),
>  
> but not with a satisfying answer.
> The error message:
>
> [...]
> (Anchor[apt::update] => Class[Apt] => Apt::Builddep[python-lxml] => 
> Exec[apt-bui
> lddep-python-lxml] => Exec[apt_update] => Class[Apt::Update] => 
> Anchor[apt::upda
> te])
> Try the '--graph' option and opening the resulting '.dot' file in 
> OmniGraffle or
>  GraphViz←[0m
>
> any known workaound? solution?
>


You are trying too hard.  This module goes to considerable effort to avoid 
making you declare relationships among its classes and resources.  The 
relationships you are manually declaring run afoul of the ones declared by 
the module itself.  In particular, it is incorrect for an apt::builddep to 
'require' Class['apt'].

Also, the module has its own provision for running "apt-get update" when 
needed, so your Exec for that purpose may be superfluous.  However, the Apt 
module will only run "apt-get update" when it modifies an Apt resource 
itself, so if you contemplate managing some sources via Puppet but not 
others (not recommended), then perhaps you do need something like that.

And as a trivial matter, it is redundant to declare class 'apt' via both 
the 'include' function and a parameterized-style declaration.

I think your code should instead look like this:

include 'apt'

package { 
['build-essential','apache2','git','python','python-dev','python-setuptools','python-pip']:
  ensure => present,
  require => Class['apt'],
}

apt::builddep { ['python-imaging','python-lxml']: }

(omitting the irrelevant 'nodejs' and 'less' stuff).

If you were to claim that it is unintuitive that apt::builddep instances 
must avoid 'require'ing class 'apt' then you would not get an argument from 
me.  Or if you complained that these details were not well documented, then 
I would not object.


John

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Package install error

[jcbollinger]

On Thursday, July 18, 2013 2:15:50 PM UTC-5, Mark Hatch wrote:
>
> Here is my manifest...
>
> package { 'tractor blade':
> provider => 'rpm',
> ensure   => present,
> source   => 
> 'puppet:///modules/mpsvfx/tractor-blade-1.7_1191418-linuxFC12_gcc44icc121.x86_64.rpm',
> name => 
> 'tractor-blade-1.7_1191418-linuxFC12_gcc44icc121.x86_64.rpm',
> }
>
>
> Here is where that file is...
>
>
> ...modules/mpsvfx/files/tractor-blade-1.7_1191418-linuxFC12_gcc44icc121.x86_64.rpm
>
> Here is the error I get...
>
> Error: Execution of '/bin/rpm -i 
> puppet:///modules/mpsvfx/tractor-blade-1.7_1191418-linuxFC12_gcc44icc121.x86_64.rpm'
>  
> returned 1: error: open of 
> puppet:///modules/mpsvfx/tractor-blade-1.7_1191418-linuxFC12_gcc44icc121.x86_64.rpm
>  
> failed: No such file or directory
>
> Anybody know what I am doing wrong?
>
>

The documentation has this to say about the Package type's 'source' 
parameter 
(http://docs.puppetlabs.com/references/3.2.latest/type.html#package):
*source*Where to find the actual package. This must be a local file (or on 
a network file system) or a URL *that your specific packaging type 
understands*; Puppet will not retrieve files for you, although you can 
manage packages as file resources.(emphasis added)

RPM does not understand URLs employing the 'puppet' protocol.  You cannot 
use Puppet's built-in file server as a substitute for a proper package 
repository.  You can, however, create a bona fide local repository of the 
appropriate type for your native packaging system, and put your package 
file(s) there.  It could live on the same host as your Puppet master if you 
prefer.


John

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Attention!!! Puppet pe-activemq not Starting

[Justin Stoller]

On Thu, Jul 18, 2013 at 12:44 AM, Ripunjay Godhani wrote:

>
>
> getting error change from stopped to running failed: Could not start
> Service[pe-activemq]: Execution of '/sbin/service pe-activemq start'
> returned 1: at
> /opt/puppet/share/puppet/modules/pe_mcollective/manifests/activemq.pp:25
>
> also while doing
>
> how to start  pe-activemq
>
> You may have better luck on the pe-users list.

What is the output (to stdout, stderr, or a log file in
/var/log/pe-activemq/*.log) when you run `/sbin/service pe-activemq start`?

 - Justin

>
> Regards,
> Ripunjay
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



-- 

Join ME at PuppetConf 2013, August 22-23 in San Francisco -
http://bit.ly/pupconf13
It's the FINAL COUNTDOWN!! 


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Multiple Puppet masters each running as their own CA connecting to a single PuppetDB instance

[Pete Brown]

On 17 July 2013 14:18, Nick Lewis  wrote:
> On Tuesday, July 16, 2013 1:25:22 PM UTC-7, replicant wrote:
>>
>> So,
>>
>> We are working on migrating a global deployment of Puppet over to a
>> single PuppetDB instance away from a single MySQL storeconfigs
>> instance and are running into an issue. It seems is that PuppetDB will
>> only allow nodes from a single Puppet master to connect if each Puppet
>> master is running as it's own CA, is this statement correct?
>>
>> Is it possible to have multiple Puppet masters, each running as their
>> own CA, talk to a single PuppetDB instance?
>>
>
> By having multiple CAs, you're effectively establishing separate networks,
> so it doesn't seem to make much sense to comingle their data. PuppetDB
> itself has no notion that the data ought to be kept separate, which means a
> master on one CA can access all the data from a master on another CA. In
> that case, you may either be undermining the purpose of having separate CAs
> or not have a good reason to have separate CAs.
>
>
> But assuming this really is what you want, you should be able to accomplish
> it by using an SSL termination proxy configured to present different
> certificates to different clients.
>

Alternatively you could consider using an external ca to sign the
certs for your two masters.
That way the whole env has a single ca and puppetdb will probably play nicer.
http://docs.puppetlabs.com/puppet/3/reference/config_ssl_external_ca.html


>>
>> --
>> I've seen things you people wouldn't believe. Attack ships on fire off
>> the shoulder of Orion. I watched C-beams glitter in the dark near the
>> Tannhauser gate. All those moments will be lost in time... like tears
>> in rain... Time to die.

This is one of my all time favourite quotes.
:)


>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.