[Puppet Users] Re: Installing MSI failed with errror: The network name cannot be found.

[tinu]

Hello Josh

Here the output from puppet agent --test --debug --trace:

ruby 1.8.7 (2012-02-08 patchlevel 358) [i386-mingw32]
C:\Program Files (x86)\Puppet Labs\Puppet\bin>puppet agent --test --debug 
--trace
debug: Failed to load library 'syslog' for feature 'syslog'
debug: Failed to load library 'selinux' for feature 'selinux'
debug: Puppet::Type::File::ProviderPosix: feature posix is missing
debug: Failed to load library 'ldap' for feature 'ldap'
debug: Failed to load library 'shadow' for feature 'libshadow'
debug: 
/File[C:/ProgramData/PuppetLabs/puppet/var/state/last_run_summary.yaml]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/var/state]
debug: /File[C:/ProgramData/PuppetLabs/puppet/var/state/resources.txt]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/var/state]
debug: /File[C:/ProgramData/PuppetLabs/puppet/var/run]: Autorequiring 
File[C:/ProgramData/PuppetLabs/puppet/var]
debug: /File[C:/ProgramData/PuppetLabs/puppet/var/state/graphs]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/var/state]
debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl]: Autorequiring 
File[C:/ProgramData/PuppetLabs/puppet/etc]
debug: 
/File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/private_keys/webtest02.infra.be.ch.pem]:
 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/private_keys]
debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/public_keys]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl]
debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/crl.pem]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl]
debug: 
/File[C:/ProgramData/PuppetLabs/puppet/var/state/last_run_report.yaml]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/var/state]
debug: /File[C:/ProgramData/PuppetLabs/puppet/var/clientbucket]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/var]
debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/certs]: Autorequiring 
File[C:/ProgramData/PuppetLabs/puppet/etc/ssl]
debug: /File[C:/ProgramData/PuppetLabs/puppet/var/client_yaml]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/var]
debug: /File[C:/ProgramData/PuppetLabs/puppet/var/lib]: Autorequiring 
File[C:/ProgramData/PuppetLabs/puppet/var]
debug: /File[C:/ProgramData/PuppetLabs/puppet/var/state/classes.txt]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/var/state]
debug: 
/File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/certificate_requests]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl]
debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/private]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl]
debug: 
/File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/public_keys/webtest02.infra.be.ch.pem]:
 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/public_keys]
debug: 
/File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/certs/webtest02.infra.be.ch.pem]:
 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/certs]
debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/puppet.conf]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc]
debug: /File[C:/ProgramData/PuppetLabs/puppet/var/log]: Autorequiring 
File[C:/ProgramData/PuppetLabs/puppet/var]
debug: /File[C:/ProgramData/PuppetLabs/puppet/var/state/state.yaml]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/var/state]
debug: /File[C:/ProgramData/PuppetLabs/puppet/var/state]: Autorequiring 
File[C:/ProgramData/PuppetLabs/puppet/var]
debug: /File[C:/ProgramData/PuppetLabs/puppet/var/facts]: Autorequiring 
File[C:/ProgramData/PuppetLabs/puppet/var]
debug: /File[C:/ProgramData/PuppetLabs/puppet/var/client_data]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/var]
debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/certs/ca.pem]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/certs]
debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/private_keys]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl]
debug: Finishing transaction 12916
debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/private_keys]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl]
debug: 
/File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/private_keys/webtest02.infra.be.ch.pem]:
 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/private_keys]
debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/private]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl]
debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/crl.pem]: 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl]
debug: 
/File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/certs/webtest02.infra.be.ch.pem]:
 
Autorequiring File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/certs]
debug: /File[C:/ProgramData/PuppetLabs/puppet/var/facts]: Autorequiring 
File[C:/ProgramData/PuppetLabs/puppet/var]
debug: /File[C:/ProgramData/PuppetLabs/puppet/var/run]: Autorequiring 
File[C:/ProgramData/PuppetLabs/puppet/var]
debug: 
/File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/public_keys/webtest02.infra.be.ch.

[Puppet Users] Re: Not collecting exported resources without storeconfigs

[Larry Long]

Well, it seems puppet config print is useless as it is incorrect with most 
values it shows. I know storeconfigs are up and running and I think its 
going to puppetdb. I am still having issues with my mod.


On Wednesday, July 24, 2013 11:57:17 PM UTC-4, Larry Long wrote:
>
> # cat /etc/redhat-release
> CentOS release 6.4 (Final)
> # puppet --version
> 3.2.3
> # rpm -q puppetdb
> puppetdb-1.3.2-1.el6.noarch
>
> I am now receiving "Not collecting exported resources without 
> storeconfigs" for my opsview module. It was working fine on puppet 2.7 with 
> Activerecord/MySQL. I am still new to puppetdb so maybe I am missing 
> something. This is from puppet.conf:
>
> storeconfigs   = true
> thin_storeconifgs = false
> storeconfigs_backend = puppetdb
>
> Any ideas?
>
> Thanks,
> -Larry
>

-- 
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] creating a (mac) package from a known good source + local patches

[Moses Mendoza]

Hi Clay,

Thanks for the patch! We'll take a look. Switching over to pkgbuild
has been on the list for awhile.

Cheers,
Moses


On Thu, Jul 25, 2013 at 3:45 PM, Clay Caviness  wrote:
> Thanks, Moses. I'll update our internal build process to use this method.
>
> Also, FYI, I created https://github.com/puppetlabs/packaging/pull/171 to
> update the apple task to use pkgbuild instead of PackageMaker (since that
> was easier than trying to find and install packagemaker...)
>
>
> On Wed, Jul 24, 2013 at 7:38 PM, Moses Mendoza  wrote:
>>
>> Hi Clay,
>>
>> I totally see your use case. We're currently looking to revisit the
>> way we build apple packages to make things more sane.
>>
>> In the meantime, there is a workaround workflow, which still uses
>> git/github but allows you to keep things offline after you download
>> them.  As noted in the ticket, the packaging tasks rely on our
>> projects' git code info, so we have to keep that around to build.  If
>> you don't want to rsync around git clones, one way I've accomplished
>> it is using git bundles[1] (like a git archive, but retains the
>> version control info). This process is the same for facter, puppet,
>> and hiera.
>>
>> Roughly:
>>
>> Clone facter and check out the tag that you want to build, e.g. 1.7.2.
>> The tags we push to github are the canonical artifacts we use to mark
>> a release.
>># git clone git://github.com/puppetlabs/facter && cd facter && git
>> checkout 1.7.2
>>
>> We sign our tags, so you can verify the tag if you have our public key
>> installed (see [2] on how to get it)
>># git verify-tag 1.7.2
>>
>> Create a git bundle of your clone
>># git bundle create facter_bundle HEAD --tags
>>
>> Clone the packaging repo and create a git archive of it as well. 0.2.0
>> is the most recent version
>># git clone git://github.com/puppetlabs/packaging && cd packaging
>> && git checkout 0.2.0
>># git bundle create packaging_bundle HEAD --tags
>>
>> With the two git bundle files, you can now create mac packages
>> offline. Take the git bundles to wherever you want to build packages,
>> and git clone then to extract.
>>   # git clone facter_bundle facter
>>   # git clone packaging_bundle facter/ext/packaging
>>   # apply your patches to facter (even branch and commit them if you want)
>>
>> Now build packages:
>>   # cd facter && rake package:apple  ; # a dmg will be staged in
>> ./pkg/apple/
>>
>> I completely understand your concern about the tasks talking to github
>> - some of them do. However, rake package:apple isn't one of them - it
>> relies entirely on tools present on the system.
>>
>> [1] http://git-scm.com/blog/2010/03/10/bundles.html
>> [2] http://puppetlabs.com/misc/download-options
>>
>> On Wed, Jul 24, 2013 at 2:28 PM, Clay Caviness 
>> wrote:
>> > I need to have a way to re-create the installation package we use for
>> > facter
>> > and puppet, offline, from a known-good source. Often, we have local
>> > patches
>> > (e.g., backporting certain providers from 3.x to 2.x because our servers
>> > are
>> > still on 2.x, or patching things not yet released upstream), so our
>> > process
>> > has been:
>> >
>> > 1) Download tarball for a given release
>> > 2) Update makefile we use to create package to refer to new tarball
>> > 3) Verify local patches are still required
>> > 4) Build (possibly patched) package using ./etc/osx/createpackage.sh
>> >
>> > Now that createpackage.sh is really fully deprecated and gone, I'm
>> > looking
>> > at the rake packaging tasks. As I found in
>> > http://projects.puppetlabs.com/issues/21760#note-4 the tarball is
>> > useless
>> > since the rake tasks assume you're in a git checkout.
>> >
>> > So now I'm at a bit of a loss on how to create these packages. Checkout
>> > a
>> > specific tag, and then make my own tarball? I'm concerned that the
>> > reliance
>> > on it being a git checkout means the tasks may end up talking to github,
>> > making the whole process not hermetic.
>> >
>> > What's the best solution for this? Shall I create this as an issue
>> > against
>> > the packaging tasks?
>> >
>> > 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 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.
>> >
>> >
>>
>>
>>
>> --
>> Moses Mendoza
>> Puppet Labs
>>
>> Join us at PuppetConf 2013, August 22-23 in San Francisco -
>> http://bit.ly/pupconf13
>> Register now and take advantage of the Final Countdown discount - save
>> 15%!
>>
>> --
>> 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 a

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

[John Warburton]

On 25 July 2013 22:54, yannig rousseau  wrote:

> Do you know if it's possible to lauch it from a script (maybe a sql
> request ?)


rake --silent node:del name=deleteme RAILS_ENV=production

I also run a job each day to tidy up the database:

# Purged nodes leave behind orphaned records:
#
http://docs.puppetlabs.com/pe/2.0/welcome_known_issues.html#consoles-reportsprune-task-leaves-orphaned-data
# http://projects.puppetlabs.com/issues/6717
rake --silent RAILS_ENV=production reports:prune:orphaned >> $LOG 2>&1

# Recover/pack space from deletions with table optimization
# http://dev.mysql.com/doc/refman/5.0/en/mysqlcheck.html
DATABASE=`grep database:
/local/puppet/dashboard/dashboard/config/database.yml | awk '{print $2}'`
USER=`grep username: /local/puppet/dashboard/dashboard/config/database.yml
| awk '{print $2}'`
PASSWORD=`grep password:
/local/puppet/dashboard/dashboard/config/database.yml | awk '{print $2}'`
mysqlcheck -u $USER --password=$PASSWORD --optimize --databases $DATABASE
>> $LOG 2>&1


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: How do I set global noop?

[Sam Morrison]

Yeah but then when we push out noop = true in puppet.conf how do we then
push out noop = false via puppet if they're all in noop.

Managing on the server is the only way to do it in a safe and scalable way
(we have 500+ nodes)





On Thu, Jul 25, 2013 at 10:18 PM, Klavs Klavsen  wrote:

> well - perhaps you can put noop = true
>
> or something in puppet.conf on the clients ?
>
> --
> 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/HzjRMtQlHRU/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 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: is there any way to see what are the resources exported by a node?

[Manoj]

The actual problem is explained in the link in my  first message and it was
caused by an older version(0.9.0-1puppetlabs1) of puppetdb. I installed
puppetdb through modules and was hopping that it would install the latest
version(1.3.2). Thar was the reason I was trying the v2 query. Then later I
looked at the puppetdb logs and in the restart message it clearly says the
version.

When I fix my apt-get and install the new puppetdb all start working.


On Thu, Jul 25, 2013 at 10:15 PM, Klavs Klavsen  wrote:

> would you mind sharing your solution - for the benefit of others who may
>>> find your question by googleing - and can't really find the answer in the
>>> irc conversation you had? :)
>>>
>>  --
> 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/5ufuFOPbcWc/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.
>
>
>



-- 
Manoj
+61-416128308

-- 
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] creating a (mac) package from a known good source + local patches

[Clay Caviness]

Thanks, Moses. I'll update our internal build process to use this method.

Also, FYI, I created https://github.com/puppetlabs/packaging/pull/171 to
update the apple task to use pkgbuild instead of PackageMaker (since that
was easier than trying to find and install packagemaker...)


On Wed, Jul 24, 2013 at 7:38 PM, Moses Mendoza  wrote:

> Hi Clay,
>
> I totally see your use case. We're currently looking to revisit the
> way we build apple packages to make things more sane.
>
> In the meantime, there is a workaround workflow, which still uses
> git/github but allows you to keep things offline after you download
> them.  As noted in the ticket, the packaging tasks rely on our
> projects' git code info, so we have to keep that around to build.  If
> you don't want to rsync around git clones, one way I've accomplished
> it is using git bundles[1] (like a git archive, but retains the
> version control info). This process is the same for facter, puppet,
> and hiera.
>
> Roughly:
>
> Clone facter and check out the tag that you want to build, e.g. 1.7.2.
> The tags we push to github are the canonical artifacts we use to mark
> a release.
># git clone git://github.com/puppetlabs/facter && cd facter && git
> checkout 1.7.2
>
> We sign our tags, so you can verify the tag if you have our public key
> installed (see [2] on how to get it)
># git verify-tag 1.7.2
>
> Create a git bundle of your clone
># git bundle create facter_bundle HEAD --tags
>
> Clone the packaging repo and create a git archive of it as well. 0.2.0
> is the most recent version
># git clone git://github.com/puppetlabs/packaging && cd packaging
> && git checkout 0.2.0
># git bundle create packaging_bundle HEAD --tags
>
> With the two git bundle files, you can now create mac packages
> offline. Take the git bundles to wherever you want to build packages,
> and git clone then to extract.
>   # git clone facter_bundle facter
>   # git clone packaging_bundle facter/ext/packaging
>   # apply your patches to facter (even branch and commit them if you want)
>
> Now build packages:
>   # cd facter && rake package:apple  ; # a dmg will be staged in
> ./pkg/apple/
>
> I completely understand your concern about the tasks talking to github
> - some of them do. However, rake package:apple isn't one of them - it
> relies entirely on tools present on the system.
>
> [1] http://git-scm.com/blog/2010/03/10/bundles.html
> [2] http://puppetlabs.com/misc/download-options
>
> On Wed, Jul 24, 2013 at 2:28 PM, Clay Caviness 
> wrote:
> > I need to have a way to re-create the installation package we use for
> facter
> > and puppet, offline, from a known-good source. Often, we have local
> patches
> > (e.g., backporting certain providers from 3.x to 2.x because our servers
> are
> > still on 2.x, or patching things not yet released upstream), so our
> process
> > has been:
> >
> > 1) Download tarball for a given release
> > 2) Update makefile we use to create package to refer to new tarball
> > 3) Verify local patches are still required
> > 4) Build (possibly patched) package using ./etc/osx/createpackage.sh
> >
> > Now that createpackage.sh is really fully deprecated and gone, I'm
> looking
> > at the rake packaging tasks. As I found in
> > http://projects.puppetlabs.com/issues/21760#note-4 the tarball is
> useless
> > since the rake tasks assume you're in a git checkout.
> >
> > So now I'm at a bit of a loss on how to create these packages. Checkout a
> > specific tag, and then make my own tarball? I'm concerned that the
> reliance
> > on it being a git checkout means the tasks may end up talking to github,
> > making the whole process not hermetic.
> >
> > What's the best solution for this? Shall I create this as an issue
> against
> > the packaging tasks?
> >
> > 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 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.
> >
> >
>
>
>
> --
> Moses Mendoza
> Puppet Labs
>
> Join us at PuppetConf 2013, August 22-23 in San Francisco -
> http://bit.ly/pupconf13
> Register now and take advantage of the Final Countdown discount - save 15%!
>
> --
> 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] large file (45M) sometimes truncated while using puppet:/// for transfers

[Matt Schurenko]

Having a strange issue that just surfaced yesterday. We have a 45Mb file 
that sometimes does not transfer fully. The upshot is when puppet goes to 
install the file (in this case it's a .deb pkg) dpkg complains with:

Debug: Executing '/usr/bin/dpkg --force-confold -i 
/usr/src/jre_1.7.0_amd64.deb'
Error: Execution of '/usr/bin/dpkg --force-confold -i 
/usr/src/jre_1.7.0_amd64.deb' returned 1: (Reading database ... 37263 files 
and directories currently installed.)
Unpacking jre (from /usr/src/jre_1.7.0_amd64.deb) ...
dpkg-deb (subprocess): short read on buffer copy for failed to write to 
pipe in copy
dpkg-deb: error: subprocess paste returned error exit status 2
dpkg: error processing /usr/src/jre_1.7.0_amd64.deb (--install):
 short read on buffer copy for backend dpkg-deb during 
`./opt/jre1.7.0_13/lib/rt.jar'
Errors were encountered while processing:
 /usr/src/jre_1.7.0_amd64.deb

Like I mentioned, the file should be 45Mb; however I've seen it end up with 
varying sizes, anywhere from 3Mb to 35Mb. This really is quite baffling. 
Shouldn't there be some kind of checksum to ensure that the size/contents 
of the file is in tact? I am running version 3.1.0 on both puppet-master 
and puppet agent(s).

I've looked into running puppet behind Apache Passenger or even just 
serving up the files from Apache or NGINX. Is this a known issue with 
puppet's built-in web server? This is affecting our deploys and am looking 
for a solution ASAP.

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 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: Not collecting exported resources without storeconfigs

[Larry Long]

Apparently it is ignoring the settings in my puppet.conf:

# puppet config --verbose --debug print|grep storeconfig
async_storeconfigs = false
storeconfigs = false
storeconfigs_backend = active_record
thin_storeconfigs = false

Researching more!

On Wednesday, July 24, 2013 11:57:17 PM UTC-4, Larry Long wrote:
>
> # cat /etc/redhat-release
> CentOS release 6.4 (Final)
> # puppet --version
> 3.2.3
> # rpm -q puppetdb
> puppetdb-1.3.2-1.el6.noarch
>
> I am now receiving "Not collecting exported resources without 
> storeconfigs" for my opsview module. It was working fine on puppet 2.7 with 
> Activerecord/MySQL. I am still new to puppetdb so maybe I am missing 
> something. This is from puppet.conf:
>
> storeconfigs   = true
> thin_storeconifgs = false
> storeconfigs_backend = puppetdb
>
> Any ideas?
>
> Thanks,
> -Larry
>

-- 
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: 3.2.2 on CentOS 6.3, and "Did not receive certificate"

[Forrie]

Having read through more threads, I ran across an article that pointed out 
the permissions and ownership of config.ru needed to be owned by 
puppet:puppet.   I changed this and now everything is working.

I'm royally annoyed, because nowhere in these logs (either via Puppet or 
Passenger) was this logged.   Seems like a real no-brainer.

Bug report.


-- 
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: Not collecting exported resources without storeconfigs

[Larry Long]

Maybe an issue with puppetdb? I see some weirdness, although no apparent 
errors on it.

On Wednesday, July 24, 2013 11:57:17 PM UTC-4, Larry Long wrote:
>
> # cat /etc/redhat-release
> CentOS release 6.4 (Final)
> # puppet --version
> 3.2.3
> # rpm -q puppetdb
> puppetdb-1.3.2-1.el6.noarch
>
> I am now receiving "Not collecting exported resources without 
> storeconfigs" for my opsview module. It was working fine on puppet 2.7 with 
> Activerecord/MySQL. I am still new to puppetdb so maybe I am missing 
> something. This is from puppet.conf:
>
> storeconfigs   = true
> thin_storeconifgs = false
> storeconfigs_backend = puppetdb
>
> Any ideas?
>
> Thanks,
> -Larry
>

-- 
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] Sysadmin Day is tomorrow! We're doing a webinar on Flash in the enterprise. You can win passes to PuppetConf 2013!

[Josh Folland]

Hey Everyone,

First time posting in the Puppet community, so I hope I'm not breaking any 
rules (I did take a quick look at the Community Guidelines 
page). 
As many of you already know, tomorrow is July 26th, also known in some 
circles as Sysadmin Day. My colleague Trevor 
Potthas organized a webinar with folks 
from Tintri, Nutanix and Proximal Data 
to talk about Flash in the enterprise with someone from CloudPhysics to 
keep them honest. This webinar is his way to give back to our fellow 
systems administrators, and during the webinar we'll be taking open 
questions from the floor. Whoever can ask a question that makes the 
panelists squirm the most will be able to win some pretty sweet prizes that 
include: 

5x passes to PuppetConf  2013 
5x Proximal Data software licenses 
5x Cloudphysics software licenses 
1x year's worth of training from Trainsignal 
1x swag bag from Trainsignal 
2x swag bags from Spiceworks

We'd love to have some folks from the Puppet community come out and play 
tomorrow. The webinar starts at 1:30pm PST, and you can find more details 
here or 
register 
directly for the webinar 
here. 
See you then!

-- 
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: Installing MSI failed with errror: The network name cannot be found.

[Josh Cooper]

Hi Tinu,


On Thu, Jul 25, 2013 at 7:44 AM, tinu  wrote:

> Hello Josh
>
> Thank you for your answers.
>
> I changed the $msi_install_dir = '"C:\\Program Files\\System Center
> Operations Manager 2007"' to "C:\\Program Files\\System Center Operations
> Manager 2007",
> and the $msi_logfile to
> "C:\\ProgramData\\PuppetLabs\\puppet\\var\\log\\$msi_package_name.log"
>
> Result from *Run Puppet Agent*:
>
> Running Puppet agent on demand ...
> info: Retrieving plugin
> info: Loading facts in
> C:/ProgramData/PuppetLabs/puppet/var/lib/facter/defaultgateway.rb
> info: Loading facts in
> C:/ProgramData/PuppetLabs/puppet/var/lib/facter/networkadapters.rb
> info: Caching catalog for webtest02.infra.be.ch
> info: Applying configuration version '1374762832'
> err: /Stage[main]/Services::Scomagent/Package[System Center Operations
> Manager 2007 R2 Agent]/ensure: change from absent to present failed: *Failed
> to install: The network name cannot be found.*
> notice: Finished catalog run in 90.96 seconds
>

Can you launch the "Start Command Prompt with Puppet", right click, select
Run as Administrator. Stop the puppet service (net stop puppet), and then
execute:

puppet agent --test --debug --trace

And reply with the resulting stack trace?

Josh

-- 
Josh Cooper
Developer, Puppet Labs

*Join us at PuppetConf 2013, August 22-23 in San Francisco - *
http://bit.ly/pupconf13*
**Register now and take advantage of the Final Countdown discount - save
15%!*

-- 
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] open source Puppet 3 cannot compile catalog on newly built Puppetmaster

[Josh Cooper]

On Thu, Jul 25, 2013 at 7:54 AM, GregC  wrote:

> Following the instructions from puppetlabs for yum install on Red Hat 6,
> no problems
>
> When I try to run a puppet test I get the following error, there are no
> manifest on the system at this time.
>
> [root@puppetmaster3:/etc/puppet/manifests]# puppet --version
> 3.2.3
>
> [root@puppetmaster3:/etc/puppet/manifests]# puppet agent -tv --test
> Info: Retrieving plugin
> Error: Failed to apply catalog: undefined method `support_format?' for
> nil:NilClass
>
> I never had this issue when building a 2.6 or 2.7 puppetmaster, anyone
> know how to resolve this?
>
> --
> 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.
>
>
>

Can you run with puppet agent --test --debug --trace and paste the
backtrace?

Josh

-- 
Josh Cooper
Developer, Puppet Labs

*Join us at PuppetConf 2013, August 22-23 in San Francisco - *
http://bit.ly/pupconf13*
**Register now and take advantage of the Final Countdown discount - save
15%!*

-- 
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] How can I read registry values?

[Josh Cooper]

Hi Tinu,


On Thu, Jul 25, 2013 at 8:04 AM, tinu  wrote:

> I should read the values of some registry keys like
> 'HKLM\SOFTWARE\Puppet\WCM\Initial_Setup'.
>
> How can I do this?
>
> Thanx
>
> Tinu
>
> --
> 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.
>
>
>

Something like this should work:

require 'win32/registry'

Win32::Registry::HKEY_LOCAL_MACHINE.open(*'*SOFTWARE\Puppet\WCM\Initial_Setup')
do |reg|
  value = reg['foo']
end

Note win32/registry is part of the ruby stdlib:
http://ruby-doc.org/stdlib-1.9.3/libdoc/dl/rdoc/Win32/Registry.html

There are also methods to read values as REG_DWORD, REG_EXPAND_SZ, etc.

Josh

-- 
Josh Cooper
Developer, Puppet Labs

*Join us at PuppetConf 2013, August 22-23 in San Francisco - *
http://bit.ly/pupconf13*
**Register now and take advantage of the Final Countdown discount - save
15%!*

-- 
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: Heria, Facts, and Puppet

[Ellison Marks]

Not sure exactly, but in general you want common to be searched last, as 
hiera by default bails when it finds an answer, so your hierarchy in the 
conf file is backwards. You'd want the env_name fact above common.

On Thursday, July 25, 2013 7:27:26 AM UTC-7, chengkai liang wrote:
>
> So something doesn't look right for me when running puppet apply -e 
> 'include ...' for looking heria via facter fact.
>
> I have hiera configure as this,
>
> :backends:
> - yaml
>
> :hierarchy:
> - common 
> - '%{env_name}'
>
> :yaml:
> :datadir: /var/lib/hiera/data
>
> and, a file envXX.yaml store in the datadir, and I can run *hiera xyz 
> env_name=envXX* to get the the value of abc associate with xyz.
>
> Yet, if I export the value variable env_name by *export 
> FACTER_env_name=*envXX, 
> and run:
>
> *puppet apply -e 'include my_module
>
> *
> puppet will complaint that it can't find data store in envXX.yaml.  From 
> the debug output,
>
> debug: importing 
> '/Users/cliang/.puppet/modules/puppet_flux2_config/manifests/init.pp' in 
> environment production
> debug: Automatically imported puppet_flux2_config from puppet_flux2_config 
> into production
> debug: hiera(): Hiera YAML backend starting
> debug: hiera(): Looking up host_header_url in YAML backend
> debug: hiera(): Looking for data source common
> Could not find data item host_header_url in any Hiera data file and no 
> default supplied at 
> /Users/cliang/.puppet/modules/puppet_flux2_config/manifests/init.pp:4 on 
> node m-mba.local
>
> It seems that it stop looking right after common, while running with *hiera 
> xyz env_name=envXX* *--debug *shows,
>
> DEBUG: Thu Jul 25 07:24:48 -0700 2013: Hiera YAML backend starting
> DEBUG: Thu Jul 25 07:24:48 -0700 2013: Looking up host_header_url in YAML 
> backend
> DEBUG: Thu Jul 25 07:24:48 -0700 2013: Looking for data source common
> DEBUG: Thu Jul 25 07:24:48 -0700 2013: Looking for data source *envXX*
> DEBUG: Thu Jul 25 07:24:48 -0700 2013: Found xyz in *envXX*
>
> So why puppet apply won't look further into envXX.yaml file?  Anybody can 
> help on this?
>
>

-- 
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: No reports in foreman

[Larry Long]

I have my foreman running over Passenger, but if you are using the default 
webrick, you need to specify the port. The default is 3000.




On Thursday, July 25, 2013 8:04:47 AM UTC-4, Andreas Dvorak wrote:
>
> Dear all
>  
> I am trying to set up reports in foreman, but foreman tells me to 
> configure it.
> What am I doing wrong?
>  
> I have on the puppet master:
> /var/lib/puppet/reports/foreman.rb
> with $foreman_url=http://rh6-puppet-master
> Do I need the port?
>  
> /etc/puppet/puppet.conf with in [main] reports = log, foreman
>  
> I restarted the service service puppetmaster restart
>  
> in /var/log/messages I find: No report named 'foreman'
>  
> On the puppet client I added the line report = true to the [agent] section 
> in the /etc/puppet/config file.
>  
> Best regards
> Andreas
>

-- 
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: Not collecting exported resources without storeconfigs

[Larry Long]

Hi Ken:

Yes, I most definitely restarted HTTPd since I have it running over 
Passenger. Although, I do see that when I make changes to puppet.conf it 
reloads according to /var/log/messages. My puppetdb version is 1.3.2-1. I 
do have puppetdb-terminus installed via RPM like puppetdb. Here is my 
puppet.conf:

# cat /etc/puppet/puppet.conf
### File managed with puppet ###
## Module:   'puppet'
## Template source:  'MODULES/puppet/templates/puppet.conf.erb'

[main]
# The Puppet log directory.
# The default value is '$vardir/log'.
logdir = /var/log/puppet

# Where Puppet PID files are kept.
# The default value is '$vardir/run'.
rundir = /var/run/puppet

# Where SSL certificates are kept.
# The default value is '$confdir/ssl'.
ssldir = $vardir/ssl

# Allow services in the 'puppet' group to access key (Foreman + proxy)
privatekeydir = $ssldir/private_keys { group = service }
hostprivkey = $privatekeydir/$certname.pem { mode = 640 }

# Puppet 3.0.x requires this in both [main] and [master] - harmless on 
agents
autosign   = $confdir/autosign.conf { mode = 664 }


[agent]
# The file in which puppetd stores a list of the classes
# associated with the retrieved configuratiion.  Can be loaded in
# the separate ``puppet`` executable using the ``--loadclasses``
# option.
# The default value is '$confdir/classes.txt'.
classfile = $vardir/classes.txt

# Where puppetd caches the local configuration.  An
# extension indicating the cache format is added automatically.
# The default value is '$confdir/localconfig'.
localconfig = $vardir/localconfig
report  = true
pluginsync  = true
masterport  = 8140
environment = prd
certname= my.puppetserver.com
server  = my.puppetserver.com
listen  = true
splay   = false
runinterval = 1800
noop= false
graph   = true
pluginsync  = true
### Next part of the file is managed by a different template ###
## Module:   'puppet'
## Template source:  'MODULES/puppet/templates/server/puppet.conf.erb'

[master]
autosign   = $confdir/autosign.conf { mode = 664 }
reports= foreman,log,store,puppetdb
external_nodes = /etc/puppet/node.rb
node_terminus  = exec
ca = true
ssldir = /var/lib/puppet/ssl
downcasefacts  = true
storeconfigs   = true
storeconfigs_backend = puppetdb

[prd]
modulepath = /etc/puppet/modules:/etc/puppet/modules/prd
manifests  = /etc/puppet/environments/prd/manifests/site.pp

Thank you!
-Larry
On Thursday, July 25, 2013 11:00:53 AM UTC-4, Ken Barber wrote:
>
> Can you post your _full_ puppet.conf? Also - what version of PuppetDB 
> are you running, and do you have the puppetdb-terminus package 
> installed on your master? I don't think this is the issue - just 
> checking. 
>
> Also - Stupid question, but you obviously restarted 
> puppet/apache/whatever after making the changes to puppet.conf right? 
> I don't mean to insult, but you'll be amazed how often people forget 
> that :-). 
>
> On Thu, Jul 25, 2013 at 3:58 PM, Larry Long > 
> wrote: 
> > I really don't want to go back to ActiveRecord... any ideas anyone? 
> > 
> > 
> > On Wednesday, July 24, 2013 11:57:17 PM UTC-4, Larry Long wrote: 
> >> 
> >> # cat /etc/redhat-release 
> >> CentOS release 6.4 (Final) 
> >> # puppet --version 
> >> 3.2.3 
> >> # rpm -q puppetdb 
> >> puppetdb-1.3.2-1.el6.noarch 
> >> 
> >> I am now receiving "Not collecting exported resources without 
> >> storeconfigs" for my opsview module. It was working fine on puppet 2.7 
> with 
> >> Activerecord/MySQL. I am still new to puppetdb so maybe I am missing 
> >> something. This is from puppet.conf: 
> >> 
> >> storeconfigs   = true 
> >> thin_storeconifgs = false 
> >> storeconfigs_backend = puppetdb 
> >> 
> >> Any ideas? 
> >> 
> >> Thanks, 
> >> -Larry 
> > 
> > -- 
> > 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. 
> > 
> > 
>

-- 
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: node_aws installation problem

[Piotr Jasiulewicz]

Is puppet enterprise free also? Not sure I would get consent from my boss... 
it's a bit sad that the provisioning project looks totally neglected by puppet 
labs.

-- 
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: Passenger with Puppet 3.0, problems running under

[Jim Toth]

As I recall, if the config.ru itself isn't owned by the puppet user, we'll 
get similar errors from Passenger (spewing out an HTML error page, which 
the agents then unhelpfully log).

It might be something else -- given that it's HTML, you might want to just 
go to https://:8140 in a browser and see what it's 
saying -- if all's well, then puppet will just say something like

The environment must be purely alphanumeric, not ''
>
>
And if that doesn't fix it, you could try uncommenting the debugging lines 
you quoted from puppet/util.rb.


I just took my own advice -- we're in the process of rebuilding a test 
puppet master, and in the process of writing this post I noticed that it 
was spewing HTML, and fairly clearly told me that I needed to do a "bundle 
install" since its Gemfile had changed (and the Gemfile.lock, which it was 
complaining about, is not owned by the puppet user by design).


On Wednesday, July 24, 2013 5:26:26 PM UTC-4, Forrie wrote:
>
> Since upgrading to 3.x I've had some problems running Puppet under 
> Passenger.   I've spent several /days/ debugging this.
>
> The first symptoms included a new agent could not get a CA cert from the 
> Puppet Master.   I checked my configs, permissions, etc.
>
> When I run puppet master in stand-alone mode, it works fine.  
>
> I wrote to the Phusion Passenger folks, but they are not familiar with 
> Puppet and so I'm still trying to figure out what is wrong. 
>
> We don't have selinux enabled.  "sestatus" confirms this.
>
> SELinux status: disabled
>
>
> Of the errors I see in the puppet logs relevant to this:
>
> puppet.log:Jul 24 14:51:19 central puppet-master[30657]: Could not prepare 
> for execution: Got 3 failure(s) while initializing: Could not set 'file' on 
> ensure:
>  Permission denied - /var/log/puppet/masterhttp.log; Could not set 'file' 
> on ensure: Permission denied - /var/log/puppet/masterhttp.log
> puppet.log:Jul 24 14:51:19 central puppet-master[30657]: Wrapped exception:
> puppet.log:Jul 24 14:51:19 central puppet-master[30657]: Permission denied 
> - /var/log/puppet/masterhttp.log; change from absent to file failed: Could 
> not set
> 'file' on ensure: Permission denied - /var/log/puppet/masterhttp.log
>
> I tried setting the "ownership" of the files in that directory to the same 
> as the apache User, no difference.   Again, under regular Puppet there's no 
> problem.
>
> This is all I have in my config.ru:
>
> $0 = "master"
> ARGV << "--rack"
> ARGV << "--confdir" << "/etc/puppet"
> ARGV << "--vardir"  << "/var/lib/puppet"
> require 'puppet/util/command_line'
> run Puppet::Util::CommandLine.new.execute
>
>
> More logs:
>
> Jul 24 14:51:14 de-prod-archive puppet-agent[28391]: #011#011 id="site_header">
> Jul 24 14:51:14 de-prod-archive puppet-agent[28391]: #011#011#011 class="corporate_identity">
> Jul 24 14:51:14 de-prod-archive puppet-agent[28391]: #011#011#011#011 class="logo">https://www.phusionpassenger.com"; 
> >Phusion
> Passenger
> Jul 24 14:51:14 de-prod-archive puppet-agent[28391]: #011#011#011
> Jul 24 14:51:14 de-prod-archive puppet-agent[28391]: #011#011
> Jul 24 14:51:14 de-prod-archive puppet-agent[28391]: #011#011 id="site_body">
> Jul 24 14:51:14 de-prod-archive puppet-agent[28391]: #011#011#011 class="error_title">Web application could not be started
> Jul 24 14:51:14 de-prod-archive puppet-agent[28391]: #011#011#011 id="content">
> Jul 24 14:51:14 de-prod-archive puppet-agent[28391]:
> #011#011#011#011exit (SystemExit)
> Jul 24 14:51:14 de-prod-archive puppet-agent[28391]:
> /usr/local/lib/ruby/gems/1.8/gems/puppet-3.2.3/lib/puppet/util.rb:518:in
> `exit'
> Jul 24 14:51:14 de-prod-archive puppet-agent[28391]:
> /usr/local/lib/ruby/gems/1.8/gems/puppet-3.2.3/lib/puppet/util.rb:518:in
> `exit_on_fail'
> Jul 24 14:51:14 de-prod-archive puppet-agent[28391]:
> /usr/local/lib/ruby/gems/1.8/gems/puppet-3.2.3/lib/puppet/application.rb:362:in
> `run'
> Jul 24 14:51:14 de-prod-archive puppet-agent[28391]:
> /usr/local/lib/ruby/gems/1.8/gems/puppet-3.2.3/lib/puppet/util/command_line.rb:132:in
> `run'
>
>
>
> It spits out a lot of HTML, CSS... and things I don't think should ever 
> happen, on the client side.
>
>
> Looks like it it exiting, mentioning line 518 of 
> /usr/local/lib/ruby/gems/1.8/gems/puppet-3.2.3/lib/puppet/util.rb, the code 
> of which 
>
> is:
>
>
>   # Now we need to catch **any** other kind of exception, because we may 
> be calling third-party
>   #  code (e.g. webrick), and we have no idea what they might throw.
>   rescue Exception => err
> ## NOTE: when debugging spec failures, these two lines can be very 
> useful
> #puts err.inspect
> #puts Puppet::Util.pretty_backtrace(err.backtrace)
> Puppet.log_exception(err, "Could not #{message}: #{err}")
> Puppet::Util::Log.force_flushqueue()
> exit(code)
>   end
>
>
> Anyway, I'm pretty stumped.   I am running Puppet 3.x on its own now.  We 
> only have 40 nodes, so it works.   Bu

Re: [Puppet Users] How can I read registry values?

[Rob Reynolds]

There is the registry module (
http://forge.puppetlabs.com/puppetlabs/registry) although it doesn't appear
to let you read a value in the registry.

--
Rob Reynolds
Developer, Puppet Labs

*Join us at PuppetConf 2013, August 22-23 in San Francisco - *
http://bit.ly/pupconf13*
**Register now and take advantage of the Final Countdown discount - save
15%!*


On Thu, Jul 25, 2013 at 10:04 AM, tinu  wrote:

> I should read the values of some registry keys like
> 'HKLM\SOFTWARE\Puppet\WCM\Initial_Setup'.
>
> How can I do this?
>
> Thanx
>
> Tinu
>
> --
> 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.

[Puppet Users] Re: node_aws installation problem

[shivaraj mathrubai]

I just installed the enterprise version and it installed all the 
dependencies required and works like a charm !

On Wednesday, 24 July 2013 16:15:17 UTC+1, Piotr Jasiulewicz wrote:
>
> Hi,
>
> found some of your entries looking around Shivaraj, have you found out 
> the cause of this issue on your CentOS intallation?
>
> Thanks,
> Piotr
>
> W dniu środa, 24 lipca 2013 12:19:37 UTC+1 użytkownik Piotr Jasiulewicz 
> napisał:
>>
>> Hi,
>>
>> tried to play around with the RUBYLIB env var but doesn't seam to help in 
>> any way. 
>>
>> Any ideas?
>>
>> Thanks,
>> Piotr
>>
>> W dniu wtorek, 23 lipca 2013 17:10:55 UTC+1 użytkownik Piotr Jasiulewicz 
>> napisał:
>>>
>>> Hi,
>>>
>>> got the whole list
>>>
>>> root@ip-10-55-86-66:/home/ubuntu# gem list
>>>
>>> *** LOCAL GEMS ***
>>>
>>> builder (3.2.2)
>>> excon (0.25.3)
>>> fog (1.14.0)
>>> formatador (0.2.4)
>>> guid (0.1.1)
>>> mime-types (1.23)
>>> mini_portile (0.5.1)
>>> minitest (1.6.0)
>>> multi_json (1.7.7)
>>> net-scp (1.1.2)
>>> net-ssh (2.6.8)
>>> nokogiri (1.6.0)
>>> rake (0.8.7)
>>> rdoc (2.5.8)
>>> ruby-hmac (0.4.0)
>>>
>>> just got the newest one...
>>>
>>> Cheers,
>>> Piotr
>>>
>>> W dniu wtorek, 23 lipca 2013 17:09:04 UTC+1 użytkownik shivaraj 
>>> mathrubai napisał:

 What is the version of Fog you have ? 

 When you do "Puppet Help" do you see an exclamation mark next to 
 node_aws ?

 On Tuesday, 23 July 2013 16:16:19 UTC+1, Piotr Jasiulewicz wrote:
>
> Hi,
>
> yeap, it;s installed allright:
>
> root@X:/home/ubuntu# gem install guid
> Successfully installed guid-0.1.1
> 1 gem installed
> Installing ri documentation for guid-0.1.1...
> Installing RDoc documentation for guid-0.1.1...
>
> getting this every time, not sure if that's correct.
>
> Maybe the version is wrong?
>
>
> cheers,
> Piotr
>
>
> W dniu wtorek, 23 lipca 2013 16:11:20 UTC+1 użytkownik shivaraj 
> mathrubai napisał:
>>
>> Did you install guid ?
>>
>> On Tuesday, 23 July 2013 11:03:14 UTC+1, Piotr Jasiulewicz wrote:
>>>
>>> Hi everyone!
>>>
>>>
>>> having a slight problem with the installing the cloud provisioning 
>>> module
>>> [code]
>>> http://docs.puppetlabs.com/guides/cloud_pack_getting_started.html
>>> [/code]
>>> everything worked until I wanted to actually try to fire it up:
>>>
>>> [code]
>>> >puppet node_aws list
>>> Error: Could not autoload puppet/face/node_aws/fingerprint: cannot 
>>> load such file -- guid
>>> Error: Could not parse application options: Could not autoload 
>>> puppet/face/node_aws/fingerprint: cannot load such file -- guid
>>> [/code]
>>>
>>> I have fog configured with my AWS credentials but it seams like the 
>>> installation is just faulty, anyone any clue?
>>>
>>>
>>> Thanks,
>>> Piotr
>>>
>>

-- 
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] How can I read registry values?

[tinu]

I should read the values of some registry keys like 
'HKLM\SOFTWARE\Puppet\WCM\Initial_Setup'.

How can I do this?

Thanx

Tinu

-- 
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: Not collecting exported resources without storeconfigs

[Ken Barber]

Can you post your _full_ puppet.conf? Also - what version of PuppetDB
are you running, and do you have the puppetdb-terminus package
installed on your master? I don't think this is the issue - just
checking.

Also - Stupid question, but you obviously restarted
puppet/apache/whatever after making the changes to puppet.conf right?
I don't mean to insult, but you'll be amazed how often people forget
that :-).

On Thu, Jul 25, 2013 at 3:58 PM, Larry Long  wrote:
> I really don't want to go back to ActiveRecord... any ideas anyone?
>
>
> On Wednesday, July 24, 2013 11:57:17 PM UTC-4, Larry Long wrote:
>>
>> # cat /etc/redhat-release
>> CentOS release 6.4 (Final)
>> # puppet --version
>> 3.2.3
>> # rpm -q puppetdb
>> puppetdb-1.3.2-1.el6.noarch
>>
>> I am now receiving "Not collecting exported resources without
>> storeconfigs" for my opsview module. It was working fine on puppet 2.7 with
>> Activerecord/MySQL. I am still new to puppetdb so maybe I am missing
>> something. This is from puppet.conf:
>>
>> storeconfigs   = true
>> thin_storeconifgs = false
>> storeconfigs_backend = puppetdb
>>
>> Any ideas?
>>
>> Thanks,
>> -Larry
>
> --
> 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.

[Puppet Users] Re: Not collecting exported resources without storeconfigs

[Larry Long]

I really don't want to go back to ActiveRecord... any ideas anyone?

On Wednesday, July 24, 2013 11:57:17 PM UTC-4, Larry Long wrote:
>
> # cat /etc/redhat-release
> CentOS release 6.4 (Final)
> # puppet --version
> 3.2.3
> # rpm -q puppetdb
> puppetdb-1.3.2-1.el6.noarch
>
> I am now receiving "Not collecting exported resources without 
> storeconfigs" for my opsview module. It was working fine on puppet 2.7 with 
> Activerecord/MySQL. I am still new to puppetdb so maybe I am missing 
> something. This is from puppet.conf:
>
> storeconfigs   = true
> thin_storeconifgs = false
> storeconfigs_backend = puppetdb
>
> Any ideas?
>
> Thanks,
> -Larry
>

-- 
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] open source Puppet 3 cannot compile catalog on newly built Puppetmaster

[GregC]

Following the instructions from puppetlabs for yum install on Red Hat 6, no 
problems

When I try to run a puppet test I get the following error, there are no 
manifest on the system at this time.

[root@puppetmaster3:/etc/puppet/manifests]# puppet --version
3.2.3

[root@puppetmaster3:/etc/puppet/manifests]# puppet agent -tv --test
Info: Retrieving plugin
Error: Failed to apply catalog: undefined method `support_format?' for 
nil:NilClass

I never had this issue when building a 2.6 or 2.7 puppetmaster, anyone know 
how to resolve this?

-- 
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: Installing MSI failed with errror: The network name cannot be found.

[tinu]

Hello Josh

Thank you for your answers.

I changed the $msi_install_dir = '"C:\\Program Files\\System Center 
Operations Manager 2007"' to "C:\\Program Files\\System Center Operations 
Manager 2007",
and the $msi_logfile to 
"C:\\ProgramData\\PuppetLabs\\puppet\\var\\log\\$msi_package_name.log"

Result from *Run Puppet Agent*:

Running Puppet agent on demand ...
info: Retrieving plugin
info: Loading facts in 
C:/ProgramData/PuppetLabs/puppet/var/lib/facter/defaultgateway.rb
info: Loading facts in 
C:/ProgramData/PuppetLabs/puppet/var/lib/facter/networkadapters.rb
info: Caching catalog for webtest02.infra.be.ch
info: Applying configuration version '1374762832'
err: /Stage[main]/Services::Scomagent/Package[System Center Operations 
Manager 2007 R2 Agent]/ensure: change from absent to present failed: *Failed 
to install: The network name cannot be found.*
notice: Finished catalog run in 90.96 seconds
Press any key to continue . . .

In my node, I have already a declaration for this class as *class { 
'services::scomagent': } *and I can install this MSI with the *exec*.
*
*
We have the following puppet versions:
Puppetmaster = 2.7.18
Puppet Agent = 2.7.19

Any other ideas?

Tinu

-- 
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] Heria, Facts, and Puppet

[chengkai liang]

So something doesn't look right for me when running puppet apply -e 
'include ...' for looking heria via facter fact.

I have hiera configure as this,

:backends:
- yaml

:hierarchy:
- common 
- '%{env_name}'

:yaml:
:datadir: /var/lib/hiera/data

and, a file envXX.yaml store in the datadir, and I can run *hiera xyz 
env_name=envXX* to get the the value of abc associate with xyz.

Yet, if I export the value variable env_name by *export FACTER_env_name=*envXX, 
and run:

*puppet apply -e 'include my_module

*
puppet will complaint that it can't find data store in envXX.yaml.  From 
the debug output,

debug: importing 
'/Users/cliang/.puppet/modules/puppet_flux2_config/manifests/init.pp' in 
environment production
debug: Automatically imported puppet_flux2_config from puppet_flux2_config 
into production
debug: hiera(): Hiera YAML backend starting
debug: hiera(): Looking up host_header_url in YAML backend
debug: hiera(): Looking for data source common
Could not find data item host_header_url in any Hiera data file and no 
default supplied at 
/Users/cliang/.puppet/modules/puppet_flux2_config/manifests/init.pp:4 on 
node m-mba.local

It seems that it stop looking right after common, while running with *hiera 
xyz env_name=envXX* *--debug *shows,

DEBUG: Thu Jul 25 07:24:48 -0700 2013: Hiera YAML backend starting
DEBUG: Thu Jul 25 07:24:48 -0700 2013: Looking up host_header_url in YAML 
backend
DEBUG: Thu Jul 25 07:24:48 -0700 2013: Looking for data source common
DEBUG: Thu Jul 25 07:24:48 -0700 2013: Looking for data source *envXX*
DEBUG: Thu Jul 25 07:24:48 -0700 2013: Found xyz in *envXX*

So why puppet apply won't look further into envXX.yaml file?  Anybody can 
help on this?

-- 
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] including classes

[Matt]

Okay, I searched the group (duh!) and seen that this has been covered
multiple times already.


On 25 July 2013 08:14,  wrote:

>
> I've been rewriting our modules as and when to the more fashionable
> parameterised structure.  Running Puppet 3.x : our modules would look like
>
> node 'bigEndian' {
>   include app1::install, app2::install
> }
>
> class app1::install {
>   include/require nodejs
>   ...app stuff..
> }
>
> class app2::install {
>   include/require nodejs
>   ...app stuff..
> }
>
> rewriting them their more like:
>
> node 'bigEndian' {
>   include app1, app2
> }
>
> class app1 {
>   class { 'nodejs' : running => true }
>   ...app stuff..
> }
>
> class app2 {
> class { 'nodejs' : running => true }
>   ...app stuff..
> }
>
> This fails as class nodejs can't be called twice.  I understand the issue
> with this as it's paramerterised different values could be passed through
> in to the class.
>
> Interested to see how people are handling this? inheritance?
>
> Matt
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+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.

[Puppet Users] No reports in foreman

[Andreas Dvorak]

Dear all
 
I am trying to set up reports in foreman, but foreman tells me to configure 
it.
What am I doing wrong?
 
I have on the puppet master:
/var/lib/puppet/reports/foreman.rb
with $foreman_url=http://rh6-puppet-master
Do I need the port?
 
/etc/puppet/puppet.conf with in [main] reports = log, foreman
 
I restarted the service service puppetmaster restart
 
in /var/log/messages I find: No report named 'foreman'
 
On the puppet client I added the line report = true to the [agent] section 
in the /etc/puppet/config file.
 
Best regards
Andreas

-- 
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] including classes

[foomatty]

I've been rewriting our modules as and when to the more fashionable 
parameterised structure.  Running Puppet 3.x : our modules would look like

node 'bigEndian' { 
  include app1::install, app2::install
}

class app1::install {
  include/require nodejs
  ...app stuff..
}

class app2::install {
  include/require nodejs
  ...app stuff..
}

rewriting them their more like:

node 'bigEndian' { 
  include app1, app2
}

class app1 {
  class { 'nodejs' : running => true }
  ...app stuff..
}

class app2 {
class { 'nodejs' : running => true }
  ...app stuff..
}

This fails as class nodejs can't be called twice.  I understand the issue 
with this as it's paramerterised different values could be passed through 
in to the class.

Interested to see how people are handling this? inheritance?

Matt

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+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: Creating Users and Hashing it's password.

[Joey Stevense]

You could also use the built in sha1 function to let puppet generate the 
hashed version for you.
Like this:

user {'sysop': 
  #uid   => 500, 
 #groups  => 'admin', 
comment=> 'Sysop', 
ensure=> present, 
home  => '/home/sysop', 
shell   => '/bin/bash', 
managehome  => true, 
password=> sha1('plaintextpasswordhere'),
 } 

On Wednesday, June 8, 2011 9:08:36 PM UTC+2, vella1tj wrote:
>
> Hi everyone I would like to first of all say thanks to anyone willing 
> to help me. 
>
> I was tasked with creating a Admin account using puppet to push to all 
> of our Macs that we have deployed around the Campus. 
>
> user {'sysop': 
>   #uid   => 500, 
>  #groups  => 'admin', 
> comment=> 'Sysop', 
> ensure=> present, 
> home  => '/home/sysop', 
> shell   => '/bin/bash', 
> managehome  => true, 
> password=> 'Haven't figured out the best way to 
> hash 
> a password and put it in here., 
> } 
>
> That's what I have so far, I don't believe I understand how Hash works 
> completely. The way I understand it is it will have a hash in the 
> password field and it will compare it to other hashes to match what 
> the password would be. So what I was hoping to get help on (or 
> anything i've done wrong or you would recommend me doing different) is 
> how do i set a resource for the hash do i put it in my files directory 
> and then point it to there is there anything special I have to do 
> so puppet understands that it's hash.

-- 
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] File ownership wrong when using vcsrepo

[dusan . dordevic]

Hi,

I created few puppet modules that pulls some Ruby code from various repos. 
All modules are identical:

class  {
vcsrepo { '/var/hg/repos/':
ensure   => present,
provider => hg,
source   => 
'ssh://user@servername//var/hg/repos/.',
owner => 'clavis',
group => 'clavis',
revision => $DQreleaseversion,
}
}

where reponame is name of repository. Puppet pulls all of them properly 
from the server, but file privileges on file system are messed up. For some 
of repos, they are correct, they are owned by clavis, but for some other is 
not and files are owned by root. I tried this on few different servers and 
it seems it is random, I could not find any reason why ownership is wrong. 
All servers are Ubuntu 12.04 with ubuntu supplied Puppet updated to latest 
revision.

Any idea what might cause this ? Thanks in advance.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+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: puppetdb v2 node api

[Ken Barber]

You should be able to use 'curl' to access the API, there are some
examples for /v2/nodes in the docs as a start ... and the rest of the
end-points have similar examples:

http://docs.puppetlabs.com/puppetdb/1.3/api/query/v2/nodes.html

Also take a look at the general curl advice page:

http://docs.puppetlabs.com/puppetdb/1.3/api/query/curl.html

If you're having issues getting it working, provide the commands you
are trying in-thread so we can see it in detail. For example, this is
my results:

# curl -G -H "Accept: application/json" 'http://localhost:8080/v2/nodes'
[ {
  "name" : "puppetdb1.vm",
  "deactivated" : null,
  "catalog_timestamp" : "2013-07-22T12:20:07.945Z",
  "facts_timestamp" : "2013-07-22T12:15:46.434Z",
  "report_timestamp" : "2013-07-22T12:15:41.000Z"
} ]

ken.

On Thu, Jul 25, 2013 at 5:49 AM, watchman  wrote:
> Hey mate,
>
> It looks liek you got this "v2"  API working. How did you setup that?
> I spend so much time to get this working but no luck. Whenever I try the url
> I get 404 error in puppetdb log...
>
> If you could help me then that would be great!
>
> Thanks
> Watchman
>
>
> On Monday, April 22, 2013 1:09:08 PM UTC+10, hyde wrote:
>>
>> In puppetdb v2 node api, it changes behavior with "GET /v2/nodes", which
>> only returns active nodes now. In v1, it would return all nodes.
>>
>> So in puppetdb v2 node api, how is it possible to return all nodes (both
>> active and deactivated ones)?
>
> --
> 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.

[Puppet Users] Re: operatingsystemrelease fact on windows

[badgerious]

Luis,

This seems useful. I've never actually used any of the facts that return 
the numeric Windows version, but have used the named version (with my own 
fact). Since it looks like the numeric version is repeated in 3 facts, 
changing one to something else seems like a good move.

Eric

-- 
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: operatingsystemrelease fact on windows

[badgerious]

Luis,

This seems useful. I've never actually used any of the facts that return 
the numeric Windows version, but have used the named version (with my own 
fact). Since it looks like this piece of information is repeated in 3 
facts, changing one to someone else seems like a good move. 

Eric

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

[yannig rousseau]

Do you know if it's possible to lauch it from a script (maybe a sql request
?)

On Thu, Jul 25, 2013 at 2:17 PM, Klavs Klavsen  wrote:

> that job just removes reports for hosts - it does't remove the actual
>> hosts.
>
>
> You need to pick the node in puppet-dashboard webinterface - and choose
> delete (upper right corner)
>
> --
> 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/ZsjSJJWxeHk/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 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] puppetlabs-ntp template discussion

[Erik Dalén]

On 13 July 2013 15:00, Ashley Penney  wrote:

> On Sat, Jul 13, 2013 at 7:15 AM, Erik Dalén 
> wrote:
>
>> I've been missing a way to set which server(s) should be preferred. We
>> generally include all our NTP servers in the config but prefer the one that
>> is in the same site as the node in question.
>>
>> So for a machine in site1 it would look like:
>>
>> server ntp.site1.example.com prefer
>> server ntp.site2.example.com
>> server ntp.site3.example.com
>>
>
> I'll take a look at this but I have a sneaky suspicion if you just pass in
> servers => [ 'ntp.site1.example.com prefer', 'ntp.site2.example.com' ] it
> should magically do the right thing.  On monday I'll find that out and make
> it do the right thing if not.
>
> I guess what you're saying is it's a pain to modify the list per site?  In
> that case we can always add a prefer => 'blah' and have that append to the
> site you pick if that works.  I think what I'm saying is here is tell me
> the API you'd like most for that and we'll do it. :)
>
>
>
I think an extra parameter like $preferred_servers accepting an array of
servers would be a nice API for this. It can default to an empty array.

-- 
Erik Dalén

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

[Puppet Users] Re: How do I set global noop?

[Klavs Klavsen]

>
> well - perhaps you can put noop = true

or something in puppet.conf on the clients ? 

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

[Klavs Klavsen]

>
> that job just removes reports for hosts - it does't remove the actual 
> hosts.


You need to pick the node in puppet-dashboard webinterface - and choose 
delete (upper right corner) 

-- 
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: is there any way to see what are the resources exported by a node?

[Klavs Klavsen]

>
> would you mind sharing your solution - for the benefit of others who may 
>> find your question by googleing - and can't really find the answer in the 
>> irc conversation you had? :)
>>
>

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

[yannig rousseau]

Hi all,

I have a few nodes which have deen decommissioned but still appear within 
my dashboard within the ureported section. I probably have forgot something 
but what ?


My puppetmaster (rhel5.9) hosts the 3 roles :  puppet-server-3.2.2, 
puppetdb-1.1.1, puppet-dashboard-1.2.22

The process I use to decommission :
 - Clean the certificate on puppetmaster : *puppet cert clean "node.domain"*
 - Delete the node itself from puppetdb : *puppet node deactivate 
"node.domain"*
Concerning the dashboard, I use a pruning job in my crontab : *35 6 * * * 
/etc/puppet/maintenance/puppet-dashboard.cleanup_reports.cron*
The job itself : 
*set -u*

*find /var/lib/puppet/reports/*/ -mtime +7 -exec rm {} \;*

*PUPPET_DB_PATH=/usr/share/puppet-dashboard*
*cd $PUPPET_DB_PATH*
*output=`rake -s -f ${PUPPET_DB_PATH}/Rakefile RAILS_ENV=production 
reports:prune upto=1 unit=wk`*

*if [ $? -ne 0 ]; then*
*  logger -i "${output}"*
*fi*

*echo $output*

Regards
Yannig

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