date:20131003

[Puppet Users] fail when install the console

2013-10-03 Thread Ho Minh Dat


Hi all  Puppet friends,
I don't know why when I install PE until setup the console step then it 
fail. I don't know what is exactly necessary for the console installation.

Pls help me to suggest the solution.

Following is the content of that step.

## Setting up the database...
Configuring postgresql server...
PostgreSQL server configured.
CREATE TABLESPACE
CREATE ROLE
CREATE DATABASE
CREATE ROLE
CREATE DATABASE
CREATE TABLESPACE
CREATE ROLE
CREATE DATABASE
## Setting up the console...

=


   There was an error running the installation. Please see the last few 
lines of

   output for more info.

   The Puppet Enterprise Installer can remove any Puppet Enterprise 
components and

   configuration files installed prior to this error.
   (Note: this does not include removal of any system packages 
installed and/or

   installed remote databases/users.)
?? Remove Puppet Enterprise components and configuration files? [y/N] y

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

Re: [Puppet Users] Re: brew and macosx and puppet

2013-10-03 Thread David Portabella

https://github.com/kelseyhightower/puppet-homebrew


-- 
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: onlyif return code

2013-10-03 Thread james . eckersall

 The exec resource has an unless parameter too which I think is what you 
need.

From: http://docs.puppetlabs.com/references/latest/type.html#exec

onlyif If this parameter is set, then this exec will only run if the 
command returns 0

unless If this parameter is set, then this exec will run unless the command 
returns 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 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] fail when install the console

2013-10-03 Thread Fernando Torres

I can't see any error message after postgresql successful migration
outputs. "The last few lines" has no error messages.


Can you look for a install_log.lastrun.${hostname} in the current directory
from where you have run puppet installer?


On Thu, Oct 3, 2013 at 7:22 AM, Ho Minh Dat  wrote:

> Hi all  Puppet friends,
> I don't know why when I install PE until setup the console step then it
> fail. I don't know what is exactly necessary for the console installation.
> Pls help me to suggest the solution.
>
> Following is the content of that step.
>
> ## Setting up the database...
> Configuring postgresql server...
> PostgreSQL server configured.
> CREATE TABLESPACE
> CREATE ROLE
> CREATE DATABASE
> CREATE ROLE
> CREATE DATABASE
> CREATE TABLESPACE
> CREATE ROLE
> CREATE DATABASE
> ## Setting up the console...
>
> ==**==**
> =
>
>
>There was an error running the installation. Please see the last few
> lines of
>output for more info.
>
>The Puppet Enterprise Installer can remove any Puppet Enterprise
> components and
>configuration files installed prior to this error.
>(Note: this does not include removal of any system packages installed
> and/or
>installed remote databases/users.)
> ?? Remove Puppet Enterprise components and configuration files? [y/N] y
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to 
> puppet-users+unsubscribe@**googlegroups.com
> .
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at 
> http://groups.google.com/**group/puppet-users
> .
> For more options, visit 
> https://groups.google.com/**groups/opt_out
> .
>

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

[Puppet Users] Re: Idiom for throwing an error if a command fails

2013-10-03 Thread jcbollinger

On Wednesday, October 2, 2013 7:42:59 PM UTC-5, Richard K. Miller wrote:
>
> Hi,
>
> What's the best idiom for executing a command on every Puppet run and 
> triggering an error if the command fails?
>
>

It depends on what you mean by "triggering an error".

If you run a command via an Exec resource, and the exit code is not zero 
(or whatever other code you specify should be expected) then that resource 
fails and the failure will be recorded in the agent's log.  If reporting is 
enabled then the failure will also be noted in the agent's report.

If you invert the sense of the command's exit code (for instance, by 
running using the "shell" provider and prefixing the command with '!') then 
you can set up other resources, such as Notify, to be applied only when the 
inverted command succeeds (i.e. when the underlying command fails).

Or you can roll the failure action into the command itself.

> For example, the following code throws an error if the machine has 
> anything other than 8 cores.
>
>   exec { "echo 'This machine does not have 8 cores!'; exit 1":
> unless => "facter processorcount | grep -q 8",
>   }
>
> The "; exit 1" changes this from a Notice to an Error, but it seems a bit 
> hackish. I couldn't discover a way to do this with err() or notify{}. 
>
>

That's a bizarre way of doing things.  Your node's facts are reported to 
the master to inform catalog compilation, so you should not need to run 
facter again when you apply resources.  I would probably write that 
particular check something like this:

if $::processorcount != 8 {
  exec { "Expected 8 processors but have ${::processorcount}":
command => '/bin/false'
  }
}

or like this

if $::processorcount != 8 {
  notify { "Expected 8 processors but have ${::processorcount}": }
}

or like this

if $::processorcount != 8 {
  exec { "log wrong processor count":
command => "logger -p local0.warn 'Expected 8 processors but have 
${::processorcount}'"
  }
}

depending on what exactly I want.

You cannot use the err() or warning() functions for this if you want the 
message to appear in the agent's log, because Puppet functions run on the 
master during catalog compilation, not on the agent.  If logging to the 
master's log would do the trick, however, then you could do this:

if $::processorcount != 8 {
  warning("Expected 8 processors on ${::hostname}, but Facter reports 
${::processorcount}")
}

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: fail when install the console

2013-10-03 Thread jcbollinger



On Thursday, October 3, 2013 5:22:48 AM UTC-5, HỒ MINH ĐẠT wrote:
>
> Hi all  Puppet friends, 
> I don't know why when I install PE until setup the console step then it 
> fail. I don't know what is exactly necessary for the console installation. 
>


Please pose new questions in their own threads instead of hijacking 
existing ones.

John

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

Re: [Puppet Users] Re: Still no nagios joy

2013-10-03 Thread jcbollinger

On Wednesday, October 2, 2013 9:44:14 AM UTC-5, David Thompson wrote:
>
>
> The puppet nagios collector: 
>
>  if $nagios_server { 
>Nagios_host <<||>> 
>  } 
>
>

And you're certain that $nagios_server evaluates to true on the machines 
that nevertheless fail to get the expected Nagios_host resources applied?  
You could probe that by changing the above to

if $nagios_server {
  Nagios_host <<| |>>
  notify { 'I am a nagios server': }
} else {
  notify { 'I am not a nagios server': }
}

That will also help you catch the case that the class containing the above 
is not included in the catalog at all, for then you would see neither the 
Notify message in the agent log.  You can also watch your query log for the 
query by which Puppet retrieves all the wanted Nagios_host resources; if 
nothing else is fruitful then the details of the query might reveal some 
useful information.

>
> The query I'm using: 
>
> curl -G 'http://localhost:8080/v3/resources' --data-urlencode 
> 'query=["=", "type", "Nagios_host"]' 
>
> (I tried updating to the latest-and-greatest puppetdb yesteday.  No 
> change.  I get the same from the v2 URI.) 
>
>

For what it's worth, it looks like you could simplify that to just

curl -G 'http://localhost:8080/v3/resources/Nagios_host'

though I don't expect using that form will change anything.  I'm more 
interested, though, in the back end.  That is, is puppetdb for some reason 
failing to serve up resources that are in fact recorded in the back-end DB, 
or are the resources either not making it to the DB in the first place, or 
are they being purged from the DB between being entered and being queried?

You said earlier that some nagios hosts are getting configured, at least on 
some machines, but I didn't completely understand which hosts are getting 
configured on which machines.  Are there machines that get all the expected 
hosts?  Are there nagios_hosts that get configured on all machines?  More 
generally, what is the nature of the correlation (that you have recognized) 
between declared nagios host resources and the machines on which puppet 
manages those resources?

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: Converting to heira format issue

2013-10-03 Thread jcbollinger

On Wednesday, October 2, 2013 8:57:07 AM UTC-5, Dan wrote:
>
> Hi
>
> I'm just getting into hiera and have now configured it, my attempts at 
> migrating to hiera have been frustratingly hard as I'm not able to get the 
> write syntax. Can someone help me in converting the below from a class 
> declaration to hiera?
>

Um, what?

Hiera is an external data access service.  Puppet 3 leverages it to access 
class parameter data for automated parameter value binding, and you can use 
it as most of a data-driven external node classifier (ENC), but although it 
may allow you to simplify class declarations, it does not replace them.

> Current declarations in my declare.pp file:
>

Whose purpose is what, exactly?

> class profile::web {
>   class { 'nsswitch':
> automount => 'files',
> hosts => ['files','dns'],
>   }
> }
>

That class definition should be in file 
/profile/manifests/web.pp.

> class { 'sudo': }
> sudo::conf { 'web-users':
> sudo_config_dir => '/etc/sudoers.d/',
> source => 'puppet:///files/web/web-users.conf',
> }
>
>
Those declarations (and though the formatting obscures it, there are two) 
probably belong inside a class or node definition.

I'm very unclear about what you are actually trying to accomplish, but 
here's one thing that may nudge you in the right direction.  If you are 
using hiera's YAML back end, connected, say, only with a single data file 
common.yaml, and that file contains

---
nsswitch::automount: files
nsswitch::hosts:
  - files
  - dns

then you should be able to shorten your profile::web class definition to 
just

class profile::web {
  include nsswitch
  # or class { 'nsswitch': }
}

to achieve the same result that the current declaration does.

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] install certificate - unless not working

2013-10-03 Thread Armindo Silva

Hi

I am installing the OpenVPN's certificate if it is not present with the 
following exec:


exec { 'OvpnCert':
  command => 'certutil.exe -addstore TrustedPublisher 
c:\installers\OpenVPN_Cert.cer',
  require => File[ 'c:/eufinity/installers/'],
  unless  => 'certutil.exe -verifystore TrustedPublisher | findstr 
OpenVPN',
  }

Even when *certutil.exe -verifystore TrustedPublisher | findstr OpenVPN*returns 
0 ( 
*echo %errorlevel%* after running the unless cmd: returns *0* when the 
OpenVPN is present and *1* otherwise), the exec always runs.
What am I doing wrong?

Thank you.
Armindo

-- 
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: Decomission node process (puppet / puppetdb / dashboard)

2013-10-03 Thread MasterPO


Unfortunately, for me all this does is make the puppet-master host go 100% 
busy between the dashboard and mysqld.

I am running Dashboard version 1.2.23 with puppet-server version 3.2.4 and 
mysql version 5.1.69 on RHEL 6.4

I get the same result running John's cli rake command.

Any ideas?

Thanks
Paul

-- 
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] install certificate - unless not working

2013-10-03 Thread Fernando Torres

Armindo

You must inform the path attribute.

Try path => "${::path};c:\\path\\to\\certutil executable"
On Oct 3, 2013 12:08 PM, "Armindo Silva"  wrote:

> Hi
>
> I am installing the OpenVPN's certificate if it is not present with the
> following exec:
>
>
> exec { 'OvpnCert':
>   command => 'certutil.exe -addstore TrustedPublisher
> c:\installers\OpenVPN_Cert.cer',
>   require => File[ 'c:/eufinity/installers/'],
>   unless  => 'certutil.exe -verifystore TrustedPublisher | findstr
> OpenVPN',
>   }
>
> Even when *certutil.exe -verifystore TrustedPublisher | findstr 
> OpenVPN*returns 0 (
> *echo %errorlevel%* after running the unless cmd: returns *0* when the
> OpenVPN is present and *1* otherwise), the exec always runs.
> What am I doing wrong?
>
> Thank you.
> Armindo
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.
> For more options, visit https://groups.google.com/groups/opt_out.
>

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

Re: [Puppet Users] Re: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers

2013-10-03 Thread Rob Reynolds

You should be able to run

facter --trace --debug


On Wed, Oct 2, 2013 at 5:18 PM, cko  wrote:

> Hi Ethan,
>
> what's the exact command that i would have to use?
>
>
> On Wednesday, October 2, 2013 11:35:29 PM UTC+2, Ethan Brown wrote:
>
>> Christian -
>>
>> I'm doing the final verification of our fix, and was hoping that I could
>> get the output from Facter run by itself?
>>
>>
>>
>> On Fri, Sep 20, 2013 at 1:36 PM, Rob Reynolds wrote:
>>
>>> I would say with all of this in mind we move forward with a fix where we
>>> look to see that the network adapter itself is also enabled. This is laid
>>> out in the ticket that I noted earlier.
>>>
>>>
>>> On Fri, Sep 20, 2013 at 7:44 AM, Rich Siegel  wrote:
>>>
 Exchange DAG is essentially a cluster and the adapter in question the
 dag ip.

 My guess is the logic for adapters should be modded for when
 netconnectionid is not null.

 In general don't try to mess with hidden adapters on dags unless you
 understand ramifications.

 --
 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
 .
 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
>>>
>>> --
>>> 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
>>> .
>>> For more options, visit 
>>> https://groups.google.com/**groups/opt_out
>>> .
>>>
>>
>>
>>
>> --
>> --
>> Ethan Brown
>> et...@puppetlabs.com
>> Software Engineer
>>
>> *Join us at PuppetConf 2014, September 23-24 in San Francisco*
>>
>  --
> 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.
>



-- 
Rob Reynolds
Developer, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
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: install certificate - unless not working

2013-10-03 Thread Armindo Silva

I forgot to add that I have the following line:

*  Exec  { path => [ "C:\\Windows\\System32", "C:\\installers" ] }*

so there isn't a path problem - without that line puppet complains about 
not finding certutil.exe.


On Thursday, October 3, 2013 4:04:17 PM UTC+1, Armindo Silva wrote:
>
> Hi
>
> I am installing the OpenVPN's certificate if it is not present with the 
> following exec:
>
>
> exec { 'OvpnCert':
>   command => 'certutil.exe -addstore TrustedPublisher 
> c:\installers\OpenVPN_Cert.cer',
>   require => File[ 'c:/eufinity/installers/'],
>   unless  => 'certutil.exe -verifystore TrustedPublisher | findstr 
> OpenVPN',
>   }
>
> Even when *certutil.exe -verifystore TrustedPublisher | findstr 
> OpenVPN*returns 0 ( 
> *echo %errorlevel%* after running the unless cmd: returns *0* when the 
> OpenVPN is present and *1* otherwise), the exec always runs.
> What am I doing wrong?
>
> Thank you.
> Armindo
>

-- 
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: Still no nagios joy

2013-10-03 Thread David Thompson


On 10/3/13 9:07 AM, jcbollinger wrote:


And you're certain that $nagios_server evaluates to true on the machines
that nevertheless fail to get the expected Nagios_host resources
applied?  You could probe that by changing the above to

>

if $nagios_server {
   Nagios_host <<| |>>
   notify { 'I am a nagios server': }
} else {
   notify { 'I am not a nagios server': }
}

That will also help you catch the case that the class containing the
above is not included in the catalog at all, for then you would see
neither the Notify message in the agent log.  You can also watch your
query log for the query by which Puppet retrieves all the wanted
Nagios_host resources; if nothing else is fruitful then the details of
the query might reveal some useful information.


First to answer.  I have one computer that runs nagios.  That's the 
(only) computer that has $nagios_server defined.  The computers that I 
want to monitor have the @@nagios_host {} resource.  I've verified this 
up and down.


I've done some more testing, and there's something very funny going on. 
 In my manifests, I have the following:


  notify {"Nagios Base: $fqdn $hostname $ipaddress": }
  @@nagios_host { $fqdn:
ensure => present,
alias => $hostname,
address => $ipaddress,
use => "linux-server",
  }

On the hosts to be monitored, I see the notify, and, as I've said, I see 
the db inserts, but then nothing comes up in the REST query.  HOWEVER, 
if I take the lines above and put them in a separate .pp file and 
"puppet apply" that file, then I see the resources via the REST query. 
My understanding was that once a resource gets defined, that's the end 
of the story, but it's clearly not what's happening here.


So, "puppet agent --test --environment production" fails to create 
resources findable via REST (and in fact removes them if they're 
present), but "puppet apply foo.pp" (with foo.pp containing the 
statements above) makes them findable (and they show up in 
nagios_hosts.cfg on the nagios server).



though I don't expect using that form will change anything.  I'm more
interested, though, in the back end.  That is, is puppetdb for some
reason failing to serve up resources that are in fact recorded in the
back-end DB, or are the resources either not making it to the DB in the
first place, or are they being purged from the DB between being entered
and being queried?


That's a very good question.  I can certainly find catalog_resource and 
resource_params records that *look* like they contain appropriate 
Nagios_host resources, but the REST API says no, and if I run the actual 
sql query out of the postgres statement log, it says no.  The sql query 
itself is a complex enough to be beyond my db-mojo to understand why 
it's not finding any Nagios_host resources.



You said earlier that some nagios hosts are getting configured, at least
on some machines, but I didn't completely understand which hosts are
getting configured on which machines.  Are there machines that get all
the expected hosts?  Are there nagios_hosts that get configured on all
machines?  More generally, what is the nature of the correlation (that
you have recognized) between declared nagios host resources and the
machines on which puppet manages those resources?


Yes, sometimes I've gotten some partial Nagios_host data generated on 
the nagios server, but never in any discernible or repeatable form.


It looks like enlightenment lies in understanding the difference between 
the puppet agent and puppet apply runs.


--
David Thompson
Waisman Center Brain Imaging and Behavior Lab
1500 Highland Ave. Room T133
Madison, WI  53705-2280
(608) 265-6608
dthompson (at) waisman (dot) wisc (dot) edu

--
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: Name or service not known issue

2013-10-03 Thread Guillermo Castellon

I ran into this problem and after much debugging it turned out to be a 
problem of whom is running the command.

In my I had set the credentials to use ssh for a user but I was running the 
command as a different user and that was the issue.  Minor details :)

On Friday, May 27, 2011 4:39:30 AM UTC-4, Sumith Sudhakaran wrote:
>
>
> Hi,
>
> When I am trying update from puppet client, getting error like blow
>
> *err: Could not request certificate: getaddrinfo: Name or service not 
> known
>  
> puppetd --test output:-
>
> err: Could not request certificate: getaddrinfo: Name or service not known
> Exiting; failed to retrieve certificate and waitforcert is disabled*
>
>
>
> Please help to solve the same..
>
>
>
>
> -- 
> *  Regards***
>
> * Sumith** *
>
>  

-- 
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] Idiom for throwing an error if a command fails

2013-10-03 Thread Richard K Miller

> For example, the following code throws an error if the machine has anything 
> other than 8 cores.
> 
>   exec { "echo 'This machine does not have 8 cores!'; exit 1":
> unless => "facter processorcount | grep -q 8",
>   }
> 
> The "; exit 1" changes this from a Notice to an Error, but it seems a bit 
> hackish. I couldn't discover a way to do this with err() or notify{}. 
> 
> 
> 
> That's a bizarre way of doing things.  Your node's facts are reported to the 
> master to inform catalog compilation, so you should not need to run facter 
> again when you apply resources.  I would probably write that particular check 
> something like this:

Exactly. I figured there was a more idiomatic way of doing this. 

> if $::processorcount != 8 {
>   exec { "Expected 8 processors but have ${::processorcount}":
> command => '/bin/false'
>   }
> }
> 

This works, and I like your using the Puppet fact natively instead of calling 
Facter manually. My only slight complaint is that the message (in Puppet 
Dashboard) is a bit opaque:
Level: err
Message: "change from notrun to 0 failed: /bin/false returned 1 instead of one 
of [0]"
Source: "/Stage[main]/Common/Exec[1. Expected 8 processors but have 4]/returns"

> or like this
> 
> if $::processorcount != 8 {
>   notify { "Expected 8 processors but have ${::processorcount}": }
> }
> 

I like this approach the best. However, because it triggers a "notice" level, 
it doesn't get reported by email or in Puppet Dashboard as a failure.

It seems there ought to exist a Puppet type called "error", parallel in 
functionality to notify, that triggers at the error level.


> or like this
> 
> if $::processorcount != 8 {
>   exec { "log wrong processor count":
> command => "logger -p local0.warn 'Expected 8 processors but have 
> ${::processorcount}'"
>   }
> }

Interesting approach that I didn't even remotely consider.


> You cannot use the err() or warning() functions for this if you want the 
> message to appear in the agent's log, because Puppet functions run on the 
> master during catalog compilation, not on the agent.  If logging to the 
> master's log would do the trick, however, then you could do this:
> 
> if $::processorcount != 8 {
>   warning("Expected 8 processors on ${::hostname}, but Facter reports 
> ${::processorcount}")
> }


You're right; this won't work because I want the client to report an error.

Thanks for your thoughts on this. I'm left wishing Puppet supported an "error" 
type because that seems like the most native idiom.

Richard


-- 
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: Announce: Puppet 3.3.1-rc3 available

2013-10-03 Thread Melissa Stone

It was kindly pointed out to me that these links are actually wrong. Sorry
about that mistake, google got the better of me. Below you'll find the
actual links to puppet 3.3.1-rc3. Enjoy!

Puppet 3.3.1-rc3 Downloads
--
Source: https://downloads.puppetlabs.com/puppet/puppet-3.3.1-rc3.tar.gz

Available in native package format in the pre-release repositories at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com

For information on how to enable the Puppet Labs pre-release repos, see:
http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#enabling-the-prerelease-repos

Gems are available via rubygems at
https://rubygems.org/downloads/puppet-3.3.1.rc3.gem
  or by using `gem install --pre puppet`

Mac packages are available at
https://downloads.puppetlabs.com/mac/puppet-3.3.1-rc3.dmg

Windows packages are available at
https://downloads.puppetlabs.com/windows/puppet-3.3.1-rc3.msi

Please report feedback via the Puppet Labs Redmine site, using an
affected puppet version of 3.3.1-rc3:
https://projects.puppetlabs.com/projects/puppet/


On Wed, Oct 2, 2013 at 4:55 PM, Melissa Stone wrote:

> **Release candidate:**
>
> Pre-release: 3.3.1 has not yet been released.
>
> RC1: September 23, 2013
> RC2: September 27, 2013
> RC3: October 02, 2013
>
> 3.3.1 is to be a bug fix release in the Puppet 3.3 series. The focus
> of the release is fixing backwards compatibility regressions that
> slipped in via the YAML deprecations in 3.3.0.
>
> **Upgrade Note**
>
> The release of Puppet 3.3.1 will supersede the upgrade warning for
> Puppet 3.3.0. As of 3.3.1, agent nodes will be compatible with all
> Puppet 3.x masters with no extra configuration.
>
>
> Puppet 3.3.1-rc3 Downloads
> --
> Source: 
> https://downloads.puppetlabs.com/puppet/puppet-3.3.1-rc3.tar.gz
>
> Available in native package format in the pre-release repositories at:
> http://yum.puppetlabs.com and http://apt.puppetlabs.com
>
> For information on how to enable the Puppet Labs pre-release repos, see:
>
> http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#enabling-the-prerelease-repos
>
> Gems are available via rubygems at
> https://rubygems.org/downloads/puppet-3.3.1.rc3.gem
>   or by using `gem install --pre puppet`
>
> Mac packages are available at
> https://downloads.puppetlabs.com/mac/puppet-3.3.1-rc3.dmg
>
> Windows packages are available at
> https://downloads.puppetlabs.com/windows/puppet-3.3.1-rc3.msi
>
> Please report feedback via the Puppet Labs Redmine site, using an
> affected puppet version of 3.3.1-rc3:
> https://projects.puppetlabs.com/projects/puppet/
>
>
> Fixes for Backwards Compatibility Regressions in 3.3.0
> 
> 
> ## Issue 22535: puppet 3.3.0 ignores File ignore in recursive copy
> ## Issue 22608: filebucket (backup) does not work with 3.3.0 master
> and older clients
> ## Issue 22530: Reports no longer work for clients older than 3.3.0
> when using a 3.3.0 puppet master
> ## Issue 22652: ignore doesn't work if pluginsync enabled
>
>
> New backward compatibility issues were discovered after the release of
> 3.3.0, so we changed our handling of deprecated wire formats.
>
> Starting with 3.3.1, you do not need to set additional settings in
> puppet.conf on your agent nodes in order to use newer agents with
> puppet masters running 3.2.4 or earlier. Agents will work with all 3.x
> masters, and they will automatically negotiate wire formats as needed.
> This behavior supersedes the behavior described for 3.3.0; the
> report_serialization_format setting is now unnecessary.
>
> Additionally, this release fixes two situations where 3.3.0 masters
> would do the wrong thing with older agents. (Reports would fail unless
> the master had report_serialization_format set to yaml, which was not
> intended, and remote filebucket backups would always fail.)
>
>
> Miscellaneous Regression Fixes
> ---
> ## Issue 22384: Excessive logging for files not found
>
> This was a regression in 3.3.0.
>
> When using multiple values in an array for the file type's source
> attribute, Puppet will check them in order and use the first one it
> finds; whenever it doesn't find one, it will log a note at the "info"
> log level, which is silent when logging isn't verbose. In 3.3.0, the
> level was accidentally changed to the "notice" level, which was too
> noisy.
>
> ## Issue 22529: apt package ensure absent/purged causes warnings on 3.3.0
>
> This was a regression in 3.3.0. The apt package provider was logging
> bogus warnings when processing resources with ensurevalues of absent
> or purged.
>
> ## Is

[Puppet Users] Re: install certificate - unless not working

2013-10-03 Thread Ellison Marks

Might have something to do with the pipe? According to the docs, the 
windows provider directly executes the binary. The pipe might be a function 
of the shell... You might try using the alternate syntax they suggest and 
execute your command through cmd.exe.

http://docs.puppetlabs.com/references/latest/type.html#exec-providers

On Thursday, October 3, 2013 8:04:17 AM UTC-7, Armindo Silva wrote:
>
> Hi
>
> I am installing the OpenVPN's certificate if it is not present with the 
> following exec:
>
>
> exec { 'OvpnCert':
>   command => 'certutil.exe -addstore TrustedPublisher 
> c:\installers\OpenVPN_Cert.cer',
>   require => File[ 'c:/eufinity/installers/'],
>   unless  => 'certutil.exe -verifystore TrustedPublisher | findstr 
> OpenVPN',
>   }
>
> Even when *certutil.exe -verifystore TrustedPublisher | findstr 
> OpenVPN*returns 0 ( 
> *echo %errorlevel%* after running the unless cmd: returns *0* when the 
> OpenVPN is present and *1* otherwise), the exec always runs.
> What am I doing wrong?
>
> Thank you.
> Armindo
>

-- 
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: install certificate - unless not working

2013-10-03 Thread Armindo Silva

Hi Elisson,

I totally missed that, exec it with *cmd /c*  made it work.
Thank you very much for your help.

Armindo

On Thursday, October 3, 2013 4:04:17 PM UTC+1, Armindo Silva wrote:
>
> Hi
>
> I am installing the OpenVPN's certificate if it is not present with the 
> following exec:
>
>
> exec { 'OvpnCert':
>   command => 'certutil.exe -addstore TrustedPublisher 
> c:\installers\OpenVPN_Cert.cer',
>   require => File[ 'c:/eufinity/installers/'],
>   unless  => 'certutil.exe -verifystore TrustedPublisher | findstr 
> OpenVPN',
>   }
>
> Even when *certutil.exe -verifystore TrustedPublisher | findstr 
> OpenVPN*returns 0 ( 
> *echo %errorlevel%* after running the unless cmd: returns *0* when the 
> OpenVPN is present and *1* otherwise), the exec always runs.
> What am I doing wrong?
>
> Thank you.
> Armindo
>

-- 
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: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers

2013-10-03 Thread cko

https://gist.github.com/anonymous/6814400


On Thursday, October 3, 2013 5:23:05 PM UTC+2, Rob Reynolds wrote:
>
> You should be able to run 
>
> facter --trace --debug
>
>
> On Wed, Oct 2, 2013 at 5:18 PM, cko >wrote:
>
>> Hi Ethan,
>>
>> what's the exact command that i would have to use? 
>>
>>
>> On Wednesday, October 2, 2013 11:35:29 PM UTC+2, Ethan Brown wrote:
>>
>>> Christian - 
>>>
>>> I'm doing the final verification of our fix, and was hoping that I could 
>>> get the output from Facter run by itself?
>>>
>>>
>>>
>>> On Fri, Sep 20, 2013 at 1:36 PM, Rob Reynolds wrote:
>>>
  I would say with all of this in mind we move forward with a fix where 
 we look to see that the network adapter itself is also enabled. This is 
 laid out in the ticket that I noted earlier.
  

 On Fri, Sep 20, 2013 at 7:44 AM, Rich Siegel  wrote:

>  Exchange DAG is essentially a cluster and the adapter in question the 
> dag ip.
>
> My guess is the logic for adapters should be modded for when 
> netconnectionid is not null.
>
> In general don't try to mess with hidden adapters on dags unless you 
> understand ramifications.
>
> --
> 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
> .
> 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
  
 -- 
 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
 .
 For more options, visit 
 https://groups.google.com/**groups/opt_out
 .

>>>
>>>
>>>
>>> -- 
>>> --
>>> Ethan Brown
>>> et...@puppetlabs.com
>>> Software Engineer
>>>
>>> *Join us at PuppetConf 2014, September 23-24 in San Francisco*
>>>  
>>  -- 
>> 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.
>> 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
>  

-- 
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: Decomission node process (puppet / puppetdb / dashboard)

2013-10-03 Thread Ramin K


On 10/3/2013 8:12 AM, MasterPO wrote:


Unfortunately, for me all this does is make the puppet-master host go
100% busy between the dashboard and mysqld.

I am running Dashboard version 1.2.23 with puppet-server version 3.2.4
and mysql version 5.1.69 on RHEL 6.4

I get the same result running John's cli rake command.

Any ideas?


	I'm guessing you have never deleted reports in Mysql and your database 
is now very very large.


I'd start with trimming the data set down to a reasonable size and then 
process your deletes. I wrote up the process I use here,


https://ask.puppetlabs.com/question/884/how-do-i-reduce-the-space-mysql-is-using-for-puppet-dashboard/

Ramin

--
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: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers

2013-10-03 Thread Rob Reynolds

Was this the entire log (minus anything you feel sensitive)?


On Thu, Oct 3, 2013 at 1:15 PM, cko  wrote:

> https://gist.github.com/anonymous/6814400
>
>
> On Thursday, October 3, 2013 5:23:05 PM UTC+2, Rob Reynolds wrote:
>
>> You should be able to run
>>
>> facter --trace --debug
>>
>>
>> On Wed, Oct 2, 2013 at 5:18 PM, cko  wrote:
>>
>>> Hi Ethan,
>>>
>>> what's the exact command that i would have to use?
>>>
>>>
>>> On Wednesday, October 2, 2013 11:35:29 PM UTC+2, Ethan Brown wrote:
>>>
 Christian -

 I'm doing the final verification of our fix, and was hoping that I
 could get the output from Facter run by itself?



 On Fri, Sep 20, 2013 at 1:36 PM, Rob Reynolds wrote:

>  I would say with all of this in mind we move forward with a fix
> where we look to see that the network adapter itself is also enabled. This
> is laid out in the ticket that I noted earlier.
>
>
> On Fri, Sep 20, 2013 at 7:44 AM, Rich Siegel wrote:
>
>>  Exchange DAG is essentially a cluster and the adapter in question
>> the dag ip.
>>
>> My guess is the logic for adapters should be modded for when
>> netconnectionid is not null.
>>
>> In general don't try to mess with hidden adapters on dags unless you
>> understand ramifications.
>>
>> --
>> 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
>> .
>> For more options, visit 
>> https://groups.google.com/**grou**ps/opt_out
>> .
>>
>
>
>
> --
> Rob Reynolds
> Developer, Puppet Labs
>
> Join us at PuppetConf 2014, September 23-24 in San Francisco
>
> --
> 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
> .
> For more options, visit 
> https://groups.google.com/**grou**ps/opt_out
> .
>



 --
 --
 Ethan Brown
 et...@puppetlabs.com
 Software Engineer

 *Join us at PuppetConf 2014, September 23-24 in San Francisco*

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



-- 
Rob Reynolds
Developer, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
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: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers

2013-10-03 Thread Christian Koep

Yes, thats all i got from *facter --trace --debug*


On Thu, Oct 3, 2013 at 8:41 PM, Rob Reynolds  wrote:

> Was this the entire log (minus anything you feel sensitive)?
>
>
> On Thu, Oct 3, 2013 at 1:15 PM, cko  wrote:
>
>> https://gist.github.com/anonymous/6814400
>>
>>
>> On Thursday, October 3, 2013 5:23:05 PM UTC+2, Rob Reynolds wrote:
>>
>>> You should be able to run
>>>
>>> facter --trace --debug
>>>
>>>
>>> On Wed, Oct 2, 2013 at 5:18 PM, cko  wrote:
>>>
 Hi Ethan,

 what's the exact command that i would have to use?


 On Wednesday, October 2, 2013 11:35:29 PM UTC+2, Ethan Brown wrote:

> Christian -
>
> I'm doing the final verification of our fix, and was hoping that I
> could get the output from Facter run by itself?
>
>
>
> On Fri, Sep 20, 2013 at 1:36 PM, Rob Reynolds wrote:
>
>>  I would say with all of this in mind we move forward with a fix
>> where we look to see that the network adapter itself is also enabled. 
>> This
>> is laid out in the ticket that I noted earlier.
>>
>>
>> On Fri, Sep 20, 2013 at 7:44 AM, Rich Siegel wrote:
>>
>>>  Exchange DAG is essentially a cluster and the adapter in question
>>> the dag ip.
>>>
>>> My guess is the logic for adapters should be modded for when
>>> netconnectionid is not null.
>>>
>>> In general don't try to mess with hidden adapters on dags unless you
>>> understand ramifications.
>>>
>>> --
>>> 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
>>> .
>>> For more options, visit 
>>> https://groups.google.com/**grou**ps/opt_out
>>> .
>>>
>>
>>
>>
>> --
>> Rob Reynolds
>> Developer, Puppet Labs
>>
>> Join us at PuppetConf 2014, September 23-24 in San Francisco
>>
>> --
>> 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
>> .
>> For more options, visit 
>> https://groups.google.com/**grou**ps/opt_out
>> .
>>
>
>
>
> --
> --
> Ethan Brown
> et...@puppetlabs.com
> Software Engineer
>
> *Join us at PuppetConf 2014, September 23-24 in San Francisco*
>
  --
 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
 .
 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
>>>
>>  --
>> 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.
>>
>
>
>
> --
> Rob Reynolds
> Developer, Puppet Labs
>
> Join us at PuppetConf 2014, September 23-24 in San Francisco
>
> --
> 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/_JSpNmSvg_I/unsubscribe.
> 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.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
You received this message because you are subscribed to the Google Grou

Re: [Puppet Users] Re: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers

2013-10-03 Thread Rob Reynolds

This verifies for us that this is a gating issue.

Would you feel comfortable helping us verify that we've fixed this issue
for you?

https://github.com/ferventcoder/facter/blob/874a5a96ac5fa778c50f1e93424850022b1756cf/lib/facter/util/ip/windows.rb#L46-L47




On Thu, Oct 3, 2013 at 1:42 PM, Christian Koep  wrote:

> Yes, thats all i got from *facter --trace --debug*
>
>
> On Thu, Oct 3, 2013 at 8:41 PM, Rob Reynolds  wrote:
>
>> Was this the entire log (minus anything you feel sensitive)?
>>
>>
>> On Thu, Oct 3, 2013 at 1:15 PM, cko  wrote:
>>
>>> https://gist.github.com/anonymous/6814400
>>>
>>>
>>> On Thursday, October 3, 2013 5:23:05 PM UTC+2, Rob Reynolds wrote:
>>>
 You should be able to run

 facter --trace --debug


 On Wed, Oct 2, 2013 at 5:18 PM, cko  wrote:

> Hi Ethan,
>
> what's the exact command that i would have to use?
>
>
> On Wednesday, October 2, 2013 11:35:29 PM UTC+2, Ethan Brown wrote:
>
>> Christian -
>>
>> I'm doing the final verification of our fix, and was hoping that I
>> could get the output from Facter run by itself?
>>
>>
>>
>> On Fri, Sep 20, 2013 at 1:36 PM, Rob Reynolds wrote:
>>
>>>  I would say with all of this in mind we move forward with a fix
>>> where we look to see that the network adapter itself is also enabled. 
>>> This
>>> is laid out in the ticket that I noted earlier.
>>>
>>>
>>> On Fri, Sep 20, 2013 at 7:44 AM, Rich Siegel wrote:
>>>
  Exchange DAG is essentially a cluster and the adapter in question
 the dag ip.

 My guess is the logic for adapters should be modded for when
 netconnectionid is not null.

 In general don't try to mess with hidden adapters on dags unless
 you understand ramifications.

 --
 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
 .
 For more options, visit https://groups.google.com/**grou**
 ps/opt_out .

>>>
>>>
>>>
>>> --
>>> Rob Reynolds
>>> Developer, Puppet Labs
>>>
>>> Join us at PuppetConf 2014, September 23-24 in San Francisco
>>>
>>> --
>>> 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
>>> .
>>> For more options, visit 
>>> https://groups.google.com/**grou**ps/opt_out
>>> .
>>>
>>
>>
>>
>> --
>> --
>> Ethan Brown
>> et...@puppetlabs.com
>> Software Engineer
>>
>> *Join us at PuppetConf 2014, September 23-24 in San Francisco*
>>
>  --
> 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
> .
> 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

>>>  --
>>> 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.
>>>
>>
>>
>>
>> --
>> Rob Reynolds
>> Developer, Puppet Labs
>>
>> Join us at PuppetConf 2014, September 23-24 in San Francisco
>>
>> --
>> 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://gro

[Puppet Users] puppet dashboard with \n\n\n

2013-10-03 Thread Matt Zagrabelny

Greetings,

I've setup puppet dashboard 1.2.23 along with puppetmaster 2.7.18.

I am seeing many \n strings all over the place when looking at
reports. Specifically the \n's are in the Metrics, Log, Events links.

My nodes are showing up okay, and it seems just to be a problem with
the reports. For instance, a Metrics page starts with:

\n
\n
Metrics
\n
\n
Events

\n\n\n\n\n\n\n\n\n

Any advice on where to dig? /usr/share/puppet-dashboard/log/* does not
yield any hints.

Thanks!

-mz

-- 
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 dashboard with \n\n\n

2013-10-03 Thread Juan Sierra Pons

El 03/10/2013 14:00, "Matt Zagrabelny"  escribió:
>
> Greetings,
>
> I've setup puppet dashboard 1.2.23 along with puppetmaster 2.7.18.
>
> I am seeing many \n strings all over the place when looking at
> reports. Specifically the \n's are in the Metrics, Log, Events links.
>
> My nodes are showing up okay, and it seems just to be a problem with
> the reports. For instance, a Metrics page starts with:
>
> \n
> \n
> Metrics
> \n
> \n
> Events
>
> \n\n\n\n\n\n\n\n\n
>
> Any advice on where to dig? /usr/share/puppet-dashboard/log/* does not
> yield any hints.
>
> Thanks!
>
> -mz
>
> --
> 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.
Hi

I had the same problem and the problem was in the ruby version

Which one are you using?

Check the dashboard webpage to find out wich one is the right one.

Regards

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

Re: [Puppet Users] puppet dashboard with \n\n\n

2013-10-03 Thread Matt Zagrabelny

On Thu, Oct 3, 2013 at 5:45 PM, Juan Sierra Pons  wrote:
>
> El 03/10/2013 14:00, "Matt Zagrabelny"  escribió:
>
>
>>
>> Greetings,
>>
>> I've setup puppet dashboard 1.2.23 along with puppetmaster 2.7.18.
>>
>> I am seeing many \n strings all over the place when looking at
>> reports. Specifically the \n's are in the Metrics, Log, Events links.
>>
>> My nodes are showing up okay, and it seems just to be a problem with
>> the reports. For instance, a Metrics page starts with:
>>
>> \n
>> \n
>> Metrics
>> \n
>> \n
>> Events
>>
>> \n\n\n\n\n\n\n\n\n
>>
>> Any advice on where to dig? /usr/share/puppet-dashboard/log/* does not
>> yield any hints.
>>
>> Thanks!
>>
>> -mz
>>
>> --
>> 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.
> Hi
>
> I had the same problem and the problem was in the ruby version
>
> Which one are you using?

realpath =ruby
/usr/bin/ruby1.9.1


> Check the dashboard webpage to find out wich one is the right one.

Looks like 1.8 is what is needed.

Looks like that worked!

Thanks!

-mz

-- 
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] fail when install the console

Re: [Puppet Users] Re: brew and macosx and puppet

[Puppet Users] Re: onlyif return code

Re: [Puppet Users] fail when install the console

[Puppet Users] Re: Idiom for throwing an error if a command fails

[Puppet Users] Re: fail when install the console

Re: [Puppet Users] Re: Still no nagios joy

[Puppet Users] Re: Converting to heira format issue

[Puppet Users] install certificate - unless not working

[Puppet Users] Re: Decomission node process (puppet / puppetdb / dashboard)

Re: [Puppet Users] install certificate - unless not working

Re: [Puppet Users] Re: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers

[Puppet Users] Re: install certificate - unless not working

Re: [Puppet Users] Re: Still no nagios joy

[Puppet Users] Re: Name or service not known issue

Re: [Puppet Users] Idiom for throwing an error if a command fails

[Puppet Users] Re: Announce: Puppet 3.3.1-rc3 available

[Puppet Users] Re: install certificate - unless not working

[Puppet Users] Re: install certificate - unless not working

Re: [Puppet Users] Re: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers

Re: [Puppet Users] Re: Decomission node process (puppet / puppetdb / dashboard)

Re: [Puppet Users] Re: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers

Re: [Puppet Users] Re: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers

Re: [Puppet Users] Re: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers

[Puppet Users] puppet dashboard with \n\n\n

Re: [Puppet Users] puppet dashboard with \n\n\n

Re: [Puppet Users] puppet dashboard with \n\n\n

27 matches

Site Navigation

Mail list logo

Footer information