[Puppet Users] Re: Issue with new install of Puppet and PuppetDB

Hi for any one who follows on from this -Djdk.tls.ephemeralDHKeySize=2048 needs to be added to the JDK - i moved to jdk 11, this seems to solve the problem ! A On Thursday, November 14, 2019 at 9:52:23 AM UTC+11, Keyzer Suze wrote: > > Hi > > I have a green field install of puppet - that bits

[Puppet Users] Re: Issue with puppetlabs-java

It looks like you need to add a package_type for deb and a case statement for Ubuntu. Would be a good time to patch the module and submit a pull request. :) On Friday, January 20, 2017 at 10:37:58 AM UTC-5, Salty Old Cowdawg wrote: > > Supposedly on the forge site it says the module was test

[Puppet Users] Re: Issue with module from forge - Duplicate declaration Class[Rsyslog]

On Thursday, October 6, 2016 at 9:04:14 AM UTC-5, re-g...@wiu.edu wrote: > > > I understand the duplicate declaration issue - I have been reading about it > for months trying to figure out this issue that keeps popping up. I am > trying to figure out how it is possible I am getting a duplicat

[Puppet Users] Re: Issue with module from forge - Duplicate declaration Class[Rsyslog]

On Wednesday, October 5, 2016 at 2:32:37 PM UTC-5, re-g...@wiu.edu wrote: > > I installed the puppet module saz-rsyslog from puppet forge. > I use The Foreman to configure nodes. The Foreman is used by puppet via > configuration [master] "external_nodes" "/etc/puppet/node.rb" > > Since the saz-r

[Puppet Users] Re: Issue with module from forge - Duplicate declaration Class[Rsyslog]

On Thursday, October 6, 2016 at 8:27:40 AM UTC-5, jcbollinger wrote: > > > > On Wednesday, October 5, 2016 at 2:32:37 PM UTC-5, re-g...@wiu.edu wrote: >> >> I installed the puppet module saz-rsyslog from puppet forge. >> I use The Foreman to configure nodes. The Foreman is used by puppet via >>

[Puppet Users] Re: Issue with module from forge - Duplicate declaration Class[Rsyslog]

On Wednesday, October 5, 2016 at 2:32:37 PM UTC-5, re-g...@wiu.edu wrote: > > I installed the puppet module saz-rsyslog from puppet forge. > I use The Foreman to configure nodes. The Foreman is used by puppet via > configuration [master] "external_nodes" "/etc/puppet/node.rb" > > Since the saz-r

[Puppet Users] Re: Issue with lvm, "Invalid parameter unless_vg(:unless_vg)"

Am Montag, 3. Oktober 2016 14:36:22 UTC+2 schrieb Stephen O'Kane: > > Hi, >I keep getting this error when running a installation using puppet. > > Physical_volume[/dev/disk/by-id/virtio-6c2cd884-c21b-4bff-b-part1]: Could > not evaluate: Invalid parameter unless_vg(:unless_vg) > > My underst

[Puppet Users] Re: issue with hiera.eyaml file

Am Donnerstag, 13. November 2014 22:55:27 UTC+1 schrieb Spriya: > > Hi All, > > I am having an issue > Cannot load backend eyaml: cannot load such file -- highline/import. > > when running this command: > > *sudo -u pe-puppet /opt/puppet/bin/hiera -c > /etc/puppetlabs/puppet/hiera.yaml --de

[Puppet Users] Re: Issue with rspec-puppet testing of roles/profiles module and class evaluation...

Note to self, need to do better at reading the manual :( The issue was a typo - It should be 'pre_condition', not 'precondition' - https://github.com/fatmcgav/rspec-deptest/commit/6a4f5a5294d7bb239b8f98cabe6c32e3522569de Tests now working... Cheers Gav On Thursday, 25 September 2014 14:42:26

[Puppet Users] Re: Issue with puppet 3.3 evaluation - puppet agent install curl command is failing

Hi Norm, I can't get to https://fwdevpup.wvus.org:8140 so it is difficult to tell what this script does. Did you try the official method

[Puppet Users] Re: Issue with Role-Profile implementation

Adding to my below post , I would like to inform that I upgraded the kernel to CentOS 6.5 X86_64 [root@puppet ~]# uname -a Linux puppet.xoriant.in 2.6.32-431.20.3.el6.x86_64 #1 SMP Thu Jun 19 21:14:45 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Issue still persists On Wednesday, 9 July 2014 14:29:

[Puppet Users] Re: Issue with exported resources and "ensure"

On Wednesday, January 16, 2013 1:45:28 PM UTC-6, Cody Robertson wrote: > > Hello folks! I hope everyone is having a great Wednesday! > > I think I may have come across a bug / a use case which isn't working > properly however I wanted to run it by some eyes on the mailing list before > I filed

[Puppet Users] Re: Issue with service => disabled and stopped

On Tuesday, November 20, 2012 6:11:17 PM UTC-6, Forrie wrote: > > Thanks, I went ahead and added an "exit 1" at the bottom of each of > these scripts to shut it up. That's probably not quite right, but maybe it will work well enough for you. > At least, in the case of the cups- > confi

[Puppet Users] Re: Issue with service => disabled and stopped

Thanks, I went ahead and added an "exit 1" at the bottom of each of these scripts to shut it up. At least, in the case of the cups- config-daemon, it's been deprecated so I can just remove that check. HIDD is another issue. Most of the init.d scripts use RETVAL=$? after the status) query -- so

[Puppet Users] Re: Issue with service => disabled and stopped

On Monday, November 19, 2012 6:37:28 PM UTC-6, Forrie wrote: > > Thanks for the explanation, I appreciate it. > > These services are provided by Redhat as are the init scripts, which > report: > > > # /etc/init.d/cups-config-daemon status > cups-config-daemon is obsolete > > # /etc/init.d/hi

Re: [Puppet Users] Re: Issue with service => disabled and stopped

Both of these init scripts always return 0. Puppet assumes that the init script will return 0 as a status for a running service and nonzero for a stopped service. Because of this, when Puppet calls `service hidd status` to see if hidd needs to be stopped, it thinks it does, as status returns 0. hi

[Puppet Users] Re: Issue with service => disabled and stopped

Thanks for the explanation, I appreciate it. These services are provided by Redhat as are the init scripts, which report: # /etc/init.d/cups-config-daemon status cups-config-daemon is obsolete # /etc/init.d/hidd status hidd is stopped I can see where the first one is unexpected to Puppet. I

[Puppet Users] Re: issue with custom types and providers

This is with puppet 2.6 and one minor difference was in my code I tried both newparam and newproperty to see if it was potentially just a simple mistake. On Tuesday, May 22, 2012 10:55:19 AM UTC-4, Matt wrote: > > So I'm trying to follow the example in the Pro Puppet book and I'm running > into

[Puppet Users] Re: Issue with pe-dashboard-workers

I don't get it, but a clean uninstall (including db files in /var/lib/mysql) followed by a reinstall seems to have worked. Thanks for listening. On Tuesday, March 6, 2012 10:19:37 AM UTC-8, mic...@linuxexam.com wrote: > > I've almost gotten PE running -- > > Based on tips from a recent Webinar,

Re: [Puppet Users] Re: Issue with RPM dependency issue

I've run into this before. The trick is to ensure that the Percona client is available and installed first and let *it* pull in perl-DBD-MySQL. If you install perl-DBD-MySQL first, it will often attempt to directly grab the RPM that best meets its requirements, which is the standard MySQL pack

[Puppet Users] Re: Issue with RPM dependency issue

On Nov 22, 8:43 am, TisMe wrote: > I am running into an issue with perl-DBD-MySQL dependency with mysql > in CentOS 5.7. > > I am trying to remove the mysql client and replace it with with > percona version of the mysql client. > > It will not let me remove the mysql client because of that > dep

[Puppet Users] Re: Issue with puppet file serving api not parsing yaml content correctly

Unfortunately, it does not work. That was the first thing I had tried to try and reproduce the problem in ruby outside a puppet run. Also, here are the ruby util modules for puppet in 0.25.4: /opt/ruby-1.8.6-p287/lib/ruby/site_ruby/1.8/puppet/util autoload autoload.rb backups.rb cacher.rb checksu

Re: [Puppet Users] Re: Issue with puppet file serving api not parsing yaml content correctly

On Mon, Jul 11, 2011 at 4:17 PM, Derek Tamsen wrote: > Thanks. Unfortunately, it seems I will need to wait until we upgrade > puppet as version 0.25.4 does not seem to have 'puppet/util/zaml'. > Then I'm more confused :) does require 'puppet' require 'yaml' just do the right thing? If not, I'

[Puppet Users] Re: Issue with puppet file serving api not parsing yaml content correctly

Thanks. Unfortunately, it seems I will need to wait until we upgrade puppet as version 0.25.4 does not seem to have 'puppet/util/zaml'. -- Derek On Jul 11, 2:56 pm, Nigel Kersten wrote: > On Mon, Jul 11, 2011 at 11:36 AM, Derek wrote: > > Thanks for everyone's help. I figured out what the issue

Re: [Puppet Users] Re: Issue with puppet file serving api not parsing yaml content correctly

On Mon, Jul 11, 2011 at 11:36 AM, Derek wrote: > Thanks for everyone's help. I figured out what the issue was over the > weekend. It appears that when the ruby script is run in a puppet run, > puppet loads the yaml dictionaries specific to puppet. However, when I > was testing the script in ruby

[Puppet Users] Re: Issue with puppet file serving api not parsing yaml content correctly

Thanks for everyone's help. I figured out what the issue was over the weekend. It appears that when the ruby script is run in a puppet run, puppet loads the yaml dictionaries specific to puppet. However, when I was testing the script in ruby I was not loading the yaml dictionaries for puppet. This

[Puppet Users] Re: Issue with "change from absent to present failed...no such file or directory"

Ah that did the trick...now a new error. I tried simplifying the module from camptocamp, https://github.com/camptocamp/puppet-dhcp, but a lot of it's usage I don't understand, and as such my "simplification" just broke it. I've got it much farther now...near the end of puppet run I get this error

[Puppet Users] Re: issue with exported resources and subscribe

> > To get this sort of thing right, you need to think in terms of > Puppet's logical model of the managed system, as opposed to in terms > of the observable result of Puppet's work.  In particular, as far as > Puppet is concerned, managing file /etc/hosts via a File resource is > logically distinc

[Puppet Users] Re: issue with exported resources and subscribe

On May 5, 1:00 am, Nathan wrote: > Hello list, > > I have a situation where if I have a hosts file generated by exported > resources it does not trigger a service restart unlike if it was > subscribing on a file that gets copied over via puppet. An example > would explain it better. > > it shoul

[Puppet Users] Re: issue with exported resources and subscribe

Hi, In my exported resource manifests, if using code like: File <<| tag == "nagios::target" |>> { notify => Service["nagios3"] } Does that work for you? Cheers, Greg -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, s

[Puppet Users] Re: Issue with scope.function_ in a template.

I'm replying to myself since I have found a completely hack-ish workaround to this issue, but still no "real" solution. It turns out that the function in question just has to be noted in the manifest *at all*. So, you can do something like the following and then use it in your template: if false

[Puppet Users] Re: Issue with naginator and elusive nagios cfg file corruption (#3712)

On 05/03/2010 03:33 PM, Joe McDonagh wrote: > Hello, I have run into a data corruption problem with naginator that is > fairly difficult for me to track down. Hand-written configurations do > not suffer from this fate. This was present in .24.8, and still present > in .25.4. I'd love to complete th

Re: [Puppet Users] Re: Issue with '|'

I actually think I figured it out what the difference was. In the set up you sent me, you have the "path" defined. In my setup I didn't and was using grep without the fully qualified path. Other than that, it escapes me for what it could have been. I've been happily rolling along since though.

Re: [Puppet Users] Re: Issue with '|'

On Friday 26 Feb 2010 16:03:41 Andrew Hamilton wrote: > I can't thank you enough. This worked perfectly for me. I don't know how > it is functionally different than what I had before, but nevertheless this > is exactly what I needed. Thanks again. > > Drew > Heh, yeah, that's the thing, it is

Re: [Puppet Users] Re: Issue with '|'

On Thursday 25 Feb 2010 23:19:33 Andrew Hamilton wrote: > > unlessIf this parameter is set, then this exec will run unless the > > command returns 0 > > I interpret this to be the return value of the command and not the output > of the command. So if the return value of my command is 0 then the

Re: [Puppet Users] Re: Issue with '|'

So this is really getting to me and I can't seem to figure it out. >From the documents: > unlessIf this parameter is set, then this exec will run unless the command > returns 0 > I interpret this to be the return value of the command and not the output of the command. So if the return value of

Re: [Puppet Users] Re: Issue with '|'

It looks to me like something is replacing your command before it gets executed. I have no idea what could be doing that but what is being entered as /usr/bin/psql -l | grep '$name *|' is then being changed to /usr/bin/psql -c '\du' | grep 'puser *|' so -l is being changed to -c '\du'. Both

Re: [Puppet Users] Re: Issue with '|'

I tried Michael's suggestion above and when running it from the command line, it does complete successfully. It returns 0 when the user exists and 1 when it doesn't. Does that make sense? Anyway, inserting the pipe back into it produces the same error as before. It's perplexing... Thanks, Dre

Re: [Puppet Users] Re: Issue with '|'

Thanks for the replies and other possibilities. I'm using version 0.25.2 of puppet. I did a different kind of workaround mostly by doing the same thing with a straight psql command with no pipe. ie. "/usr/bin/psql -c 'select * from pg_user where usename = 'myuser'" This at least seems to not e

[Puppet Users] Re: Issue with '|'

Have you checked out what that command does when you run it from the command line? Does it complete successfully? What is the return code? Possibility 1: Your version of Puppet (you didn't say which) is not correctly preserving the inner single quotation marks around '$name *|'. This seems unli

[Puppet Users] Re: Issue with template.pp

It is breaking on include baseapps, sshd, admin, default get rid of default and it should work On Wed, Feb 4, 2009 at 2:34 AM, linuxbsdfreak wrote: > > Hi i am creating a template.pp for different OS.. Following is my > template.pp file > > node basenode { > case $operatingsystem {

[Puppet Users] Re: Issue with a new fact

That got it! Thanks Guys... My Ruby is slowly improving... --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from

[Puppet Users] Re: Issue with a new fact

Quick refactoring recommendation: Pull the lookup out into a helper attr_reader :physical_proxies @physical_proxies = { XXX => "proxyX", XXY => "proxyY", ... } def proxy_lookup(virtal, ip) if virtual == "physical" physical_proxies[ip.split(/\./)[1]] elsif virtual == "openvz" some_oth

[Puppet Users] Re: Issue with a new fact

In general, ruby does not allow an explicit 'return' within blocks. Feel free to read up on the gory details, but basically, have the last statement in your block be the value you want to return, rather than an explicit return. On Jan 12, 2009, at 10:51 AM, Jeff Leggett wrote: > > If I do t

[Puppet Users] Re: Issue with a new fact

If I do that, it blows up: [jlegg...@lxp6d11m8v190 facter]$ facter /opt/etrade/p6/lib/ruby/site_ruby/1.8/facter/etproxy.rb:36: unexpected return (LocalJumpError) from /opt/etrade/p6/lib/ruby/site_ruby/1.8/facter/util/ resolution.rb:117:in `call' from /opt/etrade/p6/lib/ruby/site_r

[Puppet Users] Re: Issue with a new fact

You need to return a value, not to print it... try replacing put with return. Ohad On Sat, Jan 10, 2009 at 1:53 AM, Jeff Leggett wrote: > > OK Good to know, updated... So no error now but it still output the > facter value etproxy at the beginning of the facter outpout and > without an identifi

[Puppet Users] Re: Issue with a new fact

OK Good to know, updated... So no error now but it still output the facter value etproxy at the beginning of the facter outpout and without an identifier: [jlegg...@lxp6d11m8v190 facter]$ facter 10.X.Y.Z:8080 architecture => i386 domain => etrade.com facterversion => 1.5.2 fqdn => lxp6d11m8v190.e

[Puppet Users] Re: Issue with a new fact

Sorry, no need for the require 'facter' as you are already running inside it... (dahaa.) but if you want to try it out on irb or similar you need it. Ohad On Fri, Jan 9, 2009 at 5:51 PM, Ohad Levy wrote: > try in your code: > > require 'facter' > > Facter.value(:ipaddress) ( or Facter.ipaddress

[Puppet Users] Re: Issue with a new fact

try in your code: require 'facter' Facter.value(:ipaddress) ( or Facter.ipaddress) Cheers, Ohad On Fri, Jan 9, 2009 at 2:41 PM, Jeff Leggett wrote: > > That may be the problem - I call it by: > > ipaddr = `facter ipaddress`.chomp > > On Jan 8, 4:22 pm, James Turnbull wrote: > > -BEGIN PGP

[Puppet Users] Re: Issue with a new fact

That may be the problem - I call it by: ipaddr = `facter ipaddress`.chomp On Jan 8, 4:22 pm, James Turnbull wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > > > > Jeff Leggett wrote: > > So I wrote a new fact to determine  clients proxy.  Work's great when > > I call it via facter

[Puppet Users] Re: Issue with a new fact

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeff Leggett wrote: > So I wrote a new fact to determine clients proxy. Work's great when > I call it via facter as a single: > > [jlegg...@lxp6d11m8v190 jleggett]$ facter etproxy > 10.X.Y.Z:8080 > > But when I call facter alone (for full output o