Re: [Puppet Users] Puppet 3.1.1 Windows crashes

[Josh Cooper]

On Tuesday, June 11, 2013, Michael O'Dea wrote:

> Sorry for the long delay - since I'd mitigated I moved on to other things.
>  Thanks for the quick fix.  Deploying servers is no simple process in my
> environment so I guess I'll need to stick with the old clients for a while.
>
>
>
Do you happen to be running on non en_us systems? I'm wondering if there is
an issue with multibyte to UTF-16LE conversion of the event record data.

On Thursday, June 6, 2013 4:45:08 PM UTC-4, Josh Cooper wrote:
>>
>> Hi Michael,
>>
>> On Thu, Jun 6, 2013 at 8:01 AM, Michael O'Dea  wrote:
>>
>> I neglected to mention this crash leaves behind the lockfile, so while
>> the puppet service is still running, all future puppet runs exit saying
>> "another puppet run is in progress".
>>
>>
>>
>> On Thursday, June 6, 2013 10:55:21 AM UTC-4, Michael O'Dea wrote:
>>
>> I noticed that a number of my Windows hosts had stopped dialing in, and
>> upon closer inspection I found that Puppet was crashing in Ruby and
>> wevtapi.dll.  I can't find any reference to this in the issue tracker,
>> although I've got over a dozen occurrences in my environment, all with the
>> same descriptions as below.  I checked to see if the times were similar, in
>> case the server presented some bad data to cause the issue, but the crashes
>> occurred at all different times and days.
>>
>> My question is, has anyone else seen this? Is this a known issue?
>>
>>
>> It is now :) 
>> https://projects.**puppetlabs.com/issues/21109
>>
>>
>>   If it is fixed in 3.2.1, can I install 3.2.1 clients against a 3.1.x
>> server?
>>
>>
>> In general, running newer agents against older servers is not supported.
>>
>>
>>   In the meantime, I will be rolling back to an older 2.7.x version that
>> we'd run for some time without issue.
>>
>> Thanks in advance.  Fault details below.
>>
>> Faulting application name: ruby.exe, version: 1.8.7.371, time stamp:
>> 0x5083a46c
>>
>> Faulting module name: wevtapi.DLL, version: 6.1.7600.16385, time stamp:
>> 0x4a5bdb2d
>> Exception code: 0xc005
>> Fault offset: 0x1360
>> Faulting process id: 0xa48
>> Faulting application start time: 0x01ce5e0840c39580
>> Faulting application path: C:\Program Files (x86)\Puppet
>> Labs\Puppet\sys\ruby\bin\ruby.exe
>> Faulting module path: C:\Windows\system32\wevtapi.**DL**L
>>
>>
>> This is the DLL responsible for windows event logging (the new API in
>> Vista and up). By default, puppet creates an eventlog log destination, and
>> there must be an issue in either puppet or the win32-eventlog gem we are
>> using. What's strange is that the code is unchanged since 2.7.14. So
>> perhaps it's an issue with the message resource dll. I will take a look.
>>
>> For workarounds, you could change the default log destination to a file
>> while we debug the issue. I don't think this can be controlled via
>> puppet.conf, but you use the registry module to configure the puppet
>> service start arguments to include `--logdest ` to log to a file.
>>
>> Josh
>>
>> --
>> Josh Cooper
>> Developer, Puppet Labs
>>
>> *Join us at *
>>
>  --
> 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  'cvml', 'puppet-users%2bunsubscr...@googlegroups.com');>.
> To post to this group, send email to 
> puppet-users@googlegroups.com 'puppet-users@googlegroups.com');>
> .
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

Josh


-- 
Josh Cooper
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 Early Bird discount - save 25%!*

-- 
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 Windows package not seeing DisplayName in Registry?

[Josh Cooper]

On Thursday, June 13, 2013, Reginald Choudari wrote:

>
>
> On Wednesday, June 12, 2013 5:23:50 PM UTC-4, Josh Cooper wrote:
>>
>>
>>
>>
>> On Wed, Jun 12, 2013 at 12:51 PM, Reginald Choudari <
>> adnancho...@gmail.com> wrote:
>>
>>> Tried renaming the title of the resource to what the name attribute was
>>> set to; no go.
>>>
>>> After doing a 'puppet resource package' on the agent, I see a list of
>>> packages but the package listed here is not shown ... I confirmed that it
>>> is still showing 'ensure: created' in the event logs every puppet run.
>>>
>>> Thanks
>>
>>
>> Can you export the Uninstall registry key for that package? I want to see
>> what the SystemComponent, etc values are.
>>
>>
>>> On Friday, June 7, 2013 10:54:36 AM UTC-4, Reginald Choudari wrote:

 Hello,

 I've got Package resource on my Windows machine that keeps creating
 itself even though the package has been properly installed.

 I've got the name attribute set to the DisplayName found in the
 Registry for the package.

 Every time the agent polls, I see in the Event Logs:

 /Stage[main]/Mssql_rtwo_sptwo/Package[mssql2008r2sp2_exec]/**e**nsure:
 created

 This is what's in my manifest:

 package { 'mssql2008r2sp2_exec':
 ensure  => installed,
 name=> 'SQL Server 2008 R2 SP2 Common Files',
 provider=> windows,
 source  => "C:\\puppet_temp\\${mssql_**file**name}",
 install_options => ['/quiet', '/**IAcceptSQLServerLicenseTerms**',
 '/allinstances'],
 require => Exec['run_mssql2008r2sp2_**artif**
 act_extract_ps1'],
   }

 I'm thinking there has got to be some weird bug/error with this ... Can
 anyone help?

 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...@**googlegroups.com.
>>> To post to this group, send email to puppet...@googlegroups.com.
>>> Visit this group at 
>>> http://groups.google.com/**group/puppet-users?hl=en
>>> .
>>> For more options, visit 
>>> https://groups.google.com/**groups/opt_out
>>> .
>>>
>>>
>>>
>>
>> Josh
>>
>> --
>> Josh Cooper
>> 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 Early Bird discount - save 25%!*
>>
>  --
> 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  'cvml', 'puppet-users%2bunsubscr...@googlegroups.com');>.
> To post to this group, send email to 
> puppet-users@googlegroups.com 'puppet-users@googlegroups.com');>
> .
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

Unfortunately, Windows does not have an API for retrieving installed
packages. So we scan the registry and apply heuristics to determine which
packages to report on.

The overall goal has been for Puppet to report on the same set of packages
that you see in Add/Remove Programs. Packages whose registry
value SystemComponent=1 are hidden from ARP, so Puppet does the same, see
https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/windows/exe_package.rb#L34

Since Puppet never reports on SystemComponents, it will always think they
are absent, and need to be installed each time it runs.

I'm thinking Puppet should not exclude SystemComponents? Are there any bad
side effects if we included them?

Josh


-- 
Josh Cooper
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 Early Bird discount - save 25%!*

-- 
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] Disable A Windows Service Only If It Exists

[Josh Cooper]

On Friday, June 14, 2013, Paul Nickerson wrote:

> I came up with a solution using exec and sc.
>
> In a module I called disable_services:
>
> define disable_services {
>   exec { "stop_${title}":
> command => "C:\\Windows\\System32\\cmd.exe /c sc stop \"${title}\"",
> onlyif  => "C:\\Windows\\System32\\cmd.exe /c sc query \"${title}\"",
> unless  => "C:\\Windows\\System32\\cmd.exe /c sc query \"${title}\" |
> find \"STOPPED\"",
> before  => Exec["disable_${title}"],
> }
>   exec { "disable_${title}":
> command => "C:\\Windows\\System32\\cmd.exe /c sc config \"${title}\"
> start=disabled",
> onlyif  => "C:\\Windows\\System32\\cmd.exe /c sc query \"${title}\"",
> unless  => "C:\\Windows\\System32\\cmd.exe /c sc qc \"${title}\" |
> find \"DISABLED\"",
> require => Exec["stop_${title}"],
> }
>   }
>
> In a manifest:
>
> disable_services { ["CVSNT", "CVSNT Locking Service", "CVS", "CVSLock"]: }
>
> On Thursday, April 11, 2013 11:45:52 AM UTC-4, Paul Nickerson wrote:
>>
>> I am wondering whether it is possible to have Puppet only stop and
>> disable a Windows service if it exists. I have Puppet master 3.1.1 on
>> CentOS, and Puppet clients 3.1.1 on many Windows machines. Right now, I
>> have the bit below for certain nodes:
>>
>> service { "CVSNT":
>> ensure => 'stopped',
>> enable => 'false',
>> }
>>
>> Some of the nodes have this service, some do not. Occasionally, new nodes
>> are added that this applies to (through inherits statements), and these new
>> nodes may or may not have this service. It's not just this service, either;
>> I have an array of services I need to ensure won't run. I just simplified
>> the above example with one service.
>>
>> If the Windows node does not have the service, then the Puppet agent
>> still runs successfully. But, when I run puppet agent --test in the
>> Command Prompt with Puppet on the node, I get this error:
>>
>> Error: /Stage[main]//Node[winbase]/**Service[CVSNT]: Could not evaluate:
>> Cannot get status of CVSNT, error was: The specified service does not exist
>> as an installed service.
>>
>> The agent continues to run and completes successfully. But, getting
>> several of these lines at different points each time I run the Puppet agent
>> makes testing and debugging whatever other module I'm working on a little
>> difficult. I would like to get rid of the clutter.
>>
>> I've been researching this topic for a while, and haven't come up with
>> any solutions. Is there any way to have Puppet disable a Windows service
>> only if it exists? Or, is there a way to suppress these warning lines
>> without suppressing other output?
>
>  --
> 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  'cvml', 'puppet-users%2bunsubscr...@googlegroups.com');>.
> To post to this group, send email to 
> puppet-users@googlegroups.com '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.
>
>
>

Another approach would be to create a custom fact whose boolean value
depends on the service being installed or not. Then in your manifest, only
manage the service if and only if the fact is true.

Josh


-- 
Josh Cooper
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 Early Bird discount - save 25%!*

-- 
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: apt repository appears to have dependency issue with latest release (3.2.1)

[Justin]

Disregard, my bad.

This was a server that didn't have the Ubuntu universe repo enabled, which 
is why it could find the virt-what (facter) or libjson-ruby and ruby-json 
(hiera) packages.

On Friday, June 14, 2013 10:35:10 PM UTC-4, Justin wrote:
>
> Forgot to paste my apt-get update output (which I ran immediately after 
> installing the repo).
>
> ~# apt-get update 
> Hit http://apt.puppetlabs.com quantal Release.gpg
> Hit http://us.archive.ubuntu.com quantal Release.gpg
> Hit http://apt.puppetlabs.com quantal Release
> Hit http://us.archive.ubuntu.com quantal-security Release.gpg
> Hit http://apt.puppetlabs.com quantal/main Sources
> Hit http://us.archive.ubuntu.com quantal-updates Release.gpg
> Hit http://apt.puppetlabs.com quantal/dependencies Sources
> Hit http://us.archive.ubuntu.com quantal Release
> Hit http://apt.puppetlabs.com quantal/main amd64 Packages 
> Hit http://us.archive.ubuntu.com quantal-security Release
> Hit http://apt.puppetlabs.com quantal/dependencies amd64 Packages 
> Hit http://apt.puppetlabs.com quantal/main i386 Packages  
> Hit http://us.archive.ubuntu.com quantal-updates Release
> Hit http://apt.puppetlabs.com quantal/dependencies i386 Packages  
> Hit http://us.archive.ubuntu.com quantal/main Sources
> Hit http://us.archive.ubuntu.com quantal/main amd64 Packages
> Hit http://us.archive.ubuntu.com quantal/main i386 Packages
> Hit http://us.archive.ubuntu.com quantal/main Translation-en
> Hit http://us.archive.ubuntu.com quantal-security/main Sources
> Hit http://us.archive.ubuntu.com quantal-security/main amd64 Packages
> Hit http://us.archive.ubuntu.com quantal-security/main i386 Packages
> Hit http://us.archive.ubuntu.com quantal-security/main Translation-en
> Hit http://us.archive.ubuntu.com quantal-updates/main Sources
> Hit http://us.archive.ubuntu.com quantal-updates/main amd64 Packages
> Hit http://us.archive.ubuntu.com quantal-updates/main i386 Packages
> Ign http://apt.puppetlabs.com quantal/dependencies Translation-en_US
> Hit http://us.archive.ubuntu.com quantal-updates/main Translation-en
> Ign http://apt.puppetlabs.com quantal/dependencies Translation-en
> Ign http://apt.puppetlabs.com quantal/main Translation-en_US
> Ign http://apt.puppetlabs.com quantal/main Translation-en
> Ign http://us.archive.ubuntu.com quantal/main Translation-en_US
> Ign http://us.archive.ubuntu.com quantal-security/main Translation-en_US
> Ign http://us.archive.ubuntu.com quantal-updates/main Translation-en_US
> Reading package lists... Done
>
>
> On Friday, June 14, 2013 10:30:38 PM UTC-4, Justin wrote:
>>
>> Read through the thread and didn't see a fix. I'm running into this issue 
>> with a new Ubuntu server. Any help?
>>
>> Here's how I installed the repo.
>>
>> ~# lsb_release -a
>> No LSB modules are available.
>> Distributor ID: Ubuntu
>> Description:Ubuntu 12.10
>> Release:12.10
>> Codename:   quantal
>>
>> ~# wget -q https://apt.puppetlabs.com/puppetlabs-release-quantal.deb
>>
>> ~# dpkg -i puppetlabs-release-quantal.deb 
>> (Reading database ... 60865 files and directories currently installed.)
>> Preparing to replace puppetlabs-release 1.0-7 (using 
>> puppetlabs-release-quantal.deb) ...
>> Unpacking replacement puppetlabs-release ...
>> Setting up puppetlabs-release (1.0-7) ...
>>
>> ~# grep '^deb' /etc/apt/sources.list.d/puppetlabs.list
>> deb http://apt.puppetlabs.com quantal main
>> deb-src http://apt.puppetlabs.com quantal main
>> deb http://apt.puppetlabs.com quantal dependencies
>> deb-src http://apt.puppetlabs.com quantal dependencies
>>
>> # apt-get install puppet
>> Reading package lists... Done
>> Building dependency tree   
>> Reading state information... Done
>> Some packages could not be installed. This may mean that you have
>> requested an impossible situation or if you are using the unstable
>> distribution that some required packages have not yet been created
>> or been moved out of Incoming.
>> The following information may help to resolve the situation:
>>
>> The following packages have unmet dependencies:
>>  puppet : Depends: puppet-common (= 3.2.1-1puppetlabs1) but it is not 
>> going to be installed
>> E: Unable to correct problems, you have held broken packages.
>>
>>
>> On Thursday, May 23, 2013 5:25:52 PM UTC-4, Eric Sorenson wrote:
>>>
>>> Quick question for those of you affected by this -- what did you to do 
>>> to add the puppetlabs apt repo? 
>>>
>>> Did you do it through the method described here: 
>>> http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#for-debian-and-ubuntu
>>>
>>> .. or some other way? I'm trying to suss out whether the docs / packages 
>>> are messing people up.
>>>
>>> thx
>>> eric0
>>>
>>>

-- 
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 p

Re: [Puppet Users] ruby issue

[Stuart Cracraft]

Boo!!! Hiss!!

Be a One-Stop-Shop!

It's YOUR collective after all

--Stuart

On Jun 14, 2013, at 7:13 PM, Michael Stahnke  wrote:

> On Wed, Jun 12, 2013 at 5:52 AM, Greg Chavez  wrote:
>> Which is just fine if your company has the Optional subscription.
>> Mine doesn't.  So I'm screwed unless I write a script to manually pull
>> updates from Fedora or CentOS into a custom mrepo repository. Bit of a
>> pain, that is.
> 
> The optional repo is free from what I can tell. It's included with a
> RHEL subscription. Puppet Labs doesn't try to replace packages in
> provided by the upstream OS vendor. Therefore, we don't supply
> packages that replace things in the RHEL repo since they work just
> fine with Puppet et al.
> 
> 
>> 
>> On Tue, Jun 11, 2013 at 6:43 PM, Matthaus Owens  
>> wrote:
>>> We supply rubygems for rhel 5 because it is not available in centos or
>>> rhel 5 core (it is in EPEL). In rhel6 and cent6, it is widely and
>>> easily available (in cent6 base, and in rhel6 optional repos), so we
>>> don't supply it for el6.
>>> 
>>> On Tue, Jun 11, 2013 at 2:37 PM, Greg Chavez  wrote:
 The rubygems package is available from here:
 
 https://yum.puppetlabs.com/el/5/dependencies/x86_64/
 
 So why wouldn't it be available from 6?  I'm pretty sure it used to be
 there since I've kicked several rhel 6 systems that had no problem
 installing puppet from puppetlabs.  Was it mistakenly dropped from the
 puppetlabs rhel 6 repo?
 
 Thanks
 --Greg Chavez
 
 On Mon, Jun 10, 2013 at 11:12 AM, Stuart Cracraft  
 wrote:
> You are most welcome.
> 
> On Jun 10, 2013, at 7:40 AM, Lab Yizhar  wrote:
> 
> Thanks m8 for the mental support :)
> 
> As you already know, as an open source believer ,I'm kind of into it and 
> the
> solution is there, But I want to do it without RHN subscription that will
> used on our production env.
> 
> Couple of humps and I'll be there this way or the offical other...
> 
> On Mon, Jun 10, 2013 at 4:31 PM, Stuart Cracraft  
> wrote:
>> 
>> It's not that hard!
>> 
>> You can do it!!!
>> 
>> Also, you could buy some books on the subject!
>> 
>> On Jun 10, 2013, at 5:51 AM, Yizhar A.  wrote:
>> 
>> Hi,
>> 
>> Finish my things on this issue for now as the last one in this chain
>> talented enough to be asking for pay for answering this
>> 
>> I'll update when I'll figure it out else.
>> 
>> Stay tuned,
>> 
>> Yizhar
>> 
>> "Don't ask what the community can contribute to you ? ask what I can
>> contribute the community"
>> On Sunday, June 9, 2013 3:06:48 PM UTC+3, Yizhar A. wrote:
>>> 
>>> Dear Stuart,
>>> 
>>> Kind of my first steps into puppet on RHEL 6 and I wonder how you manage
>>> to solve the rubygems issue.
>>> 
>>> Since I'm using RHEL 6.4 (.x86_64) in my test env. with only puppetlabs
>>> repo I can't see from where I can get the rubygems missing package.
>>> 
>>> As you after wiki'd it :) can you give me a piece of advise in here or
>>> attached your docs to help me through ?
>>> 
>>> Thanks,
>>> 
>>> --Yizhar
>>> 
>>> 
>>> On Saturday, June 1, 2013 8:49:16 AM UTC+3, Stuart Cracraft wrote:
 
 Hey, good news.
 
 All is well.
 
 Ruby & related are good. Puppet too. And Red Hat.
 
 Also, I've documented/wiki'd the Puppet Master + Client install with
 respect
 to bare metal to delivered system for all related aspects and
 transmitted, fully,
 disclosed entirely, to staff.
 
 Next week, I will be tuning the configuration file on master and agents
 and
 writing many more puppet patterns plus training staff.
 
 As it is their only hope!
 
 --Stuart
 
 P.S. The firm's personnel have had heart attacks, strokes and other
 major maladies amongst
 staff in the past year due to the LACK OF AUTOMATION!!!
 
 Puppet is the Cure
 
 Kick Chef and CF Engine's non-collective butts!
 
 
>> 
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Puppet Users" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/puppet-users/ghDZsdkC3C0/unsubscribe?hl=en.
>> To unsubscribe from this group and all its topics, 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?hl=en.
>> For more options, visit https://groups.google.com/groups/opt_out.
>> 
>> 
>> 
>> 
>> --
>> You received this messa

Re: [Puppet Users] Re: apt repository appears to have dependency issue with latest release (3.2.1)

[Justin]

Forgot to paste my apt-get update output (which I ran immediately after 
installing the repo).

~# apt-get update 
Hit http://apt.puppetlabs.com quantal Release.gpg
Hit http://us.archive.ubuntu.com quantal Release.gpg
Hit http://apt.puppetlabs.com quantal Release
Hit http://us.archive.ubuntu.com quantal-security Release.gpg
Hit http://apt.puppetlabs.com quantal/main Sources
Hit http://us.archive.ubuntu.com quantal-updates Release.gpg
Hit http://apt.puppetlabs.com quantal/dependencies Sources
Hit http://us.archive.ubuntu.com quantal Release
Hit http://apt.puppetlabs.com quantal/main amd64 Packages 
Hit http://us.archive.ubuntu.com quantal-security Release
Hit http://apt.puppetlabs.com quantal/dependencies amd64 Packages 
Hit http://apt.puppetlabs.com quantal/main i386 Packages  
Hit http://us.archive.ubuntu.com quantal-updates Release
Hit http://apt.puppetlabs.com quantal/dependencies i386 Packages  
Hit http://us.archive.ubuntu.com quantal/main Sources
Hit http://us.archive.ubuntu.com quantal/main amd64 Packages
Hit http://us.archive.ubuntu.com quantal/main i386 Packages
Hit http://us.archive.ubuntu.com quantal/main Translation-en
Hit http://us.archive.ubuntu.com quantal-security/main Sources
Hit http://us.archive.ubuntu.com quantal-security/main amd64 Packages
Hit http://us.archive.ubuntu.com quantal-security/main i386 Packages
Hit http://us.archive.ubuntu.com quantal-security/main Translation-en
Hit http://us.archive.ubuntu.com quantal-updates/main Sources
Hit http://us.archive.ubuntu.com quantal-updates/main amd64 Packages
Hit http://us.archive.ubuntu.com quantal-updates/main i386 Packages
Ign http://apt.puppetlabs.com quantal/dependencies Translation-en_US
Hit http://us.archive.ubuntu.com quantal-updates/main Translation-en
Ign http://apt.puppetlabs.com quantal/dependencies Translation-en
Ign http://apt.puppetlabs.com quantal/main Translation-en_US
Ign http://apt.puppetlabs.com quantal/main Translation-en
Ign http://us.archive.ubuntu.com quantal/main Translation-en_US
Ign http://us.archive.ubuntu.com quantal-security/main Translation-en_US
Ign http://us.archive.ubuntu.com quantal-updates/main Translation-en_US
Reading package lists... Done


On Friday, June 14, 2013 10:30:38 PM UTC-4, Justin wrote:
>
> Read through the thread and didn't see a fix. I'm running into this issue 
> with a new Ubuntu server. Any help?
>
> Here's how I installed the repo.
>
> ~# lsb_release -a
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description:Ubuntu 12.10
> Release:12.10
> Codename:   quantal
>
> ~# wget -q https://apt.puppetlabs.com/puppetlabs-release-quantal.deb
>
> ~# dpkg -i puppetlabs-release-quantal.deb 
> (Reading database ... 60865 files and directories currently installed.)
> Preparing to replace puppetlabs-release 1.0-7 (using 
> puppetlabs-release-quantal.deb) ...
> Unpacking replacement puppetlabs-release ...
> Setting up puppetlabs-release (1.0-7) ...
>
> ~# grep '^deb' /etc/apt/sources.list.d/puppetlabs.list
> deb http://apt.puppetlabs.com quantal main
> deb-src http://apt.puppetlabs.com quantal main
> deb http://apt.puppetlabs.com quantal dependencies
> deb-src http://apt.puppetlabs.com quantal dependencies
>
> # apt-get install puppet
> Reading package lists... Done
> Building dependency tree   
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
>  puppet : Depends: puppet-common (= 3.2.1-1puppetlabs1) but it is not 
> going to be installed
> E: Unable to correct problems, you have held broken packages.
>
>
> On Thursday, May 23, 2013 5:25:52 PM UTC-4, Eric Sorenson wrote:
>>
>> Quick question for those of you affected by this -- what did you to do to 
>> add the puppetlabs apt repo? 
>>
>> Did you do it through the method described here: 
>> http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#for-debian-and-ubuntu
>>
>> .. or some other way? I'm trying to suss out whether the docs / packages 
>> are messing people up.
>>
>> thx
>> eric0
>>
>> On Thursday, May 23, 2013 12:38:37 PM UTC-7, Matthew Kennedy wrote:
>>>
>>> I resolved this by adding the 'dependency' repo. I do wonder what the 
>>> purpose of having a separate repo? 
>>> On May 23, 2013 12:46 PM, "Chris Prior"  wrote:
>>>
 I am having the same issue...

 Running on Ubuntu as below:


 Distributor ID: Ubuntu
 Description: Ubuntu 12.04 LTS
 Release: 12.04
 Codename: precise


 Managed using Vagrant, puppet master being installed via the puppetlabs 
 puppet module from puppet forge:


 err: /Stage[main]/Puppet/Package[puppet]/ensure: change from purged to 
 lates

Re: [Puppet Users] Re: apt repository appears to have dependency issue with latest release (3.2.1)

[Justin]

Read through the thread and didn't see a fix. I'm running into this issue 
with a new Ubuntu server. Any help?

Here's how I installed the repo.

~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 12.10
Release:12.10
Codename:   quantal

~# wget -q https://apt.puppetlabs.com/puppetlabs-release-quantal.deb

~# dpkg -i puppetlabs-release-quantal.deb 
(Reading database ... 60865 files and directories currently installed.)
Preparing to replace puppetlabs-release 1.0-7 (using 
puppetlabs-release-quantal.deb) ...
Unpacking replacement puppetlabs-release ...
Setting up puppetlabs-release (1.0-7) ...

~# grep '^deb' /etc/apt/sources.list.d/puppetlabs.list
deb http://apt.puppetlabs.com quantal main
deb-src http://apt.puppetlabs.com quantal main
deb http://apt.puppetlabs.com quantal dependencies
deb-src http://apt.puppetlabs.com quantal dependencies

# apt-get install puppet
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 puppet : Depends: puppet-common (= 3.2.1-1puppetlabs1) but it is not going 
to be installed
E: Unable to correct problems, you have held broken packages.


On Thursday, May 23, 2013 5:25:52 PM UTC-4, Eric Sorenson wrote:
>
> Quick question for those of you affected by this -- what did you to do to 
> add the puppetlabs apt repo? 
>
> Did you do it through the method described here: 
> http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#for-debian-and-ubuntu
>
> .. or some other way? I'm trying to suss out whether the docs / packages 
> are messing people up.
>
> thx
> eric0
>
> On Thursday, May 23, 2013 12:38:37 PM UTC-7, Matthew Kennedy wrote:
>>
>> I resolved this by adding the 'dependency' repo. I do wonder what the 
>> purpose of having a separate repo? 
>> On May 23, 2013 12:46 PM, "Chris Prior"  wrote:
>>
>>> I am having the same issue...
>>>
>>> Running on Ubuntu as below:
>>>
>>>
>>> Distributor ID: Ubuntu
>>> Description: Ubuntu 12.04 LTS
>>> Release: 12.04
>>> Codename: precise
>>>
>>>
>>> Managed using Vagrant, puppet master being installed via the puppetlabs 
>>> puppet module from puppet forge:
>>>
>>>
>>> err: /Stage[main]/Puppet/Package[puppet]/ensure: change from purged to 
>>> latest failed: Could not update: Execution of '/usr/bin/apt-get -q -y -o 
>>> DPkg::Options::=--force-confold install puppet' returned 100: Reading 
>>> package lists...
>>> Building dependency tree...
>>> Reading state information...
>>> Some packages could not be installed. This may mean that you have 
>>> requested an impossible situation or if you are using the unstable 
>>> distribution that some required packages have not yet been created or been 
>>> moved out of Incoming.
>>> The following information may help to resolve the situation:
>>>
>>> The following packages have unmet dependencies:
>>> puppet : Depends: puppet-common (= 3.2.1-1puppetlabs1) but it is not 
>>> going to be installed
>>> E: Unable to correct problems, you have held broken packages.
>>> at /tmp/vagrant-puppet/modules-0/puppet/manifests/init.pp:39
>>>
>>>
>>> Chris
>>>
>>> On Wednesday, 22 May 2013 22:53:21 UTC+1, Matthew Kennedy wrote:

 When trying to install puppetmaster-passenger** from puppetlabs apt 
 repo I get... was working 2ish hours ago (before the 3.2 release)

 Some packages could not be installed. This may mean that you have
 requested an impossible situation or if you are using the unstable
 distribution that some required packages have not yet been created
 or been moved out of Incoming.
 The following information may help to resolve the situation:

 The following packages have unmet dependencies:
  puppetmaster-passenger : Depends: puppetmaster-common (= 
 3.2.1-1puppetlabs1) but it is not going to be installed
 E: Unable to correct problems, you have held broken packages.

 Thanks,
 Matt

>>>  -- 
>>> 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...@googlegroups.com.
>>> To post to this group, send email to puppet...@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
>>> 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 

Re: [Puppet Users] ruby issue

[Michael Stahnke]

On Wed, Jun 12, 2013 at 5:52 AM, Greg Chavez  wrote:
> Which is just fine if your company has the Optional subscription.
> Mine doesn't.  So I'm screwed unless I write a script to manually pull
> updates from Fedora or CentOS into a custom mrepo repository. Bit of a
> pain, that is.

The optional repo is free from what I can tell. It's included with a
RHEL subscription. Puppet Labs doesn't try to replace packages in
provided by the upstream OS vendor. Therefore, we don't supply
packages that replace things in the RHEL repo since they work just
fine with Puppet et al.


>
> On Tue, Jun 11, 2013 at 6:43 PM, Matthaus Owens  
> wrote:
>> We supply rubygems for rhel 5 because it is not available in centos or
>> rhel 5 core (it is in EPEL). In rhel6 and cent6, it is widely and
>> easily available (in cent6 base, and in rhel6 optional repos), so we
>> don't supply it for el6.
>>
>> On Tue, Jun 11, 2013 at 2:37 PM, Greg Chavez  wrote:
>>> The rubygems package is available from here:
>>>
>>> https://yum.puppetlabs.com/el/5/dependencies/x86_64/
>>>
>>> So why wouldn't it be available from 6?  I'm pretty sure it used to be
>>> there since I've kicked several rhel 6 systems that had no problem
>>> installing puppet from puppetlabs.  Was it mistakenly dropped from the
>>> puppetlabs rhel 6 repo?
>>>
>>> Thanks
>>> --Greg Chavez
>>>
>>> On Mon, Jun 10, 2013 at 11:12 AM, Stuart Cracraft  wrote:
 You are most welcome.

 On Jun 10, 2013, at 7:40 AM, Lab Yizhar  wrote:

 Thanks m8 for the mental support :)

 As you already know, as an open source believer ,I'm kind of into it and 
 the
 solution is there, But I want to do it without RHN subscription that will
 used on our production env.

 Couple of humps and I'll be there this way or the offical other...

 On Mon, Jun 10, 2013 at 4:31 PM, Stuart Cracraft  wrote:
>
> It's not that hard!
>
> You can do it!!!
>
> Also, you could buy some books on the subject!
>
> On Jun 10, 2013, at 5:51 AM, Yizhar A.  wrote:
>
> Hi,
>
> Finish my things on this issue for now as the last one in this chain
> talented enough to be asking for pay for answering this
>
> I'll update when I'll figure it out else.
>
> Stay tuned,
>
> Yizhar
>
> "Don't ask what the community can contribute to you ? ask what I can
> contribute the community"
> On Sunday, June 9, 2013 3:06:48 PM UTC+3, Yizhar A. wrote:
>>
>> Dear Stuart,
>>
>> Kind of my first steps into puppet on RHEL 6 and I wonder how you manage
>> to solve the rubygems issue.
>>
>> Since I'm using RHEL 6.4 (.x86_64) in my test env. with only puppetlabs
>> repo I can't see from where I can get the rubygems missing package.
>>
>> As you after wiki'd it :) can you give me a piece of advise in here or
>> attached your docs to help me through ?
>>
>> Thanks,
>>
>> --Yizhar
>>
>>
>> On Saturday, June 1, 2013 8:49:16 AM UTC+3, Stuart Cracraft wrote:
>>>
>>> Hey, good news.
>>>
>>> All is well.
>>>
>>> Ruby & related are good. Puppet too. And Red Hat.
>>>
>>> Also, I've documented/wiki'd the Puppet Master + Client install with
>>> respect
>>> to bare metal to delivered system for all related aspects and
>>> transmitted, fully,
>>> disclosed entirely, to staff.
>>>
>>> Next week, I will be tuning the configuration file on master and agents
>>> and
>>> writing many more puppet patterns plus training staff.
>>>
>>> As it is their only hope!
>>>
>>> --Stuart
>>>
>>> P.S. The firm's personnel have had heart attacks, strokes and other
>>> major maladies amongst
>>> staff in the past year due to the LACK OF AUTOMATION!!!
>>>
>>> Puppet is the Cure
>>>
>>> Kick Chef and CF Engine's non-collective butts!
>>>
>>>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Puppet Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/puppet-users/ghDZsdkC3C0/unsubscribe?hl=en.
> To unsubscribe from this group and all its topics, 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?hl=en.
> 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/g

Re: [Puppet Users] Re: Packages for Ubuntu 13.04 (raring)

[Andreas Ntaflos]

On 2013-06-14 01:49, Vlad wrote:
> Any news about the packages for Raring?

I've opened a bug report for this:
http://projects.puppetlabs.com/issues/21242

No feedback yet.

Andreas



signature.asc
Description: OpenPGP digital signature

[Puppet Users] Re: Agent revoked and reinstalled, now can't get server to see its new cert

[Josiah Ritchie]

No, I don't have anything in the certificate_requests folder.

On Friday, June 14, 2013 4:49:04 PM UTC-4, Nick Fagerlund wrote:
>
> Is this the behavior we covered in this other thread? 
> https://groups.google.com/forum/?fromgroups=#!topic/puppet-users/znlupoGbigMIf
>  an agent has an old file hanging around in certificate_requests, it will 
> try to download a signed certificate without first asking to have one 
> signed. 
>
> On Friday, June 14, 2013 11:43:24 AM UTC-7, Josiah Ritchie wrote:
>>
>> I just tried adding another agent without the cruft of the past to the 
>> puppet master and am getting the same activity as I was with the previous 
>> note. The two interact with each other and then simply. I tried wiping out 
>> the puppet/ssl directory of the master and another agent, then running the 
>> master in debug and agent in --no-daemonize --debug and the agents with 
>> --waitforcert 60.
>>
>> I keep seeing this in the master, but can only find information on what 
>> this means when it comes from the agent:
>>
>> Info: Could not find certificate for 'agent1'
>> Info: Could not find certificate for 'agent2'
>> Info: Could not find certificate for 'agent3'
>>
>> When I type 'sudo puppet cert list' it still shows me nothing to sign. 
>> When I try that with --all, it only shows me its own cert.
>>
>>
>> On Thursday, June 13, 2013 3:40:02 PM UTC-4, Josiah Ritchie wrote:
>>>
>>> I have a Ubuntu agent that I did all sorts of things to including 
>>> revoking the cert. It was a master for awhile and I played with foreman on 
>>> it. I then went through and apt-get purged all puppet related packages and 
>>> cleaned out anything left in the file system that had the name "puppet" in 
>>> it including puppet-common, did an apt-get autoremove.
>>>
>>> After the cleanup I went to the master and did a 'puppet cert clean 
>>> agent.name' and checked 'puppet cert list --all' to be certain it 
>>> wasn't present, stopped apache2 and made sure all master and passenger 
>>> services were stopped. Restarted apache2. 
>>>
>>> I went back to the agent, 'sudo apt-get install puppet' and 'sudo puppet 
>>> agent -t'. It generated the new key using the name I'd expect and cached 
>>> it, exiting with the message "no certificate found and waitforcert is 
>>> disabled"
>>>
>>> I can ping puppet and puppet.mydomain from the agent. It has the proper 
>>> IP set in /etc/hosts. The master can also ping the agent using the 
>>> appropriate name with and without domain.
>>>
>>> I went into /var/lib/puppet/ssl/ca/inventory.txt and removed the 
>>> reference to the agent. I confirmed nothing was in 
>>> /var/lib/puppet/ssl/certificate_requests and this agent is not 
>>> in /var/lib/puppet/ssl/ca/signed and ca/requests is empty.
>>>
>>> I tried 'locate agentname' and found nothing in the file system.
>>>
>>> I used tcpdump to confirm that when I run 'puppet agent -t' on the agent 
>>> it does talk to the master and the master talks back on port 8140.
>>>
>>> If I run it as 'sudo puppet agent --server puppet.mydomain 
>>> --no-daemonize --onetime --certname testagent.myotherdomain --waitforcert 
>>> 60', it dutifully creates a cert and waits while I go to the master and 
>>> find nothing it the 'puppet cert list'. Every 60 seconds I see 17 packets 
>>> of info passed around.
>>>
>>> What else can I do to get this agent back in the pen?
>>>
>>> Thanks,
>>> JSR/
>>>
>>

-- 
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: Agent revoked and reinstalled, now can't get server to see its new cert

[Nick Fagerlund]

Is this the behavior we covered in this other thread? 
https://groups.google.com/forum/?fromgroups=#!topic/puppet-users/znlupoGbigM 
If an agent has an old file hanging around in certificate_requests, it will 
try to download a signed certificate without first asking to have one 
signed. 

On Friday, June 14, 2013 11:43:24 AM UTC-7, Josiah Ritchie wrote:
>
> I just tried adding another agent without the cruft of the past to the 
> puppet master and am getting the same activity as I was with the previous 
> note. The two interact with each other and then simply. I tried wiping out 
> the puppet/ssl directory of the master and another agent, then running the 
> master in debug and agent in --no-daemonize --debug and the agents with 
> --waitforcert 60.
>
> I keep seeing this in the master, but can only find information on what 
> this means when it comes from the agent:
>
> Info: Could not find certificate for 'agent1'
> Info: Could not find certificate for 'agent2'
> Info: Could not find certificate for 'agent3'
>
> When I type 'sudo puppet cert list' it still shows me nothing to sign. 
> When I try that with --all, it only shows me its own cert.
>
>
> On Thursday, June 13, 2013 3:40:02 PM UTC-4, Josiah Ritchie wrote:
>>
>> I have a Ubuntu agent that I did all sorts of things to including 
>> revoking the cert. It was a master for awhile and I played with foreman on 
>> it. I then went through and apt-get purged all puppet related packages and 
>> cleaned out anything left in the file system that had the name "puppet" in 
>> it including puppet-common, did an apt-get autoremove.
>>
>> After the cleanup I went to the master and did a 'puppet cert clean 
>> agent.name' and checked 'puppet cert list --all' to be certain it wasn't 
>> present, stopped apache2 and made sure all master and passenger services 
>> were stopped. Restarted apache2. 
>>
>> I went back to the agent, 'sudo apt-get install puppet' and 'sudo puppet 
>> agent -t'. It generated the new key using the name I'd expect and cached 
>> it, exiting with the message "no certificate found and waitforcert is 
>> disabled"
>>
>> I can ping puppet and puppet.mydomain from the agent. It has the proper 
>> IP set in /etc/hosts. The master can also ping the agent using the 
>> appropriate name with and without domain.
>>
>> I went into /var/lib/puppet/ssl/ca/inventory.txt and removed the 
>> reference to the agent. I confirmed nothing was in 
>> /var/lib/puppet/ssl/certificate_requests and this agent is not 
>> in /var/lib/puppet/ssl/ca/signed and ca/requests is empty.
>>
>> I tried 'locate agentname' and found nothing in the file system.
>>
>> I used tcpdump to confirm that when I run 'puppet agent -t' on the agent 
>> it does talk to the master and the master talks back on port 8140.
>>
>> If I run it as 'sudo puppet agent --server puppet.mydomain --no-daemonize 
>> --onetime --certname testagent.myotherdomain --waitforcert 60', it 
>> dutifully creates a cert and waits while I go to the master and find 
>> nothing it the 'puppet cert list'. Every 60 seconds I see 17 packets of 
>> info passed around.
>>
>> What else can I do to get this agent back in the pen?
>>
>> Thanks,
>> JSR/
>>
>

-- 
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: 3.1.1 -> 3.2.1 load increase

[Jakov Sosic]

On 06/13/2013 04:26 PM, christian.le.fl...@gmail.com wrote:

Hi,
I recently updated from puppet 3.1.1 to 3.2.1 and noticed quite a bit of
increased load on the puppetmaster machine. I'm using
the Apache/passenger/rack way of puppetmastering.
Main symptom is: higher load on puppetmaster machine (8 cores):

  * 3.1.1: around 4
  * 3.2.1: around 9-10

Any idea why there's more load on the machine with 3.2.1?


You have to be a little bit more specific. Is load only CPU related, or 
I/O? Also, what do the log say? 3.2 pushes lots of notices about syntax 
obsolescence in the logs...



--
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] Re: Agent revoked and reinstalled, now can't get server to see its new cert

[Josiah Ritchie]

I just tried adding another agent without the cruft of the past to the 
puppet master and am getting the same activity as I was with the previous 
note. The two interact with each other and then simply. I tried wiping out 
the puppet/ssl directory of the master and another agent, then running the 
master in debug and agent in --no-daemonize --debug and the agents with 
--waitforcert 60.

I keep seeing this in the master, but can only find information on what 
this means when it comes from the agent:

Info: Could not find certificate for 'agent1'
Info: Could not find certificate for 'agent2'
Info: Could not find certificate for 'agent3'

When I type 'sudo puppet cert list' it still shows me nothing to sign. When 
I try that with --all, it only shows me its own cert.


On Thursday, June 13, 2013 3:40:02 PM UTC-4, Josiah Ritchie wrote:
>
> I have a Ubuntu agent that I did all sorts of things to including revoking 
> the cert. It was a master for awhile and I played with foreman on it. I 
> then went through and apt-get purged all puppet related packages and 
> cleaned out anything left in the file system that had the name "puppet" in 
> it including puppet-common, did an apt-get autoremove.
>
> After the cleanup I went to the master and did a 'puppet cert clean 
> agent.name' and checked 'puppet cert list --all' to be certain it wasn't 
> present, stopped apache2 and made sure all master and passenger services 
> were stopped. Restarted apache2. 
>
> I went back to the agent, 'sudo apt-get install puppet' and 'sudo puppet 
> agent -t'. It generated the new key using the name I'd expect and cached 
> it, exiting with the message "no certificate found and waitforcert is 
> disabled"
>
> I can ping puppet and puppet.mydomain from the agent. It has the proper IP 
> set in /etc/hosts. The master can also ping the agent using the appropriate 
> name with and without domain.
>
> I went into /var/lib/puppet/ssl/ca/inventory.txt and removed the reference 
> to the agent. I confirmed nothing was in 
> /var/lib/puppet/ssl/certificate_requests and this agent is not 
> in /var/lib/puppet/ssl/ca/signed and ca/requests is empty.
>
> I tried 'locate agentname' and found nothing in the file system.
>
> I used tcpdump to confirm that when I run 'puppet agent -t' on the agent 
> it does talk to the master and the master talks back on port 8140.
>
> If I run it as 'sudo puppet agent --server puppet.mydomain --no-daemonize 
> --onetime --certname testagent.myotherdomain --waitforcert 60', it 
> dutifully creates a cert and waits while I go to the master and find 
> nothing it the 'puppet cert list'. Every 60 seconds I see 17 packets of 
> info passed around.
>
> What else can I do to get this agent back in the pen?
>
> Thanks,
> JSR/
>

-- 
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: Disable A Windows Service Only If It Exists

[Paul Nickerson]

I came up with a solution using exec and sc.

In a module I called disable_services:

define disable_services {
  exec { "stop_${title}":
command => "C:\\Windows\\System32\\cmd.exe /c sc stop \"${title}\"",
onlyif  => "C:\\Windows\\System32\\cmd.exe /c sc query \"${title}\"",
unless  => "C:\\Windows\\System32\\cmd.exe /c sc query \"${title}\" | 
find \"STOPPED\"",
before  => Exec["disable_${title}"],
}
  exec { "disable_${title}":
command => "C:\\Windows\\System32\\cmd.exe /c sc config \"${title}\" 
start=disabled",
onlyif  => "C:\\Windows\\System32\\cmd.exe /c sc query \"${title}\"",
unless  => "C:\\Windows\\System32\\cmd.exe /c sc qc \"${title}\" | find 
\"DISABLED\"",
require => Exec["stop_${title}"],
}
  }

In a manifest:

disable_services { ["CVSNT", "CVSNT Locking Service", "CVS", "CVSLock"]: }

On Thursday, April 11, 2013 11:45:52 AM UTC-4, Paul Nickerson wrote:
>
> I am wondering whether it is possible to have Puppet only stop and disable 
> a Windows service if it exists. I have Puppet master 3.1.1 on CentOS, and 
> Puppet clients 3.1.1 on many Windows machines. Right now, I have the bit 
> below for certain nodes:
>
> service { "CVSNT":
> ensure => 'stopped',
> enable => 'false',
> }
>
> Some of the nodes have this service, some do not. Occasionally, new nodes 
> are added that this applies to (through inherits statements), and these new 
> nodes may or may not have this service. It's not just this service, either; 
> I have an array of services I need to ensure won't run. I just simplified 
> the above example with one service.
>
> If the Windows node does not have the service, then the Puppet agent still 
> runs successfully. But, when I run puppet agent --test in the Command 
> Prompt with Puppet on the node, I get this error:
>
> Error: /Stage[main]//Node[winbase]/Service[CVSNT]: Could not evaluate: 
> Cannot get status of CVSNT, error was: The specified service does not exist 
> as an installed service.
>
> The agent continues to run and completes successfully. But, getting 
> several of these lines at different points each time I run the Puppet agent 
> makes testing and debugging whatever other module I'm working on a little 
> difficult. I would like to get rid of the clutter.
>
> I've been researching this topic for a while, and haven't come up with any 
> solutions. Is there any way to have Puppet disable a Windows service only 
> if it exists? Or, is there a way to suppress these warning lines 
> without suppressing other output?

-- 
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 apply and send reports?

[Chris Lee]

I forgot to say thank you. The changes below worked perfectly.

At first I tried them just by changing on command line. Using 
--reports=http and --reporturl=
https://dashboard.example.com:3000/reports/upload , worked, but though I 
wasn't able to use --report=true so still nothing happened.
Modifying the report=true however on the central puppet.conf file on our 
netbooted systems worked perfectly and our dashboard very quickly started 
getting reports from all the nodes

Thanks again

Cheers
Chris

On Sunday, 24 February 2013 19:58:13 UTC+1, Nick Fagerlund wrote:
>
> Yes, you can definitely rig puppet apply to send reports. The trick is 
> that it works like a puppet master, not like a puppet agent, so you need to 
> configure the nodes to talk directly to the dashboard server; they can't go 
> through the puppet master. (It also means that by default, puppet apply has 
> "reports = store" and puts its run reports on the local disk in the 
> reportdir. I guess you could find those and manually import them into 
> dashboard, if you felt like it.)
>
> So, you need to set the following in each node's puppet.conf:
>
> # Use http report processor; don't bother storing reports on disk
> reports = http
> # Send reports to dashboard server
> reporturl = https://dashboard.example.com:3000/reports/upload
>

-- 
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] defined() implicitly requiring resource reference

[jcbollinger]

On Friday, June 14, 2013 9:14:07 AM UTC-5, jcbollinger wrote:
>
> Nevertheless, if it is not feasible for you to determine up front all the 
> packages your apps may be using or may want to use, then you can get by 
> with a smaller list, consisting of just the union of those packages 
> currently installed and those you want to be installed.
>


Do note, by the way, that this general approach of relying on a dynamic, 
client-supplied list of packages that may need to be removed is inherently 
more risky than one based on a centrally managed, static list of packages.  
If your custom fact malfunctions (or is subverted) then you could end up 
removing packages you did not intend to remove, including packages 
essential to the client's operation.


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] defined() implicitly requiring resource reference

[jcbollinger]

On Friday, June 14, 2013 2:01:50 AM UTC-5, Tom Lanyon wrote:
>
> Hi John 
>
> On 14/06/2013, at 12:06 AM, jcbollinger [...] wrote: 
>
> This is where it fell apart for me before, I didn't realise that you 
> assumed $::app_packages was every possible package;  in my first post I'd 
> specified that $::app_packages was a fact generated on each node from the 
> list of *currently installed* packages, so it contains all of the packages 
> which have been previously been installed but not packages which may be 
> installed in the future. 
>


My apologies for the confusion.

 

>
> I think it's going to be a managerial nightmare to update some such list 
> of all possible packages, so might look for an alternate solution.  I don't 
> think Puppet really meets our needs here, unless there's a way we can 
> programmatically parse out all of the versions of the package specified in 
> our manifests to include them in the $::app_packages (so they get defined 
> as 'purged') before building the rest of the catalog which would override 
> them as 'present'.



I think you're looking at it the wrong way around.  It is a fundamental 
problem for you if you don't know what all the packages you (may) want to 
manage are.  This is not information that ought to be gleaned from your 
manifest set, nor even information that you ought to be collecting 
dynamically from clients, but rather information which you ought to have a 
priori.  How you store it and keep it updated is a separate matter that I 
have heretofore avoided, but Puppet does have a capable external data 
interface, Hiera, that could reasonably be applied to the problem.

Nevertheless, if it is not feasible for you to determine up front all the 
packages your apps may be using or may want to use, then you can get by 
with a smaller list, consisting of just the union of those packages 
currently installed and those you want to be installed.  You already have 
those data at hand, and it is possible to merge them into the needed list.  
For example, rewriting my app::packages this way should help:

class app::packages {
$apps = unique(concat(split($::app_packages, ','), ))
package { $apps:
ensure => 'purged'
}
}

That might be paired with app::myapp declarations there or elsewhere of the 
form

app::myapp { : }

The  represents an array of the names of the packages you 
want installed, which could be a variable (including a parameter) of some 
class in the 'app' module (even app::packages itself), or might be a 
function call (e.g. to an external data service) or maybe something else.  
The unique() and concat() functions are available from PuppetLabs's popular 
"stdlib" add-in module.  


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: How to apply puppet manifests toa remote host?

[jcbollinger]

On Thursday, June 13, 2013 5:29:31 AM UTC-5, Sirisha wrote:
>
> Hi All,
>
> Am new to puppet and started writing simple  manifest files.
>
> I have setup Server/Client mode for puppet and when I try to apply my 
> manifest to local machine using "puppet agent" everything works well.
>
> Is there any option to apply the manifests to a remote machine without ssh 
> into the machine?
>


You cannot do anything to any machine without some kind of assistance from 
that machine.

The usual mode of operation for Puppet is to configure the agent to 
retrieve and apply configuration on some regular schedule, either by 
running it in daemon mode or by using an external scheduler such as cron.  
Regularly scheduled runs are great for ensuring that your machines retain 
their intended target configurations, including tracking any changes to 
that target.

On the other hand, if you're asking for a way to trigger runs *on 
demand*without logging in to the target machine, then you can configure the 
agent 
to listen on the network for signals from the master, generated by running 
'puppetrun' or 'puppet kick' there.  The agent will perform an ordinary run 
whenever it receives the correct signal.  The target node needs already to 
be paired with the master before this will work.


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] Executing a script after creating vhosts with create_resources

[Rachel Andrew]

On 12 Jun 2013, at 11:29, Brian Lalor  wrote:

> I'm pretty sure you'll have to do a custom define to make that happen, which 
> should play well with create_resources.  You could also play with a single 
> notify used by all of the resources that have been created…

thanks for the pointer, I mostly wanted to make sure I wasn't missing anything 
obvious. Still pretty new to Puppet.

Just in case anyone else reads this thread I wound up creating a custom define 
as a wrapper around vhost and database creation and using that for 
create_resources. Inside that I just make sure all the things are created 
before the execute command and it seems to be working nicely :)

Rachel

-- 
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: Introducing Pysa - Reverse your servers’ configurations!

[Thibault Bronchain]

Hi!

Indeed, it is similar to Blueprint. There is a quick comparison at the end 
of the Documentation (see links below).

It's my mistake for the links. You can get all informations about Pysa on 
Github and Pypi:
http://pypi.python.org/pypi/Pysa
http://github.com/MadeiraCloud/pysa

Best regards,
Thibault.


On Thursday, June 13, 2013 8:42:00 PM UTC+8, Thibault Bronchain wrote:
>
> Greetings all,
>
> I’m leaving this message about the development of a new configuration 
> reverse engineering tool: Pysa.
>
> Pysa aims to help anyone who wants to replicate an existing configuration 
> and not simply clone the entire machine.
> It can be use to migrate configurations from one computer to another (as 
> physical machines to virtual clouds), backup existing configurations, or 
> any other migration purpose.
>
> After scanning your system configuration, Pysa generates some Puppet 
> recipes for the basic setup of your servers: groups, users, hosts, 
> packages, configuration files, SSH keys, services, crons, source 
> repositories, etc.
> From this starting point you can modify the scripts to suit your exact 
> requirements.
>
> Pysa is open-source software (GNU/GPL license) published under 
> MadeiraCloud Ltd. Authority, and is still in its early-development stage 
> (alpha release).
> Please don’t hesitate to report any bugs, requirements, advice, 
> criticisms, hate or love messages to either pysa-user@googlegroups.comfor 
> public discussions and 
> p...@mc2.io for private messages.
>
> We depend on your feedback to help make this a useful tool for the 
> community.
>
> Best Regards,
>
> Thibault BRONCHAIN
> Pysa Lead Developer
>
>

-- 
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] defined() implicitly requiring resource reference

[Tom Lanyon]

Hi John

On 14/06/2013, at 12:06 AM, jcbollinger  wrote:
>> 
>> On Wednesday, June 12, 2013 9:15:22 AM UTC-5, Tom Lanyon wrote:
>> On 05/06/2013, at 11:51 PM, jcbollinger [...] wrote: 
>> > I don't much like that general approach in the first place on account of 
>> > the $requested_package parameter.  That you encounter difficulty when you 
>> > try something a bit dodgy should not be surprising. 
>> 
>> Can you explain this further so I can understand the issue? 
> 
> Initially, it was mostly a gut feeling.  After having had time to step back 
> from the issue and return to it fresh, I think it's a combination of things, 
> mostly revolving around what you're actually modeling, and how you're 
> modeling it.
> 
> Basically, the 'myapp' definition represents one package chosen from a list 
> of mutually exclusive packages.  If that's all it is, then its name is 
> misleading -- it should be more generic -- and it should probably take the 
> exclusive list as a second parameter.  On the other hand, if it is indeed 
> supposed to be something specific, then it doesn't take much advantage of 
> that.  In particular -- and here's where my previous comment came from -- if 
> it supposed to represent something specific to your application, then why 
> doesn't it know anything about the application's package names?
> 
> Also, if the point is supposed to be that only one version of the application 
> can be installed at a time, and the definition is specific to that 
> application, then it really ought to be a class instead.

Alas, the whole intention of this is that multiple versions of the package must 
be installed at the same time.  This is where the problem lies, in that we have 
no way to clean up old unused versions once they're no longer needed.

We have instances of an application MyApp, which utilise a shared Package in 
many to one relationship:

Package[one] ___ MyApp[app1]

Package[two] ___ MyApp[app2]
\___ MyApp[app3]

Package[three] _ MyApp[app4]
  \_ MyApp[app5]
  \_ MyApp[app6]

In the above example, if we upgraded MyApp[app2] and MyApp[app3] to 
Package[three], we'd still have Package[two] installed on all of the hosts but 
no MyApp instances would be using it.  This is the unused Package we're trying 
to clean up with Puppet (there's no longer a MyApp resource definition which 
references Package[two]).

There is no mutually exclusive packages or any other such conflicts.


>> > In fact, despite my dissatisfaction with your approach, you can indeed do 
>> > this without defined(), and without even disrupting your current structure 
>> > very much.  Here's one way I think would work: 
>> > 
>> > # This class ensures all known app packages are 
>> > # by default purged 
>> > class app::packages { 
>> >$apps = split($::app_packages, ',') 
>> >package { $apps: 
>> >ensure => 'purged' 
>> >} 
>> > } 
>> > 
>> > # Overrides the requested package to be declared 
>> > # present instead of purged. 
>> > define app::myapp($requested_package) { 
>> >include 'app::packages' 
>> >Package<| title == $requested_package |> { 
>> >ensure => 'present' 
>> >} 
>> > } 
>> > 
>> > # no separate package_cleanup required 
>> 
>> 
>> OK, I wondered whether we could do something like this however - forgive my 
>> naivety - I still can't see how this could be a complete solution without 
>> something like defined(). 
>> 
>> As an example... your above snippet works fine to ensure already installed 
>> packages remain installed, but what if we wanted to install a brand new 
>> version of app::myapp?  Because a 'package' resource with title 
>> $requested_package does not yet exist, the Package<||> collector matches no 
>> resources and the new package is not installed.  The only solution that I 
>> can come up with is to check whether such a resource is already defined and, 
>> if not, define one. 
> 
> You appear to have a serious misunderstanding.  Resource collectors have no 
> direct relationship with or dependency on which resources are already 
> installed on the target system.  They work exclusively with resource 
> declarations in your manifests, and they do so at catalog compilation time.  
> Moreover, they are independent of parse order (though the example anyway 
> ensures a parse order that would work if collectors were parse-order 
> dependent).

No, I understand this.

> Explanation of the example:
>   • class app::packages declares all of the possible application 
> packages, specifying the intended state for each one as 'purged'.  If that is 
> the only thing applied to the target node then it will cause the removal of 
> each and every one of those packages that is installed.  ('purged' is 
> stronger than 'absent'.  The former is more sure to remove the specified 
> package, but the latter takes care to avoid causing any other packages to be 
> removed, and therefore fails if any other package depends