[Puppet Users] template + sign and storedconfig = mysql -> Error 400

[Johan De Wit]

Hi,

Anyone experienced a simular issue ?

We have a template which is in fact a patch file, thus containing 
mutliple lines where the first character is a +

We use storedconfigs, at the moment mysql,
Thin_storeconfigs = false (default)

whenever we use this template in a file resource, we get following error :

err: Could not retrieve catalog from remote server: Error 400 on SERVER: 
syntax error on line 8, col 8: `+Summary: Samba vfs_gpfs module'


No matter what we do, like removing the file resource, this error is 
persistent with every puppet run on this node.


We had to do following steps ...

on the master in the config ...   thin_storeconfigs = true on the master
on the master : puppet node clean 
rm -rf /etc/puppet/ssl on the node

Then all is working again.

Just curious if someone encountered something simular

puppet version 2.7.20
OS on node : thel 6.4

expert of the template :
--- samba_orig.spec2013-09-09 08:36:58.810502410 +0200
+++ samba.spec2013-09-09 10:56:23.694946448 +0200
@@ -95,6 +96,25 @@
 Samba uses NetBIOS over TCP/IP (NetBT) protocols and does NOT
 need the NetBEUI (Microsoft Raw NetBIOS frame) protocol.

+%define gpfs_version <%= @gpfs_version %>-<%= @gpfs_update %>
+%package vfs_gpfs-%{gpfs_version}
+Summary: Samba vfs_gpfs module
+Group: Applications/System
+Requires : gpfs.base = %{gpfs_version}
+BuildRequires: gpfs.base = %{gpfs_version}
+
+%description vfs_gpfs-%{gpfs_version}
+

Grts

Jo

--
Johan De Wit

Open Source Consultant

Red Hat Certified Engineer (805008667232363)
Puppet Certified Professional 2013 (PCP006)
_
 
Open-Future Phone +32 (0)2/255 70 70

Zavelstraat 72  Fax   +32 (0)2/255 70 71
3071 KORTENBERG Mobile+32 (0)474/42 40 73
BELGIUM http://www.open-future.be
_
 


Next Events:
Puppet Advanced Training: 10th till 12th of September 2013 | 
https://www.open-future.be/puppet-advanced-training-10-till-12th-september
Zabbix Certified Training: 23th till 25th of September 2013 | 
https://www.open-future.be/zabbix-certified-training-23-till-25th-september
Zabbix Large Environments Training: 26th till 27th of September 2013 | 
https://www.open-future.be/zabbix-large-environments-training-26-till-27th-september
Subscribe to our newsletter | http://eepurl.com/BUG8H
Puppet Exam Rebate:
25% off a Puppet Certification Exam! Use code PU2511852A67 | 
http://bit.ly/Sv3tQa

--
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] Puppet Master fails when dashboard is unreachable

[Chris Lee]

I would like to know if anyone has seen this before or has any suggestions.

After a power cut recently we were bringing our farm back on line, and our 
dashboard server (separate to our puppet master) was not online yet as 
reporting at this point was not considered critical. 
However, we noticed that none of our critical machines completed their 
puppet runs. It appears to us that puppet freezes when its unable to get a 
response back from the dashboard, and never times out.

As soon as we brought the dashboard back online everything started working 
again.

Cheers
Chris

-- 
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] vcsrepo: "Error 400 on Server: Invalid parameter provider"

[milesnpeebles]

With custom type 'vcsrepo', I've been getting this error ever since I 
restarted my master box:

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
Invalid parameter provider at 
/etc/puppet/environments/local/modules/user_mpeebles/manifests/init.pp:56 
on node 1001.milespeebles.org
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

---

This is the definition found at line 56:

vcsrepo { '/home/mpeebles/.vim' :
 ensure  => latest,
 user=> mpeebles,
 owner   => mpeebles,
 group   => users,
 provider=> 'git',
 source  => 'https://github.com/mpeebles/vim-config.git',
 revision=> 'master',
}

---

Researching this issue myself, I I have tried adding 'pluginsync = true' 
under '[main]' in /etc/puppet/puppet.conf, to no avail. Not really sure 
what's wrong.

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

Re: [Puppet Users] Puppet Master fails when dashboard is unreachable

[Marcus Franke]

Hi,
I guess the puppetdb is running on the dashboard server aswell? I think the
storeconfigs/exported ressources will fail with the database unavailable.

Marcus

-- 
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] puppetdb query not working as expected

[hai wu]

Running puppet only at around 4am once a day here. And I noticed that
puppetdb query not working as expected, if using it to query nodes based on
some custom fact value.

During the days, things are working fine. But if I ran the same query at
around say 3am (searching nodes based on some custom fact's value), then it
would not be able to return node information. But if I ran puppet on that
node at that time, then I could see the node showing up in the query output
right away. And if I ran puppetdb query based on custom fact after 5am,
then it is working as expected.

Is there some configuration settings control this behavior? This does not
occur for facter's built-in facts though.

Thanks,
Hai

-- 
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] Setting up PE from scratch with PuppetDB/Postgres on separate box

[Steven James]

Hi All,

I'm trying to setup a new Pupp Ent instance from scratch with 
PuppetDB/Postgres on a sep box. I think I have it working, but it took a 
bit of doing. I just wanted to check that there's not a more straight 
forward way.

I'm aiming for an HA proxy load balanced pair of PuppetMasters, CA active 
on only one, with replicated pair of PuppetDB/Postgres.

First of all...the assumptions.it seems that it not possible to install 
the console role (on the PM) without also installing PuppetDB (with option 
to connect to remote PG server). I was imagining that my PuppetDB jetty 
containers would both sit happily only on the 2 database servers, and not 
be required on the PM?? I was imagining that 
/etc/puppetlabs/puppet/puppetdb.conf on the PMs would "simply" point down 
to the active PG PuppetDB instance?? False assumption?

The next question I just wanted to validatethe only way I could get the 
installer to play nice, was to install the DB layer first, with it 
continuing on not having a PM to point at yet, then loading up the PM, 
*having* to say Yes to the PuppetDB option, in order to get a console on 
the PM, then specifying a remote PG database server.

If one does have to install the DB first, then maybe the following link 
needs to be updated?

http://docs.puppetlabs.com/pe/latest/install_system_requirements.html

Then had to remove DB server's ssl dir, regenerate and sign the request on 
the PM (CA), then run puppetdb-ssl-setup to finish off.

So I've ended up with PuppetDB running on both my PM *and* of course on my 
DB. I feel like I should be doing a `service pe-puppetdb stop` on the PM.

There didn't seem to be any prebaked examples/answers files that 
accommodated this (reasonably std) architecture?? Lots of other great 
examples though.

Is my setup the correct way to go about this???

The next stage will be to use the same answers file from PM1 on PM2, 
disabling the ca_server, and assuring that my dns_alt_names have both the 
puppet service address, and the addresses of both of the PMs.

There seems to be a patch required to allow PuppetDB to drive a replicated 
Postgres pair via Puppet Enterprise itself. Nice that this is now possible!

One last questionand assuming I can run PuppetDB on both Postgres 
servers, with both pointing at the active PG box..I'm also assuming 
that I should also be configuring HAProxy to load balance requests to both 
PuppetDB instances?? i.e. load balance the SSL connects over 8081??  If so, 
I'm smelling some SSL challenges ahead.anybody got any thoughts on that 
one? If both PuppetDB instances are signed against the primary CA, should 
all else be fine?

Thanks for your input, and I'm happy to post updates if anybody has any 
suggestions.

Steven

-- 
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: Ordering and templates question/issue

[jcbollinger]

On Monday, September 9, 2013 6:13:46 PM UTC-5, sjr wrote:
>
> Hi,
>
> I've been doing some tests with some internal methods just to mess a 
> little and learn a bit about puppet internals but found myself in a 
> situation which I don't really understand and I was hoping someone around 
> could help me to get it.
>
> I have a test module with the following init.pp:
>
> class test1 
> { 
>   
>
>
>   file 
> {'/tmp/test1':
>   
> 
>
> content => 
> template('test1/test1.erb'),  
>   
> 
>
>   
> } 
>   
>  
>
>   
>   
>
>
>   Test1::Print <| |> -> 
> File['/tmp/test1']
>   
>
>
> }
>
> The define test1::print looks like:
>
> define test1::print 
> ( 
>   
>
>
>   
> $message  
>   
>  
>
> ) 
> { 
>   
>  
>
>   notify{$message: 
> } 
>   
> 
>
> }
>
> So nothing really special, then in the template I try to catch all the 
> resources in the catalog with "scope.catalog.resources" method, nothing I 
> came up with by myself I saw it in a module and thought it was a neat trick 
> and wanted to try it and learn what else I could do with this kind of stuff.
>
> The problem I'm having is that the template seems to be "compiled" before 
> all the resources are in the catalog as the file only contains the 
> following list of resources:
>
> Stage[main]
> Class[Settings]
> Class[main]
> Node[default]
> Class[Test1]
>
> In puppet's output, the relationships seem to be well defined but feels 
> like puppet is somehow applying (catching?) the template even before 
> creating the actual file.
>
> The template has the following content:
>
> <% @test = scope.catalog.resources.select { |r| r.type } -%>
> <% @test.each do |t| -%>
> <%= t %>
> <% end %>
>
> Am I missing anything? I expected to see in the file the defined type 
> test1::print...
>
>
You are missing several things, including at least

   1. Puppet relationships, such as are declared via the arrow operators or 
   'require' and 'before' metaparameters, influence only the order in which 
   resources are applied by the agent.  They have no bearing on the order of 
   events during catalog compilation.
   2. Defined types are *types*, not resources.  They are thoroughly 
   analogous to native resource types such as File.  You could see *
   instances* of defined types among your catalog resources if you declared 
   any (you didn't), but you will not see the defined types themselves.
   3. scope.catalog.resources is an awful hack, not a "neat trick", because 
   it is sensitive to when during the compilation process the template is 
   evaluated.  To build robust and reliable classes and modules you must avoid 
   depending on mechanisms that are sensitive to evaluation order (sometimes 
   inaccurately called "parse order", including by me).


John

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

[Puppet Users] Re: Ordering and templates question/issue

[sjr]

Hi John,

thanks for your answer, first of all I must say I just wanted to experiment 
and learn, it's not like I'm going to put such "awful hacks" :-) in 
productionmostly because I guess it's easy they can be changed over the 
time as they are not part of puppet DSL and so, it can be harder to 
maintain and for other colleagues to understand.

OK, now to the point...I forgot to include the node definition, sorry about 
that, it looks like:

node hostname {
  class {'test1': }
  test1::print {'test11':
message => 'test11',
  }
  test1::print {'test12':
message => 'test13',
  }
  test1::print {'test13':
message => 'test13',
  }

So I understand that when you say I haven't defined any resource it's 
because I forgot to mention that part, right? If so, why the define types 
are not showing up in the file? Also, as you can see in the content of the 
file I included in my previous message, Class[test1] was declared and 
showed in the content of the file, but the File resource itself was not 
there when the template was built.

I have the feeling the template is evaluated before all this resources are 
present in the catalog...am I wrong? Is that expected behavior?


Thanks.
Sergio.

On Tuesday, September 10, 2013 3:23:47 PM UTC+2, jcbollinger wrote:
>
>
>
> On Monday, September 9, 2013 6:13:46 PM UTC-5, sjr wrote:
>>
>> Hi,
>>
>> I've been doing some tests with some internal methods just to mess a 
>> little and learn a bit about puppet internals but found myself in a 
>> situation which I don't really understand and I was hoping someone around 
>> could help me to get it.
>>
>> I have a test module with the following init.pp:
>>
>> class test1 
>> {
>>  
>>  
>>
>>   file 
>> {'/tmp/test1':   
>>  
>>   
>>
>> content => 
>> template('test1/test1.erb'), 
>>  
>>   
>>
>>   
>> }
>>  
>>
>>
>>  
>>  
>>  
>>
>>   Test1::Print <| |> -> 
>> File['/tmp/test1']   
>>  
>>  
>>
>> }
>>
>> The define test1::print looks like:
>>
>> define test1::print 
>> (
>>  
>>  
>>
>>   
>> $message 
>>  
>>
>>
>> ) 
>> {
>>  
>>
>>
>>   notify{$message: 
>> }
>>  
>>   
>>
>> }
>>
>> So nothing really special, then in the template I try to catch all the 
>> resources in the catalog with "scope.catalog.resources" method, nothing I 
>> came up with by myself I saw it in a module and thought it was a neat trick 
>> and wanted to try it and learn what else I could do with this kind of stuff.
>>
>> The problem I'm having is that the template seems to be "compiled" before 
>> all the resources are in the catalog as the file only contains the 
>> following list of resources:
>>
>> Stage[main]
>> Class[Settings]
>> Class[main]
>> Node[default]
>> Class[Test1]
>>
>> In puppet's output, the relationships seem to be well defined but feels 
>> like puppet is somehow applying (catching?) the template even before 
>> creating the actual file.
>>
>> The template has the following content:
>>
>> <% @test = scope.catalog.resources.select { |r| r.type } -%>
>> <% @test.each do |t| -%>
>> <%= t %>
>> <% end %>
>>
>> Am I missing anything? I expected to see in the file the defined type 
>> test1::print...
>>
>>
> You are missing several things, including at least
>
>1. Puppet relationships, such as are declared via the arrow operators 
>or 'requ

[Puppet Users] Re: Puppet Master fails when dashboard is unreachable

[Chris Lee]

Hi Marcus

We aren't running PuppetDB, so hoping that shouldn't effect anything?

Chris

-- 
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: Importing declarations into node/class scope

[jcbollinger]

On Monday, September 9, 2013 2:17:48 PM UTC-5, Stepan Seycek wrote:
>
>  Hi John,
>
> Am 09.09.2013 15:39, schrieb jcbollinger:
>  
>
>
> On Monday, September 9, 2013 1:52:43 AM UTC-5, Stepan Seycek wrote: 
>>
>>  Hi John,
>>
>>  thanks for your reply. Unfortunately that does not solve my actual 
>> problem. I want to avoid maintaining multiple vhost entries inside one file.
>>  
>
>
> My suggestion accomplishes that.  Following Puppet best practices and 
> autoloader requirements, each vhost class would go into a separate file.
>
>  
>
>>  Instead I want to be able to add a vhost by simply adding one file 
>> dedicated to that vhost to a directory.
>>  
>
>
> You didn't say the part before.
>
>  
>
>>  This would allow me to easily integrate puppet with a tool that rolls 
>> out whole application stacks including the vhosts.
>>
>>   
> It can be done -- with 'import', even -- but most of the options for such 
> a setup are poor practice.  To suggest a good alternative, I would like to 
> better understand your planned usage.  Will you be using Puppet in agent / 
> master mode, or standalone mode?  Are you looking for one-time deployment, 
> or continuing vhost management?  Will you ever have to support multiple 
> servers with different vhosts?  With overlapping vhosts?  Do you need to 
> provide for removing unwanted vhosts?  Would it be an unacceptable burden 
> to run a second tool after the one that produces the vhost information, 
> before it is ready for Puppet?
>
>   
> Puppet runs in master/agent mode.
>


Ok.

 

> Puppet shall be used for continuous vhost management.
>


Ok.

 

> There will be multiple servers providing reverse proxy services with 
> apache httpd vhosts (different vhosts on different servers).
>


Ok.

So the master will support multiple distinct clients hosting httpd servers, 
each with its own set of vhosts.

 

> Removal of vhosts is definitely a requirement for the undeployment of an 
> application stack.
>


I think you will find that the requirement for removing vhosts torpedoes 
your plan for controlling which vhosts are declared by only adding or 
removing definition files from some directory.  Although Puppet does have a 
mechanism for purging unmanaged resources of some types from the target 
node, it depends on being able to enumerate all the instances present 
there, and I would be surprised if your vhost type had that ability.  If 
it's a defined type (as opposed to a custom native type) then it surely 
doesn't.

 

> An additional tool processing the configuration for puppet is no problem.
>
> I know I could maintain the information about active vhosts in my roll-out 
> tool and when submitting to puppet generate a class file that would contain 
> all active vhost declarations and would declare removals for those that 
> have been active before and are not among the active ones any more. 
> However, as mentioned before, I would prefer to generate a file for every 
> to-be-added vhost and every to-be-removed vhost.
>
>

What about managing the vhosts that are already present and intended to 
stay?  Your desired approach is not very consistent with Puppet's general 
architecture.  Puppet is a state management tool, so its native usage 
paradigm involves you modeling the target *state* you want, and letting 
Puppet figure out what, if anything it needs to do to put the target 
machine into that state.  With to-be-added and to-be-removed lists, you 
focus on the exact dual of Puppet's native paradigm: you emphasize the 
transitions between states and leave implicit the details of the desired 
state.  Especially, you leave unmanaged those vhosts that already exist and 
don't need to be removed.  You can use Puppet that way, but it will be 
harder.

Perhaps a good compromise would be to let your roll-out tool perform 
transition-based changes on your manifest set (so it doesn't need to 
maintain overall state), and use a post-processor to prepare Puppet 
declarations from the result that capture the overall target state.  For 
example, when you add a vhost to a given server, your roll-out tool drops a 
vhost-specific class definition file in an appropriate directory, and when 
you remove one it does the same, overwriting any previous file for that 
vhost.  Importantly, the tool otherwise avoids removing any of the files it 
previously dropped -- those are your persistent record of the target 
state.  Thus, you might have

modules/proxies/manifests/server1/vhost1.pp
modules/proxies/manifests/server1/vhost2.pp
...

where modules/proxies/manifests/server1/vhost1.pp contains a class 
declaring vhost1 (possibly ensuring it absent):

class proxies::server1::vhost1 {
  include 'apache'
  apache::vhost { 's1_vhost1':
ensure => 'present', # or 'absent'
# ...
  }
}

After you run the roll-out tool or otherwise modify the vhosts, you run a 
second tool that scans the contents of the per-server directories and 
creates a class declaring all the vhost classes.  For example

[Puppet Users] Re: Puppet calls the ENC twice for some nodes.

[jcbollinger]

On Monday, September 9, 2013 6:26:26 AM UTC-5, pierra mathieu wrote:
>
> Hi everyone, 
>
> I have an issue setting up Puppet with an ENC.
> For some nodes, puppet calls my ENC twice with a 2 sec interval.
>
> All my agents share the same configuration file. 
>
>
> Considering this very basic ENC : 
>
> #!/bin/bash
>> nodeName=$1
>> echo `date` $nodeName >> /tmp/encCalls
>> echo "---
>> classes:
>>   testClass:"
>
>
>
> Here is the content of /tmp/encCalls after a few run on two nodes.
>
> Mon Sep  9 11:36:15 CEST 2013 : host1
>> Mon Sep  9 11:36:17 CEST 2013 : host1
>> Mon Sep  9 11:41:04 CEST 2013 : host2
>> Mon Sep  9 11:42:04 CEST 2013 : host1
>> Mon Sep  9 11:42:06 CEST 2013 : host1
>> Mon Sep  9 11:45:13 CEST 2013 : host2
>
>
>
> Anybody knows why two calls are made ?
>
>

My first guess would be that you have two copies of the agent running on 
some nodes.  If your manifest set is as simple as your ENC, then the Puppet 
agent could perform a full cycle fast enough that two separate catalog 
requests from the same node are received within 2 seconds.


John

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

[Puppet Users] Regarding puppet server + foreman + passenger + Mcollective + RabbitQ setup guide with latesh centos OS

[shyam sundar Keshari]

Hi Team,

Kindly guide me to setup puppet server + foreman + passenger + Mcollective
+ RabbitQ on cenots Latest OS with latest version of Puppet and all other
components.

Does anyone has any script for this which install all at once .

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: Incorrect return code for failed exec

[Igor Berger]

Should log an issue about this someplace?


On Tuesday, September 3, 2013 10:56:01 AM UTC-4, Igor Berger wrote:
>
> It returns 1053. The "sc start" command prints:
>
> [SC] StartService FAILED 1053: The service did not respond to the 
> start or control request in a timely fashion.
>
> You can easily reproduce it by registering a service with a non-existing 
> executable:
>
> sc create MyService binPath= C:\NotThere.exe
>
> Then add this to a test.cmd file:
>
> sc start MyService
> echo %errorlevel%
>
>
> On Tuesday, September 3, 2013 10:34:32 AM UTC-4, Rob Reynolds wrote:
>>
>> What does "cmd /c sc start MyService" return?
>>
>>
>> On Tue, Sep 3, 2013 at 9:23 AM, Igor Berger  wrote:
>>
>>> As I mentioned, I'm running into this issue when the service fails to 
>>> start.
>>> "sc start" returns a failure, Puppet mentions it in the log file.
>>>
>>> The problem is that "puppet apply" returns 0 (success) to the shell when 
>>> "sc start" fails.
>>> However, "puppet apply --detailed-exitcodes" returns a failure to the 
>>> shell correctly.
>>>
>>>
>>>
>>> On Monday, September 2, 2013 1:51:31 AM UTC-4, Rahul Khengare wrote:

 Hi Igor,
You can run "sc start MyService" command manually on your machine 
 and check whether the service run correctly. Also check the environment 
 parameters are set for that service.
 Can you explain your query in more detail manner.  

 Thanks and Regards,
 Rahul Khengare,
 NTT DATA OSS Center, Pune, India.


 On Saturday, August 31, 2013 3:20:54 AM UTC+5:30, Igor Berger wrote:
>
> Hello,
>
> I'm running puppet agent standalone on Windows.
>
> The last step in the manifest is "exec { 'start_service': command => 
> "sc start MyService" }".
>
> When the service has a problem and doesn't start, Puppet logs:
>
> /Stage[main]//Exec[start_**service]/returns (err): change from notrun 
> to 0 failed: sc start MyService returned 29 instead of one of [0]
>
> However, the %errorlevel% returned is still 0.
>
> However, if I use "--detailed-exitcodes", the %errorlevel% is 
> correctly set to 6.
>
> Regards,
> Igor.
>
>  -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Puppet Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to puppet-users...@googlegroups.com.
>>> To post to this group, send email to puppet...@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/puppet-users.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>
>>
>>
>> -- 
>> Rob Reynolds
>> Developer, Puppet Labs
>>
>> Join us at PuppetConf 2014, September 23-24 in San Francisco
>>  
>

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

[Puppet Users] Re: Use of defined()

[jcbollinger]

On Monday, September 9, 2013 10:44:30 AM UTC-5, blalor wrote:
>
> As my previous email this morning probably indicated, I'm struggling with 
> the use of the defined( ) function.  The 
> documentation
>  says 
> its operation is parse-order dependent; I'm trying to figure out how it's 
> usable at all.
>


It isn't.  Do not use it.

 

>  Since resource order with Puppet is nondeterministic (without explicitly 
> using chaining arrows or before/after),
>


'before', 'after', and chaining do not enter the picture.  They affect only 
the order in which resources are applied to the target, but what you need 
to worry about is the order in which declarations are evaluated during 
catalog compilation.

 

> how can I reliably test for the presence of a resource, like a package?
>


You should not test for the presence of a resource in the catalog.  You can 
use a custom fact to test for the presence of a resource on the target 
system, or you can design your manifest set so that you know whether a 
particular resource is supposed to be declared (even if the declaration has 
not yet been evaluated), but you should avoid testing the current state of 
the catalog.  Testing current catalog state during compilation is 
inherently evaluation-order dependent.

 

>  I see lots of instances of 
>
> if ! defined(Package['some-package']) { … }
>
>

Alas, the computing world is awash in poor code.  Its prevalence should not 
be taken as an indication of quality.

 

> in other peoples' code.  Maybe I'm not understanding what's meant by 
> "parse order", however.  Could someone explain?
>
>

"Parse order" is actually a bit of a misnomer, of which I am as guilty as 
anybody.  I'm trying to shift my personal usage to the term "evaluation 
order", though the difference is probably of little significance to most 
Puppet users.

The particular example you present seems to be a relatively common 
anti-pattern.  It attempts to address the problem that a particular class 
depends on a given package being present on the target system, but is 
uncertain whether that package is managed by another class.  It wants to 
declare the class if it is not managed by someone else, therefore it uses 
defined() to test for a declaration already present in the catalog.

That approach suffers from an insidious problem: it can subvert more 
specific, or even conflicting, declarations elsewhere in the manifest set 
without notification.  Worse, it may flip back and forth between doing so 
and not as the manifest set changes.  And that's not all.  The approach 
works reliably (in that catalog compilation succeeds) only if *all*declarations 
of the resource are guarded the same way.  If even one is not 
guarded, then whether catalog compilation succeeds or fails is 
evaluation-order dependent.

One alternative is to provide a virtual declaration of the relevant 
resource in some central class that is reliably included in the catalog, 
and have those classes that need the resource realize it (or collect it) 
instead of declaring it themselves.  Alternatively, a central class can 
provide a concrete declaration of the desired resource, and other classes 
that want the resource can 'include' the declaring class.

The main objections to any of these approaches involve modularity and 
module compatibility.  You would like to be able to use third-party modules 
without modifying them, and you would like your modules to avoid 
conflicting with each other.  Additionally, you would prefer for your 
modules to be self-contained, or at least to be insensitive to declarations 
elsewhere in your manifest set.  Unfortunately, *none* of the approaches 
above adequately address all those issues.  This is a longstanding issue in 
Puppet, and although we have discussed possible approaches, no good 
solution has made it into the product yet.


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] Where does the puppet master get its hostname

[Nathan Valentine]

Check both of the following: /etc/hosts and /etc/sysconfig/network.

-- 
---
Nathan Valentine - nat...@puppetlabs.com
Puppet Labs Professional Services
GV: 415.504.2173
Skype: nrvale0

-- 
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] Where does the puppet master get its hostname

[Greg Coit]

Hi all,

I have a new puppet server named grover.example.com.  I've set both 
the server and certname to grover.example.com in /etc/puppet/puppet.conf 
(this is CentOS 6.4).  I've also verified the hostname:

hostname:
grover.example.com

However, when I start puppetmaster, it always created a cert named grover 
and *not* grover.example.com:

puppet master --no-daemonize --verbose:
Info: Creating a new SSL key for grover
Info: Creating a new SSL certificate request for grover
Info: Certificate Request fingerprint (SHA256): 
07:04:47:E0:F5:26:7A:B3:29:83:12:72:09:E0:45:9F:17:9F:E1:57:DC:05:71:10:FE:31:47:5E:4F:47:38:8A
Notice: grover has a waiting certificate request
Notice: Signed certificate request for grover
Notice: Removing file Puppet::SSL::CertificateRequest grover at 
'/var/lib/puppet/ssl/ca/requests/grover.pem'
Notice: Removing file Puppet::SSL::CertificateRequest grover at 
'/var/lib/puppet/ssl/certificate_requests/grover.pem'
Notice: Starting Puppet master version 3.2.4

Using "puppet master --no-daemonize --verbose --server grover.example.com" 
makes no difference.

Any ideas how to fix this?

Thank you!!!

Greg

-- 
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] Where does the puppet master get its hostname

[Cory Stoker]

Puppet uses Facter to determine the FQDN.  I believe Facter uses a few
methods to try and figure out the domain part, namely:
hostname -f
dnsdomainname
parse out /etc/resolv.conf for the domain or search lines.

HTH,
Cory


On Tue, Sep 10, 2013 at 1:16 PM, Nathan Valentine  wrote:
> Check both of the following: /etc/hosts and /etc/sysconfig/network.
>
> --
> ---
> Nathan Valentine - nat...@puppetlabs.com
> Puppet Labs Professional Services
> GV: 415.504.2173
> Skype: nrvale0
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.
> For more options, visit https://groups.google.com/groups/opt_out.

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

Re: [Puppet Users] Where does the puppet master get its hostname

[Greg Coit]

Man, I could have swear i tested this...

/etc/sysconfig/network was correct.

/ets/hosts had:

ip grover grover.example.com

I switched that to:

ip grover.example.com grover

and the cert is now named grover.example.com.  :) 

Thank you!!!

Greg

On Tuesday, September 10, 2013 12:16:12 PM UTC-7, Nathan Valentine wrote:
>
> Check both of the following: /etc/hosts and /etc/sysconfig/network. 
>
> -- 
> ---
> Nathan Valentine - nat...@puppetlabs.com 
> Puppet Labs Professional Services
> GV: 415.504.2173
> Skype: nrvale0
>  

-- 
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] Where does the puppet master get its hostname

[Nathan Valentine]

Out of curiosity, your Puppet master was spun up how? As a Vagrant VM?


On Tue, Sep 10, 2013 at 3:23 PM, Greg Coit  wrote:

> Man, I could have swear i tested this...
>
> /etc/sysconfig/network was correct.
>
> /ets/hosts had:
>
> ip grover grover.example.com
>
> I switched that to:
>
> ip grover.example.com grover
>
> and the cert is now named grover.example.com.  :)
>
> Thank you!!!
>
> Greg
>
> On Tuesday, September 10, 2013 12:16:12 PM UTC-7, Nathan Valentine wrote:
>
>> Check both of the following: /etc/hosts and /etc/sysconfig/network.
>>
>> --
>> ---
>> Nathan Valentine - nat...@puppetlabs.com
>>
>> Puppet Labs Professional Services
>> GV: 415.504.2173
>> Skype: nrvale0
>>
>  --
> 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.
>



-- 
---
Nathan Valentine - nat...@puppetlabs.com
Puppet Labs Professional Services
GV: 415.504.2173
Skype: nrvale0

-- 
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] Custom Fact undefined in manifests

[David Thompson]

I'm working with custom facts with facter 1.7.2.  I've created a fact file 
with an ntp configuration fact in it:

# grep ntp_conf /etc/facter/facts.d/myfacts.txt 
v_ntp__ntp_conf=puppet:///modules/ntp/DEFAULT/ntp_conf

facter knows the fact is there:

# facter -p v_ntp__ntp_conf
puppet:///modules/ntp/DEFAULT/ntp_conf

...but puppet thinks the variable is undefined:

# cat /tmp/notify.pp 
notify{$hardwaremodel:}
notify{$v_ntp__ntp_conf:}
[root@sazabi facts.d]# puppet apply /tmp/notify.pp 
Notice: x86_64
Notice: /Stage[main]//Notify[x86_64]/message: defined 'message' as 'x86_64'
Notice: undef
Notice: /Stage[main]//Notify[undef]/message: defined 'message' as 'undef'
Notice: Finished catalog run in 0.28 seconds

What am I missing here?  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.

Re: [Puppet Users] Where does the puppet master get its hostname

[Greg Coit]

Nathan,

It was spun up by hand from a CentOS 6.4 disk.  I added the grover
lines to the /etc/hosts file myself after setting the hostname.

Greg
--
Greg Coit
gregc...@gmail.com
707-845-0317


On Tue, Sep 10, 2013 at 12:34 PM, Nathan Valentine
 wrote:
> Out of curiosity, your Puppet master was spun up how? As a Vagrant VM?
>
>
> On Tue, Sep 10, 2013 at 3:23 PM, Greg Coit  wrote:
>>
>> Man, I could have swear i tested this...
>>
>> /etc/sysconfig/network was correct.
>>
>> /ets/hosts had:
>>
>> ip grover grover.example.com
>>
>> I switched that to:
>>
>> ip grover.example.com grover
>>
>> and the cert is now named grover.example.com.  :)
>>
>> Thank you!!!
>>
>> Greg
>>
>> On Tuesday, September 10, 2013 12:16:12 PM UTC-7, Nathan Valentine wrote:
>>>
>>> Check both of the following: /etc/hosts and /etc/sysconfig/network.
>>>
>>> --
>>> ---
>>> Nathan Valentine - nat...@puppetlabs.com
>>>
>>> Puppet Labs Professional Services
>>> GV: 415.504.2173
>>> Skype: nrvale0
>>
>> --
>> 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.
>
>
>
>
> --
> ---
> Nathan Valentine - nat...@puppetlabs.com
>
> Puppet Labs Professional Services
> GV: 415.504.2173
> Skype: nrvale0
>
> --
> 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/MKzWpt1m7mQ/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] Custom Fact undefined in manifests

[Denmat]

Hi,

That looks a weird way of using facts. In my opinion that kind of detail should 
be in your puppet code, not your fact code.

What I would push out as facts are things like:

> v_ntp__ntp_conf=default

And then use puppet code to manage the 'if $::v_ntp...' (Notice top scope there 
for the fact variable). An alternative much better than this is to use Hiera.

Now, why is puppet not seeing that fact, I honestly don't know. Try different 
things like removing the puppet:/// schema and see if it works. Does a single 
word work without and forward slashes?

But really, I don't like the way your code is headed :)

HTH
Den

On 11/09/2013, at 1:38, David Thompson  wrote:

> I'm working with custom facts with facter 1.7.2.  I've created a fact file 
> with an ntp configuration fact in it:
> 
> # grep ntp_conf /etc/facter/facts.d/myfacts.txt 
> puppet:///modules/ntp/DEFAULT/ntp_conf
> 
> facter knows the fact is there:
> 
> # facter -p v_ntp__ntp_conf
> puppet:///modules/ntp/DEFAULT/ntp_conf
> 
> ...but puppet thinks the variable is undefined:
> 
> # cat /tmp/notify.pp 
> notify{$hardwaremodel:}
> notify{$v_ntp__ntp_conf:}
> [root@sazabi facts.d]# puppet apply /tmp/notify.pp 
> Notice: x86_64
> Notice: /Stage[main]//Notify[x86_64]/message: defined 'message' as 'x86_64'
> Notice: undef
> Notice: /Stage[main]//Notify[undef]/message: defined 'message' as 'undef'
> Notice: Finished catalog run in 0.28 seconds
> 
> What am I missing here?  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.

-- 
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: Puppet Forge Happenings

[Erik Dalén]

For this purpose I created a simple forge implementation:
https://github.com/dalen/simple-puppet-forge


On 9 September 2013 16:19, octomeow  wrote:

> How do I create forge server for internal modules?  Due to security
> concerns, we are limited in
> what we can public back to the community, but would like to use the forge
> format vs librarian.
> thanks
>
>
> On Tuesday, October 2, 2012 7:35:34 PM UTC-7, Ryan Coleman wrote:
>
>> Hello,
>>
>> If you weren't at PuppetConf or didn't catch my talk, here's a quick
>> recap. I'm product owner for the Puppet Forge team which formed in
>> July with 2 awesome engineers and an equally awesome designer. We're a
>> team dedicated to the Forge and while ramping up, we've shipped three
>> small improvements to the Forge that we hope you enjoy.
>>
>> * Two lists were added to the homepage, highlighting recently active
>> modules and contributors
>> * An authors Gravatar is now displayed on each module page.
>> * Today, the Forge will now retrieve information about GitHub issues
>> and pull requests for a module for display on a module page. This has
>> been automatically enabled for any module that lists GitHub as its
>> 'Project Issue Tracker URL'.
>>
>> The team is just getting started. In the mean-time, we've been making
>> improvements to our back-end services, user-testing new feature ideas
>> and getting ready for the next wave of functionality. Our next
>> features will focus on these two areas. A) Making it easy for you to
>> contribute your module & B) Improve the information you have to make a
>> decision about which module to use.
>>
>> As we develop and test ideas to address these goals, we want your
>> feedback!
>>
>> Feel free to file bugs, features --anything really-- to our Redmine
>> project: 
>> https://projects.puppetlabs.**com/projects/module-site/**issues
>> Aside from that and this user list, you may always email me directly
>> -- ry...@puppetlabs.com -- or find me on #puppet as ryancoleman. I'm
>> always connected via ZNC so if you don't get an immediate response in
>> IRC, know that I'll see your message and reply if I can.
>>
>>
>> Finally, if you haven't tried out the Forge in a while, please give it
>> another go. http://forge.puppetlabs.com -- Each day new content is
>> added or updated and there's some truly awesome stuff amongst the 500+
>> Forge modules. There's also a blog-post series showcasing a new one
>> each week. links.puppetlabs.com/motw
>>
>> Thanks for your time and for being an awesome community!
>>
>> --Ryan
>>
>  --
> 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.
>



-- 
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: Run a build module on first logon for new puppet clients

[kdo]

Thank you very much for your replies, they got me thinking and I now think 
I have a work around that could work in our environment using a custom fact 
at first sign in which then calls a build module. once the build module has 
run it clears up the trigger and the server then gets filtered as normal 
depending on the environment its in. many thanks for taking the time to 
reply, very much appreciated.

On Monday, September 9, 2013 9:37:55 AM UTC+10, kdo wrote:
>
> Hey All,
>
> I have been wondering how it might be possible to run a specific build 
> module when a puppet client signs in for the first time after being built. 
> So I guess the puppet master would need to be run in auto sign in mode and 
> then have a specific build module applied, ideally just once. Anyone looked 
> into this before ?
>
> this build module is used to configure a server from start to finish at 
> build time only and is the removed. this would remove an additional step in 
> our build process
>
>
>
>
>

-- 
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] Announce: Simple Puppet Forge implementation

[Erik Dalén]

Here's a simple implementation of the puppet forge (only supports the API
to download and install modules) if you want to run a site local forge. It
doesn't require any database backend and instead just reads the modules
from a directory on disk. So to add more modules to it just copy/scp/rsync
them in.

https://github.com/dalen/simple-puppet-forge

Requires Sinatra and GNU tar.

-- 
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: Purge puppet's reports

[Andrew]

Using tidy to clean up logs, this is pretty self-explanatory, so I wont 
bother explaining :)

case $hostname {
/^puppet$/: {
tidy { 'puppet::reports':
 path => '/var/lib/puppet/reports',
 matches => '*',
 age => '14d',
 backup => false,
 recurse => true,
 rmdirs => true,
 type => 'ctime',
 }
 # notify { "debug: tidy command should run now": }
}
}


Ciao,
Andrew.

-- 
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] chocolatey, windows, powershell and fault bucket

[Josh Cooper]

On Saturday, August 24, 2013, badgerious wrote:

> I opened a ticket about this a few days ago:
> http://projects.puppetlabs.com/issues/22258
>
> (Doing a bit of reading/poking at code, but so far everything I know is on
> the ticket)
>
> 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  'cvml', 'puppet-users%2bunsubscr...@googlegroups.com');>.
> To post to this group, send email to 
> puppet-users@googlegroups.com '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.
>


This should be resolved in puppet 3.3.0-rc3 thanks to Eric for the patch.

Josh


-- 
Josh Cooper
Developer, 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: Error 400 on SERVER: Could not find class pentaho for server.test.com

[Sneha More]

Hi
   Have you changed any facts and used in your class pentaho? broken 
handeling of facts may give such error.
will you please elaborate on your development environment?

Thanks & Regards,
Sneha More,
NTT DATA GTS, OSS Center, India (Pune),


On Monday, September 9, 2013 8:47:04 PM UTC+5:30, Eduardo Terzella wrote:
>
> Good morning ,
>
> I could help to debug this problem ?
>
> "puppet agent - test"
>
>
> Debug: catalog supports formats: b64_zlib_yaml dot pson raw yaml; using 
> pson
> Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
> Could not find class pentaho for s 
> erver.test.com
> /usr/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:185:in `is_http_200?'
> /usr/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:100:in `find'
> /usr/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:197:in `find'
> /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:243:in 
> `retrieve_new_catalog'
> /usr/lib/ruby/vendor_ruby/puppet/util.rb:351:in `thinmark'
> /usr/lib/ruby/1.8/benchmark.rb:308:in `realtime'
> /usr/lib/ruby/vendor_ruby/puppet/util.rb:350:in `thinmark'
> /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:242:in 
> `retrieve_new_catalog'
> /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:67:in `retrieve_catalog'
> /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:107:in 
> `prepare_and_retrieve_catalog'
> /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:159:in `run'
> /usr/lib/ruby/vendor_ruby/puppet/agent.rb:45:in `run'
> /usr/lib/ruby/vendor_ruby/puppet/agent/locker.rb:20:in `lock'
> /usr/lib/ruby/vendor_ruby/puppet/agent.rb:45:in `run'
> /usr/lib/ruby/1.8/sync.rb:230:in `synchronize'
> /usr/lib/ruby/vendor_ruby/puppet/agent.rb:45:in `run'
> /usr/lib/ruby/vendor_ruby/puppet/agent.rb:119:in `with_client'
> /usr/lib/ruby/vendor_ruby/puppet/agent.rb:42:in `run'
> /usr/lib/ruby/vendor_ruby/puppet/agent.rb:84:in `run_in_fork'
> /usr/lib/ruby/vendor_ruby/puppet/agent.rb:41:in `run'
> /usr/lib/ruby/vendor_ruby/puppet/application.rb:179:in `call'
> /usr/lib/ruby/vendor_ruby/puppet/application.rb:179:in `controlled_run'
> /usr/lib/ruby/vendor_ruby/puppet/agent.rb:39:in `run'
> /usr/lib/ruby/vendor_ruby/puppet/application/agent.rb:353:in `onetime'
> /usr/lib/ruby/vendor_ruby/puppet/application/agent.rb:327:in `run_command'
> /usr/lib/ruby/vendor_ruby/puppet/application.rb:364:in `run'
> /usr/lib/ruby/vendor_ruby/puppet/application.rb:456:in `plugin_hook'
> /usr/lib/ruby/vendor_ruby/puppet/application.rb:364:in `run'
> /usr/lib/ruby/vendor_ruby/puppet/util.rb:504:in `exit_on_fail'
> /usr/lib/ruby/vendor_ruby/puppet/application.rb:364:in `run'
> /usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:132:in `run'
> /usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:86:in `execute'
> /usr/bin/puppet:4
> Warning: Not using cache on failed catalog
> Error: Could not retrieve catalog; skipping run
> Debug: report supports formats: b64_zlib_yaml pson raw yaml; using pson
>
>
> The same module , works in production environment ( inside the puppet ) , 
> when I change the server to the development environment and use the same 
> code , this error happens .
>

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