[Puppet Users] Puppet own function
Good day. Im trying to make my own function. I keep getting this message. err: Could not retrieve catalog from remote server: Error 400 on SERVER: Function 'brent_k' does not return a value at /etc/puppet/modules/munin/manifests/init.pp:17 on node XYZ.com Here is my simple code xyz.com:/etc/puppet/modules/munin/lib/puppet/parser/functions# cat brent_k.rb module Puppet::Parser::Functions newfunction(:brent_k, :type = :rvalue) do |args| val = 'ok' val end end And then in my manifest, I have $a = brent_k() I tried return val too. Thanks if you can help Brent -- 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 this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Different return codes on exec during puppet agent run vs command line Windows
Trying to run this exec in one of our manifests. When the resource is run
during a puppet run, it returns a error code 87. But when I execute the
same command on command prompt, it returns 3010. Is there any way to dig
and and find out why the return codes are different. FYI, I am using the
sysnative path to avoid the file system redirection on windows.
Platform: Windows 2008R2 64 bit
Running PE 2.6 agent and PE 2.6 master.
Exec statement(It's horrendous I know) :
$AILogFile='C:\\Program Files\\HELLO_WORLD\\log\\IIS7.log'
exec { 'install_iis':
command = c:\\Windows\\sysnative\\dism.exe /online /norestart
/logpath:\C:\\temp\\log.etw.txt\ /enable-feature /ignorecheck
/featurename:\IIS-ApplicationDevelopment\ /featurename:\IIS-ASP\
/featurename:\IIS-ASPNET\ /featurename:\IIS-BasicAuthentication\
/featurename:\IIS-CGI\
/featurename:\IIS-ClientCertificateMappingAuthentication\
/featurename:\IIS-CommonHttpFeatures\ /featurename:\IIS-CustomLogging\
/featurename:\IIS-DefaultDocument\
/featurename:\IIS-DigestAuthentication\
/featurename:\IIS-DirectoryBrowsing\
/featurename:\IIS-HealthAndDiagnostics\
/featurename:\IIS-HostableWebCore\
/featurename:\IIS-HttpCompressionDynamic\
/featurename:\IIS-HttpCompressionStatic\ /featurename:\IIS-HttpErrors\
/featurename:\IIS-HttpLogging\ /featurename:\IIS-HttpRedirect\
/featurename:\IIS-HttpTracing\
/featurename:\IIS-IIS6ManagementCompatibility\
/featurename:\IIS-IISCertificateMappingAuthentication\
/featurename:\IIS-IPSecurity\ /featurename:\IIS-ISAPIExtensions\
/featurename:\IIS-ISAPIFilter\ /featurename:\IIS-LegacyScripts\
/featurename:\IIS-LegacySnapIn\ /featurename:\IIS-LoggingLibraries\
/featurename:\IIS-ManagementConsole\
/featurename:\IIS-ManagementScriptingTools\
/featurename:\IIS-ManagementService\ /featurename:\IIS-Metabase\
/featurename:\IIS-NetFxExtensibility\ /featurename:\IIS-Performance\
/featurename:\IIS-RequestFiltering\ /featurename:\IIS-RequestMonitor\
/featurename:\IIS-Security\ /featurename:\IIS-ServerSideIncludes\
/featurename:\IIS-StaticContent\ /featurename:\IIS-URLAuthorization\
/featurename:\IIS-WebDAV\ /featurename:\IIS-WebServer\
/featurename:\IIS-WebServerManagementTools\
/featurename:\IIS-WebServerRole\
/featurename:\IIS-WindowsAuthentication\
/featurename:\IIS-WMICompatibility\ /featurename:\NetFx3\
/featurename:\WAS-ConfigurationAPI\ /featurename:\WAS-NetFxEnvironment\
/featurename:\WAS-ProcessModel\
/featurename:\WAS-WindowsActivationService\
/featurename:\WCF-HTTP-Activation\
/featurename:\WCF-NonHTTP-Activation\ \${param::AILogFile}\ 21,
returns = ['0','1003', '3010'],
unless = 'REG QUERY
\HKLM\SOFTWARE\HELLO_WORLD\AutoInstall\IISSubTypes\ /v IIS /t REG_DWORD
/d /f 1',
require = Exec['echo Install_IIS']
}
Output if I do a puppet agent --debug --test:
debug: Executing 'c:\Windows\sysnative\dism.exe /online /norestart
/logpath:C:\temp\log.etw.txt /enable-feature /ignor
echeck /featurename:IIS-ApplicationDevelopment /featurename:IIS-ASP
/featurename:IIS-ASPNET /featurename:IIS-Basi
cAuthentication /featurename:IIS-CGI
/featurename:IIS-ClientCertificateMappingAuthentication
/featurename:IIS-Comm
onHttpFeatures /featurename:IIS-CustomLogging
/featurename:IIS-DefaultDocument /featurename:IIS-DigestAuthenticati
on /featurename:IIS-DirectoryBrowsing
/featurename:IIS-HealthAndDiagnostics /featurename:IIS-HostableWebCore
/fea
turename:IIS-HttpCompressionDynamic
/featurename:IIS-HttpCompressionStatic /featurename:IIS-HttpErrors
/featurenam
e:IIS-HttpLogging /featurename:IIS-HttpRedirect
/featurename:IIS-HttpTracing /featurename:IIS-IIS6ManagementCompa
tibility /featurename:IIS-IISCertificateMappingAuthentication
/featurename:IIS-IPSecurity /featurename:IIS-ISAPIEx
tensions /featurename:IIS-ISAPIFilter /featurename:IIS-LegacyScripts
/featurename:IIS-LegacySnapIn /featurename:
IIS-LoggingLibraries /featurename:IIS-ManagementConsole
/featurename:IIS-ManagementScriptingTools /featurename:IIS
-ManagementService /featurename:IIS-Metabase
/featurename:IIS-NetFxExtensibility /featurename:IIS-Performance /fe
aturename:IIS-RequestFiltering /featurename:IIS-RequestMonitor
/featurename:IIS-Security /featurename:IIS-ServerS
ideIncludes /featurename:IIS-StaticContent
/featurename:IIS-URLAuthorization /featurename:IIS-WebDAV /featurename
:IIS-WebServer /featurename:IIS-WebServerManagementTools
/featurename:IIS-WebServerRole /featurename:IIS-WindowsA
uthentication /featurename:IIS-WMICompatibility /featurename:NetFx3
/featurename:WAS-ConfigurationAPI /featurenam
e:WAS-NetFxEnvironment /featurename:WAS-ProcessModel
/featurename:WAS-WindowsActivationService /featurename:WCF-H
TTP-Activation /featurename:WCF-NonHTTP-Activation C:\\Program
Files\\HELLO_WORLD\\log\\IIS7.log 21'
err: /Stage[main]/Win-iis-install::Iis-config/Exec[install_iis]/returns:
change from notrun to 0 1003 3010 failed:
c:\Windows\sysnative\dism.exe /online /norestart
[Puppet Users] err: Could not retrieve catalog from remote server: Error 400 on SERVER: allocator undefined for Proc
My puppet setup break just a few hours with this message. I didn't upgrade anything, didn't really changed my module and it just broke. The node what where working suddenly stop working. I'm using the official Puppet 3.0 on Scientific Linux (aka Redhat) 6.3 Can some one explain me this magic ? -- 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 this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Different return codes on exec during puppet agent run vs command line Windows
On Wednesday, October 17, 2012 9:59:54 PM UTC-5, Beeny wrote:
Trying to run this exec in one of our manifests. When the resource is run
during a puppet run, it returns a error code 87. But when I execute the
same command on command prompt, it returns 3010. Is there any way to dig
and and find out why the return codes are different. FYI, I am using the
sysnative path to avoid the file system redirection on windows.
Platform: Windows 2008R2 64 bit
Running PE 2.6 agent and PE 2.6 master.
Exec statement(It's horrendous I know) :
$AILogFile='C:\\Program Files\\HELLO_WORLD\\log\\IIS7.log'
exec { 'install_iis':
[...]
returns = ['0','1003', '3010'],
unless = 'REG QUERY
\HKLM\SOFTWARE\HELLO_WORLD\AutoInstall\IISSubTypes\ /v IIS /t REG_DWORD
/d /f 1',
require = Exec['echo Install_IIS']
}
Output if I do a puppet agent --debug --test:
debug: Executing 'c:\Windows\sysnative\dism.exe /online /norestart
/logpath:C:\temp\log.etw.txt /enable-feature /ignor
[...]
featurename:WCF-NonHTTP-Activation C:\\Program
Files\\HELLO_WORLD\\log\\IIS7.log 21 returned 87 instead of
one of [0,1003,3010] at
/etc/puppetlabs/puppet/modules/win-iis-install/manifests/iis-config.pp:15
But if I run on command line I get the below:
C:\Program Files (x86)\Puppet Labs\Puppet
Enterprise\binc:\Windows\sysnative\dism.exe /online /norestart /logpath:
[...]
C:\Program Files (x86)\Puppet Labs\Puppet Enterprise\binecho %errorlevel%
3010
Any help? This has me completely stumped since I'm running puppet and
running the command from exactly the same command shell window on the
server. I ran:
I'm not well versed on Windows-specific aspects of Puppet, but in a more
general context problems such as you describe are usually the result of
differences in execution environment. In particular, Puppet does not
forward its own environment variables -- not even the PATH -- to processes
it launches. If the command you are trying to run requires anything in
particular in its environment then you need to set those variables
specifically in the Exec resource. This behavior is intentional: it
fosters consistent and (more) secure behavior when applying Execs.
Also, it might be worthwhile to investigate the meaning of exit code 87 for
the command you are running. If it's documented then that may help you in
your troubleshooting.
John
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/7LtaQ6a1qaUJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] err: Could not retrieve catalog from remote server: Error 400 on SERVER: allocator undefined for Proc
Could you check the server logs and run the master with --verbose --debug --trace? The information I'm looking for is a backtrace to the file and ljne number that raised that exception. Thanks, -Jeff On Oct 18, 2012, at 5:26 AM, Fabrice Bacchella fbacche...@spamcop.net wrote: My puppet setup break just a few hours with this message. I didn't upgrade anything, didn't really changed my module and it just broke. The node what where working suddenly stop working. I'm using the official Puppet 3.0 on Scientific Linux (aka Redhat) 6.3 Can some one explain me this magic ? -- 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 this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- 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 this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Using collections
On Wed, Oct 17, 2012 at 11:47 AM, Maarten Thibaut mthib...@cisco.comwrote: http://forge.puppetlabs.com/mthibaut/mutual_trust Awesome! Thank you for sharing your work on the Forge! -- Ryan Coleman | @ryanycoleman Modules Forge | Puppet Labs -- 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 this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Different return codes on exec during puppet agent run vs command line Windows
Hi Ben,
On Wed, Oct 17, 2012 at 7:59 PM, Beeny beenybe...@gmail.com wrote:
Trying to run this exec in one of our manifests. When the resource is run
during a puppet run, it returns a error code 87. But when I execute the same
command on command prompt, it returns 3010. Is there any way to dig and and
find out why the return codes are different. FYI, I am using the sysnative
path to avoid the file system redirection on windows.
Platform: Windows 2008R2 64 bit
Running PE 2.6 agent and PE 2.6 master.
Exec statement(It's horrendous I know) :
$AILogFile='C:\\Program Files\\HELLO_WORLD\\log\\IIS7.log'
exec { 'install_iis':
command = c:\\Windows\\sysnative\\dism.exe /online /norestart
/logpath:\C:\\temp\\log.etw.txt\ /enable-feature /ignorecheck
/featurename:\IIS-ApplicationDevelopment\ /featurename:\IIS-ASP\
/featurename:\IIS-ASPNET\ /featurename:\IIS-BasicAuthentication\
/featurename:\IIS-CGI\
/featurename:\IIS-ClientCertificateMappingAuthentication\
/featurename:\IIS-CommonHttpFeatures\ /featurename:\IIS-CustomLogging\
/featurename:\IIS-DefaultDocument\
/featurename:\IIS-DigestAuthentication\
/featurename:\IIS-DirectoryBrowsing\
/featurename:\IIS-HealthAndDiagnostics\
/featurename:\IIS-HostableWebCore\
/featurename:\IIS-HttpCompressionDynamic\
/featurename:\IIS-HttpCompressionStatic\ /featurename:\IIS-HttpErrors\
/featurename:\IIS-HttpLogging\ /featurename:\IIS-HttpRedirect\
/featurename:\IIS-HttpTracing\
/featurename:\IIS-IIS6ManagementCompatibility\
/featurename:\IIS-IISCertificateMappingAuthentication\
/featurename:\IIS-IPSecurity\ /featurename:\IIS-ISAPIExtensions\
/featurename:\IIS-ISAPIFilter\ /featurename:\IIS-LegacyScripts\
/featurename:\IIS-LegacySnapIn\ /featurename:\IIS-LoggingLibraries\
/featurename:\IIS-ManagementConsole\
/featurename:\IIS-ManagementScriptingTools\
/featurename:\IIS-ManagementService\ /featurename:\IIS-Metabase\
/featurename:\IIS-NetFxExtensibility\ /featurename:\IIS-Performance\
/featurename:\IIS-RequestFiltering\ /featurename:\IIS-RequestMonitor\
/featurename:\IIS-Security\ /featurename:\IIS-ServerSideIncludes\
/featurename:\IIS-StaticContent\ /featurename:\IIS-URLAuthorization\
/featurename:\IIS-WebDAV\ /featurename:\IIS-WebServer\
/featurename:\IIS-WebServerManagementTools\
/featurename:\IIS-WebServerRole\
/featurename:\IIS-WindowsAuthentication\
/featurename:\IIS-WMICompatibility\ /featurename:\NetFx3\
/featurename:\WAS-ConfigurationAPI\ /featurename:\WAS-NetFxEnvironment\
/featurename:\WAS-ProcessModel\
/featurename:\WAS-WindowsActivationService\
/featurename:\WCF-HTTP-Activation\ /featurename:\WCF-NonHTTP-Activation\
\${param::AILogFile}\ 21,
returns = ['0','1003', '3010'],
unless = 'REG QUERY
\HKLM\SOFTWARE\HELLO_WORLD\AutoInstall\IISSubTypes\ /v IIS /t REG_DWORD /d
/f 1',
require = Exec['echo Install_IIS']
}
Output if I do a puppet agent --debug --test:
debug: Executing 'c:\Windows\sysnative\dism.exe /online /norestart
/logpath:C:\temp\log.etw.txt /enable-feature /ignor
echeck /featurename:IIS-ApplicationDevelopment /featurename:IIS-ASP
/featurename:IIS-ASPNET /featurename:IIS-Basi
cAuthentication /featurename:IIS-CGI
/featurename:IIS-ClientCertificateMappingAuthentication
/featurename:IIS-Comm
onHttpFeatures /featurename:IIS-CustomLogging
/featurename:IIS-DefaultDocument /featurename:IIS-DigestAuthenticati
on /featurename:IIS-DirectoryBrowsing
/featurename:IIS-HealthAndDiagnostics /featurename:IIS-HostableWebCore
/fea
turename:IIS-HttpCompressionDynamic
/featurename:IIS-HttpCompressionStatic /featurename:IIS-HttpErrors
/featurenam
e:IIS-HttpLogging /featurename:IIS-HttpRedirect
/featurename:IIS-HttpTracing /featurename:IIS-IIS6ManagementCompa
tibility /featurename:IIS-IISCertificateMappingAuthentication
/featurename:IIS-IPSecurity /featurename:IIS-ISAPIEx
tensions /featurename:IIS-ISAPIFilter /featurename:IIS-LegacyScripts
/featurename:IIS-LegacySnapIn /featurename:
IIS-LoggingLibraries /featurename:IIS-ManagementConsole
/featurename:IIS-ManagementScriptingTools /featurename:IIS
-ManagementService /featurename:IIS-Metabase
/featurename:IIS-NetFxExtensibility /featurename:IIS-Performance /fe
aturename:IIS-RequestFiltering /featurename:IIS-RequestMonitor
/featurename:IIS-Security /featurename:IIS-ServerS
ideIncludes /featurename:IIS-StaticContent
/featurename:IIS-URLAuthorization /featurename:IIS-WebDAV /featurename
:IIS-WebServer /featurename:IIS-WebServerManagementTools
/featurename:IIS-WebServerRole /featurename:IIS-WindowsA
uthentication /featurename:IIS-WMICompatibility /featurename:NetFx3
/featurename:WAS-ConfigurationAPI /featurenam
e:WAS-NetFxEnvironment /featurename:WAS-ProcessModel
/featurename:WAS-WindowsActivationService /featurename:WCF-H
TTP-Activation /featurename:WCF-NonHTTP-Activation C:\\Program
Files\\HELLO_WORLD\\log\\IIS7.log 21'
err: /Stage[main]/Win-iis-install::Iis-config/Exec[install_iis]/returns:
[Puppet Users] Re: PuppetDB Connection Failures
Hello Bee, This message is often the result of one of the following: 1) Firewall blocking the puppetdb port 2) DNS issue with the hostname specified in your puppetdb.conf 3) DNS issue with the ssl-host specified in your jetty.ini on the puppetdb server Are you able to connect (e.g. via telnet) from the master machine to port 8081 on the puppetdb machine? Please feel free to jump on the #puppet channel in Freenode if you need rapid assistance! We'll be happy to help. Thanks Chris On Wednesday, October 17, 2012 1:42:06 PM UTC-7, Worker Bee wrote: Hi Everyone; I am now getting a puppetdb connection error when I attempt to run #puppet agent --test Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit 'replace facts' command for puppetdev to PuppetDB at puppetdev:8081: Connection refused - connect(2) puppet.conf [master] storeconfigs = true storeconfigs_backend = puppetdb puppetdb.conf [main] server = puppetdev04 port = 8081 JAVA_ARGS=-Xmx192m I am running 3.0 open source with passenger Using postgres I have the puppetdb daemin running Any advice, as always, would be greatly appreciated! Bee -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/DwtFZvuAGtcJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Puppet dashboard over passenger: The environment must be purely alphanumeric, not ''
Hi andrew, that error is one that comes from the puppet master process itself when you connect to it with a regular HTTP client. So it looks like your apache virtualhost setup is pointing connections to that port/host at the puppetmaster config.ru, not dashboard. Does that help track down the issue? -=Eric On Tuesday, October 16, 2012 12:50:59 PM UTC-7, Andrew Gooding wrote: Hello, I installed puppet-server, passenger and dashboard. I have tested every step in between to make sure all is running well and not errors are carrying forward. Dashboard worked well with my test in WEBrick. After configure the dashboard with passenger I got the message” The environment must be purely alphanumeric, not ''” instead of the dashboard. I verified the configuration files and all look to be in place, but I should be missing something. This is my current environment: CentOS release 6.3 x86_64 puppet-2.7.19-1.el6.noarch puppet-server-2.7.19-1.el6.noarch puppet-dashboard-1.2.12-1.el6.noarch *** LOCAL GEMS *** activemodel (3.2.8) activerecord (3.2.8) activesupport (3.2.8) arel (3.0.2) builder (3.0.3) daemon_controller (1.0.0) fastthread (1.0.7) i18n (0.6.1) json (1.4.6) multi_json (1.3.6) passenger (3.0.17) rack (1.4.1) rake (0.9.2.2, 0.8.7) tzinfo (0.3.33) # rpm -qa | grep ruby ruby-devel-1.8.7.352-7.el6_2.x86_64 ruby-mysql-2.8.2-1.el6.x86_64 ruby-libs-1.8.7.352-7.el6_2.x86_64 ruby-irb-1.8.7.352-7.el6_2.x86_64 rubygems-1.3.7-1.el6.noarch ruby-shadow-1.4.1-13.el6.x86_64 libselinux-ruby-2.0.94-5.3.el6.x86_64 ruby-augeas-0.4.1-1.el6.x86_64 rubygem-json-1.4.6-1.el6.x86_64 rubygem-rake-0.8.7-2.1.el6.noarch ruby-ri-1.8.7.352-7.el6_2.x86_64 ruby-1.8.7.352-7.el6_2.x86_64 ruby-rdoc-1.8.7.352-7.el6_2.x86_64 rpm -qa | grep mysql ruby-mysql-2.8.2-1.el6.x86_64 mysql-5.1.61-4.el6.x86_64 mysql-devel-5.1.61-4.el6.x86_64 mysql-libs-5.1.61-4.el6.x86_64 mysql-server-5.1.61-4.el6.x86_64 Any help will be welcome. Thanks, Andrew -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/WYUESZuF8bMJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: PuppetDB Connection Failures
Thanks so much! I actually got to the bottom of the issue late last night. It was an issue with how I had configured postgres. Thanks everyone! On Thu, Oct 18, 2012 at 12:33 PM, Chris Price ch...@puppetlabs.com wrote: Hello Bee, This message is often the result of one of the following: 1) Firewall blocking the puppetdb port 2) DNS issue with the hostname specified in your puppetdb.conf 3) DNS issue with the ssl-host specified in your jetty.ini on the puppetdb server Are you able to connect (e.g. via telnet) from the master machine to port 8081 on the puppetdb machine? Please feel free to jump on the #puppet channel in Freenode if you need rapid assistance! We'll be happy to help. Thanks Chris On Wednesday, October 17, 2012 1:42:06 PM UTC-7, Worker Bee wrote: Hi Everyone; I am now getting a puppetdb connection error when I attempt to run #puppet agent --test Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit 'replace facts' command for puppetdev to PuppetDB at puppetdev:8081: Connection refused - connect(2) puppet.conf [master] storeconfigs = true storeconfigs_backend = puppetdb puppetdb.conf [main] server = puppetdev04 port = 8081 JAVA_ARGS=-Xmx192m I am running 3.0 open source with passenger Using postgres I have the puppetdb daemin running Any advice, as always, would be greatly appreciated! Bee -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/DwtFZvuAGtcJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- 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 this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Foreman failing for db::migrate for puppet 3.0 with the following error :rake aborted! uninitialized constant HostObserver
Hello Everybody, I am trying to configure foreman for puppet 3.0. on centos 6.3 I have followed the instructions provided over here to install foreman:- http://theforeman.org/projects/foreman/wiki/RPM's_distribution_based_installation I have installed the following rpm: http://yum.theforeman.org/development/el6/foreman-release.rpm I have done the settings for the files in /etc/foreman as follows:- settings.yaml has the following contents: :puppet_server: puppet :unattended: true :puppetconfdir: /etc/puppet/puppet.conf :login: false :require_ssl: false database.yaml has the following contents: # SQLite version 3.x # gem install sqlite3 development: adapter: sqlite3 database: db/development.sqlite3 pool: 5 timeout: 5000 # Warning: The database defined as test will be erased and # re-generated from your development database when you run rake. # Do not set this db to the same as development or production. test: adapter: sqlite3 database: db/test.sqlite3 pool: 5 timeout: 5000 #production: # adapter: sqlite3 # database: db/production.sqlite3 # pool: 5 # timeout: 5000 production: adapter: mysql database: puppetdb username: puppetdb password: puppetdb host: 10.12.14.107 socket: /var/run/mysqld/mysqld.sock I am getting the following error when am trying to execute db:migrate command: su - foreman -s /bin/bash -c /usr/share/foreman/extras/dbmigrate It fails with the following error: /usr/lib/ruby/gems/1.8/gems/ruby_parser-2.3.1/lib/ruby_parser_extras.rb:10: warning: already initialized constant ENC_NONE /usr/lib/ruby/gems/1.8/gems/ruby_parser-2.3.1/lib/ruby_parser_extras.rb:11: warning: already initialized constant ENC_EUC /usr/lib/ruby/gems/1.8/gems/ruby_parser-2.3.1/lib/ruby_parser_extras.rb:12: warning: already initialized constant ENC_SJIS /usr/lib/ruby/gems/1.8/gems/ruby_parser-2.3.1/lib/ruby_parser_extras.rb:13: warning: already initialized constant ENC_UTF8 ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment rake aborted! uninitialized constant HostObserver When i tried to run it with trace option I get the following output: /usr/lib/ruby/gems/1.8/gems/ruby_parser-2.3.1/lib/ruby_parser_extras.rb:10: warning: already initialized constant ENC_NONE /usr/lib/ruby/gems/1.8/gems/ruby_parser-2.3.1/lib/ruby_parser_extras.rb:11: warning: already initialized constant ENC_EUC /usr/lib/ruby/gems/1.8/gems/ruby_parser-2.3.1/lib/ruby_parser_extras.rb:12: warning: already initialized constant ENC_SJIS /usr/lib/ruby/gems/1.8/gems/ruby_parser-2.3.1/lib/ruby_parser_extras.rb:13: warning: already initialized constant ENC_UTF8 ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment rake aborted! uninitialized constant HostObserver /usr/lib/ruby/gems/1.8/gems/rake-0.9.2.2/lib/rake/ext/module.rb:36:in `const_missing' /usr/lib/ruby/gems/1.8/gems/activesupport-3.0.15/lib/active_support/inflector/methods.rb:113:in `constantize' /usr/lib/ruby/gems/1.8/gems/activesupport-3.0.15/lib/active_support/inflector/methods.rb:112:in `each' /usr/lib/ruby/gems/1.8/gems/activesupport-3.0.15/lib/active_support/inflector/methods.rb:112:in `constantize' /usr/lib/ruby/gems/1.8/gems/activesupport-3.0.15/lib/active_support/core_ext/string/inflections.rb:43:in `constantize' /usr/lib/ruby/gems/1.8/gems/activemodel-3.0.15/lib/active_model/observing.rb:66:in `instantiate_observer' /usr/lib/ruby/gems/1.8/gems/activemodel-3.0.15/lib/active_model/observing.rb:39:in `instantiate_observers' /usr/lib/ruby/gems/1.8/gems/activemodel-3.0.15/lib/active_model/observing.rb:39:in `each' /usr/lib/ruby/gems/1.8/gems/activemodel-3.0.15/lib/active_model/observing.rb:39:in `instantiate_observers' /usr/lib/ruby/gems/1.8/gems/activerecord-3.0.15/lib/active_record/railtie.rb:83 /usr/lib/ruby/gems/1.8/gems/activesupport-3.0.15/lib/active_support/lazy_load_hooks.rb:36:in `instance_eval' /usr/lib/ruby/gems/1.8/gems/activesupport-3.0.15/lib/active_support/lazy_load_hooks.rb:36:in `execute_hook' /usr/lib/ruby/gems/1.8/gems/activesupport-3.0.15/lib/active_support/lazy_load_hooks.rb:26:in `on_load' /usr/lib/ruby/gems/1.8/gems/activerecord-3.0.15/lib/active_record/railtie.rb:82 /usr/lib/ruby/gems/1.8/gems/activesupport-3.0.15/lib/active_support/lazy_load_hooks.rb:34:in `call' /usr/lib/ruby/gems/1.8/gems/activesupport-3.0.15/lib/active_support/lazy_load_hooks.rb:34:in `execute_hook' /usr/lib/ruby/gems/1.8/gems/activesupport-3.0.15/lib/active_support/lazy_load_hooks.rb:43:in
[Puppet Users] Re: Foreman failing for db::migrate for puppet 3.0 with the following error :rake aborted! uninitialized constant HostObserver
I am using the following version of Ruby :ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] On Thursday, October 18, 2012 2:20:24 PM UTC-4, Nishant Jain wrote: Hello Everybody, I am trying to configure foreman for puppet 3.0. on centos 6.3 I have followed the instructions provided over here to install foreman:- http://theforeman.org/projects/foreman/wiki/RPM's_distribution_based_installation I have installed the following rpm: http://yum.theforeman.org/development/el6/foreman-release.rpm I have done the settings for the files in /etc/foreman as follows:- settings.yaml has the following contents: :puppet_server: puppet :unattended: true :puppetconfdir: /etc/puppet/puppet.conf :login: false :require_ssl: false database.yaml has the following contents: # SQLite version 3.x # gem install sqlite3 development: adapter: sqlite3 database: db/development.sqlite3 pool: 5 timeout: 5000 # Warning: The database defined as test will be erased and # re-generated from your development database when you run rake. # Do not set this db to the same as development or production. test: adapter: sqlite3 database: db/test.sqlite3 pool: 5 timeout: 5000 #production: # adapter: sqlite3 # database: db/production.sqlite3 # pool: 5 # timeout: 5000 production: adapter: mysql database: puppetdb username: puppetdb password: puppetdb host: 10.12.14.107 socket: /var/run/mysqld/mysqld.sock I am getting the following error when am trying to execute db:migrate command: su - foreman -s /bin/bash -c /usr/share/foreman/extras/dbmigrate It fails with the following error: /usr/lib/ruby/gems/1.8/gems/ruby_parser-2.3.1/lib/ruby_parser_extras.rb:10: warning: already initialized constant ENC_NONE /usr/lib/ruby/gems/1.8/gems/ruby_parser-2.3.1/lib/ruby_parser_extras.rb:11: warning: already initialized constant ENC_EUC /usr/lib/ruby/gems/1.8/gems/ruby_parser-2.3.1/lib/ruby_parser_extras.rb:12: warning: already initialized constant ENC_SJIS /usr/lib/ruby/gems/1.8/gems/ruby_parser-2.3.1/lib/ruby_parser_extras.rb:13: warning: already initialized constant ENC_UTF8 ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment rake aborted! uninitialized constant HostObserver When i tried to run it with trace option I get the following output: /usr/lib/ruby/gems/1.8/gems/ruby_parser-2.3.1/lib/ruby_parser_extras.rb:10: warning: already initialized constant ENC_NONE /usr/lib/ruby/gems/1.8/gems/ruby_parser-2.3.1/lib/ruby_parser_extras.rb:11: warning: already initialized constant ENC_EUC /usr/lib/ruby/gems/1.8/gems/ruby_parser-2.3.1/lib/ruby_parser_extras.rb:12: warning: already initialized constant ENC_SJIS /usr/lib/ruby/gems/1.8/gems/ruby_parser-2.3.1/lib/ruby_parser_extras.rb:13: warning: already initialized constant ENC_UTF8 ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment rake aborted! uninitialized constant HostObserver /usr/lib/ruby/gems/1.8/gems/rake-0.9.2.2/lib/rake/ext/module.rb:36:in `const_missing' /usr/lib/ruby/gems/1.8/gems/activesupport-3.0.15/lib/active_support/inflector/methods.rb:113:in `constantize' /usr/lib/ruby/gems/1.8/gems/activesupport-3.0.15/lib/active_support/inflector/methods.rb:112:in `each' /usr/lib/ruby/gems/1.8/gems/activesupport-3.0.15/lib/active_support/inflector/methods.rb:112:in `constantize' /usr/lib/ruby/gems/1.8/gems/activesupport-3.0.15/lib/active_support/core_ext/string/inflections.rb:43:in `constantize' /usr/lib/ruby/gems/1.8/gems/activemodel-3.0.15/lib/active_model/observing.rb:66:in `instantiate_observer' /usr/lib/ruby/gems/1.8/gems/activemodel-3.0.15/lib/active_model/observing.rb:39:in `instantiate_observers' /usr/lib/ruby/gems/1.8/gems/activemodel-3.0.15/lib/active_model/observing.rb:39:in `each' /usr/lib/ruby/gems/1.8/gems/activemodel-3.0.15/lib/active_model/observing.rb:39:in `instantiate_observers' /usr/lib/ruby/gems/1.8/gems/activerecord-3.0.15/lib/active_record/railtie.rb:83 /usr/lib/ruby/gems/1.8/gems/activesupport-3.0.15/lib/active_support/lazy_load_hooks.rb:36:in `instance_eval' /usr/lib/ruby/gems/1.8/gems/activesupport-3.0.15/lib/active_support/lazy_load_hooks.rb:36:in `execute_hook' /usr/lib/ruby/gems/1.8/gems/activesupport-3.0.15/lib/active_support/lazy_load_hooks.rb:26:in `on_load' /usr/lib/ruby/gems/1.8/gems/activerecord-3.0.15/lib/active_record/railtie.rb:82
Re: [Puppet Users] dynamic data in hiera
For further reference: I found the problem with the CPU burning. It seems
hiera lookups can end up in an endless loop when specifying meaningful
regex characters (like $,+,?) in your lookup variables.
So specifying key:%{$var} will cause an endless loop. I created a ticket
http://projects.puppetlabs.com/issues/17094 to address the issue and
suggested a possible fix (using Regexp.escape) .
Otherwise, hiera is a great tool to work with! Such a level of flexibility
you add to your puppet environment!
Peter
On Wed, Oct 17, 2012 at 11:54 PM, Peter De Cleyn peter.decl...@gmail.comwrote:
No, just plain manifests and hiera yaml files.
Peter
On 17 Oct 2012, at 19:36, Douglas Brancaglion douglas.rea...@gmail.com
wrote:
i have the same problem with cpu...
You are using stororeconfigs?
Douglas Brancaglion
2012/10/17 pdcleyn peter.decl...@gmail.com
thx! that works!
However, in testing just now I bumped against something strange. When I
add %{$nodeID} (which I should not), the CPU usage of the puppet master
shoots to 100% and stays there. The client will eventually time out
(execution expired) and the puppet master keeps burning CPU cycles. This is
a test setup up, so no other nodes are connected but one and it is quite
reproducable on this setup. Is this a known issue?
Peter
Op woensdag 17 oktober 2012 16:30:03 UTC+2 schreef R.I. Pienaar het
volgende:
- Original Message -
From: Peter De Cleyn pe...@decleyn.net
To: puppet...@googlegroups.com
Sent: Wednesday, October 17, 2012 3:24:30 PM
Subject: [Puppet Users] dynamic data in hiera
Hi list,
I wondered if I could include 'dynamic' data inside a hiera yaml
file. I would like to be able to add variables in scope of the
resource which performs a hiera call. So e.g.
in hiera yaml:
address: 192.168.1.#{nodeID}
try %{nodeID}
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/uoayA6QJge8J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
Douglas Brancaglion
Security Analist
--
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 this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
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 this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announce: Puppet 3.0.1 Available
Puppet 3.0.1 is a bugfix release for the 3.x series of Puppet. To see a list of the issues addressed by this release, check out the 3.0.1 version in our issue tracter at: https://projects.puppetlabs.com/versions/328. This release contains contributions from the following people: Andrew Parker, Jeff McCune, Josh Cooper, Matthaus Owens, Moses Mendoza, Nick Fagerlund, Niels Abspoel, Patrick Carlisle, Stijn Tintel, and Will Farrington. Downloads are available at: * Source https://downloads.puppetlabs.com/puppet/puppet-3.0.1.tar.gz RPMs are available at https://yum.puppetlabs.com Debs are available at https://apt.puppetlabs.com Gems are available via rubygems at https://rubygems.org/downloads/puppet-3.0.1.gem or by using `gem install puppet` Mac packages are available at https://downloads.puppetlabs.com/mac/puppet-3.0.1.dmg Windows packages are available at https://downloads.puppetlabs.com/windows/puppet-3.0.1.msi See the Verifying Puppet Download section at: https://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet Please report feedback via the Puppet Labs Redmine site, using an affected puppet version of 3.0.1: https://projects.puppetlabs.com/projects/puppet/ Puppet 3.0.1 Changelog Andrew Parker (9): (#15717) Require puppet/run in the agent (#15717) Allow pluginsync as an option to Puppet::Run (#16698) Do not set Node cache_terminus for storedconfigs (#16698) Add acceptance test for using store configs with an enc (#16922) Quote strings that contain : (#16922) Quote strings that contain : (#16698) Exclude enc+storeconfig test from solaris (Maint) Fix acceptance test to work on centos5 (Maint) Exclude test from windows Jeff McCune (6): (maint) Add .yardopts file (maint) Add yard generated documentation to git ignore (#16637) Add spec test for non-root puppet master confdir and vardir (#16637) Fix default confdir and vardir with puppet master as normal user (Maint) Update config.ru to fix issue with vardir (#16769) Fix header too long error with ExportCertData Josh Cooper (9): (#15717) Acceptance tests for puppet kick (#15717) Kick agent using its fqdn (#16757) Move rubygems require to application entry point (#16757) Deprecate Puppet.features.rubygems? (#16757) Don't require rubygems (#16757) Prevent using rubygems when bundler is in use (#16801) Remove mongrel references from manpage (#16801) Remove mongrel references (#17000) Use --no-client argument to prevent agent from starting Matthaus Litteken (1): (#16376) Fix rails compatibility layer for activerecord 3.0 Matthaus Owens (9): (#16801) Remove mongrel references from init scripts Maint: Retab puppetmaster init scripts Maint: Remove unused $prog variable from redhat puppetmaster init script Update redhat logrotate to signal correct process Remove unused suse packaging files (#16801) Update suse server.init and remove mongrel refs Update suse client.init for new pidfile, process name Update suse puppet.spec for Telly Update PUPPETVERSION for 3.0.1-rc1 Moses Mendoza (2): fail better in package repo rake tasks Update PUPPETVERSION for 3.0.1 Nick Fagerlund (1): (#16585) Remove dead ldapnodes setting Niels Abspoel (2): This will fix Refactor #16643. sample_module.pp refactored text: include sample-module into include sample_module Patrick Carlisle (2): (#16757) Only load rubygems in bin/puppet (#16757) Don't load rubygems if bundler is running Stijn Tintel (2): (#16801) Remove lib/puppet/network/http/mongrel (#16801) Remove mongrel_spec.rb as it is no longer in use. Will Farrington (1): Fix up dependencies for Hiera and Facter in RubyGems. -- 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 this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Using Puppet to push Windows Updates?
Hi, I'm very new to puppet but am looking to implement it in our environment. One thing I'm struggling with is that I would like Puppet to be the only tool that makes changes to our servers, but as we run Windows for most of our systems, we need to run the continuous onslaught of Windows updates as well as normal configuration changes and software installation / updates. Are there any recommendations on how to use puppet to achieve this task? I don't really want to go download every windows update installer and build it into a manifest to push out. Any advice? Resource suggestions? -David -- 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 this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Puppet 3.0 upgrade issue
I'm running into a similar problem; however, even the changes to config.ru
don't seem to make a difference. First, here are the GEMs I have
installed:
daemon_controller (1.0.0)
facter (1.6.13)
fastthread (1.0.7)
ffi (1.1.5)
hiera (1.1.0, 1.0.0)
json (1.7.5)
libvirt-ruby (1.0.2)
passenger (3.0.17)
puppet (3.0.1)
puppet-lint (0.3.1)
puppet-module (0.3.4)
rack (1.4.1)
rack-protection (1.2.0)
rake (0.9.2.2)
rubygems-update (1.8.24)
sinatra (1.3.3)
stomp (1.2.6)
tilt (1.3.3)
tzinfo (0.3.33)
I built a staging system to test out Puppet 3.0.1 and Passenger, latest
versions. I have another similar system, running Puppet 2.x with
Passenger which is working fine.
Here is my config.ru (hash comments removed for brevity):
$0 = master
ARGV --rack
ARGV --confdir /etc/puppet
require 'puppet/util/command_line'
run Puppet::Util::CommandLine.new.execute
The file is owned by puppet:puppet as is the Rack directory, which is
/etc/puppet/rack/puppetmasterd/public
My /etc/httpd/conf.d/passenger.conf is simple enough:
LoadModule passenger_module
/usr/local/lib/ruby/gems/1.8/gems/passenger-3.0.17/ext/apache2/mod_passenger.so
PassengerRoot /usr/local/lib/ruby/gems/1.8/gems/passenger-3.0.17
PassengerRuby /usr/local/bin/ruby
Listen 8140
VirtualHost *:8140
SSLEngine On
# SSLCipherSuite SSLv2:-LOW:-EXPORT:RC4+RSA
SSLCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:-LOW:-SSLv2:-EXP
SSLCertificateFile /var/lib/puppet/ssl/certs/stage1.myserver.com.pem
SSLCertificateKeyFile
/var/lib/puppet/ssl/private_keys/stage1.myserver.com.pem
SSLCertificateChainFile /var/lib/puppet/ssl/ca/ca_crt.pem
SSLCACertificateFile /var/lib/puppet/ssl/ca/ca_crt.pem
SSLCARevocationFile /var/lib/puppet/ssl/ca/ca_crl.pem
SSLVerifyClient optional
SSLVerifyDepth 1
SSLOptions +StdEnvVars
# The following client headers allow the same configuration to work with
Pound.
RequestHeader set X-SSL-Subject %{SSL_CLIENT_S_DN}e
RequestHeader set X-Client-DN %{SSL_CLIENT_S_DN}e
RequestHeader set X-Client-Verify %{SSL_CLIENT_VERIFY}e
PassengerHighPerformance on
PassengerMaxPoolSize 15
PassengerPoolIdleTime 300
PassengerUseGlobalQueue on
PassengerStatThrottleRate 120
RackAutoDetect On
RailsAutoDetect Off
RackBaseURI /
DocumentRoot /etc/puppet/rack/puppetmasterd/public
Directory /etc/puppet/rack/puppetmasterd/public
Options None
AllowOverride None
Order allow,deny
allow from all
/Directory
/VirtualHost
I've tried this with the AutoDetect of Rails and Rack on|off. What I see
is httpd starts up fine, along with the Passenger processes, but there is
no puppet.
I can run puppet by itself with no trouble, however.
I've been poring over this since yesterday and I honestly can't figure out
what's wrong. Unless it has to do with GEM versions that are not working
correctly?
Before I put this out into production, I want to be sure the steps to get
this working are clearly documented in case it breaks, etc.
Thanks.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/xro1t8Kr10gJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Puppet 3.0 upgrade issue
On Thu, Oct 18, 2012 at 2:37 PM, Forrie for...@gmail.com wrote: Here is my config.ru (hash comments removed for brevity): $0 = master ARGV --rack ARGV --confdir /etc/puppet require 'puppet/util/command_line' run Puppet::Util::CommandLine.new.execute I overlooked a setting for 3.0.0 and it's fixed in the 3.0.1 example config.ru. https://github.com/puppetlabs/puppet/blob/master/ext/rack/files/config.ru#L14-18 Could you try adding ARGV --vardir /var/lib/puppet (Or, whatever is the default for your platform)? -Jeff -- 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 this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Puppet 3.0 upgrade issue
Is it the case that the application doesn't technically exist until an agent tries to hit the port? On Thursday, October 18, 2012 2:52:16 PM UTC-7, Forrie wrote: I added that and restarted httpd (stop, then start) and still no luck. Here is what passenger-status says: --- General information --- max = 15 count= 0 active = 0 inactive = 0 Waiting on global queue: 0 --- Application groups --- So it's not even seeing the Application.Yet, something binds to the port as I can't start puppet master while Passenger is running. My Platform is CentOS 5 64-bit. On Thursday, October 18, 2012 5:48:08 PM UTC-4, Jeff McCune wrote: On Thu, Oct 18, 2012 at 2:37 PM, Forrie for...@gmail.com wrote: Here is my config.ru (hash comments removed for brevity): $0 = master ARGV --rack ARGV --confdir /etc/puppet require 'puppet/util/command_line' run Puppet::Util::CommandLine.new.execute I overlooked a setting for 3.0.0 and it's fixed in the 3.0.1 example config.ru. https://github.com/puppetlabs/puppet/blob/master/ext/rack/files/config.ru#L14-18 Could you try adding ARGV --vardir /var/lib/puppet (Or, whatever is the default for your platform)? -Jeff -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/wvLwETvqavkJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Using Puppet to push Windows Updates?
Hi David, On Thu, Oct 18, 2012 at 1:02 PM, David Groce dgr...@tableausoftware.com wrote: Hi, I'm very new to puppet but am looking to implement it in our environment. One thing I'm struggling with is that I would like Puppet to be the only tool that makes changes to our servers, but as we run Windows for most of our systems, we need to run the continuous onslaught of Windows updates as well as normal configuration changes and software installation / updates. Are there any recommendations on how to use puppet to achieve this task? I don't really want to go download every windows update installer and build it into a manifest to push out. Any advice? Resource suggestions? -David -- 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 this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. If you are okay using the built-in windows update capability, you could create an exec resource to run during specified change windows, using the schedule metaparameter: http://docs.puppetlabs.com/references/latest/metaparameter.html#schedule Your exec resource could just execute a powershell script to trigger the update, something like: http://www.flobee.net/programmatically-run-windows-update-as-part-of-a-broader-patch-and-reboot-process/ Josh -- Josh Cooper Developer, Puppet Labs -- 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 this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Puppet 3.0 upgrade issue
Interesting question - I tested this out and it does indeed seem to be the case. Unexpected behavior, however. On Thursday, October 18, 2012 6:02:22 PM UTC-4, Ellison Marks wrote: Is it the case that the application doesn't technically exist until an agent tries to hit the port? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/BKqbvuxDKDEJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Puppet 3.0 upgrade issue
On 10/18/2012 3:36 PM, Forrie wrote: Interesting question - I tested this out and it does indeed seem to be the case. Unexpected behavior, however. Standard behavior under Passenger. If you want Puppet to start immediately when the webserver starts do the following. 1. Make sure you're using Passenger 3.0.x 2. Add this line to the bottom of your Puppet vhost outside the VirtualHost bits PassengerPreStart https://puppet.mydomain.com:8140 3. Assuming you want Puppet Rack process running at all times, set this in your passenger module conf file or also in the vhost file PassengerMinInstances 1 Ramin -- 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 this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Puppet 3.0: Not authorized to call find on /file_metadata, more issues?
I've just built a staging system, to work out the issues I've been having with Puppet 3.x. We now have 3.0.1 installed there. I am again running into this fileserver issue and the same errors. I read through some complaints here and I see mention that auth.conf is only able to use allow_ip. In that file, I have allow * under path /file which should allow everyone. I read that the allow_ip is not yet working for fileserver.conf. My fileserver.conf has allow 192.168.0.0/24 which was working until the upgrade. So, can someone explain to me in plain english how we're supposed to get this working properly now. I read through more notes and I don't see mention of this in upgrading, etc. Perhaps I missed something -- I just want to get it working. If it's an outstanding but that is preventing Puppet from working right now, I would think this would be a high-priority fix :-) Thanks. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/wvCuF3fd2H8J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Puppet 3.0 upgrade issue
Thanks for that pointer... I put that in my config. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/oHhOu4PZsb0J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] How catch a notify inside a define
Hi,
I have created a define with packages services and a mount inside, but when
I notify the define all of them receive the notify but I want only refresh
the mount.
It is possible?
Here is my define:
define xmount (
$device= undef,
$device_base = undef,
$device_qa = undef,
$device_dev= undef,
$options = defaults,
$options_base = undef,
$options_qa= undef,
$options_dev = undef,
$path = undef,
$atboot= true,
$ensure= mounted,
$fstype= undef,
$remounts = true,
$remounts_lazy = false,
$dump = 0,
$pass = 0) {
if ($fstype = nfs) {
if !defined(Package[portmap]) {
package { portmap: ensure = present; }
}
if !defined(Package[initscripts]) {
package { initscripts: ensure = present; }
}
if !defined(Service[portmap]) {
service { portmap:
enable = true,
ensure = running,
hasrestart = true,
hasstatus = true,
subscribe = Package[portmap, initscripts],
notify = Mount[${path}];
}
}
if !defined(Service[netfs]) {
service { netfs:
enable = true,
ensure = running,
hasrestart = true,
hasstatus = true,
subscribe = Package[portmap, initscripts],
notify = Mount[${path}];
}
}
}
case $pool {
default: {
$deviceA = $device
$optionsA = $options
}
/.*-q-prt$/, /.*-q-pla$/, /.*-qa$/ : {
$deviceA = $device_qa
$optionsA = $options_qa
}
/.*-s-prt$/, /.*-s-pla$/, /.*-stg$/, /.*-dev$/ : {
$deviceA = $device_dev
$optionsA = $options_dev
}
/.*-base$/ : {
$deviceA = $device_base
$optionsA = $options_base
}
}
$device_chosed = ${deviceA} ? {
default = ${deviceA},
undef = ${device}
}
$options_chosed = ${optionsA} ? {
default = ${optionsA},
undef = ${options}
}
if ($device_chosed != ) {
exec { define_xmount_recursedir-${title}-${path}:
command = mkdir -p '${path}',
unless= test -d '${path}',
cwd = /tmp,
logoutput = on_failure,
path = [
/bin,
/sbin,
/usr/bin,
/usr/sbin],
timeout = 2;
}
mount { ${path}:
atboot = $atboot,
device = $mount_chosed,
ensure = $ensure,
fstype = $fstype,
options = $options_chosed,
remounts = $remounts,
dump = $dump,
pass = $pass,
require = Exec[define_xmount_recursedir-${title}-${path}];
}
}
}
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/86W7_S9LIUAJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] dynamic data in hiera
On Thursday, October 18, 2012 11:39:05 AM UTC-7, pdcleyn wrote:
... endless loop when specifying meaningful regex characters (like $,+,?)
in your lookup variables.
Oh! That's probably exactly what happened when I was experimenting w/
interpolating members of hash and array vars received from Puppet. (i.e.
testvalue: %{myhash['some_key']} )
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/4jmQ_Rm5gd4J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Setting directory permission on when copying directory contents using recurse = remote...
I am trying to copy out the contents of home directories via puppet while
controlling the home directory permissions at the same time and I am stuck.
I don't see a good way to copy contents of a directory using the remote
directive while still managing the directory permissions directly.
e.g. I want to set $home to owner/group ${user}/${group} and enforce the
mode of 0700. I would like to copy all of the files from the source intact
with no permission or ownership changes.
I would like to see something like the following:
file { $home:
path = puppet://modules/users/${user},
mode = 0700,
owner = ${user},
group = ${group},
require = User[${user}],
recurselimit = 1,
}
Where the recurselimit setting of 1 (or some other sensible setting) makes
the directory the only item that gets managed.
Thanks,
--Robert
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/nRcEg8YF4YUJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] pocco - a puppet manifest documentation experiment
Hi! The existing puppet manifests documentation generated via rdoc isn't very dry. I quite like docco generated documentation so I borrowed from rocco to create a puppet manifests documentation tool called pocco. Here's a module that will install the tool: https://github.com/nanliu/puppet-pocco Here's a sample documentation generated from the manifest in the module: http://nanliu.github.com/puppet-pocco/ WARNING: unless pymentize is installed, manifests are shipped to pygments.appspot.com for highlighting, so don't try this on anything sensitive. It's just an experiment, but feel free to provide feedback. Thanks, Nan -- 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 this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
