[Puppet Users] 2016.4.0 ubuntu puppet enterprise install

2016-11-08 Thread Jay Benner
seems this command is failing and I don't know how I can make "puppet 
enterprise" be a valid subcommand.:

2016-11-08 14:32:21,008 Running command: /opt/puppetlabs/puppet/bin/puppet 
enterprise configure --debug --detailed-exitcodes --modulepath 
/opt/puppetlabs/server/data/enterprise/modules

*Error: Unknown Puppet subcommand 'enterprise'*



Can anyone tell me what I am doing wrong?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/8d83f366-d6e0-4ff5-be9d-fe79c6ec27a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] puppetdb api/powershell

2015-05-20 Thread Jay Benner
I wanted to use the puppetdb api to be able to sniff out some various 
anomalies that the console doesn't easily show me.  I wanted to do this via 
powershell because I know it better than bash or Python or whatever 
language smarter folks than me would use.  I had to wade through some 
poorly documented challenges and I thought I would share them with the 
other kids here.

Firstly, you need to make the certs meet up nicely.  The instructions for 
curl give three certs to use, but powershell's invoke-webrequest only 
accepts one.  I had to install openssl (cinst openssl.light) and run:

openssl pkcs12 -export -out c:\pupcert.pfx -inkey 
"C:\ProgramData\PuppetLabs\puppet\etc\ssl\private_keys\.pem" 
-in "C:\ProgramData\PuppetLabs\puppet\etc\ssl\certs\.pem" 
-certfile "C:\ProgramData\PuppetLabs\puppet\etc\ssl\certs\ca.pem"

I entered no password, but don't tell nobody.
Before it works, you'll need to whitelist the node you plan on using to run 
the script at "/etc/puppetlabs/puppetdb/certificate-whitelist".  If you do 
not, you will get the error "You shall not pass!" or somesuch sass.
Then, you can read the cert and start making requests and working with the 
data.  Here is a small script to view nodes that don't have the package 
"newrelic_dotnet_agent" in their catalog.


$package = "newrelic_dotnet_agent"
$cert = get-pfxCertificate c:\pupcert.pfx
$a = Invoke-WebRequest -Uri https://puppet:8081/v3/nodes -method GET 
-Certificate $cert
$c = $a.Content | ConvertFrom-Json

  foreach ($b in $c){
$d = $b.name
$e = Invoke-WebRequest -Uri 
https://puppet:8081/v3/nodes/$d/resources/Package/$package -method GET 
-Certificate $cert
if ($e.content -eq "[ ]"){
$d
}
clear-variable $e
}





I hope this saves someone else a lot of hassle working with certs and 
whitelists and specificurls.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/2340a9d0-6bed-4546-9d9d-0f3c6f291ce9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Puppet Users] Fresh Puppet PE 3.8 install error

2015-05-01 Thread Jay Benner
Nailed it!  Not sure which package did the trick, but smooth sailing after 
installing these.

On Thursday, April 30, 2015 at 5:21:20 PM UTC-7, Kamil Keski wrote:
>
> Scratch 2.1.5 as the issue.  Quick lsof shows that everything is still 
> using the 1.9.1 binary pulled in the install.  Only other thing I installed 
> was the following packages as they are my default pulls for a ruby build.
>
> zlib1g-dev build-essential libssl-dev libreadline-dev libyaml-dev 
> libsqlite3-dev sqlite3 libxml2-dev libxslt1-dev libcurl4-openssl-dev 
> python-software-properties
>
> I'm not going any deeper than that on this one.  I'm tired of drudging 
> through .rb's and am leaving this as is.
>
> Still, on a pure fresh Ubuntu 12.04 or 14.04 install there is a dependency 
> that the PE installer is not pulling down.
>
> If you're a user and need a quick fix just install the above packages.
>
> Puppet devs, if you can track down which and package that into the 
> installer that would be fantastic.
>
> Thanks,
> K
>
> On Thursday, April 30, 2015 at 3:43:27 PM UTC-6, Kamil Keski wrote:
>>
>> Going to answer my own question here as there is likely no way a fresh 
>> install of PE 3.8 will succeed on Ubuntu 12.04 or 14.04.  Ruby comes 
>> preinstalled with the distro's with a version of 1.9 (old for sure). 
>>  However this should be known.  I Installed 2.1.5, made global and the 
>> installation of PE 3.8 succeeded.
>>
>> I'd like to see the PE install updated to pull a version of Ruby that it 
>> requires (who knows, 2.0 may be sufficient).  At minimum listing that you 
>> have a minimum version of Ruby installed as a prerequisite.
>>
>> On Thursday, April 30, 2015 at 12:50:27 PM UTC-6, Kamil Keski wrote:
>>>
>>> Yes, I've added the temp path arg to the pe-puppetserver init as well. 
>>>  No go.
>>>
>>> Has anyone installed successfully from scratch using an ubuntu 12.04 or 
>>> 14.04 distro?  Not an existing one, but a nice fresh build?
>>>
>>> On Thursday, April 30, 2015 at 11:49:29 AM UTC-6, Martin Alfke wrote:

 Hi Kamil,

 have you tried setting the path attribute at the exec resource?
 Puppet exec starts with an empty environment and you are using several 
 Unix commands without full path.

 hth,
 Martin
 On Apr 30, 2015 7:29 PM, "Kamil Keski"  wrote:

> Thanks for the reply Josh.  I worked through this and other posts I 
> found pointing to the tmp issue.  However I don't have /tmp or /usr/tmp 
> mounted, they are just dir's on the root mount.
>
> fstab:
>
> #
> /dev/mapper/ITTPuppet--vg-root /   ext4   
>  errors=remount-ro 0   1
> # /boot was on /dev/sda1 during installation
> UUID=89c2c14f-03a6-4f43-9935-25061c52e4f9 /boot   ext2   
>  defaults0   2
> /dev/mapper/ITTPuppet--vg-swap_1 noneswapsw   
>0   0
> /dev/fd0/media/floppy0  autorw,user,noauto,exec,utf8 0 
>   0
>
> Pretty vanilla stuff here, so noexecute should not be an issue in this 
> instance.  For good measure I tried creating a new dir (/usr/tmp) with 
> 777 
> and defined -Djava.io.tmpdir=/usr/tmp globally via my /bashrc profile for 
> the user I'm running under and root.  Verified that was picked up via 
> java 
> -version.
>
> Picked up _JAVA_OPTIONS: -Djava.io.tmpdir=/usr/tmp
> java version "1.6.0_35"
> OpenJDK Runtime Environment (IcedTea6 1.13.7) 
> (6b35-1.13.7-1ubuntu0.12.04.2)
> OpenJDK 64-Bit Server VM (build 23.25-b01, mixed mode)
>
> Still same behavior.  I don't see how anyone has worked through a 
> fresh install on Ubuntu at this point.
>
> Thanks,
> K
>
> On Wednesday, April 29, 2015 at 4:03:13 PM UTC-6, Josh Cooper wrote:
>>
>>
>>
>> On Wed, Apr 29, 2015 at 1:10 PM, Kamil Keski  
>> wrote:
>>
>>> Clean slate install on Ubuntu 14.04 produces the following error and 
>>> will not proceed.
>>>
>>> ** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= curl --tlsv1 -s 
>>> https://puppetmaster.local:8140
>>> ** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= curl --tlsv1 -s 
>>> https://puppetmaster.local:8140
>>> ** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= curl --tlsv1 -s 
>>> https://puppetmaster.local:8140
>>> ** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= curl --tlsv1 -s 
>>> https://puppetmaster.local:8140
>>>
>>> 
>>> ** cp /opt/puppet/share/installer/install_log.lastrun.ITTPuppet.log 
>>> /var/log/pe-installer
>>> ** sed "s/^\(q_.*password\)=.*/#\1=REDACTED/g" < 
>>> "/tmp/pe-installer-M4MbxK1G/install/answers.lastrun.ITTPuppet" > 
>>> "/var/log/pe-installer/answers.install"
>>> !! ERROR: The puppet master service failed to start within 120
>>>seconds; u

[Puppet Users] Re: Fresh Puppet PE 3.8 install error

2015-04-29 Thread Jay Benner
I've been chasing this around all day today.  I have no idea what this is 
or how to get around it.  

On Wednesday, April 29, 2015 at 1:41:20 PM UTC-7, Kamil Keski wrote:
>
> Clean slate install on Ubuntu 14.04 produces the following error and will 
> not proceed.
>
> ** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= curl --tlsv1 -s 
> https://puppetmaster.local:8140
> ** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= curl --tlsv1 -s 
> https://puppetmaster.local:8140
> ** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= curl --tlsv1 -s 
> https://puppetmaster.local:8140
> ** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= curl --tlsv1 -s 
> https://puppetmaster.local:8140
>
> 
> ** cp /opt/puppet/share/installer/install_log.lastrun.ITTPuppet.log 
> /var/log/pe-installer
> ** sed "s/^\(q_.*password\)=.*/#\1=REDACTED/g" < 
> "/tmp/pe-installer-M4MbxK1G/install/answers.lastrun.ITTPuppet" > 
> "/var/log/pe-installer/answers.install"
> !! ERROR: The puppet master service failed to start within 120
>seconds; unable to proceed
>
>
> I am using puppetmaster.local as the FQDN which is resolvable from the 
> server and the client machine I'm executing the web install from (mapped in 
> hosts file for testing).  Nothing else of interest in the log files.  Have 
> tried on two separate clean images to no avail.
>
> pe-puppetserver log shows the following.
>
> Failed to load feature test for posix: can't find user for 0
> Cannot run on Microsoft Windows without the win32-process, win32-dir and 
> win32-service gems: Win32API only supported on win32
> Puppet::Error: Cannot determine basic system flavour
>  (root) at 
> /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/feature/base.rb:32
> require at org/jruby/RubyKernel.java:1071
>
> Well that's interesting..
>
> All default packages have been updated.
>
> Maddening!
>
> Any idea's?
>
> Thanks,
> K
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/2dc91117-c122-4c9a-ad2c-01fa34eb2eb9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] rake edits not showing up in the console

2014-09-20 Thread Jay Benner
Edits done via node:groups are reporting back "successfully edited", but 
when I look in the console, no change.  What gives?

Ubuntu 12.04
Puppet Enterprise 3.2.0

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/134492c6-5bad-4550-91fc-7aff38543097%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] report all nodes that do NOT have a certain class assigned to them

2014-06-24 Thread Jay Benner
Seems like this should be easy, but I am having a tough time sorting it 
out.  
I am using PE 3.1 and I want to know which of my nodes are missing a 
certain class.  Its pretty easy to get a list of the nodes that have the 
class in the console, but that still leaves a lot of math for me to do as I 
have thousands of nodes.  The search inventory tool has something close 
with being able to search via fact presence or absence, but there doesn't 
seem to be a fact that corresponds to my class.  Even if I distributed a 
fact with my class, that would only report for nodes that actually got the 
class, whereas I want hits on the fact's absence.  Anyone solved this 
riddle already?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/e5187012-2753-42a1-9a56-6f0d4bacb252%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] Puppet enterprise console, all nodes 'unresponsive'.

2014-05-06 Thread Jay Benner
I had some corruption in my puppetdb and had to rebuild my KahaDB 
directory.  After doing so I restarted everything, but all of the puppet 
nodes still show 'unresponsive', even after a successful puppet run.  Looks 
like things are running smoothely now, only the console isn't updating 
properly. 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/8d568cc9-962b-4b83-af8c-8947bb9e3513%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] Error 400 on SERVER: invalid byte sequence in UTF-8

2014-03-05 Thread Jay Benner
I keep getting this error with a module I wrote.  Apparently, it doesn't 
like something about my module, but I don't see anything interesting about 
it.  I found the bug below, but I don't know which config.ru to edit for 
the workaround.  Has anyone else seen this?

https://projects.puppetlabs.com/issues/20897

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/7c9b79b9-325e-4afc-8b26-ec3907ea457f%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [Puppet Users] Re: moving from previous manual install to puppet/chocolatey

2014-02-18 Thread Jay Benner
Thats cutting it pretty close for me.  I am preparing for a pretty high 
profile demo to some execs next Wednesday.  I'll need at least a day to 
test it out.  I don't think I'll be fired if I'm not ready to demo this 
module, but it would really help me evangelize the product against a high 
profile issue.

On Tuesday, February 18, 2014 10:26:15 AM UTC-8, Rob Reynolds wrote:
>
>
>
>
> On Tue, Feb 18, 2014 at 12:10 PM, Jay Benner 
> > wrote:
>
>> PS - This system that I am working on is very much a test system, so we 
>> can try whatever we want on it.  It is representative of a lot of other 
>> systems on my network, though, so I do need to land on a semi-elegant 
>> solution at some point.
>>
>
> Ah fantastic. Let's hope I can get the provider to stop throwing that 
> error sometime this week or next. Would that be within your range of 
> needing a solution?
>  
>
>>
>> On Tuesday, February 18, 2014 8:03:45 AM UTC-8, Rob Reynolds wrote:
>>>
>>>
>>>
>>>
>>> On Mon, Feb 17, 2014 at 2:57 PM, Jay Benner  wrote:
>>>
>>>> I tried them in chocolatey.ps1, but that just seemed to break 
>>>> chocolatey.
>>>>
>>>>
>>>> On Monday, February 17, 2014 11:11:25 AM UTC-8, Jay Benner wrote:
>>>>>
>>>>> If I am going to use the workarounds mentioned in the bug article you 
>>>>> referenced, should I put that code into chocolateyinstall.ps1?
>>>>>
>>>>
>>> Those workarounds will likely need to go back into chocolatey or the 
>>> provider itself. It seems to be running into some error but once it tries 
>>> to write the error it runs into the issue you are running into, making the 
>>> error harder to find. 
>>>  
>>>
>>>>
>>>>> On Friday, February 14, 2014 1:57:12 PM UTC-8, Rob Reynolds wrote:
>>>>>>
>>>>>> It looks to be a possible bug in the chocolatey provider that happens 
>>>>>> when we try to capture both error and regular logging when an error has 
>>>>>> occurred. Keep a watch on the issue itself for updates.
>>>>>>
>>>>>> In the meantime if you are using SYSTEM for the puppet agent, I would 
>>>>>> switch to something with network access and see if chocolatey works 
>>>>>> inside 
>>>>>> of puppet.
>>>>>>
>>>>>>
>>>>>> On Fri, Feb 14, 2014 at 3:33 PM, Jay Benner wrote:
>>>>>>
>>>>>>> Some improvement.  I'll attach another chocolateyinstall log below.  
>>>>>>> It still didn't install the agent, but it also didn't add an entry to 
>>>>>>> /lib, 
>>>>>>> so I'm guessing it will keep trying.  Looks like the same error 
>>>>>>> downloading 
>>>>>>> the file.
>>>>>>>
>>>>>>> http://pastebin.com/BFd90qkb
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Friday, February 14, 2014 10:55:51 AM UTC-8, Rob Reynolds wrote:
>>>>>>>
>>>>>>>> Let's have you upgrade chocolatey to 0.9.8.23 and see if the issue 
>>>>>>>> still happens. The paste bin shows 0.9.8.20.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Fri, Feb 14, 2014 at 12:53 PM, Rob Reynolds >>>>>>> > wrote:
>>>>>>>>
>>>>>>>>> You are running into an issue we have seen but have not been able 
>>>>>>>>> to reproduce effectively - https://github.com/chocolatey/
>>>>>>>>> puppet-chocolatey/issues/18
>>>>>>>>>  
>>>>>>>>>
>>>>>>>>> On Fri, Feb 14, 2014 at 12:47 PM, Jay Benner wrote:
>>>>>>>>>
>>>>>>>>>> The following is a copy of my log:
>>>>>>>>>> http://pastebin.com/wz5peZbG
>>>>>>>>>> Looks like the download failed.  Perhaps a problem with puppet 
>>>>>>>>>> not being able to access my personal temp folder?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Friday, February 14, 2014 9:58:53 AM UTC-8, Rob Reynolds wrote:
>>>>>>>>>>

Re: [Puppet Users] Re: moving from previous manual install to puppet/chocolatey

2014-02-18 Thread Jay Benner
PS - This system that I am working on is very much a test system, so we can 
try whatever we want on it.  It is representative of a lot of other systems 
on my network, though, so I do need to land on a semi-elegant solution at 
some point.

On Tuesday, February 18, 2014 8:03:45 AM UTC-8, Rob Reynolds wrote:
>
>
>
>
> On Mon, Feb 17, 2014 at 2:57 PM, Jay Benner 
> > wrote:
>
>> I tried them in chocolatey.ps1, but that just seemed to break chocolatey.
>>
>>
>> On Monday, February 17, 2014 11:11:25 AM UTC-8, Jay Benner wrote:
>>>
>>> If I am going to use the workarounds mentioned in the bug article you 
>>> referenced, should I put that code into chocolateyinstall.ps1?
>>>
>>
> Those workarounds will likely need to go back into chocolatey or the 
> provider itself. It seems to be running into some error but once it tries 
> to write the error it runs into the issue you are running into, making the 
> error harder to find. 
>  
>
>>
>>> On Friday, February 14, 2014 1:57:12 PM UTC-8, Rob Reynolds wrote:
>>>>
>>>> It looks to be a possible bug in the chocolatey provider that happens 
>>>> when we try to capture both error and regular logging when an error has 
>>>> occurred. Keep a watch on the issue itself for updates.
>>>>
>>>> In the meantime if you are using SYSTEM for the puppet agent, I would 
>>>> switch to something with network access and see if chocolatey works inside 
>>>> of puppet.
>>>>
>>>>
>>>> On Fri, Feb 14, 2014 at 3:33 PM, Jay Benner  wrote:
>>>>
>>>>> Some improvement.  I'll attach another chocolateyinstall log below.  
>>>>> It still didn't install the agent, but it also didn't add an entry to 
>>>>> /lib, 
>>>>> so I'm guessing it will keep trying.  Looks like the same error 
>>>>> downloading 
>>>>> the file.
>>>>>
>>>>> http://pastebin.com/BFd90qkb
>>>>>
>>>>>
>>>>>
>>>>> On Friday, February 14, 2014 10:55:51 AM UTC-8, Rob Reynolds wrote:
>>>>>
>>>>>> Let's have you upgrade chocolatey to 0.9.8.23 and see if the issue 
>>>>>> still happens. The paste bin shows 0.9.8.20.
>>>>>>
>>>>>>
>>>>>> On Fri, Feb 14, 2014 at 12:53 PM, Rob Reynolds 
>>>>>> wrote:
>>>>>>
>>>>>>> You are running into an issue we have seen but have not been able to 
>>>>>>> reproduce effectively - https://github.com/chocolatey/
>>>>>>> puppet-chocolatey/issues/18
>>>>>>>  
>>>>>>>
>>>>>>> On Fri, Feb 14, 2014 at 12:47 PM, Jay Benner wrote:
>>>>>>>
>>>>>>>> The following is a copy of my log:
>>>>>>>> http://pastebin.com/wz5peZbG
>>>>>>>> Looks like the download failed.  Perhaps a problem with puppet not 
>>>>>>>> being able to access my personal temp folder?
>>>>>>>>
>>>>>>>>
>>>>>>>> On Friday, February 14, 2014 9:58:53 AM UTC-8, Rob Reynolds wrote:
>>>>>>>>
>>>>>>>>> I looks like it does install the package, but may be running into 
>>>>>>>>> something else when it is running. In C:\chocolatey\
>>>>>>>>> chocolateyInstall there are some log files, what does the log 
>>>>>>>>> file say about the installation?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thu, Feb 13, 2014 at 2:10 PM, Jay Benner wrote:
>>>>>>>>>
>>>>>>>>>>  I had deleted the entry in /lib.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wednesday, February 12, 2014 2:37:49 PM UTC-8, Jay Benner 
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> I have a bunch of windows servers with NewRelic installed on 
>>>>>>>>>>> them and I want to start managing those installs with Puppet.  
>>>>>>>>>>> Seemed like 
>>>>>>>>>>> the thing to do would be to have chocolatey uninstall what is there 
>>>>>>>>>>>

Re: [Puppet Users] Re: moving from previous manual install to puppet/chocolatey

2014-02-17 Thread Jay Benner
I tried them in chocolatey.ps1, but that just seemed to break chocolatey.

On Monday, February 17, 2014 11:11:25 AM UTC-8, Jay Benner wrote:
>
> If I am going to use the workarounds mentioned in the bug article you 
> referenced, should I put that code into chocolateyinstall.ps1?
>
> On Friday, February 14, 2014 1:57:12 PM UTC-8, Rob Reynolds wrote:
>>
>> It looks to be a possible bug in the chocolatey provider that happens 
>> when we try to capture both error and regular logging when an error has 
>> occurred. Keep a watch on the issue itself for updates.
>>
>> In the meantime if you are using SYSTEM for the puppet agent, I would 
>> switch to something with network access and see if chocolatey works inside 
>> of puppet.
>>
>>
>> On Fri, Feb 14, 2014 at 3:33 PM, Jay Benner  wrote:
>>
>>> Some improvement.  I'll attach another chocolateyinstall log below.  It 
>>> still didn't install the agent, but it also didn't add an entry to /lib, so 
>>> I'm guessing it will keep trying.  Looks like the same error downloading 
>>> the file.
>>>
>>> http://pastebin.com/BFd90qkb
>>>
>>>
>>>
>>> On Friday, February 14, 2014 10:55:51 AM UTC-8, Rob Reynolds wrote:
>>>
>>>> Let's have you upgrade chocolatey to 0.9.8.23 and see if the issue 
>>>> still happens. The paste bin shows 0.9.8.20.
>>>>
>>>>
>>>> On Fri, Feb 14, 2014 at 12:53 PM, Rob Reynolds wrote:
>>>>
>>>>> You are running into an issue we have seen but have not been able to 
>>>>> reproduce effectively - https://github.com/chocolatey/
>>>>> puppet-chocolatey/issues/18
>>>>>  
>>>>>
>>>>> On Fri, Feb 14, 2014 at 12:47 PM, Jay Benner wrote:
>>>>>
>>>>>> The following is a copy of my log:
>>>>>> http://pastebin.com/wz5peZbG
>>>>>> Looks like the download failed.  Perhaps a problem with puppet not 
>>>>>> being able to access my personal temp folder?
>>>>>>
>>>>>>
>>>>>> On Friday, February 14, 2014 9:58:53 AM UTC-8, Rob Reynolds wrote:
>>>>>>
>>>>>>> I looks like it does install the package, but may be running into 
>>>>>>> something else when it is running. In C:\chocolatey\chocolateyInstall 
>>>>>>> there are some log files, what does the log file say about the 
>>>>>>> installation?
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Feb 13, 2014 at 2:10 PM, Jay Benner wrote:
>>>>>>>
>>>>>>>>  I had deleted the entry in /lib.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wednesday, February 12, 2014 2:37:49 PM UTC-8, Jay Benner wrote:
>>>>>>>>
>>>>>>>>> I have a bunch of windows servers with NewRelic installed on them 
>>>>>>>>> and I want to start managing those installs with Puppet.  Seemed like 
>>>>>>>>> the 
>>>>>>>>> thing to do would be to have chocolatey uninstall what is there and 
>>>>>>>>> reinstall within the framework of chocolatey so that I get 
>>>>>>>>> addressable 
>>>>>>>>> version information and the like.  I created the following chocolatey 
>>>>>>>>> package and it works fine when run from the command line using cinst: 
>>>>>>>>> any 
>>>>>>>>> existing version is removed and the new version, managed by 
>>>>>>>>> chocolatey, 
>>>>>>>>> gets put in its place.  However, when I run it from Puppet, it does 
>>>>>>>>> the 
>>>>>>>>> uninstall ok, but the install never happens, even though chocolatey 
>>>>>>>>> seems 
>>>>>>>>> to think that the package is installed.  
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> stop-service "LiveVault Backup Service"
>>>>>>>>> $app = Get-WmiObject -Class Win32_Product | Where-Object { 
>>>>>>>>> $_.Name -match "New Relic Server Monitor" 
>>>>>>>>> }
>>>>>>>>>
>>>>>>>>> $app.Uninstall()
&

Re: [Puppet Users] Re: moving from previous manual install to puppet/chocolatey

2014-02-17 Thread Jay Benner
If I am going to use the workarounds mentioned in the bug article you 
referenced, should I put that code into chocolateyinstall.ps1?

On Friday, February 14, 2014 1:57:12 PM UTC-8, Rob Reynolds wrote:
>
> It looks to be a possible bug in the chocolatey provider that happens when 
> we try to capture both error and regular logging when an error has 
> occurred. Keep a watch on the issue itself for updates.
>
> In the meantime if you are using SYSTEM for the puppet agent, I would 
> switch to something with network access and see if chocolatey works inside 
> of puppet.
>
>
> On Fri, Feb 14, 2014 at 3:33 PM, Jay Benner 
> > wrote:
>
>> Some improvement.  I'll attach another chocolateyinstall log below.  It 
>> still didn't install the agent, but it also didn't add an entry to /lib, so 
>> I'm guessing it will keep trying.  Looks like the same error downloading 
>> the file.
>>
>> http://pastebin.com/BFd90qkb
>>
>>
>>
>> On Friday, February 14, 2014 10:55:51 AM UTC-8, Rob Reynolds wrote:
>>
>>> Let's have you upgrade chocolatey to 0.9.8.23 and see if the issue still 
>>> happens. The paste bin shows 0.9.8.20.
>>>
>>>
>>> On Fri, Feb 14, 2014 at 12:53 PM, Rob Reynolds wrote:
>>>
>>>> You are running into an issue we have seen but have not been able to 
>>>> reproduce effectively - https://github.com/chocolatey/
>>>> puppet-chocolatey/issues/18
>>>>  
>>>>
>>>> On Fri, Feb 14, 2014 at 12:47 PM, Jay Benner  wrote:
>>>>
>>>>> The following is a copy of my log:
>>>>> http://pastebin.com/wz5peZbG
>>>>> Looks like the download failed.  Perhaps a problem with puppet not 
>>>>> being able to access my personal temp folder?
>>>>>
>>>>>
>>>>> On Friday, February 14, 2014 9:58:53 AM UTC-8, Rob Reynolds wrote:
>>>>>
>>>>>> I looks like it does install the package, but may be running into 
>>>>>> something else when it is running. In C:\chocolatey\chocolateyInstall 
>>>>>> there are some log files, what does the log file say about the 
>>>>>> installation?
>>>>>>
>>>>>>
>>>>>> On Thu, Feb 13, 2014 at 2:10 PM, Jay Benner wrote:
>>>>>>
>>>>>>>  I had deleted the entry in /lib.
>>>>>>>
>>>>>>>
>>>>>>> On Wednesday, February 12, 2014 2:37:49 PM UTC-8, Jay Benner wrote:
>>>>>>>
>>>>>>>> I have a bunch of windows servers with NewRelic installed on them 
>>>>>>>> and I want to start managing those installs with Puppet.  Seemed like 
>>>>>>>> the 
>>>>>>>> thing to do would be to have chocolatey uninstall what is there and 
>>>>>>>> reinstall within the framework of chocolatey so that I get addressable 
>>>>>>>> version information and the like.  I created the following chocolatey 
>>>>>>>> package and it works fine when run from the command line using cinst: 
>>>>>>>> any 
>>>>>>>> existing version is removed and the new version, managed by 
>>>>>>>> chocolatey, 
>>>>>>>> gets put in its place.  However, when I run it from Puppet, it does 
>>>>>>>> the 
>>>>>>>> uninstall ok, but the install never happens, even though chocolatey 
>>>>>>>> seems 
>>>>>>>> to think that the package is installed.  
>>>>>>>>
>>>>>>>>
>>>>>>>> stop-service "LiveVault Backup Service"
>>>>>>>> $app = Get-WmiObject -Class Win32_Product | Where-Object { 
>>>>>>>> $_.Name -match "New Relic Server Monitor" 
>>>>>>>> }
>>>>>>>>
>>>>>>>> $app.Uninstall()
>>>>>>>> $licensekey = "XX"
>>>>>>>>
>>>>>>>> $packageName = 'NewRelic_ServerMonitor'
>>>>>>>> $installerType = 'MSI' 
>>>>>>>> $url = 'http://download.newrelic.com/windows_server_monitor/
>>>>>>>> release/NewRelicServerMonitor_x86_2.0.0.198.msi'
>>>>>>>> $url64 = 'http://download.newreli

Re: [Puppet Users] Re: moving from previous manual install to puppet/chocolatey

2014-02-14 Thread Jay Benner
I ran it as me and it behaved the same.

On Friday, February 14, 2014 1:57:12 PM UTC-8, Rob Reynolds wrote:
>
> It looks to be a possible bug in the chocolatey provider that happens when 
> we try to capture both error and regular logging when an error has 
> occurred. Keep a watch on the issue itself for updates.
>
> In the meantime if you are using SYSTEM for the puppet agent, I would 
> switch to something with network access and see if chocolatey works inside 
> of puppet.
>
>
> On Fri, Feb 14, 2014 at 3:33 PM, Jay Benner 
> > wrote:
>
>> Some improvement.  I'll attach another chocolateyinstall log below.  It 
>> still didn't install the agent, but it also didn't add an entry to /lib, so 
>> I'm guessing it will keep trying.  Looks like the same error downloading 
>> the file.
>>
>> http://pastebin.com/BFd90qkb
>>
>>
>>
>> On Friday, February 14, 2014 10:55:51 AM UTC-8, Rob Reynolds wrote:
>>
>>> Let's have you upgrade chocolatey to 0.9.8.23 and see if the issue still 
>>> happens. The paste bin shows 0.9.8.20.
>>>
>>>
>>> On Fri, Feb 14, 2014 at 12:53 PM, Rob Reynolds wrote:
>>>
>>>> You are running into an issue we have seen but have not been able to 
>>>> reproduce effectively - https://github.com/chocolatey/
>>>> puppet-chocolatey/issues/18
>>>>  
>>>>
>>>> On Fri, Feb 14, 2014 at 12:47 PM, Jay Benner  wrote:
>>>>
>>>>> The following is a copy of my log:
>>>>> http://pastebin.com/wz5peZbG
>>>>> Looks like the download failed.  Perhaps a problem with puppet not 
>>>>> being able to access my personal temp folder?
>>>>>
>>>>>
>>>>> On Friday, February 14, 2014 9:58:53 AM UTC-8, Rob Reynolds wrote:
>>>>>
>>>>>> I looks like it does install the package, but may be running into 
>>>>>> something else when it is running. In C:\chocolatey\chocolateyInstall 
>>>>>> there are some log files, what does the log file say about the 
>>>>>> installation?
>>>>>>
>>>>>>
>>>>>> On Thu, Feb 13, 2014 at 2:10 PM, Jay Benner wrote:
>>>>>>
>>>>>>>  I had deleted the entry in /lib.
>>>>>>>
>>>>>>>
>>>>>>> On Wednesday, February 12, 2014 2:37:49 PM UTC-8, Jay Benner wrote:
>>>>>>>
>>>>>>>> I have a bunch of windows servers with NewRelic installed on them 
>>>>>>>> and I want to start managing those installs with Puppet.  Seemed like 
>>>>>>>> the 
>>>>>>>> thing to do would be to have chocolatey uninstall what is there and 
>>>>>>>> reinstall within the framework of chocolatey so that I get addressable 
>>>>>>>> version information and the like.  I created the following chocolatey 
>>>>>>>> package and it works fine when run from the command line using cinst: 
>>>>>>>> any 
>>>>>>>> existing version is removed and the new version, managed by 
>>>>>>>> chocolatey, 
>>>>>>>> gets put in its place.  However, when I run it from Puppet, it does 
>>>>>>>> the 
>>>>>>>> uninstall ok, but the install never happens, even though chocolatey 
>>>>>>>> seems 
>>>>>>>> to think that the package is installed.  
>>>>>>>>
>>>>>>>>
>>>>>>>> stop-service "LiveVault Backup Service"
>>>>>>>> $app = Get-WmiObject -Class Win32_Product | Where-Object { 
>>>>>>>> $_.Name -match "New Relic Server Monitor" 
>>>>>>>> }
>>>>>>>>
>>>>>>>> $app.Uninstall()
>>>>>>>> $licensekey = "XX"
>>>>>>>>
>>>>>>>> $packageName = 'NewRelic_ServerMonitor'
>>>>>>>> $installerType = 'MSI' 
>>>>>>>> $url = 'http://download.newrelic.com/windows_server_monitor/
>>>>>>>> release/NewRelicServerMonitor_x86_2.0.0.198.msi'
>>>>>>>> $url64 = 'http://download.newrelic.com/windows_server_monito
>>>>>>>> r/release/NewRelicServerMonitor_x64

Re: [Puppet Users] Re: moving from previous manual install to puppet/chocolatey

2014-02-14 Thread Jay Benner
Some improvement.  I'll attach another chocolateyinstall log below.  It 
still didn't install the agent, but it also didn't add an entry to /lib, so 
I'm guessing it will keep trying.  Looks like the same error downloading 
the file.

http://pastebin.com/BFd90qkb


On Friday, February 14, 2014 10:55:51 AM UTC-8, Rob Reynolds wrote:
>
> Let's have you upgrade chocolatey to 0.9.8.23 and see if the issue still 
> happens. The paste bin shows 0.9.8.20.
>
>
> On Fri, Feb 14, 2014 at 12:53 PM, Rob Reynolds 
> 
> > wrote:
>
>> You are running into an issue we have seen but have not been able to 
>> reproduce effectively - 
>> https://github.com/chocolatey/puppet-chocolatey/issues/18
>>  
>>
>> On Fri, Feb 14, 2014 at 12:47 PM, Jay Benner 
>> > wrote:
>>
>>> The following is a copy of my log:
>>> http://pastebin.com/wz5peZbG
>>> Looks like the download failed.  Perhaps a problem with puppet not being 
>>> able to access my personal temp folder?
>>>
>>>
>>> On Friday, February 14, 2014 9:58:53 AM UTC-8, Rob Reynolds wrote:
>>>
>>>> I looks like it does install the package, but may be running into 
>>>> something else when it is running. In C:\chocolatey\chocolateyInstall 
>>>> there are some log files, what does the log file say about the 
>>>> installation?
>>>>
>>>>
>>>> On Thu, Feb 13, 2014 at 2:10 PM, Jay Benner  wrote:
>>>>
>>>>>  I had deleted the entry in /lib.
>>>>>
>>>>>
>>>>> On Wednesday, February 12, 2014 2:37:49 PM UTC-8, Jay Benner wrote:
>>>>>
>>>>>> I have a bunch of windows servers with NewRelic installed on them and 
>>>>>> I want to start managing those installs with Puppet.  Seemed like the 
>>>>>> thing 
>>>>>> to do would be to have chocolatey uninstall what is there and reinstall 
>>>>>> within the framework of chocolatey so that I get addressable version 
>>>>>> information and the like.  I created the following chocolatey package 
>>>>>> and 
>>>>>> it works fine when run from the command line using cinst: any existing 
>>>>>> version is removed and the new version, managed by chocolatey, gets put 
>>>>>> in 
>>>>>> its place.  However, when I run it from Puppet, it does the uninstall 
>>>>>> ok, 
>>>>>> but the install never happens, even though chocolatey seems to think 
>>>>>> that 
>>>>>> the package is installed.  
>>>>>>
>>>>>>
>>>>>> stop-service "LiveVault Backup Service"
>>>>>> $app = Get-WmiObject -Class Win32_Product | Where-Object { 
>>>>>> $_.Name -match "New Relic Server Monitor" 
>>>>>> }
>>>>>>
>>>>>> $app.Uninstall()
>>>>>> $licensekey = "XX"
>>>>>>
>>>>>> $packageName = 'NewRelic_ServerMonitor'
>>>>>> $installerType = 'MSI' 
>>>>>> $url = 'http://download.newrelic.com/windows_server_monitor/release/
>>>>>> NewRelicServerMonitor_x86_2.0.0.198.msi'
>>>>>> $url64 = 'http://download.newrelic.com/windows_server_monito
>>>>>> r/release/NewRelicServerMonitor_x64_2.0.0.198.msi' 
>>>>>> $validExitCodes = @(0) 
>>>>>> $silentArgs = "/L*v install_Agent.log /qn NR_LICENSE_KEY=`"
>>>>>> $licensekey`"" 
>>>>>> Install-ChocolateyPackage "$packageName" "$installerType" "$
>>>>>> silentArgs" "$url" "$url64"  -validExitCodes $validExitCodes
>>>>>>
>>>>>> start-service "LiveVault Backup Service"
>>>>>> Start-service "New Relic Server Monitor"
>>>>>>
>>>>>  -- 
>>>>> 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 view this discussion on the web visit https://groups.google.com/d/
>>>>> msgid/puppet-users/22e5472b-f50d-4d93-aadc-69ebaa2c9f74%
>>>>

Re: [Puppet Users] Re: moving from previous manual install to puppet/chocolatey

2014-02-14 Thread Jay Benner
The following is a copy of my log:
http://pastebin.com/wz5peZbG
Looks like the download failed.  Perhaps a problem with puppet not being 
able to access my personal temp folder?

On Friday, February 14, 2014 9:58:53 AM UTC-8, Rob Reynolds wrote:
>
> I looks like it does install the package, but may be running into 
> something else when it is running. In C:\chocolatey\chocolateyInstall there 
> are some log files, what does the log file say about the installation?
>
>
> On Thu, Feb 13, 2014 at 2:10 PM, Jay Benner 
> > wrote:
>
>> I had deleted the entry in /lib.
>>
>>
>> On Wednesday, February 12, 2014 2:37:49 PM UTC-8, Jay Benner wrote:
>>
>>> I have a bunch of windows servers with NewRelic installed on them and I 
>>> want to start managing those installs with Puppet.  Seemed like the thing 
>>> to do would be to have chocolatey uninstall what is there and reinstall 
>>> within the framework of chocolatey so that I get addressable version 
>>> information and the like.  I created the following chocolatey package and 
>>> it works fine when run from the command line using cinst: any existing 
>>> version is removed and the new version, managed by chocolatey, gets put in 
>>> its place.  However, when I run it from Puppet, it does the uninstall ok, 
>>> but the install never happens, even though chocolatey seems to think that 
>>> the package is installed.  
>>>
>>>
>>> stop-service "LiveVault Backup Service"
>>> $app = Get-WmiObject -Class Win32_Product | Where-Object { 
>>> $_.Name -match "New Relic Server Monitor" 
>>> }
>>>
>>> $app.Uninstall()
>>> $licensekey = "XX"
>>>
>>> $packageName = 'NewRelic_ServerMonitor'
>>> $installerType = 'MSI' 
>>> $url = 'http://download.newrelic.com/windows_server_monitor/release/
>>> NewRelicServerMonitor_x86_2.0.0.198.msi'
>>> $url64 = 'http://download.newrelic.com/windows_server_monitor/release/
>>> NewRelicServerMonitor_x64_2.0.0.198.msi' 
>>> $validExitCodes = @(0) 
>>> $silentArgs = "/L*v install_Agent.log /qn NR_LICENSE_KEY=`"$licensekey`"
>>> " 
>>> Install-ChocolateyPackage "$packageName" "$installerType" "$silentArgs" 
>>> "$url" "$url64"  -validExitCodes $validExitCodes
>>>
>>> start-service "LiveVault Backup Service"
>>> Start-service "New Relic Server Monitor"
>>>
>>  -- 
>> 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 view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/22e5472b-f50d-4d93-aadc-69ebaa2c9f74%40googlegroups.com
>> .
>>
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
>
> -- 
> Rob Reynolds
> Developer, Puppet Labs
>
> *Join us at PuppetConf 2014, September 23-24 in San Francisco - *
> http://bit.ly/pupconf14
>  

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/34cf3a92-716b-4ef2-84d9-1da968ded783%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[Puppet Users] Re: moving from previous manual install to puppet/chocolatey

2014-02-13 Thread Jay Benner
I had deleted the entry in /lib.

On Wednesday, February 12, 2014 2:37:49 PM UTC-8, Jay Benner wrote:
>
> I have a bunch of windows servers with NewRelic installed on them and I 
> want to start managing those installs with Puppet.  Seemed like the thing 
> to do would be to have chocolatey uninstall what is there and reinstall 
> within the framework of chocolatey so that I get addressable version 
> information and the like.  I created the following chocolatey package and 
> it works fine when run from the command line using cinst: any existing 
> version is removed and the new version, managed by chocolatey, gets put in 
> its place.  However, when I run it from Puppet, it does the uninstall ok, 
> but the install never happens, even though chocolatey seems to think that 
> the package is installed.  
>
>
> stop-service "LiveVault Backup Service"
> $app = Get-WmiObject -Class Win32_Product | Where-Object { 
> $_.Name -match "New Relic Server Monitor" 
> }
>
> $app.Uninstall()
> $licensekey = "XX"
>
> $packageName = 'NewRelic_ServerMonitor'
> $installerType = 'MSI' 
> $url = '
> http://download.newrelic.com/windows_server_monitor/release/NewRelicServerMonitor_x86_2.0.0.198.msi
> '
> $url64 = '
> http://download.newrelic.com/windows_server_monitor/release/NewRelicServerMonitor_x64_2.0.0.198.msi
> ' 
> $validExitCodes = @(0) 
> $silentArgs = "/L*v install_Agent.log /qn NR_LICENSE_KEY=`"$licensekey`"" 
> Install-ChocolateyPackage "$packageName" "$installerType" "$silentArgs" 
> "$url" "$url64"  -validExitCodes $validExitCodes
>
> start-service "LiveVault Backup Service"
> Start-service "New Relic Server Monitor"
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/22e5472b-f50d-4d93-aadc-69ebaa2c9f74%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [Puppet Users] Re: moving from previous manual install to puppet/chocolatey

2014-02-13 Thread Jay Benner
The results of the test run:
http://pastebin.com/00msu7VB

My manifest:
# Class: newrelic_server_monitor
#
# This module manages newrelic_server_monitor

class newrelic_server_monitor {
  
  #check installed version and remove if it is older than 2.0.0.198
  case 
  
$pkg = 'NewRelic_Servermonitor'

  package { $pkg:
ensure  => installed,
provider=> 'chocolatey',
source  =>  '\\myfileserver\everyone\devops\chocolatey\packages',
  }
}



On Thursday, February 13, 2014 9:18:59 AM UTC-8, Rob Reynolds wrote:
>
> Can you share your manifest?
>
> Also would you run puppet agent --test --verbose --debug and post that 
> output (preferably in a gist / pastebin and then link that here)? Remove 
> the sensitive information such as the license.
>
>
> On Thu, Feb 13, 2014 at 10:55 AM, Jay Benner 
> > wrote:
>
>> I got it from the forge.
>> I don't know how to tell what version of chocolatey I have.
>> Name of the package is "newrelic_servermonitor".
>> The package does appear in /lib, even though the software did not install.
>> UAC is off.
>> Thanks for the response, I posted in Puppet because it seems to work 
>> perfectly when I run chocolatey from the command prompt.  I didn't realize 
>> that the chocolatey group supported the puppet provider as well; I'll note 
>> it in the future.
>>
>>
>> On Wednesday, February 12, 2014 2:37:49 PM UTC-8, Jay Benner wrote:
>>>
>>> I have a bunch of windows servers with NewRelic installed on them and I 
>>> want to start managing those installs with Puppet.  Seemed like the thing 
>>> to do would be to have chocolatey uninstall what is there and reinstall 
>>> within the framework of chocolatey so that I get addressable version 
>>> information and the like.  I created the following chocolatey package and 
>>> it works fine when run from the command line using cinst: any existing 
>>> version is removed and the new version, managed by chocolatey, gets put in 
>>> its place.  However, when I run it from Puppet, it does the uninstall ok, 
>>> but the install never happens, even though chocolatey seems to think that 
>>> the package is installed.  
>>>
>>>
>>> stop-service "LiveVault Backup Service"
>>> $app = Get-WmiObject -Class Win32_Product | Where-Object { 
>>> $_.Name -match "New Relic Server Monitor" 
>>> }
>>>
>>> $app.Uninstall()
>>> $licensekey = "XX"
>>>
>>> $packageName = 'NewRelic_ServerMonitor'
>>> $installerType = 'MSI' 
>>> $url = 'http://download.newrelic.com/windows_server_monitor/release/
>>> NewRelicServerMonitor_x86_2.0.0.198.msi'
>>> $url64 = 'http://download.newrelic.com/windows_server_monitor/release/
>>> NewRelicServerMonitor_x64_2.0.0.198.msi' 
>>> $validExitCodes = @(0) 
>>> $silentArgs = "/L*v install_Agent.log /qn NR_LICENSE_KEY=`"$licensekey`"
>>> " 
>>> Install-ChocolateyPackage "$packageName" "$installerType" "$silentArgs" 
>>> "$url" "$url64"  -validExitCodes $validExitCodes
>>>
>>> start-service "LiveVault Backup Service"
>>> Start-service "New Relic Server Monitor"
>>>
>>  -- 
>> 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 view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/2c7df372-bb8b-4841-b986-22a1fb9efa08%40googlegroups.com
>> .
>>
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
>
> -- 
> Rob Reynolds
> Developer, Puppet Labs
>
> *Join us at PuppetConf 2014, September 23-24 in San Francisco - *
> http://bit.ly/pupconf14
>  

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/684233cb-fc24-4f38-94bb-e0029bc3f807%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[Puppet Users] Re: moving from previous manual install to puppet/chocolatey

2014-02-13 Thread Jay Benner
I got it from the forge.
I don't know how to tell what version of chocolatey I have.
Name of the package is "newrelic_servermonitor".
The package does appear in /lib, even though the software did not install.
UAC is off.
Thanks for the response, I posted in Puppet because it seems to work 
perfectly when I run chocolatey from the command prompt.  I didn't realize 
that the chocolatey group supported the puppet provider as well; I'll note 
it in the future.

On Wednesday, February 12, 2014 2:37:49 PM UTC-8, Jay Benner wrote:
>
> I have a bunch of windows servers with NewRelic installed on them and I 
> want to start managing those installs with Puppet.  Seemed like the thing 
> to do would be to have chocolatey uninstall what is there and reinstall 
> within the framework of chocolatey so that I get addressable version 
> information and the like.  I created the following chocolatey package and 
> it works fine when run from the command line using cinst: any existing 
> version is removed and the new version, managed by chocolatey, gets put in 
> its place.  However, when I run it from Puppet, it does the uninstall ok, 
> but the install never happens, even though chocolatey seems to think that 
> the package is installed.  
>
>
> stop-service "LiveVault Backup Service"
> $app = Get-WmiObject -Class Win32_Product | Where-Object { 
> $_.Name -match "New Relic Server Monitor" 
> }
>
> $app.Uninstall()
> $licensekey = "XX"
>
> $packageName = 'NewRelic_ServerMonitor'
> $installerType = 'MSI' 
> $url = '
> http://download.newrelic.com/windows_server_monitor/release/NewRelicServerMonitor_x86_2.0.0.198.msi
> '
> $url64 = '
> http://download.newrelic.com/windows_server_monitor/release/NewRelicServerMonitor_x64_2.0.0.198.msi
> ' 
> $validExitCodes = @(0) 
> $silentArgs = "/L*v install_Agent.log /qn NR_LICENSE_KEY=`"$licensekey`"" 
> Install-ChocolateyPackage "$packageName" "$installerType" "$silentArgs" 
> "$url" "$url64"  -validExitCodes $validExitCodes
>
> start-service "LiveVault Backup Service"
> Start-service "New Relic Server Monitor"
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/2c7df372-bb8b-4841-b986-22a1fb9efa08%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[Puppet Users] moving from previous manual install to puppet/chocolatey

2014-02-12 Thread Jay Benner
I have a bunch of windows servers with NewRelic installed on them and I 
want to start managing those installs with Puppet.  Seemed like the thing 
to do would be to have chocolatey uninstall what is there and reinstall 
within the framework of chocolatey so that I get addressable version 
information and the like.  I created the following chocolatey package and 
it works fine when run from the command line using cinst: any existing 
version is removed and the new version, managed by chocolatey, gets put in 
its place.  However, when I run it from Puppet, it does the uninstall ok, 
but the install never happens, even though chocolatey seems to think that 
the package is installed.  


stop-service "LiveVault Backup Service"
$app = Get-WmiObject -Class Win32_Product | Where-Object { 
$_.Name -match "New Relic Server Monitor" 
}

$app.Uninstall()
$licensekey = "XX"

$packageName = 'NewRelic_ServerMonitor'
$installerType = 'MSI' 
$url = 
'http://download.newrelic.com/windows_server_monitor/release/NewRelicServerMonitor_x86_2.0.0.198.msi'
$url64 = 
'http://download.newrelic.com/windows_server_monitor/release/NewRelicServerMonitor_x64_2.0.0.198.msi'
 
$validExitCodes = @(0) 
$silentArgs = "/L*v install_Agent.log /qn NR_LICENSE_KEY=`"$licensekey`"" 
Install-ChocolateyPackage "$packageName" "$installerType" "$silentArgs" 
"$url" "$url64"  -validExitCodes $validExitCodes

start-service "LiveVault Backup Service"
Start-service "New Relic Server Monitor"

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/56fe586f-6c6e-49fb-a432-3a814ac3e65e%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[Puppet Users] Re: External Facts on Windows with Powershell

2013-10-10 Thread Jay Benner
Did you figure this out?  I am having the same trouble.

On Tuesday, April 9, 2013 10:44:38 AM UTC-5, Grant Trevor wrote:
>
> I'm trying to follow the steps on 
> http://docs.puppetlabs.com/guides/custom_facts.html in regards to 
> declaring External Facts using powershell.
>
> I've created a simple .ps1 file outputing a single key pair eg: Write-Host 
> "mykey=123456", however if I run Facter from the Command Prompt(with 
> puppet) my value isn't present.
>
> Also if I run 'puppet apply MyModule.pp --verbose'  I don't receive any 
> information about it attempting to load facts.
>
> I've also tried a simple txt file with no luck.  
>
> I'm using Puppet 2.7.17 installed via chocolatey, could this be a 
> configuration issue, do I need to enable External Task parsing?
>

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