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
profi
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.
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 Reyno
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 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, Feb
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 captu
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 its
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 netwo
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:5
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/
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
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 downloa
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 /l
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 uninsta
Did you have the package in C:\chocolatey\lib already? It will not attempt
to install if it finds a package with the same name
Also you may want to switch to ensure => latest.
On Thu, Feb 13, 2014 at 12:22 PM, Jay Benner wrote:
> The results of the test run:
> http://pastebin.com/00msu7VB
>
>
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'
You may need to remove the package folder from c:\chocolatey\lib first.
On Thu, Feb 13, 2014 at 11:18 AM, 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 he
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 fo
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
perfectl
19 matches
Mail list logo
