[Puppet Users] Announce: PuppetDB 3.2.4 available

[Russell Mull]

PuppetDB 3.2.4 - February 25, 2016

PuppetDB 3.2.4 Downloads



Available in native package format as part of Puppet Collection 1 (PC1). 
More information on the PC1 repositories is available here: 
http://bit.ly/1HQJDNb

Binary tarball: http://downloads.puppetlabs.com/puppetdb/

Source: http://github.com/puppetlabs/puppetdb

Please report feedback via the Puppet Labs tickets site by submitting a 
ticket with an “Affects Version/s” field of “PDB 3.2.4”: 
https://tickets.puppetlabs.com/browse/PDB

Documentation: http://docs.puppetlabs.com/puppetdb/3.2/

Puppet module: http://forge.puppetlabs.com/puppetlabs/puppetdb

PuppetDB 3.2.4 Release Notes



PuppetDB 3.2.4 is a backward-compatible security and bugfix release that 
fixes a

directory permissions issue, improves the performance of certain metrics

queries, and reduces the size of anonymized export tarballs.

More information on the specifics of the release can be found in the 
official release notes: 
https://docs.puppetlabs.com/puppetdb/3.2/release_notes.html 

Also see the related security advisory: 
https://puppetlabs.com/security/cve/puppetdb-feb-2016-advisory

Contributors

---

Andrew Roetker, Garrett Guillotte, Geoff Nichols, Isaac Eldridge, Ken 
Barber, Kurt Wall, Russell Mull, Ryan Senior, Sean P. McDonald, and Wyatt 
Alt

-- 
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/0026eb2c-3ac6-4a25-b7c6-a81d4d23d6df%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] 'export' is a reserved word?

[Henrik Lindberg]

On 25/02/16 22:56, Tim Skirvin wrote:

 Summary: using the word 'export' as a definition in a parameter
seems to have stopped working somewhere between puppet-agent 1.2.2 and
puppet-agent 1.3.5.  Is this intentional/documented somewhere, or is it a
bug?  Has anybody else seen this?


 More details:

 I'm evaluating puppet-agent 1.3.5, upgrading from 1.2.2, on RHEL
systems.  The first machine I tested on failed to run right away, with an
error like this:

 Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
Evaluation Error: Error while evaluating a Resource Statement, Invalid export in
P_nfs_server::Exports::Line[/foo]: {"foo"=>"ro", "bar"=>"rw", ...} is not a 
resource on node foobar.fnal.gov

 The data structure in mind comes from hiera, and calls a
definition (with create_resources) that looks like this:

 define p_nfs_server::exports::line (
   Enum['present', 'absent'] $ensure = present,
   Hash $export = {}
 ) { [...] }

 If I rename 'export' to 'exports' across the board, then
everything suddenly works.  That is, this is fine:

 define p_nfs_server::exports::line (
   Enum['present', 'absent'] $ensure = present,
   Hash $exports = {}
 ) { [...] }


 So is this a bug, or known behaviour?  Again, this wasn't an
issue back in 1.2.2.  It sure seems like the word 'export' is the kind of
word that could end up on a 'reserved' list somewhere.

 Side note: if I upgrade the client first, before the server (so
I'm running client 1.3.5 against server 1.2.2), I get this error instead:

 Error: Failed to apply catalog: Parameter export failed on 
P_nfs_server::Exports::Line[/foo]: Puppet::Resource.new does not take a hash as 
the first argument. Did you mean (nil, nil) ?

 And I haven't tried 1.3.5 vs 1.3.5 yet because, well, this is
still curious.

 - Tim Skirvin (tskir...@fnal.gov)

You are not the first to use $export: 
https://www.chriscowley.me.uk/blog/2013/04/11/using-hiera-with-puppet/


- henrik

--

Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/

--
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/56CF8BA7.8060308%40puppetlabs.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] 'export' is a reserved word?

[Henrik Lindberg]

On 25/02/16 22:56, Tim Skirvin wrote:

 Summary: using the word 'export' as a definition in a parameter
seems to have stopped working somewhere between puppet-agent 1.2.2 and
puppet-agent 1.3.5.  Is this intentional/documented somewhere, or is it a
bug?  Has anybody else seen this?


 More details:

 I'm evaluating puppet-agent 1.3.5, upgrading from 1.2.2, on RHEL
systems.  The first machine I tested on failed to run right away, with an
error like this:

 Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
Evaluation Error: Error while evaluating a Resource Statement, Invalid export in
P_nfs_server::Exports::Line[/foo]: {"foo"=>"ro", "bar"=>"rw", ...} is not a 
resource on node foobar.fnal.gov

 The data structure in mind comes from hiera, and calls a
definition (with create_resources) that looks like this:

 define p_nfs_server::exports::line (
   Enum['present', 'absent'] $ensure = present,
   Hash $export = {}
 ) { [...] }

 If I rename 'export' to 'exports' across the board, then
everything suddenly works.  That is, this is fine:

 define p_nfs_server::exports::line (
   Enum['present', 'absent'] $ensure = present,
   Hash $exports = {}
 ) { [...] }


 So is this a bug, or known behaviour?  Again, this wasn't an
issue back in 1.2.2.  It sure seems like the word 'export' is the kind of
word that could end up on a 'reserved' list somewhere.

 Side note: if I upgrade the client first, before the server (so
I'm running client 1.3.5 against server 1.2.2), I get this error instead:

 Error: Failed to apply catalog: Parameter export failed on 
P_nfs_server::Exports::Line[/foo]: Puppet::Resource.new does not take a hash as 
the first argument. Did you mean (nil, nil) ?

 And I haven't tried 1.3.5 vs 1.3.5 yet because, well, this is
still curious.

 - Tim Skirvin (tskir...@fnal.gov)



There is no "export" keyword in puppet, it is not reserved in any way. 
This sounds like it has something to do with the backends or the data 
format used there.


- henrik

--

Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/

--
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/56CF8B3D.5030402%40puppetlabs.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] 'export' is a reserved word?

[Tim Skirvin]

Summary: using the word 'export' as a definition in a parameter
seems to have stopped working somewhere between puppet-agent 1.2.2 and
puppet-agent 1.3.5.  Is this intentional/documented somewhere, or is it a
bug?  Has anybody else seen this?


More details:

I'm evaluating puppet-agent 1.3.5, upgrading from 1.2.2, on RHEL
systems.  The first machine I tested on failed to run right away, with an
error like this:

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
Evaluation Error: Error while evaluating a Resource Statement, Invalid export in
P_nfs_server::Exports::Line[/foo]: {"foo"=>"ro", "bar"=>"rw", ...} is not a 
resource on node foobar.fnal.gov

The data structure in mind comes from hiera, and calls a
definition (with create_resources) that looks like this:

define p_nfs_server::exports::line (
  Enum['present', 'absent'] $ensure = present,
  Hash $export = {}
) { [...] } 

If I rename 'export' to 'exports' across the board, then
everything suddenly works.  That is, this is fine:

define p_nfs_server::exports::line (
  Enum['present', 'absent'] $ensure = present,
  Hash $exports = {}
) { [...] } 


So is this a bug, or known behaviour?  Again, this wasn't an
issue back in 1.2.2.  It sure seems like the word 'export' is the kind of
word that could end up on a 'reserved' list somewhere.

Side note: if I upgrade the client first, before the server (so
I'm running client 1.3.5 against server 1.2.2), I get this error instead:

Error: Failed to apply catalog: Parameter export failed on 
P_nfs_server::Exports::Line[/foo]: Puppet::Resource.new does not take a hash as 
the first argument. Did you mean (nil, nil) ?

And I haven't tried 1.3.5 vs 1.3.5 yet because, well, this is
still curious.

- Tim Skirvin (tskir...@fnal.gov)
-- 
HPC Systems Administrator / Developer  http://www.linkedin.com/in/tskirvin
   USCMS-T1 Collaboration Fermilab ECF

-- 
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/20160225215612.GW34112%40fnal.gov.
For more options, visit https://groups.google.com/d/optout.


pgpRVEvJxFSWP.pgp
Description: PGP signature

Re: [Puppet Users] downgrading package with puppet

[tetlika]

using yum

100% sure its available, generally this error happens each time I try to do 
downgrade of any package

четвер, 25 лютого 2016 р. 17:54:41 UTC+2 користувач Hristo Mohamed написав:
>
> Which provider are you using? Are you sure this version is available?
>
> Hristo
>
> On Thu, Feb 25, 2016 at 4:49 PM, tetlika > 
> wrote:
>
>> hi, I have a problem  with puppet sw management
>>
>> when I do in puppet:
>>
>> package { "nginx" :
>> ensure => "1.8.1-1"
>> }
>>
>> the nginx version 1.8.1 is successfully installed and everything is fine
>>
>> when later on the same machine I do:
>>
>> package { "nginx" :
>> ensure => "1.8.0-1"
>> }
>>
>>
>> I receive error:
>>
>> ensure: change from absent to present failed: Could not find package 
>> nginx-1.8.0-1
>>
>>
>> why is that happening?
>>
>> thx
>>
>> -- 
>> 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/ef6a3794-9d82-449e-a2a3-9f2988265140%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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/861b38c6-35d2-4904-997a-c9e842066baf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] downgrading package with puppet

[Hristo Mohamed]

Which provider are you using? Are you sure this version is available?

Hristo

On Thu, Feb 25, 2016 at 4:49 PM, tetlika  wrote:

> hi, I have a problem  with puppet sw management
>
> when I do in puppet:
>
> package { "nginx" :
> ensure => "1.8.1-1"
> }
>
> the nginx version 1.8.1 is successfully installed and everything is fine
>
> when later on the same machine I do:
>
> package { "nginx" :
> ensure => "1.8.0-1"
> }
>
>
> I receive error:
>
> ensure: change from absent to present failed: Could not find package
> nginx-1.8.0-1
>
>
> why is that happening?
>
> thx
>
> --
> 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/ef6a3794-9d82-449e-a2a3-9f2988265140%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CALuoJ67oGZ5UF1d-_-7FvfaAGPnmS6W2aUCoVard-Vzw0QEmtA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] downgrading package with puppet

[tetlika]

hi, I have a problem  with puppet sw management

when I do in puppet:

package { "nginx" :
ensure => "1.8.1-1"
}

the nginx version 1.8.1 is successfully installed and everything is fine

when later on the same machine I do:

package { "nginx" :
ensure => "1.8.0-1"
}


I receive error:

ensure: change from absent to present failed: Could not find package 
nginx-1.8.0-1


why is that happening?

thx

-- 
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/ef6a3794-9d82-449e-a2a3-9f2988265140%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] problem with function lookup provider.

[RG]

Henrik thanks for the reply,
I probably shouldnt have posted the tree info, i am testing both the hiera 
in-module as well as the 
function in-module lookup thats why it looks like an environment. But I can 
see data function return on the server,

#===
# On server 
% puppet apply -e 'notice vartmp::data()'
Notice: Scope(Class[main]): {vartmp::localerb => vartmp/vartmp.erb, 
vartmp::vtfile => /var/tmp/VAR-TMP-FILE}
Notice: Compiled catalog for puppetserver in environment production in 0.08 
seconds
Notice: Applied catalog in 0.16 seconds
You have new mail in /var/spool/mail/root

Its the client that is not getting the data. I can put the function in the 
modules namespace, but it seemed like the 
documentation says you dont need to..

On Wednesday, February 24, 2016 at 11:56:38 PM UTC-5, Henrik Lindberg wrote:
>
> On 24/02/16 21:57, RG wrote: 
> > 
> > I am using puppet 4.3 and it looks like the new function lookup provider 
> > is not working, unless i am missing something. 
> > I am working from this: 
> > 
> https://docs.puppetlabs.com/puppet/latest/reference/lookup_quick_module.html 
> > 
> > I am just testing with this simple example. 
> > % puppet status 
> > { 
> >"is_alive": true, 
> >"version": "4.3.2" 
> > } 
> > 
> > % tree 
> > . 
> > ├── data 
> > │   └── common.yaml 
> > ├── functions 
> > │   └── data.pp 
> > ├── hiera.yaml 
> > ├── manifests 
> > │   └── init.pp 
> > ├── metadata.jason 
> > └── templates 
> >  └── vartmp.erb 
> > #== 
> > 
> > % cat functions/data.pp 
> > function vartmp::data() { 
> > 
> >$base_params = { 
> >  'vartmp::localerb'   => 'vartmp/vartmp.erb', 
> >  'vartmp::vtfile' => '/var/tmp/VAR-TMP-FILE', 
> >} 
> > 
> >$base_params 
> > } 
> > 
> > #== 
> > % cat manifests/init.pp 
> > # Class : vartmp 
> > # 
> > class vartmp ( 
> >$vtfile, 
> >$localerb 
> > ) { 
> > 
> >file { $vtfile: 
> >  owner   => 'root', 
> >  group   => 'root', 
> >  mode=> '0644', 
> >  content => template($localerb), 
> >} 
> > 
> > } 
> > 
> > #== 
> > % egrep data metadata.jason 
> >"data_provider": "function" 
> > #== 
> > 
> This looks odd.The rest of your layout looks like it is for an 
> environment. An environment does not have a metadata.json that is only 
> for modules. For an environment you need to specify the data_provider in 
> environment.conf and set it to 'function'. It will then call the 
> function named 'environment::data()'. 
>
> If you are intstead doing this for a module, the name of the function 
> should be in the module's namespace e.g. 'mymodule::data()'. 
>
> Does that help? 
>
> Since the data functions are just regular functions you can test by 
> calling them directly - e.g: 
>
> puppet apply -e 'notice environment::data()' 
> puppet apply -e 'notice mymodule::data()' 
>
> You can also use 'puppet lookup' command line tool with '--explain' to 
> get detailed trace information about what is going on. 
>
> There are bugs in 4.3 though, but the basic use cases should work. 
> There are many fixes in the upcoming puppet 4.4.0 for lookup/data binding. 
>
>
> - henrik 
>
> > puppet-lint and pupper parser validate both return clean. 
> > 
> > #== 
> > On client. 
> > % puppet status 
> > { 
> >"is_alive": true, 
> >"version": "4.3.2" 
> > } 
> > 
> > % puppet agent -t 
> > Info: Using configured environment 'production' 
> > Info: Retrieving pluginfacts 
> > Info: Retrieving plugin 
> > Info: Loading facts 
> > Error: Could not retrieve catalog from remote server: Error 400 on 
> > SERVER: Evaluation Error: Error while evaluating a Resource Statement, 
> > Class[Vartmp]: 
> >expects a value for parameter 'localerb' 
> >expects a value for parameter 'vtfile' on node puppetclient 
> > Warning: Not using cache on failed catalog 
> > Error: Could not retrieve catalog; skipping run 
> > 
> > Anybody know/see what i am missing? 
> > Thanks 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> > Groups "Puppet Users" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> > an email to puppet-users...@googlegroups.com  
> > . 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/puppet-users/f424077b-1656-4626-b971-033433a570e5%40googlegroups.com
>  
> > <
> https://groups.google.com/d/msgid/puppet-users/f424077b-1656-4626-b971-033433a570e5%40googlegroups.com?utm_medium=email&utm_source=footer>.
>  
>
> > For more options, visit https://groups.google.com/d/optout. 
>
>
> -- 
>
> Visit my Blog "Puppet on the Edge" 
> http://puppet-on-the-edge.blogspot.se/ 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" gr

Re: [Puppet Users] puppet installation

[warron.french]

Moonsun1124, go to this site and look at the appropriate Install Links for
your variation of the installation - https://docs.puppetlabs.com/

Happy hunting.

--
Warron French


On Thu, Feb 25, 2016 at 8:37 AM, warron.french 
wrote:

> P.S.  What particular version of Puppet did you install?
>
> Was it the limited 10-count PuppetLabs Puppet Enterprise?
>
> Provide much more detail as it will help someone with much more experience
> than me to help you.
>
> --
> Warron French
>
>
> On Thu, Feb 25, 2016 at 8:35 AM, warron.french 
> wrote:
>
>> During the installation process, it works you through the configuration
>> steps and build process.  It even tells you to make sure that you have port
>> 8140 open in the firewall.
>>
>> The *default* account = admin.
>> The password for that account, is whatever was typed into the fields( 1st
>> initial, 2nd confirm).
>>
>> If you have a working DNS, and you have opened up port 8140/tcp, then
>> browse to the hostname you provided during the installation phase (also
>> through a web interface) on port 8140.
>>
>> For example, if the hostname you gave it was puppydog; browse to
>> https://puppydog, because the site is already SSL secured; granted the
>> certificate was issued by a Puppet CA, as opposed to your own corporations
>> CA.
>>
>>
>>
>> --
>> Warron French
>>
>>
>> On Tue, Feb 23, 2016 at 7:27 PM,  wrote:
>>
>>> Hi All,
>>>
>>> I am new to puppet. I think we have two type of installations one is
>>> tarball another with packages(rpm or yum).
>>>
>>> if we install puppet master and agent with yum, how we can access puppet
>>> web console.
>>>
>>> Thanks,
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Puppet Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to puppet-users+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/puppet-users/8eb526fc-0518-401b-96f2-fdb4d7bb5c78%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>

-- 
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/CAJdJdQ%3DrS%2B8_7_jaqC5vLvvvgdgC1pmS2sOJ4LeO7-bCTz6xcw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet installation

[warron.french]

P.S.  What particular version of Puppet did you install?

Was it the limited 10-count PuppetLabs Puppet Enterprise?

Provide much more detail as it will help someone with much more experience
than me to help you.

--
Warron French


On Thu, Feb 25, 2016 at 8:35 AM, warron.french 
wrote:

> During the installation process, it works you through the configuration
> steps and build process.  It even tells you to make sure that you have port
> 8140 open in the firewall.
>
> The *default* account = admin.
> The password for that account, is whatever was typed into the fields( 1st
> initial, 2nd confirm).
>
> If you have a working DNS, and you have opened up port 8140/tcp, then
> browse to the hostname you provided during the installation phase (also
> through a web interface) on port 8140.
>
> For example, if the hostname you gave it was puppydog; browse to
> https://puppydog, because the site is already SSL secured; granted the
> certificate was issued by a Puppet CA, as opposed to your own corporations
> CA.
>
>
>
> --
> Warron French
>
>
> On Tue, Feb 23, 2016 at 7:27 PM,  wrote:
>
>> Hi All,
>>
>> I am new to puppet. I think we have two type of installations one is
>> tarball another with packages(rpm or yum).
>>
>> if we install puppet master and agent with yum, how we can access puppet
>> web console.
>>
>> Thanks,
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to puppet-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-users/8eb526fc-0518-401b-96f2-fdb4d7bb5c78%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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/CAJdJdQkeyTWhMVjZdab6GSH%3DrtHW4bX3K87%2Bh8WfpS7p57YchQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet installation

[warron.french]

During the installation process, it works you through the configuration
steps and build process.  It even tells you to make sure that you have port
8140 open in the firewall.

The *default* account = admin.
The password for that account, is whatever was typed into the fields( 1st
initial, 2nd confirm).

If you have a working DNS, and you have opened up port 8140/tcp, then
browse to the hostname you provided during the installation phase (also
through a web interface) on port 8140.

For example, if the hostname you gave it was puppydog; browse to
https://puppydog, because the site is already SSL secured; granted the
certificate was issued by a Puppet CA, as opposed to your own corporations
CA.



--
Warron French


On Tue, Feb 23, 2016 at 7:27 PM,  wrote:

> Hi All,
>
> I am new to puppet. I think we have two type of installations one is
> tarball another with packages(rpm or yum).
>
> if we install puppet master and agent with yum, how we can access puppet
> web console.
>
> Thanks,
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/8eb526fc-0518-401b-96f2-fdb4d7bb5c78%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAJdJdQmxQg97pMpGVpN4bQfA2QBXrjOutcMCiT2%3DoMfmnzoXjg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Augeas failing when acting on smb.conf

['Josh Sinfield' via Puppet Users]

Hi,

I think this is the error you are seeing:
https://fedorahosted.org/augeas/ticket/354
https://github.com/hercules-team/augeas/issues/276

We also receive this error.
There seems to be no rpm package available for RHEL6 >1.0.0 nor >1.1.0 for 
RHEL7. >=1.2.0 contains the fix we need. 1.2.0 is available on RHEL5 
however?!?!

I am going to look at building our own rpm from source, but don't have time 
right now. I tried yesterday but it failed near the end.

Cheers,
Josh





On Tuesday, 4 August 2015 15:56:08 UTC+1, Fabrizio Zelaya wrote:
>
> Here's the file and I will open a bug report too. Maybe between here and 
> there we can find the issue.
>
> Thank you!
>
> On Tue, Aug 4, 2015 at 10:42 AM, Raphaël Pinson  > wrote:
>
>> Is there a way you can post the entire file somewhere maybe? Ideally even 
>> open a bug report on Augeas, with the file.
>>
>>
>>
>> On Tuesday, August 4, 2015 at 4:35:38 PM UTC+2, Fabrizio Zelaya wrote:
>>>
>>> Martin: We don't use templates because our server have different shares 
>>> and printers declare on smb.conf and we don't want to touch that. We want 
>>> puppet to manage only the part that's relevant to DC.
>>>
>>> Werner and Raphael: Thanks for clarifying a little bit, as I mentioned 
>>> I'm very new to augeas and I'm trying to make sense of the messages too.
>>>
>>> There's no line 2545 and on line 67 I got 
>>> idmap config * : backend = rid
>>>
>>> There's no column 2545 either following lines are 
>>>winbind rpc only = true
>>>winbind normalize names = true
>>>
>>>
>>>
>>>
>>>
>>> On Tue, Aug 4, 2015 at 10:29 AM, Raphaël Pinson <
>>> raphael...@camptocamp.com> wrote:
>>>
 Sorry, my bad. What's on line 67 of your file?


 On Tuesday, August 4, 2015 at 3:05:12 PM UTC+2, Werner Flamme wrote:
>
> Raphaël Pinson [04.08.2015 14:03]: 
> > Hello, 
> > 
> > 
> > What do you have on line 2545 in your smb.conf? 
>
> Isn't this line 67, character 2545? 
>
> I guess the characters are counted through the whole file and not for 
> each line ;) 
>
> > 
> > 
> > 
> > Regards, 
> > 
> > Raphaël Pinson 
> > 
> > 
> > 
> > 
> > On Monday, August 3, 2015 at 11:04:01 PM UTC+2, Fabrizio Zelaya 
> wrote: 
> >> 
> >> Hello everyone! 
> >> 
> >> I am trying to run puppet agent on a SL-6 Machine and one action 
> I'm 
> >> trying to apply is to add the machine to our domain. However I ran 
> into an 
> >> issue when running puppet agent -t 
> >> 
> >> Debug: Augeas[global](provider=augeas): Opening augeas with root /, 
> lens 
> >> path /var/lib/puppet/lib/augeas/lenses, flags 64 
> >> Debug: Augeas[global](provider=augeas): Augeas version 1.0.0 is 
> installed 
> >> Warning: Augeas[global](provider=augeas): Loading failed for one or 
> more 
> >> files, see debug for /augeas//error output 
> >> Debug: Augeas[global](provider=augeas): 
> >> /augeas/files/etc/samba/smb.conf/error = parse_failed 
> >> Debug: Augeas[global](provider=augeas): 
> >> /augeas/files/etc/samba/smb.conf/error/pos = 2545 
> >> Debug: Augeas[global](provider=augeas): 
> >> /augeas/files/etc/samba/smb.conf/error/line = 67 
> >> Debug: Augeas[global](provider=augeas): 
> >> /augeas/files/etc/samba/smb.conf/error/char = 0 
> >> Debug: Augeas[global](provider=augeas): 
> >> /augeas/files/etc/samba/smb.conf/error/lens = 
> >> /usr/share/augeas/lenses/dist/inifile.aug:391.25-.43: 
> >> Debug: Augeas[global](provider=augeas): 
> >> /augeas/files/etc/samba/smb.conf/error/message = Get did not match 
> entire 
> >> input 
> >> 
>
>
> -- 
>
>
> -- 
 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/6a25b9c4-0cd8-4189-a54c-0b90bfeac924%40googlegroups.com
  
 
 .

 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>>>
>>> -- 
>>> Faltan 43 en Ayotzinapa!
>>> Faltan 43 en Mi Casa!
>>>
>>> Fabrizio Zelaya
>>> Systems Administrator
>>>
>>> -- 
>> 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/9b2bb310-1dc9-43cd-8865-b4f73b0c3978%40googlegroups.com
>>  
>>