[Puppet Users] Error applying a catalog when the agent is restarted in the middle of a catalog run

2016-01-14 Thread César
Hi all,

we have seen the following error when the puppet agent is restarted in the 
middle of a catalog run


Dec 20 07:19:18 helios puppet-agent[22331]: Reopening log files
Dec 20 07:19:18 helios puppet-agent[22331]: Starting Puppet client version 3.3.2
Dec 20 07:19:18 helios puppet-agent[22331]: Could not run: source did not 
contain any PSON!
Dec 20 07:19:19 helios puppet-agent[22329]: source did not contain any PSON!


Digging further in the issue, this error seems to occur when the agent gets 
an empty catalog to apply.
Puppet is configured to run every 3 minutes, but after the error is seen 
the agent does not recover by itself and requires another restart of the 
service.

Is there any setting that we are missing that would help us get rid of the 
problem or is it a malfunction? 


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/0e78aa32-4829-4228-9859-bf16add6b1f5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] Re: ensure => file, creating directories

2016-01-14 Thread Russell Anderson
We used to get this in spurts. Moving the file to a template always fixed the 
issue for us.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/39e7cf49-dcc8-499a-8ab7-e1b652e20542%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Puppet Users] puppetserver 2.2.1-1puppetlabs1 r10k gem jruby not found

2016-01-14 Thread Rudy Gevaert


On Wednesday, January 13, 2016 at 6:12:35 PM UTC+1, Kevin Corcoran wrote:
>
> On Wed, Jan 13, 2016 at 9:04 AM, Kevin Corcoran  > wrote:
>>
>> Even though r10k runs on the master, it runs as a separate process (not 
>> inside of Puppet Server) and uses the system ruby (likely MRI).
>>
>
> ... unless we're talking about the r10k used by the new Code Manager 
> feature in Puppet Enterprise 2015.3, which *does* run inside Puppet Server 
> ... although it still doesn't use JRuby ... for now, although it likely 
> will in the future.  I don't how this could possibly confuse anyone!  ;)
>
> Snark aside ... Rudy, I think you just want to use the system ruby.
>
>
Hi Kevin, thanks for your replies.  Indeed it's an option to use the system 
ruby.  I'll need to go down that route.  But previously this was working 
(IIRC). 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/cf910216-ffe3-48cf-83b4-068b9d41e47f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] Puppet x64 msi not installing files

2016-01-14 Thread Gary Greene
I’ve got a user on Windows 10 x64 Pro that we’ve been having some issues with 
the puppet install on his machine. To fix, I tried upgrading the client from 
3.8.3 to 3.8.4 from the Puppet Open Source downloads for Windows x64.

When running the install, everything _appears_ to install, and the Windows 
Installer throws no error, but when I look at his filesystem, the files that I 
expect to be in C:\Program Files\Puppet Labs\ are not present at all.

The logs all state that the MSI install completed without issue, but as I said, 
the files never show up.

Has anyone else seen this? And if so, what’s the workaround for this so I can 
ensure that the rest of the Windows fleet aren’t going to be an issue upgrading 
to the latest release?

--
Gary L. Greene, Jr.
==
Volunteer developer of the KDE F/OSS project and Project Lead for AltimatOS
http://www.kde.org/ http://www.altimatos.com/
Please refrain from sending me proprietary binary documents (Doc, Xls, Ppt)
  Use a free office suite with standards approved formats like LibreOffice.
http://www.libreoffice.org/
==

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/2C79886B-ADC8-42A5-8B05-589F415A55B3%40tolharadys.net.
For more options, visit https://groups.google.com/d/optout.


Re: [Puppet Users] Facter - custom fact regex

2016-01-14 Thread Mike Reed
Hey Hristo,

This did not work for me but I wanted to thank you for the info.  It turns 
out the fact wasn't being sync'd correctly to the client and therefore not 
all my changes were being reflected locally.

Thank you again for the info. 

Cheers,

Mike.

On Wednesday, January 13, 2016 at 3:26:18 AM UTC-8, Hristo Mohamed wrote:
>
> Try :
> setcode { network }
>
> From puppett docs:
>
>
>1. A call to Facter.add('fact_name'), which determines the name of the 
>fact
>2. A setcode statement for simple resolutions, which is evaluated to 
>determine the fact’s value.
>
>
> On Wed, Jan 13, 2016 at 12:42 AM, Mike Reed  > wrote:
>
>> Hello all,
>>
>> I'm having some trouble with a custom fact and I was hoping somebody 
>> could tell me what I'm doing wrong.  
>>
>> Here is an example of the code:
>>
>> require 'facter'
>> Facter.add('network') do
>>   setcode do
>> hostname = Facter.value(:hostname)
>> ipaddress = Facter.value(:ipaddress)
>> case 
>>   when 
>> ipaddres.match(/^(\d[10]\.)(\d[10]\.)([1][2][7]\.)([1-9][1-9][1-9])?/)
>> network = 'net1'  
>>   when hostname.match(/^nettwo/)
>> network = 'net2'
>>   when hostname.match(/^netthree/)
>> network = 'net3'
>>   when hostname.match(/^netfour/)
>> network = 'net4'
>>   else
>> network = 'nonet'
>>   end
>> network
>> end
>> end
>>
>> I've gotten myself into a pickle in that most hosts have a hostname 
>> prefix to designate what network they are on.  In this case, I don't have a 
>> prefix but the physical ip is different and my thoughts were to regex match 
>> the ip address and bingo...but no luck.
>>
>> Puppet runs and pluginsync does pull down the fact but I never get the 
>> value of network back.   No errors are displayed or logged when running 
>> 'facter -p' but again, I never get the value of network back.  I've done 
>> quite a bit of reading and can't figure out why this one doesn't work.  
>>
>> Does anybody perhaps have any suggestions as to how I might accomplish 
>> this?
>>
>> Thank you in advance for your assistance.
>>
>> Cheers,
>>
>> Mike
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Puppet Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to puppet-users...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/cbf9ea68-fffd-4e14-a467-486d8832bc0e%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/4d44092b-6b1f-4999-8a52-c7b0b41a5150%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] Re: Facter - custom fact regex

2016-01-14 Thread Mike Reed
Thank you for the info John.  I did fix the typo and it looks like the fact 
wasn't sync'd correctly to the client.  It's all fixed up now and working 
as expected.

You've always been a great help and I very much appreciate your time.

Let me know where to send the six pack.

Cheers,

Mike

On Wednesday, January 13, 2016 at 6:31:20 AM UTC-8, jcbollinger wrote:
>
>
>
> On Tuesday, January 12, 2016 at 5:42:45 PM UTC-6, Mike Reed wrote:
>>
>> Hello all,
>>
>> I'm having some trouble with a custom fact and I was hoping somebody 
>> could tell me what I'm doing wrong.  
>>
>> Here is an example of the code:
>>
>> require 'facter'
>> Facter.add('network') do
>>   setcode do
>> hostname = Facter.value(:hostname)
>> ipaddress = Facter.value(:ipaddress)
>> case 
>>   when 
>> ipaddres.match(/^(\d[10]\.)(\d[10]\.)([1][2][7]\.)([1-9][1-9][1-9])?/)
>> network = 'net1'  
>>   when hostname.match(/^nettwo/)
>> network = 'net2'
>>   when hostname.match(/^netthree/)
>> network = 'net3'
>>   when hostname.match(/^netfour/)
>> network = 'net4'
>>   else
>> network = 'nonet'
>>   end
>> network
>> end
>> end
>>
>> I've gotten myself into a pickle in that most hosts have a hostname 
>> prefix to designate what network they are on.  In this case, I don't have a 
>> prefix but the physical ip is different and my thoughts were to regex match 
>> the ip address and bingo...but no luck.
>>
>> Puppet runs and pluginsync does pull down the fact but I never get the 
>> value of network back.   No errors are displayed or logged when running 
>> 'facter -p' but again, I never get the value of network back.  I've done 
>> quite a bit of reading and can't figure out why this one doesn't work.
>>
>
>
> You misspell "ipaddress" in the first "when" clause.  I wouldn't have 
> expected that to cause the fact to be silently ignored, and maybe it 
> doesn't, but you should fix it regardless.
>
> Otherwise, I don't see anything inherently wrong with your fact code.  If 
> after you fix the misspelling, the fact is not submitted to the master, and 
> 'facter -p' neither prints it nor emits any error message, then my first 
> guess would be that it has not properly been synced, your assertion to the 
> contrary notwithstanding.  In that case, look into where the synced file 
> actually went (if anywhere).  If it is indeed in a subdirectory "facter" of 
> some directory in the Ruby load path, then verify that the file and every 
> directory in the path to it is accessible to puppet and facter.  Even with 
> the agent running with privilege, as normally it must do, it is possible 
> for it to be denied access to some files and directories.
>
>
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/87f28dbb-00c3-420f-9985-123c38c8c2c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] Re: Facter - custom fact regex

2016-01-14 Thread Mike Reed
That is a great idea and I'll get that changed to something else.

Cheers,

Mike

On Thursday, January 14, 2016 at 10:23:06 AM UTC-8, Thomas Müller wrote:
>
> IMHO the fact "network" is a default fact from facter >= 3. i would change 
> the name.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/04bddc6a-0b09-4c41-8675-46d63ce8910e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] Facter - custom fact regex

2016-01-14 Thread Thomas Müller
IMHO the fact "network" is a default fact from facter >= 3. i would change the 
name.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/e01d06a4-d191-414f-8966-ff4d41fda8d0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] Recommended way to get mcollective working with PC1

2016-01-14 Thread Kenton Brede
It doesn't look like PC1 includes middleware for mcollective.  I'm not
finding documentation specifically for mcollective and PC1.

Is activemq still the preferred middleware?

If so, should I install the activemq (0.0.1) gem or the jruby-activemq gem
(5.5.1)?

How can I get the puppetmaster to see activemq if its installed outside the
PC1 environment?

Thanks,

-- 
Kent Brede

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CA%2BnSE3_ZjJa93wjO1NTJAnjFRzhbArZxMmetaxtoq%2BhX-vavQg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Puppet Users] How to manage half file.

2016-01-14 Thread Albert Shih
 Le 13/01/2016 à 13:21:51-0800, Hunter Haugen a écrit
> Does the application have an "include" syntax that would allow you do have one
> file that is one line that the application manages, and the file that puppet
> manages includes it where appropriate?

WellI would like itbut no...

>
> Or a stupid workaround would be to have a fact that is that one line, and a
> puppet template that adds the line. So puppet would manage the whole file but
> the line would not be affected by a puppet run.

Hummsorry I don't understand your workaround

Thanks.

JAS
--
Albert SHIH
DIO bâtiment 15
Observatoire de Paris
5 Place Jules Janssen
92195 Meudon Cedex
France
Téléphone : +33 1 45 07 76 26/+33 6 86 69 95 71
xmpp: j...@obspm.fr
Heure local/Local time:
jeu 14 jan 2016 17:46:08 CET

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/20160114164728.GA18250%40pcjas.obspm.fr.
For more options, visit https://groups.google.com/d/optout.