Re: [Puppet Users] Re: apache 2.4 support in puppetlabs/apache
Hi, I did fork the repo and submitted a pull request but I don't think it has been merged yet. My for is here if that helps. https://github.com/rendhalver/puppetlabs-apache I have been pretty busy lately and I haven't had a chance to chase up what is happening. On 24 July 2013 00:09, Pawel Tomulik ptomu...@meil.pw.edu.pl wrote: Pete, do you have any info regarding 2.4 support? Have you been successful with creating the fork mentioned? I'm playing with FreeBSD (9.x+) support and wish to have apache 2.4 at once. W dniu wtorek, 12 lutego 2013 07:19:00 UTC+1 użytkownik Pete napisał: Just letting people know I have made a start on this. It seems the best way to achieve it is to write a custom fact or two and a couple of functions. Will setup a fork of the code soon and put my results in it. I will post a link to my fork if anyone wants to help test once I have it setup. On 12 February 2013 10:14, Peter Brown rendh...@gmail.com wrote: Hi everyone, I started testing out the puppetlabs/apache module from forge on a Fedora 18 server and noticed it doesn't have multiple version support for apache. Fedora 18 runs apache 2.4 and there are a few of modules that don't exist any more and a few config changes. I was pondering forking the module on github and adding attempting to add support for apache 2.4 but I thought I would check if anyone is working on this before I proceed. Good work on the module by the way. Pete. -- 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: 3.2.2 on CentOS 6.3, and Did not receive certificate
When having problems like this it is often a good idea to shut down the Apache web server and run: # puppet master --debug from a console instead. If that works then your Puppet setup is okay and you should look at your web server and passenger config. - Keith On 18 Jul 2013 20:21, Forrie for...@gmail.com wrote: Actually, with the improvements to Puppet 3.x, I wonder if it's really necessary to run Puppet under Passenger anymore... we have less than 100 hosts, but that could change. -- 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] Debugging Puppetmaster with Apache/Rack/Passenger
I believe the --debug in config.ru sends output to syslog so either look in
/var/log/messages (or similar) or specify a log destination filename like:
ARGV --logdest /var/log/puppet/puppet-master.log
- Keith
On 23 Jul 2013 09:15, Christian Flamm christian.le.fl...@gmail.com
wrote:
Hi,
I'm currently trying to debug a performance issue I'm having. Therefore I
would need DEBUG output. When using one puppetmaster process, this is
fairly easy by starting it like this:
puppet master --no-daemonize --debug
Now I need to see this debug output when running puppetmaster the way I
ususally do - using Apache/Rack/Passenger. After looking around a bit in
the vhost config file
cat /etc/httpd/conf.d/puppetmaster.conf
LoadModule passenger_module
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.10/buildout/apache2/mod_passenger.so
PassengerRoot /usr/lib/ruby/gems/1.8/gems/passenger-4.0.10
PassengerDefaultRuby /usr/bin/ruby
# TODO evaluate benefit of ThrottleRate
PassengerStatThrottleRate 120
PassengerHighPerformance On
PassengerMaxPoolSize 12
PassengerMaxRequests 1000
PassengerPoolIdleTime 600
Listen 8140
VirtualHost *:8140
SSLEngine On
# Only allow high security cryptography. Alter if needed for
compatibility.
SSLProtocol All -SSLv2
SSLCipherSuite HIGH:!ADH:RC4+RSA:-MEDIUM:-LOW:-EXP
SSLCertificateFile /var/lib/puppet/ssl/certs/puppetmaster
.pem
SSLCertificateKeyFile /var/lib/puppet/ssl/private_keys/
puppetmaster.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 +ExportCertData
# These request headers are used to pass the client certificate
# authentication information on to the puppet master process
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
DocumentRoot /usr/share/puppet/rack/puppetmasterd/public/
Directory /usr/share/puppet/rack/puppetmasterd/
Options None
AllowOverride None
Order Allow,Deny
Allow from All
/Directory
/VirtualHost
I had a look at /usr/share/puppet/rack/puppetmasterd/config.ru which
contains this:
[snippet]
# if you want debugging:
# ARGV --debug
... so I enabled it. But this actually only gives me extra lines I believe
belong to INFO log level:
Jul 22 17:17:47 puppetmaster puppet-master[22132]:
(access[^/catalog/([^/]+)$]) allowing 'method' find Jul 22 17:17:47
puppetmaster puppet-master[22132]: (access[^/catalog/([^/]+)$]) allowing
$1 access Jul 22 17:17:47 puppetmaster puppet-master[22132]:
(access[^/node/([^/]+)$]) allowing 'method' find Jul 22 17:17:47
puppetmaster puppet-master[22132]: (access[^/node/([^/]+)$]) allowing $1
access Jul 22 17:17:47 puppetmaster puppet-master[22132]:
(access[/certificate_revocation_list/ca]) allowing 'method' find Jul
22 17:17:47 puppetmaster puppet-master[22132]:
(access[/certificate_revocation_list/ca]) allowing * access Jul 22
17:17:47 puppetmaster puppet-master[22132]: (access[/report]) allowing
'method' save Jul 22 17:17:47 puppetmaster puppet-master[22132]:
(access[/report]) allowing * access Jul 22 17:17:47 puppetmaster
puppet-master[22132]: (access[/file]) allowing * access Jul 22
17:17:47 puppetmaster puppet-master[22132]: (access[/certificate/ca])
adding authentication any Jul 22 17:17:47 puppetmaster
puppet-master[22132]: (access[/certificate/ca]) allowing 'method' find
Jul 22 17:17:47 puppetmaster puppet-master[22132]:
(access[/certificate/ca]) allowing * access Jul 22 17:17:47
puppetmaster puppet-master[22132]: (access[/certificate/]) adding
authentication any Jul 22 17:17:47 puppetmaster
puppet-master[22132]: (access[/certificate/]) allowing 'method' find Jul
22 17:17:47 puppetmaster puppet-master[22132]: (access[/certificate/])
allowing * access Jul 22 17:17:47 puppetmaster
puppet-master[22132]: (access[/certificate_request]) adding authentication
any Jul 22 17:17:47 puppetmaster puppet-master[22132]:
(access[/certificate_request]) allowing 'method' find Jul 22 17:17:47
puppetmaster puppet-master[22132]: (access[/certificate_request])
allowing 'method' save Jul 22 17:17:47 puppetmaster
puppet-master[22132]: (access[/certificate_request]) allowing * access
Jul 22 17:17:47 puppetmaster puppet-master[22132]: (access[/]) adding
authentication any Jul 22 17:17:47 puppetmaster
puppet-master[22132]: Inserting default '~ ^/report/([^/]+)$' (auth true)
Re: [Puppet Users] Debugging Puppetmaster with Apache/Rack/Passenger
Did what you posted.
Strange thing happened: nothing appears in the specified logdest. Instead:
the (wanted) debug output it now sent to apache's error log!
I have no idea what's going on - but at least I have the output I was
looking for :-/
Thanks,
Christian
Am Mittwoch, 24. Juli 2013 09:42:14 UTC+2 schrieb Keith Burdis:
I believe the --debug in config.ru sends output to syslog so either look
in /var/log/messages (or similar) or specify a log destination filename
like:
ARGV --logdest /var/log/puppet/puppet-master.log
- Keith
On 23 Jul 2013 09:15, Christian Flamm
christian...@gmail.comjavascript:
wrote:
Hi,
I'm currently trying to debug a performance issue I'm having. Therefore I
would need DEBUG output. When using one puppetmaster process, this is
fairly easy by starting it like this:
puppet master --no-daemonize --debug
Now I need to see this debug output when running puppetmaster the way I
ususally do - using Apache/Rack/Passenger. After looking around a bit in
the vhost config file
cat /etc/httpd/conf.d/puppetmaster.conf
LoadModule passenger_module
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.10/buildout/apache2/mod_passenger.so
PassengerRoot /usr/lib/ruby/gems/1.8/gems/passenger-4.0.10
PassengerDefaultRuby /usr/bin/ruby
# TODO evaluate benefit of ThrottleRate
PassengerStatThrottleRate 120
PassengerHighPerformance On
PassengerMaxPoolSize 12
PassengerMaxRequests 1000
PassengerPoolIdleTime 600
Listen 8140
VirtualHost *:8140
SSLEngine On
# Only allow high security cryptography. Alter if needed for
compatibility.
SSLProtocol All -SSLv2
SSLCipherSuite HIGH:!ADH:RC4+RSA:-MEDIUM:-LOW:-EXP
SSLCertificateFile /var/lib/puppet/ssl/certs/puppetmaster
.pem
SSLCertificateKeyFile /var/lib/puppet/ssl/private_keys/
puppetmaster.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 +ExportCertData
# These request headers are used to pass the client certificate
# authentication information on to the puppet master process
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
DocumentRoot /usr/share/puppet/rack/puppetmasterd/public/
Directory /usr/share/puppet/rack/puppetmasterd/
Options None
AllowOverride None
Order Allow,Deny
Allow from All
/Directory
/VirtualHost
I had a look at /usr/share/puppet/rack/puppetmasterd/config.ru which
contains this:
[snippet]
# if you want debugging:
# ARGV --debug
... so I enabled it. But this actually only gives me extra lines I
believe belong to INFO log level:
Jul 22 17:17:47 puppetmaster puppet-master[22132]:
(access[^/catalog/([^/]+)$]) allowing 'method' find Jul 22 17:17:47
puppetmaster puppet-master[22132]: (access[^/catalog/([^/]+)$]) allowing
$1 access Jul 22 17:17:47 puppetmaster puppet-master[22132]:
(access[^/node/([^/]+)$]) allowing 'method' find Jul 22 17:17:47
puppetmaster puppet-master[22132]: (access[^/node/([^/]+)$]) allowing $1
access Jul 22 17:17:47 puppetmaster puppet-master[22132]:
(access[/certificate_revocation_list/ca]) allowing 'method' find Jul
22 17:17:47 puppetmaster puppet-master[22132]:
(access[/certificate_revocation_list/ca]) allowing * access Jul 22
17:17:47 puppetmaster puppet-master[22132]: (access[/report]) allowing
'method' save Jul 22 17:17:47 puppetmaster puppet-master[22132]:
(access[/report]) allowing * access Jul 22 17:17:47 puppetmaster
puppet-master[22132]: (access[/file]) allowing * access Jul 22
17:17:47 puppetmaster puppet-master[22132]: (access[/certificate/ca])
adding authentication any Jul 22 17:17:47 puppetmaster
puppet-master[22132]: (access[/certificate/ca]) allowing 'method' find
Jul 22 17:17:47 puppetmaster puppet-master[22132]:
(access[/certificate/ca]) allowing * access Jul 22 17:17:47
puppetmaster puppet-master[22132]: (access[/certificate/]) adding
authentication any Jul 22 17:17:47 puppetmaster
puppet-master[22132]: (access[/certificate/]) allowing 'method' find Jul
22 17:17:47 puppetmaster puppet-master[22132]: (access[/certificate/])
allowing * access Jul 22 17:17:47 puppetmaster
puppet-master[22132]: (access[/certificate_request]) adding authentication
any Jul 22 17:17:47 puppetmaster puppet-master[22132]:
(access[/certificate_request]) allowing 'method'
[Puppet Users] Re: node_aws installation problem
Hi, tried to play around with the RUBYLIB env var but doesn't seam to help in any way. Any ideas? Thanks, Piotr W dniu wtorek, 23 lipca 2013 17:10:55 UTC+1 użytkownik Piotr Jasiulewicz napisał: Hi, got the whole list root@ip-10-55-86-66:/home/ubuntu# gem list *** LOCAL GEMS *** builder (3.2.2) excon (0.25.3) fog (1.14.0) formatador (0.2.4) guid (0.1.1) mime-types (1.23) mini_portile (0.5.1) minitest (1.6.0) multi_json (1.7.7) net-scp (1.1.2) net-ssh (2.6.8) nokogiri (1.6.0) rake (0.8.7) rdoc (2.5.8) ruby-hmac (0.4.0) just got the newest one... Cheers, Piotr W dniu wtorek, 23 lipca 2013 17:09:04 UTC+1 użytkownik shivaraj mathrubai napisał: What is the version of Fog you have ? When you do Puppet Help do you see an exclamation mark next to node_aws ? On Tuesday, 23 July 2013 16:16:19 UTC+1, Piotr Jasiulewicz wrote: Hi, yeap, it;s installed allright: root@X:/home/ubuntu# gem install guid Successfully installed guid-0.1.1 1 gem installed Installing ri documentation for guid-0.1.1... Installing RDoc documentation for guid-0.1.1... getting this every time, not sure if that's correct. Maybe the version is wrong? cheers, Piotr W dniu wtorek, 23 lipca 2013 16:11:20 UTC+1 użytkownik shivaraj mathrubai napisał: Did you install guid ? On Tuesday, 23 July 2013 11:03:14 UTC+1, Piotr Jasiulewicz wrote: Hi everyone! having a slight problem with the installing the cloud provisioning module [code] http://docs.puppetlabs.com/guides/cloud_pack_getting_started.html [/code] everything worked until I wanted to actually try to fire it up: [code] puppet node_aws list Error: Could not autoload puppet/face/node_aws/fingerprint: cannot load such file -- guid Error: Could not parse application options: Could not autoload puppet/face/node_aws/fingerprint: cannot load such file -- guid [/code] I have fog configured with my AWS credentials but it seams like the installation is just faulty, anyone any clue? Thanks, Piotr -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Debugging Puppetmaster with Apache/Rack/Passenger
Debug output is sent to Apache error log, because of missing permissions to
write to the defined logdest.
So - bottom line - thanks for your reply, --logdest is necessary. Without
it debug output is (per default) not sent to /var/log/messages.
Am Mittwoch, 24. Juli 2013 09:59:40 UTC+2 schrieb Christian Flamm:
Did what you posted.
Strange thing happened: nothing appears in the specified logdest. Instead:
the (wanted) debug output it now sent to apache's error log!
I have no idea what's going on - but at least I have the output I was
looking for :-/
Thanks,
Christian
Am Mittwoch, 24. Juli 2013 09:42:14 UTC+2 schrieb Keith Burdis:
I believe the --debug in config.ru sends output to syslog so either look
in /var/log/messages (or similar) or specify a log destination filename
like:
ARGV --logdest /var/log/puppet/puppet-master.log
- Keith
On 23 Jul 2013 09:15, Christian Flamm christian...@gmail.com wrote:
Hi,
I'm currently trying to debug a performance issue I'm having. Therefore
I would need DEBUG output. When using one puppetmaster process, this
is fairly easy by starting it like this:
puppet master --no-daemonize --debug
Now I need to see this debug output when running puppetmaster the way I
ususally do - using Apache/Rack/Passenger. After looking around a bit in
the vhost config file
cat /etc/httpd/conf.d/puppetmaster.conf
LoadModule passenger_module
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.10/buildout/apache2/mod_passenger.so
PassengerRoot /usr/lib/ruby/gems/1.8/gems/passenger-4.0.10
PassengerDefaultRuby /usr/bin/ruby
# TODO evaluate benefit of ThrottleRate
PassengerStatThrottleRate 120
PassengerHighPerformance On
PassengerMaxPoolSize 12
PassengerMaxRequests 1000
PassengerPoolIdleTime 600
Listen 8140
VirtualHost *:8140
SSLEngine On
# Only allow high security cryptography. Alter if needed for
compatibility.
SSLProtocol All -SSLv2
SSLCipherSuite HIGH:!ADH:RC4+RSA:-MEDIUM:-LOW:-EXP
SSLCertificateFile /var/lib/puppet/ssl/certs/puppetmaster
.pem
SSLCertificateKeyFile /var/lib/puppet/ssl/private_keys/
puppetmaster.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 +ExportCertData
# These request headers are used to pass the client certificate
# authentication information on to the puppet master process
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
DocumentRoot /usr/share/puppet/rack/puppetmasterd/public/
Directory /usr/share/puppet/rack/puppetmasterd/
Options None
AllowOverride None
Order Allow,Deny
Allow from All
/Directory
/VirtualHost
I had a look at /usr/share/puppet/rack/puppetmasterd/config.ru which
contains this:
[snippet]
# if you want debugging:
# ARGV --debug
... so I enabled it. But this actually only gives me extra lines I
believe belong to INFO log level:
Jul 22 17:17:47 puppetmaster puppet-master[22132]:
(access[^/catalog/([^/]+)$]) allowing 'method' find Jul 22 17:17:47
puppetmaster puppet-master[22132]: (access[^/catalog/([^/]+)$]) allowing
$1 access Jul 22 17:17:47 puppetmaster puppet-master[22132]:
(access[^/node/([^/]+)$]) allowing 'method' find Jul 22 17:17:47
puppetmaster puppet-master[22132]: (access[^/node/([^/]+)$]) allowing $1
access Jul 22 17:17:47 puppetmaster puppet-master[22132]:
(access[/certificate_revocation_list/ca]) allowing 'method' find Jul
22 17:17:47 puppetmaster puppet-master[22132]:
(access[/certificate_revocation_list/ca]) allowing * access Jul 22
17:17:47 puppetmaster puppet-master[22132]: (access[/report]) allowing
'method' save Jul 22 17:17:47 puppetmaster puppet-master[22132]:
(access[/report]) allowing * access Jul 22 17:17:47 puppetmaster
puppet-master[22132]: (access[/file]) allowing * access Jul 22
17:17:47 puppetmaster puppet-master[22132]: (access[/certificate/ca])
adding authentication any Jul 22 17:17:47 puppetmaster
puppet-master[22132]: (access[/certificate/ca]) allowing 'method' find
Jul 22 17:17:47 puppetmaster puppet-master[22132]:
(access[/certificate/ca]) allowing * access Jul 22 17:17:47
puppetmaster puppet-master[22132]: (access[/certificate/]) adding
authentication any Jul 22 17:17:47 puppetmaster
puppet-master[22132]: (access[/certificate/]) allowing 'method' find
Jul 22
[Puppet Users] PE3 on physical server...how to carve up the filesystems?
Hey all, I need to configure a 1 x physical server, with RHEL6 + PE3. The following questions relate to this. I'm wondering if it's generally considered to be a good idea to set up a separate filesystem for the Puppet (Enterprise 3) filebucket. I would imagine that this could grow fairly quickly, and am not aware of any automated purging to control disk space. Maybe a script if the only way, via something like the following would be appropriate? find . -mtime +30 -atime +30 -print | xarg -0 rm Presumably I could also move the default filebucket location by updating the path attribute in puppet.conf on the PM? Ref http://docs.puppetlabs.com/references/latest/type.html#filebucket Any other thoughts on how best to separate the rest of the dir onto filesystems? It seems to be quite popular to split off the traditional *nix areas of concern (/, /tmp and /home), and PuppetDB (/var/lib/pgsql ?). Any other logical filesystem separation points recommended? Regs, Stephen -- 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: Array use as loop-type construct?
For completeness, I solved this myself by using a template instead of
trying to do this all within a manifest:
#!/bin/sh
% databases.each do |db| -%
%= mysqldump --user admin #{db} | gzip mysql-#{db}-`date +%Y%m%d`.gz %
% end -%
% remote_dest.each do |rd| -%
%= rsync -arzv #{bkp_dest} #{rd} %
% end -%
And the manifest then simplifies to:
file { backup-script:
ensure = present,
path = $mysql-backup-script,
content = template('backups/backup-mysql.erb'),
mode = 744,
owner = root,
group = root,
}
cron { backup-mysql:
command = $mysql-backup-script,
hour = 1,
minute = 20,
require = File['backup-script'],
}
On Tuesday, July 23, 2013 1:32:43 PM UTC-4, Bret Wortman wrote:
I'm trying to use a puppet manifest to set up a series of backup jobs on
servers which are each running a variety of mysql databases. My manifest
currently looks something like this, which almost works:
class backups () {
Cron {
ensure = present,
user = root,
}
$remote_dest = ['zx2:/data/src/backups','zx3:/data/backups']
if $hostname == www {
$databases = ['phpbb3','wikidb','rt4','wordpress']
$bkp_dest = /data/backup
elsif...
:
}
cron { $databses:
command = mysqldump --user admin $databases | gzip
mysql-$databases-`date +%Y%m%d`.gz,
hour = 1,
minute = 20,
}
cron { $remote_dest:
command = rsync -arzv $bkp_dest $remote_dest,
hour = 4,
minute = 40,
}
}
I get the right number of cron jobs built, but when the array variables
are quoted, I get the contents all concatenated together. What I'd like is
to simulate a for x in array kind of construct. Is that possible using
puppet? I'd rather not have to build this and specify each job by hand,
which seems really clunky given the elegance of the tool. I'm sure I'm just
not seeing something.
Thanks!
Bret
--
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] updating package and all dependency updates with puppet
Hello Brian,
Yum should solve dependencies (unless you tell it not to). So puppet is
skipping dependencies on package updates?
On Tue, Jul 23, 2013 at 12:02 PM, Brian Mathis brian.mat...@betteradmin.com
wrote:
You are relying on the functionality of 'yum' to pull in the dependencies,
which is a shortcut, and this is the kind of problem such shortcuts bring.
You should be making new puppet modules for each of the dependencies, and
have the zend package 'require' all of those modules. You can update the
versions in the dependency modules by using ensure = latest.
The yum update exec will work, but it would be missing the point of
Puppet and no different than managing systems with a shell script.
❧ Brian Mathis
On Tue, Jul 23, 2013 at 9:21 AM, cko dert...@gmail.com wrote:
hi,
im trying to update the zend server package the following way:
package { zend-server-php-5.4-6.1.0:
ensure = present,
require = [Yumrepo[ZendRepo],Yumrepo[Zend_noarch]],
notify = File[/etc/ld.so.conf.d/zend_server.conf]
}
when i install a node from scratch, the latest version (*including *the
latest depencencies) gets installed.
when i apply this to an existing node (with an older version of zend
server) *ONLY *the package zend-server-php- gets updated. updates for
the packages mod-php-5.4-apache2-zend-server-* and php*-5.4.16 (the
dependencies) are ignored.
whats the best way to solve this?
i was thinking about an yum update php* exec?
--
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.
--
Marcelo
¿No será acaso que esta vida moderna está teniendo más de moderna que de
vida? (Mafalda)
--
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: puppet module upgrade dilemma with Subversion
I also have my puppetmaster files in Subversion, and I'm running into the same problem with upgrading modules from Puppet Forge. This question on Stack Exchange (http://stackoverflow.com/q/5664666/190298) doesn't have any fancy solutions either. Here are some of the ideas I've come up with so far: - Write a shell script to automate the process of deleting, committing, re-downloading, re-committing, so that it takes place as quickly as possible. - Set up a QA environment based on the same SVN repository. Do the module upgrade here and commit. Then a single svn up on the production files will bring them all in line. - Use git instead of subversion. It doesn't suffer from the same source tree pollution that .svn folders do. - It might be possible to have a git working copy instead of the svn working copy, but add the .git hidden folder to svn:ignore. Then git could be used to pull updates from GitHub, where most of the puppet forge modules are developed. -- Nic On Friday, 12 April 2013 05:55:52 UTC-7, Ygor wrote: I use Subversion to maintain the $confdir of my puppet-masters and I just discovered that when one does an upgrade, the entire tree is blown away and replaced -- all my .svn directories are gone. I see nothing in the documentation (man page and such) to address this. Suggestions ? “Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.” Bill Waterson (Calvin Hobbes) -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: node_aws installation problem
Hi, found some of your entries looking around Shivaraj, have you found out the cause of this issue on your CentOS intallation? Thanks, Piotr W dniu środa, 24 lipca 2013 12:19:37 UTC+1 użytkownik Piotr Jasiulewicz napisał: Hi, tried to play around with the RUBYLIB env var but doesn't seam to help in any way. Any ideas? Thanks, Piotr W dniu wtorek, 23 lipca 2013 17:10:55 UTC+1 użytkownik Piotr Jasiulewicz napisał: Hi, got the whole list root@ip-10-55-86-66:/home/ubuntu# gem list *** LOCAL GEMS *** builder (3.2.2) excon (0.25.3) fog (1.14.0) formatador (0.2.4) guid (0.1.1) mime-types (1.23) mini_portile (0.5.1) minitest (1.6.0) multi_json (1.7.7) net-scp (1.1.2) net-ssh (2.6.8) nokogiri (1.6.0) rake (0.8.7) rdoc (2.5.8) ruby-hmac (0.4.0) just got the newest one... Cheers, Piotr W dniu wtorek, 23 lipca 2013 17:09:04 UTC+1 użytkownik shivaraj mathrubai napisał: What is the version of Fog you have ? When you do Puppet Help do you see an exclamation mark next to node_aws ? On Tuesday, 23 July 2013 16:16:19 UTC+1, Piotr Jasiulewicz wrote: Hi, yeap, it;s installed allright: root@X:/home/ubuntu# gem install guid Successfully installed guid-0.1.1 1 gem installed Installing ri documentation for guid-0.1.1... Installing RDoc documentation for guid-0.1.1... getting this every time, not sure if that's correct. Maybe the version is wrong? cheers, Piotr W dniu wtorek, 23 lipca 2013 16:11:20 UTC+1 użytkownik shivaraj mathrubai napisał: Did you install guid ? On Tuesday, 23 July 2013 11:03:14 UTC+1, Piotr Jasiulewicz wrote: Hi everyone! having a slight problem with the installing the cloud provisioning module [code] http://docs.puppetlabs.com/guides/cloud_pack_getting_started.html [/code] everything worked until I wanted to actually try to fire it up: [code] puppet node_aws list Error: Could not autoload puppet/face/node_aws/fingerprint: cannot load such file -- guid Error: Could not parse application options: Could not autoload puppet/face/node_aws/fingerprint: cannot load such file -- guid [/code] I have fog configured with my AWS credentials but it seams like the installation is just faulty, anyone any clue? Thanks, Piotr -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Error: Could not run: failed to allocate memory
On Tue, Jul 23, 2013 at 10:57 PM, Josh D joshuadavid...@gmail.com wrote: I installed Cygwin on some Windows 7 x64 client nodes (v3.2.3) and was in the process of removing it. Because I cannot modify CIFS/SAMBA shares or change the puppet service to run as a domain user, I'm basically reduced to getting the installers for each package on the machine prior to installing them. I was just using simple file types for this. Therefore, as part of the uninstallation of Cygwin, I was trying to remove the installer as well. The file is quite large, clocking in close to 2GB. Is there anything i can do to increase the amount of memory available to the agent or somehow avoid this error? Error: /Stage[main]/Win7_user/File[CygwinInstaller1]/ensure: change from file to absent failed: failed to allocate memory Error: Could not run: failed to allocate memory C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/file_bucket/dipper.rb:35:in `binread' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/file_bucket/dipper.rb:35:in `backup' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/util/backups.rb:84:in `backup_file_with_filebucket' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/util/backups.rb:28:in `perform_backup_with_bucket' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/util/backups.rb:15:in `perform_backup' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/type/file.rb:817:in`backup_existing' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/type/file.rb:628:in`remove_existing' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/type/file/ensure.rb:160:in `sync' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/transaction/resource_harness.rb:114:in `apply_parameter' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/transaction/resource_harness.rb:56:in `perform_changes' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/transaction/resource_harness.rb:139:in `evaluate' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/transaction.rb:48:in `apply' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/transaction.rb:83:in `eval_resource' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/transaction.rb:103:in `block (2 levels) in evaluate' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/util.rb:351:in `block in thinmark' C:/Program Files (x86)/Puppet Labs/Puppet/sys/ruby/lib/ruby/1.9.1/benchmark.rb:295:in `realtime' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/util.rb:350:in `thinmark' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/transaction.rb:103:in `block in evaluate' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/transaction.rb:382:in `traverse' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/transaction.rb:98:in `evaluate' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/resource/catalog.rb:146:in `apply' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/configurer.rb:122:in `block in apply_catalog' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/util.rb:179:in `block in benchmark' C:/Program Files (x86)/Puppet Labs/Puppet/sys/ruby/lib/ruby/1.9.1/benchmark.rb:295:in `realtime' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/util.rb:178:in `benchmark' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/configurer.rb:121:in `apply_catalog' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/configurer.rb:179:in `run' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:45:in `block (5 levels) in run' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent/locker.rb:20:in `lock' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:45:in `block (4 levels) in run' C:/Program Files (x86)/Puppet Labs/Puppet/sys/ruby/lib/ruby/1.9.1/sync.rb:227:in `sync_synchronize' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:45:in `block (3 levels) in run' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:119:in `with_client' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:42:in `block (2 levels) in run' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:84:in `run_in_fork' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:41:in `block in run' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/application.rb:179:in `call' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/application.rb:179:in `controlled_run' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:39:in `run' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/application/agent.rb:353:in `onetime' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/application/agent.rb:327:in `run_command' C:/Program Files
Re: [Puppet Users] updating package and all dependency updates with puppet
On the initial install, yum will resolve and install the dependencies, but
we're talking about updates.
If a package requires php, and php-5.4.1 is already installed, that will
satisfy the requirement, even if php-5.4.2 is available, and the updated
package will not be installed. You would need to use Puppet to explicitly
state that you want the package updated, and that requires its own module,
or at least its own resource definition.
❧ Brian Mathis
On Wed, Jul 24, 2013 at 9:42 AM, Marcelo Roccasalva roc...@gmail.comwrote:
Hello Brian,
Yum should solve dependencies (unless you tell it not to). So puppet is
skipping dependencies on package updates?
On Tue, Jul 23, 2013 at 12:02 PM, Brian Mathis
brian.mat...@betteradmin.com wrote:
You are relying on the functionality of 'yum' to pull in the
dependencies, which is a shortcut, and this is the kind of problem such
shortcuts bring.
You should be making new puppet modules for each of the dependencies, and
have the zend package 'require' all of those modules. You can update the
versions in the dependency modules by using ensure = latest.
The yum update exec will work, but it would be missing the point of
Puppet and no different than managing systems with a shell script.
❧ Brian Mathis
On Tue, Jul 23, 2013 at 9:21 AM, cko dert...@gmail.com wrote:
hi,
im trying to update the zend server package the following way:
package { zend-server-php-5.4-6.1.0:
ensure = present,
require = [Yumrepo[ZendRepo],Yumrepo[Zend_noarch]],
notify = File[/etc/ld.so.conf.d/zend_server.conf]
}
when i install a node from scratch, the latest version (*including *the
latest depencencies) gets installed.
when i apply this to an existing node (with an older version of zend
server) *ONLY *the package zend-server-php- gets updated. updates
for the packages mod-php-5.4-apache2-zend-server-* and php*-5.4.16
(the dependencies) are ignored.
whats the best way to solve this?
i was thinking about an yum update php* exec?
--
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.
--
Marcelo
¿No será acaso que esta vida moderna está teniendo más de moderna que de
vida? (Mafalda)
--
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: 3.2.2 on CentOS 6.3, and Did not receive certificate
The only response to puppet master --debug in the log is : Info: Could not find certificate for 'ourmachine.domain.com' And there is no reference to this system in the master's content under /var/lib/puppet. So it would seem that whatever mechanism that accepts CA requests and creation is borked... ? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: 3.2.2 on CentOS 6.3, and Did not receive certificate
Now this is really strange. I removed /var/lib/puppet on the client side and manually did a puppet agent test while doing a command line puppet test on the master and I got: Info: Could not find certificate for 'ourserver.ourdomain.com' Info: Could not find certificate_request for 'ourserver.ourdomain.com' Notice: ourserver.ourdomain.com has a waiting certificate request Notice: Signed certificate request for ourserver.ourdomain.com Notice: Removing file Puppet::SSL::CertificateRequest ourserver.ourdomain.com at '/var/lib/puppet/ssl/ca/requests/ourserver.domain.com.pem' Info: Caching node for ourserver.ourdomain.com Now I am suspicious that there is a problem with rack. My config.ru is based on what is in the latest puppet docs: $0 = master # ARGV --debug ARGV --confdir /etc/puppet ARGV --vardir /var/lib/puppet ARGV --rack require 'puppet/application/master' run Puppet::Application[:master].run And I have no idea if/how/why this would affect Certs. Still going to have to look into this. OR, I can just ditch Passenger and go back to running Puppet by itself. We have 40 hosts, so I don't think I'll miss Passenger, or having to update the *.conf every time there's an update. Thoughts? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: 3.2.2 on CentOS 6.3, and Did not receive certificate
When I updated the config.ru to what's in GIT for puppet, I get a slew of
crap errors that lists the library content for puppet. Here's what is in
GIT now:
# a config.ru, for use with every rack-compatible webserver.
# SSL needs to be handled outside this, though.
# if puppet is not in your RUBYLIB:
# $LOAD_PATH.unshift('/opt/puppet/lib')
$0 = master
# if you want debugging:
# ARGV --debug
ARGV --rack
# Rack applications typically don't start as root. Set --confdir and
--vardir
# to prevent reading configuration from ~puppet/.puppet/puppet.conf and
writing
# to ~puppet/.puppet
ARGV --confdir /etc/puppet
ARGV --vardir /var/lib/puppet
# NOTE: it's unfortunate that we have to use the CommandLine class
# here to launch the app, but it contains some initialization logic
# (such as triggering the parsing of the config file) that is very
# important. We should do something less nasty here when we've
# gotten our API and settings initialization logic cleaned up.
#
# Also note that the $0 = master line up near the top here is
# the magic that allows the CommandLine class to know that it's
# supposed to be running master.
#
# --cprice 2012-05-22
require 'puppet/util/command_line'
# we're usually running inside a Rack::Builder.new {} block,
# therefore we need to call run *here*.
run Puppet::Util::CommandLine.new.execute
I think I'm done with Passenger, as it's been nothing but a headache since
I started using it.
--
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] Problem running rake node:del for Puppet Dashboard databse hosted on RDS
Hi guys, The command below was working when my puppet dashboard mysql database was running in the same machine as the puppet master. rake RAILS_ENV=production -f /usr/share/puppet-dashboard/Rakefile node:del name=my-app-server However now I moved the mysql database to RDS and it doesn't work anymore, my database.yml reflects the change and the Puppet Dashboard web interface works fine accessing the RDS database, but the rake task to delete is broken. Interesting is that node:list works and list all my nodes. production: database: dashboard_production username: username password: password host: something.at.rds.amazonaws.com encoding: utf8 adapter: mysql Did I miss something during the local mysql to RDS migration ? Thanks, Felipe -- 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] Geppetto Project doesn't show folder structure
I'm feeling a bit besieged right now. I'm starting an extended project and I wanted to work in Kate. Kate's syntax highlighting is broken, so I check for an xml file and found one from reductive labs that gives a lovely 404.http://projects.reductivelabs.com/repositories/browse/puppet/ext/kate I'm no Eclipse guru, but I decided to give geppetto a try so I downloaded and ran it. Clicked File New Project Puppet Module Project. Then I went to my server and copied the beginnings of my project to my desktop and here geppetto nicely created a Puppet Module directory structure for me. And then in its infinite wisdom, elected not to show it in the Project Explorer. Pardon my snarkiness. I'd just like to start this project with beautiful syntax highlighting and ease of navigation. Kate has one but not the other. Apparently geppetto has the other but not the one. How can I get the Project Explorer to Explore? TIA, Dave P.S. Does one have to be an Eclipse guru to use geppetto? -- 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. attachment: geppetto1.jpeg
[Puppet Users] Re: Geppetto Project doesn't show folder structure
Ok, the joke's on me. Select the project, right click and Refresh. I said I was feeling besieged... :-| -- 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] Installing PuppetDB on Red Hat 6.4 Postgresql issues
Follwed the instructions for installing PuppetDB from pupptlabs url: http://docs.puppetlabs.com/puppetdb/latest/configure.html#using-postgresql After running the following commands to create puppetdb user and puppetdb database I cannot login with the password I provided for puppetdb $ sudo -u postgres sh $ createuser -DRSP puppetdb $ createdb -E UTF8 -O puppetdb puppetdb $ exit I keep getting a connection error, can anyone shed any light on this, appreciate your help in advance. [postgres@puppetmaster3:~]$ psql -h localhost puppetdb puppetdb psql: FATAL: Ident authentication failed for user puppetdb -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Installing PuppetDB on Red Hat 6.4 Postgresql issues
I was able to run a psql puppetdb without issue and then saw the creation of the puppetdb database. On Wednesday, July 24, 2013 3:37:10 PM UTC-4, GregC wrote: Follwed the instructions for installing PuppetDB from pupptlabs url: http://docs.puppetlabs.com/puppetdb/latest/configure.html#using-postgresql After running the following commands to create puppetdb user and puppetdb database I cannot login with the password I provided for puppetdb $ sudo -u postgres sh $ createuser -DRSP puppetdb $ createdb -E UTF8 -O puppetdb puppetdb $ exit I keep getting a connection error, can anyone shed any light on this, appreciate your help in advance. [postgres@puppetmaster3:~]$ psql -h localhost puppetdb puppetdb psql: FATAL: Ident authentication failed for user puppetdb -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Installing PuppetDB on Red Hat 6.4 Postgresql issues
Hello: I always seem to not be able to use localhost even with Posgtres bound to all addresses. The command I tend to use is like: psql -h 10.10.10.10 -d puppetdb -U puppetdb -W then enter your password. HTH On Wed, Jul 24, 2013 at 2:01 PM, GregC greg.caldwe...@gmail.com wrote: I was able to run a psql puppetdb without issue and then saw the creation of the puppetdb database. On Wednesday, July 24, 2013 3:37:10 PM UTC-4, GregC wrote: Follwed the instructions for installing PuppetDB from pupptlabs url: http://docs.puppetlabs.com/puppetdb/latest/configure.html#using-postgresql After running the following commands to create puppetdb user and puppetdb database I cannot login with the password I provided for puppetdb $ sudo -u postgres sh $ createuser -DRSP puppetdb $ createdb -E UTF8 -O puppetdb puppetdb $ exit I keep getting a connection error, can anyone shed any light on this, appreciate your help in advance. [postgres@puppetmaster3:~]$ psql -h localhost puppetdb puppetdb psql: FATAL: Ident authentication failed for user puppetdb -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Problem running rake node:del for Puppet Dashboard databse hosted on RDS
I had a friend helping me to debug and looks like it is taking forever to delete the entries from resource status table (a lot of entries). Is that something we can improve ? On Wednesday, July 24, 2013 11:42:26 AM UTC-7, Felipe Salum wrote: Hi guys, The command below was working when my puppet dashboard mysql database was running in the same machine as the puppet master. rake RAILS_ENV=production -f /usr/share/puppet-dashboard/Rakefile node:del name=my-app-server However now I moved the mysql database to RDS and it doesn't work anymore, my database.yml reflects the change and the Puppet Dashboard web interface works fine accessing the RDS database, but the rake task to delete is broken. Interesting is that node:list works and list all my nodes. production: database: dashboard_production username: username password: password host: something.at.rds.amazonaws.com encoding: utf8 adapter: mysql Did I miss something during the local mysql to RDS migration ? Thanks, Felipe -- 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: Problem running rake node:del for Puppet Dashboard databse hosted on RDS
On 7/24/2013 1:49 PM, Felipe Salum wrote: I had a friend helping me to debug and looks like it is taking forever to delete the entries from resource status table (a lot of entries). Is that something we can improve ? env RAILS_ENV=production rake reports:prune upto=5 unit=day env RAILS_ENV=production rake reports:prune:orphaned You can change the RAILS_ENV and number of day, weeks, months, etc to match your system and its needs. Sounds like you've never pruned so it's going to be slow going. Try walking it forward like so. env RAILS_ENV=production rake reports:prune upto=3 unit=mon env RAILS_ENV=production rake reports:prune upto=1 unit=mon env RAILS_ENV=production rake reports:prune upto=2 unit=wk env RAILS_ENV=production rake reports:prune upto=5 unit=day Don't forget to add this to your crontab with the retentions settings that best fit your system. Ramin -- 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: Problem running rake node:del for Puppet Dashboard databse hosted on RDS
I actually do for 2 weeks. rake RAILS_ENV=production reports:prune upto=2 unit=wk On Wed, Jul 24, 2013 at 2:03 PM, Ramin K ramin-l...@badapple.net wrote: On 7/24/2013 1:49 PM, Felipe Salum wrote: I had a friend helping me to debug and looks like it is taking forever to delete the entries from resource status table (a lot of entries). Is that something we can improve ? env RAILS_ENV=production rake reports:prune upto=5 unit=day env RAILS_ENV=production rake reports:prune:orphaned You can change the RAILS_ENV and number of day, weeks, months, etc to match your system and its needs. Sounds like you've never pruned so it's going to be slow going. Try walking it forward like so. env RAILS_ENV=production rake reports:prune upto=3 unit=mon env RAILS_ENV=production rake reports:prune upto=1 unit=mon env RAILS_ENV=production rake reports:prune upto=2 unit=wk env RAILS_ENV=production rake reports:prune upto=5 unit=day Don't forget to add this to your crontab with the retentions settings that best fit your system. Ramin -- 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/7-**sjp1Ef1p0/unsubscribehttps://groups.google.com/d/topic/puppet-users/7-sjp1Ef1p0/unsubscribe . To unsubscribe from this group and all its topics, send an email to puppet-users+unsubscribe@**googlegroups.compuppet-users%2bunsubscr...@googlegroups.com . To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/**group/puppet-usershttp://groups.google.com/group/puppet-users . For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out . -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] creating a (mac) package from a known good source + local patches
I need to have a way to re-create the installation package we use for facter and puppet, offline, from a known-good source. Often, we have local patches (e.g., backporting certain providers from 3.x to 2.x because our servers are still on 2.x, or patching things not yet released upstream), so our process has been: 1) Download tarball for a given release 2) Update makefile we use to create package to refer to new tarball 3) Verify local patches are still required 4) Build (possibly patched) package using ./etc/osx/createpackage.sh Now that createpackage.sh is really fully deprecated and gone, I'm looking at the rake packaging tasks. As I found in http://projects.puppetlabs.com/issues/21760#note-4 the tarball is useless since the rake tasks assume you're in a git checkout. So now I'm at a bit of a loss on how to create these packages. Checkout a specific tag, and then make my own tarball? I'm concerned that the reliance on it being a git checkout means the tasks may end up talking to github, making the whole process not hermetic. What's the best solution for this? Shall I create this as an issue against the packaging tasks? Thanks -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Puppet, Yum, Cassandra, openjdk and --nodeps
Hello, puppet n00b here. Trying to install cassandra via puppet. Works great, only caveat is cassandra (dsc12 package) lists openjdk as a dependency. Ironically enough, the datastax guys themselves recommend using Oracle JRE instead of openjdk, and there is even a bug https://bugzilla.redhat.com/show_bug.cgi?id=907485that prevents cassandra from starting if it's using openjdk. Anyway, I fixed it by adding an exec to my puppet-java module that sets the Oracle JRE runtime as the defaults via alternatives, and it works fine. However, I still end up with two different java runtimes installed which I find to be a bit unclean. The root of the problem to me, though, is that by having puppet install dsc12, I lose visibility into what all those dependencies were that got installed along with it (I didn't realize openjdk was even installing until I started investigating why cassandra wasn't starting). So what I'd prefer to do is add each individual package dependency into my cassandra module itself, thereby explicitly installing only what I intend to install, and nothing else. The only way this works, though, is if I can somehow pass the --nodeps option into yum during puppet apply time. Otherwise, regardless of whether I already installed Oracle JRE, using yum to install dsc12 will automatically install openjdk. How have you guys handled scenarios like this? I tried searching through the topics here for yum nodeps but it seems people found different ways of solving their individual problems rather than sending flags to the yum provider itself. I also noticed this puppet feature requesthttps://projects.puppetlabs.com/issues/4976which unfortunately has remained open(?) for 3 years. I've also seen people suggest that nodeps should never be used with yum since the purpose of yum is to handle dependencies... but we also like some of the other features of yum, like being able to pull packages down by name automatically from our yum repo (which we manage in-house). Anyway, any insights would be great! Thanks, Paul -- 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] Passenger with Puppet 3.0, problems running under
Since upgrading to 3.x I've had some problems running Puppet under
Passenger. I've spent several /days/ debugging this.
The first symptoms included a new agent could not get a CA cert from the
Puppet Master. I checked my configs, permissions, etc.
When I run puppet master in stand-alone mode, it works fine.
I wrote to the Phusion Passenger folks, but they are not familiar with
Puppet and so I'm still trying to figure out what is wrong.
We don't have selinux enabled. sestatus confirms this.
SELinux status: disabled
Of the errors I see in the puppet logs relevant to this:
puppet.log:Jul 24 14:51:19 central puppet-master[30657]: Could not prepare
for execution: Got 3 failure(s) while initializing: Could not set 'file' on
ensure:
Permission denied - /var/log/puppet/masterhttp.log; Could not set 'file'
on ensure: Permission denied - /var/log/puppet/masterhttp.log
puppet.log:Jul 24 14:51:19 central puppet-master[30657]: Wrapped exception:
puppet.log:Jul 24 14:51:19 central puppet-master[30657]: Permission denied
- /var/log/puppet/masterhttp.log; change from absent to file failed: Could
not set
'file' on ensure: Permission denied - /var/log/puppet/masterhttp.log
I tried setting the ownership of the files in that directory to the same
as the apache User, no difference. Again, under regular Puppet there's no
problem.
This is all I have in my config.ru:
$0 = master
ARGV --rack
ARGV --confdir /etc/puppet
ARGV --vardir /var/lib/puppet
require 'puppet/util/command_line'
run Puppet::Util::CommandLine.new.execute
More logs:
Jul 24 14:51:14 de-prod-archive puppet-agent[28391]: #011#011div
id=site_header
Jul 24 14:51:14 de-prod-archive puppet-agent[28391]: #011#011#011ul
class=corporate_identity
Jul 24 14:51:14 de-prod-archive puppet-agent[28391]: #011#011#011#011li
class=logoa href=https://www.phusionpassenger.com;
https://www.phusionpassenger.comspanPhusion
Passenger/span/a/li
Jul 24 14:51:14 de-prod-archive puppet-agent[28391]: #011#011#011/ul
Jul 24 14:51:14 de-prod-archive puppet-agent[28391]: #011#011/div
Jul 24 14:51:14 de-prod-archive puppet-agent[28391]: #011#011div
id=site_body
Jul 24 14:51:14 de-prod-archive puppet-agent[28391]: #011#011#011h1
class=error_titleWeb application could not be started/h1
Jul 24 14:51:14 de-prod-archive puppet-agent[28391]: #011#011#011div
id=content
Jul 24 14:51:14 de-prod-archive puppet-agent[28391]:
#011#011#011#011preexit (SystemExit)
Jul 24 14:51:14 de-prod-archive puppet-agent[28391]:
/usr/local/lib/ruby/gems/1.8/gems/puppet-3.2.3/lib/puppet/util.rb:wbr518:wbrin
`exitapos;
Jul 24 14:51:14 de-prod-archive puppet-agent[28391]:
/usr/local/lib/ruby/gems/1.8/gems/puppet-3.2.3/lib/puppet/util.rb:wbr518:wbrin
`exit_on_failapos;
Jul 24 14:51:14 de-prod-archive puppet-agent[28391]:
/usr/local/lib/ruby/gems/1.8/gems/puppet-3.2.3/lib/puppet/application.rb:wbr362:wbrin
`runapos;
Jul 24 14:51:14 de-prod-archive puppet-agent[28391]:
/usr/local/lib/ruby/gems/1.8/gems/puppet-3.2.3/lib/puppet/util/command_line.rb:wbr132:wbrin
`runapos;
It spits out a lot of HTML, CSS... and things I don't think should ever happen,
on the client side.
Looks like it it exiting, mentioning line 518 of
/usr/local/lib/ruby/gems/1.8/gems/puppet-3.2.3/lib/puppet/util.rb, the code of
which
is:
# Now we need to catch **any** other kind of exception, because we may
be calling third-party
# code (e.g. webrick), and we have no idea what they might throw.
rescue Exception = err
## NOTE: when debugging spec failures, these two lines can be very
useful
#puts err.inspect
#puts Puppet::Util.pretty_backtrace(err.backtrace)
Puppet.log_exception(err, Could not #{message}: #{err})
Puppet::Util::Log.force_flushqueue()
exit(code)
end
Anyway, I'm pretty stumped. I am running Puppet 3.x on its own now. We only
have 40 nodes, so it works. But I'd like to figure out what the heck is wrong
with Passenger :-)
Anyone else encounter this problem?
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] Re: Problem running rake node:del for Puppet Dashboard databse hosted on RDS
Doesn't matter, it's the size of the data and the amount you're deleting. Let's say that your reports:prune upto=2 unit=wk is ultimately going to delete 100k records because you've never pruned the database before. reports:prune upto=2 unit=wk, 100k, time: 3600s By breaking it up, it'll run faster because large deletes can cause poor performance in Mysql. reports:prune upto=9 unit=wk, deletes: 9k, time: 280s reports:prune upto=8 unit=wk, deletes: 11k, time: 250s reports:prune upto=7 unit=wk, deletes: 10k, time: 251s reports:prune upto=6 unit=wk, deletes: 12k, time: 239s reports:prune upto=5 unit=wk, deletes: 11k, time: 205s reports:prune upto=4 unit=wk, deletes: 11k, time: 180s reports:prune upto=2 unit=wk, deletes: 22k, time: 200s Running it nightly with a fully prune data set. reports:prune upto=2 unit=wk, deletes: 1.5k, time: 25s ** I made up all these numbers up, but the performance ratio should be roughly correct based on past experience. ymmv. ** Also the Rake task will load the id of the records it plans to delete into memory. This can be quite large and is another reason to break it into smaller chunks. Ramin On 7/24/2013 2:08 PM, Felipe Salum wrote: I actually do for 2 weeks. rake RAILS_ENV=production reports:prune upto=2 unit=wk On Wed, Jul 24, 2013 at 2:03 PM, Ramin K ramin-l...@badapple.net mailto:ramin-l...@badapple.net wrote: On 7/24/2013 1:49 PM, Felipe Salum wrote: I had a friend helping me to debug and looks like it is taking forever to delete the entries from resource status table (a lot of entries). Is that something we can improve ? env RAILS_ENV=production rake reports:prune upto=5 unit=day env RAILS_ENV=production rake reports:prune:orphaned You can change the RAILS_ENV and number of day, weeks, months, etc to match your system and its needs. Sounds like you've never pruned so it's going to be slow going. Try walking it forward like so. env RAILS_ENV=production rake reports:prune upto=3 unit=mon env RAILS_ENV=production rake reports:prune upto=1 unit=mon env RAILS_ENV=production rake reports:prune upto=2 unit=wk env RAILS_ENV=production rake reports:prune upto=5 unit=day Don't forget to add this to your crontab with the retentions settings that best fit your system. Ramin -- 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/7-__sjp1Ef1p0/unsubscribe https://groups.google.com/d/topic/puppet-users/7-sjp1Ef1p0/unsubscribe. To unsubscribe from this group and all its topics, send an email to puppet-users+unsubscribe@__googlegroups.com mailto:puppet-users%2bunsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com mailto:puppet-users@googlegroups.com. Visit this group at http://groups.google.com/__group/puppet-users http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/__groups/opt_out 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. -- 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: Problem running rake node:del for Puppet Dashboard databse hosted on RDS
I understood, what I wanted to say is that I run a cron job every day for the 2 weeks prune.. and I have less than 2 weeks data in the database right now since I moved it recently to a new server. I'm running a optimize task, the resource_statuses is really big. On Wed, Jul 24, 2013 at 3:21 PM, Ramin K ramin-l...@badapple.net wrote: Doesn't matter, it's the size of the data and the amount you're deleting. Let's say that your reports:prune upto=2 unit=wk is ultimately going to delete 100k records because you've never pruned the database before. reports:prune upto=2 unit=wk, 100k, time: 3600s By breaking it up, it'll run faster because large deletes can cause poor performance in Mysql. reports:prune upto=9 unit=wk, deletes: 9k, time: 280s reports:prune upto=8 unit=wk, deletes: 11k, time: 250s reports:prune upto=7 unit=wk, deletes: 10k, time: 251s reports:prune upto=6 unit=wk, deletes: 12k, time: 239s reports:prune upto=5 unit=wk, deletes: 11k, time: 205s reports:prune upto=4 unit=wk, deletes: 11k, time: 180s reports:prune upto=2 unit=wk, deletes: 22k, time: 200s Running it nightly with a fully prune data set. reports:prune upto=2 unit=wk, deletes: 1.5k, time: 25s ** I made up all these numbers up, but the performance ratio should be roughly correct based on past experience. ymmv. ** Also the Rake task will load the id of the records it plans to delete into memory. This can be quite large and is another reason to break it into smaller chunks. Ramin On 7/24/2013 2:08 PM, Felipe Salum wrote: I actually do for 2 weeks. rake RAILS_ENV=production reports:prune upto=2 unit=wk On Wed, Jul 24, 2013 at 2:03 PM, Ramin K ramin-l...@badapple.net mailto:ramin-list@badapple.**net ramin-l...@badapple.net wrote: On 7/24/2013 1:49 PM, Felipe Salum wrote: I had a friend helping me to debug and looks like it is taking forever to delete the entries from resource status table (a lot of entries). Is that something we can improve ? env RAILS_ENV=production rake reports:prune upto=5 unit=day env RAILS_ENV=production rake reports:prune:orphaned You can change the RAILS_ENV and number of day, weeks, months, etc to match your system and its needs. Sounds like you've never pruned so it's going to be slow going. Try walking it forward like so. env RAILS_ENV=production rake reports:prune upto=3 unit=mon env RAILS_ENV=production rake reports:prune upto=1 unit=mon env RAILS_ENV=production rake reports:prune upto=2 unit=wk env RAILS_ENV=production rake reports:prune upto=5 unit=day Don't forget to add this to your crontab with the retentions settings that best fit your system. Ramin -- 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/7-__** sjp1Ef1p0/unsubscribehttps://groups.google.com/d/__topic/puppet-users/7-__sjp1Ef1p0/unsubscribe https://groups.google.com/d/**topic/puppet-users/7-** sjp1Ef1p0/unsubscribehttps://groups.google.com/d/topic/puppet-users/7-sjp1Ef1p0/unsubscribe . To unsubscribe from this group and all its topics, send an email to puppet-users+unsubscribe@__goo**glegroups.comhttp://googlegroups.com mailto:puppet-users%**2bunsubscr...@googlegroups.compuppet-users%252bunsubscr...@googlegroups.com **. To post to this group, send email to puppet-users@googlegroups.com mailto:puppet-users@**googlegroups.compuppet-users@googlegroups.com . Visit this group at http://groups.google.com/__**group/puppet-usershttp://groups.google.com/__group/puppet-users http://groups.google.com/**group/puppet-usershttp://groups.google.com/group/puppet-users . For more options, visit https://groups.google.com/__**groups/opt_outhttps://groups.google.com/__groups/opt_out https://groups.google.com/**groups/opt_outhttps://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+unsubscribe@**googlegroups.compuppet-users%2bunsubscr...@googlegroups.com . To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/**group/puppet-usershttp://groups.google.com/group/puppet-users . For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out . -- 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/7-**sjp1Ef1p0/unsubscribehttps://groups.google.com/d/topic/puppet-users/7-sjp1Ef1p0/unsubscribe . To unsubscribe from this group
Re: [Puppet Users] updating package and all dependency updates with puppet
I get it... but, if you have a module for zend and there is a new version
of zend that _yum_ depends on the new version of php, then both zend and
php get updated?
On Wed, Jul 24, 2013 at 1:00 PM, Brian Mathis
brian.mat...@betteradmin.comwrote:
On the initial install, yum will resolve and install the dependencies, but
we're talking about updates.
If a package requires php, and php-5.4.1 is already installed, that will
satisfy the requirement, even if php-5.4.2 is available, and the updated
package will not be installed. You would need to use Puppet to explicitly
state that you want the package updated, and that requires its own module,
or at least its own resource definition.
❧ Brian Mathis
On Wed, Jul 24, 2013 at 9:42 AM, Marcelo Roccasalva roc...@gmail.comwrote:
Hello Brian,
Yum should solve dependencies (unless you tell it not to). So puppet is
skipping dependencies on package updates?
On Tue, Jul 23, 2013 at 12:02 PM, Brian Mathis
brian.mat...@betteradmin.com wrote:
You are relying on the functionality of 'yum' to pull in the
dependencies, which is a shortcut, and this is the kind of problem such
shortcuts bring.
You should be making new puppet modules for each of the dependencies,
and have the zend package 'require' all of those modules. You can update
the versions in the dependency modules by using ensure = latest.
The yum update exec will work, but it would be missing the point of
Puppet and no different than managing systems with a shell script.
❧ Brian Mathis
On Tue, Jul 23, 2013 at 9:21 AM, cko dert...@gmail.com wrote:
hi,
im trying to update the zend server package the following way:
package { zend-server-php-5.4-6.1.0:
ensure = present,
require = [Yumrepo[ZendRepo],Yumrepo[Zend_noarch]],
notify = File[/etc/ld.so.conf.d/zend_server.conf]
}
when i install a node from scratch, the latest version (*including *the
latest depencencies) gets installed.
when i apply this to an existing node (with an older version of zend
server) *ONLY *the package zend-server-php- gets updated. updates
for the packages mod-php-5.4-apache2-zend-server-* and php*-5.4.16
(the dependencies) are ignored.
whats the best way to solve this?
i was thinking about an yum update php* exec?
--
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.
--
Marcelo
¿No será acaso que esta vida moderna está teniendo más de moderna que de
vida? (Mafalda)
--
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.
--
Marcelo
¿No será acaso que esta vida moderna está teniendo más de moderna que de
vida? (Mafalda)
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] creating a (mac) package from a known good source + local patches
Hi Clay, I totally see your use case. We're currently looking to revisit the way we build apple packages to make things more sane. In the meantime, there is a workaround workflow, which still uses git/github but allows you to keep things offline after you download them. As noted in the ticket, the packaging tasks rely on our projects' git code info, so we have to keep that around to build. If you don't want to rsync around git clones, one way I've accomplished it is using git bundles[1] (like a git archive, but retains the version control info). This process is the same for facter, puppet, and hiera. Roughly: Clone facter and check out the tag that you want to build, e.g. 1.7.2. The tags we push to github are the canonical artifacts we use to mark a release. # git clone git://github.com/puppetlabs/facter cd facter git checkout 1.7.2 We sign our tags, so you can verify the tag if you have our public key installed (see [2] on how to get it) # git verify-tag 1.7.2 Create a git bundle of your clone # git bundle create facter_bundle HEAD --tags Clone the packaging repo and create a git archive of it as well. 0.2.0 is the most recent version # git clone git://github.com/puppetlabs/packaging cd packaging git checkout 0.2.0 # git bundle create packaging_bundle HEAD --tags With the two git bundle files, you can now create mac packages offline. Take the git bundles to wherever you want to build packages, and git clone then to extract. # git clone facter_bundle facter # git clone packaging_bundle facter/ext/packaging # apply your patches to facter (even branch and commit them if you want) Now build packages: # cd facter rake package:apple ; # a dmg will be staged in ./pkg/apple/ I completely understand your concern about the tasks talking to github - some of them do. However, rake package:apple isn't one of them - it relies entirely on tools present on the system. [1] http://git-scm.com/blog/2010/03/10/bundles.html [2] http://puppetlabs.com/misc/download-options On Wed, Jul 24, 2013 at 2:28 PM, Clay Caviness ccavin...@gmail.com wrote: I need to have a way to re-create the installation package we use for facter and puppet, offline, from a known-good source. Often, we have local patches (e.g., backporting certain providers from 3.x to 2.x because our servers are still on 2.x, or patching things not yet released upstream), so our process has been: 1) Download tarball for a given release 2) Update makefile we use to create package to refer to new tarball 3) Verify local patches are still required 4) Build (possibly patched) package using ./etc/osx/createpackage.sh Now that createpackage.sh is really fully deprecated and gone, I'm looking at the rake packaging tasks. As I found in http://projects.puppetlabs.com/issues/21760#note-4 the tarball is useless since the rake tasks assume you're in a git checkout. So now I'm at a bit of a loss on how to create these packages. Checkout a specific tag, and then make my own tarball? I'm concerned that the reliance on it being a git checkout means the tasks may end up talking to github, making the whole process not hermetic. What's the best solution for this? Shall I create this as an issue against the packaging tasks? Thanks -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out. -- Moses Mendoza Puppet Labs Join us at PuppetConf 2013, August 22-23 in San Francisco - http://bit.ly/pupconf13 Register now and take advantage of the Final Countdown discount - save 15%! -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] updating package and all dependency updates with puppet
I have not tested that myself, so I'm not sure what Puppet would do in this
case. I'm pretty sure yum would also install the updates, but only if the
main (rpm/deb) package specifically requires the newer version.
Given the original poster's request, it can be assumed that the package
does not have the updated version number as part of the package definition,
so it needs to be managed separately by Puppet. I don't think its uncommon
to see a package that requires (e.g.) version 5.4, and not get so
specific as 5.4.3.
❧ Brian Mathis
On Wed, Jul 24, 2013 at 7:20 PM, Marcelo Roccasalva roc...@gmail.comwrote:
I get it... but, if you have a module for zend and there is a new version
of zend that _yum_ depends on the new version of php, then both zend and
php get updated?
On Wed, Jul 24, 2013 at 1:00 PM, Brian Mathis
brian.mat...@betteradmin.com wrote:
On the initial install, yum will resolve and install the dependencies,
but we're talking about updates.
If a package requires php, and php-5.4.1 is already installed, that
will satisfy the requirement, even if php-5.4.2 is available, and the
updated package will not be installed. You would need to use Puppet to
explicitly state that you want the package updated, and that requires its
own module, or at least its own resource definition.
❧ Brian Mathis
On Wed, Jul 24, 2013 at 9:42 AM, Marcelo Roccasalva roc...@gmail.comwrote:
Hello Brian,
Yum should solve dependencies (unless you tell it not to). So puppet is
skipping dependencies on package updates?
On Tue, Jul 23, 2013 at 12:02 PM, Brian Mathis
brian.mat...@betteradmin.com wrote:
You are relying on the functionality of 'yum' to pull in the
dependencies, which is a shortcut, and this is the kind of problem such
shortcuts bring.
You should be making new puppet modules for each of the dependencies,
and have the zend package 'require' all of those modules. You can update
the versions in the dependency modules by using ensure = latest.
The yum update exec will work, but it would be missing the point of
Puppet and no different than managing systems with a shell script.
❧ Brian Mathis
On Tue, Jul 23, 2013 at 9:21 AM, cko dert...@gmail.com wrote:
hi,
im trying to update the zend server package the following way:
package { zend-server-php-5.4-6.1.0:
ensure = present,
require = [Yumrepo[ZendRepo],Yumrepo[Zend_noarch]],
notify = File[/etc/ld.so.conf.d/zend_server.conf]
}
when i install a node from scratch, the latest version (*including *the
latest depencencies) gets installed.
when i apply this to an existing node (with an older version of zend
server) *ONLY *the package zend-server-php- gets updated. updates
for the packages mod-php-5.4-apache2-zend-server-* and php*-5.4.16
(the dependencies) are ignored.
whats the best way to solve this?
i was thinking about an yum update php* exec?
--
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.
--
Marcelo
¿No será acaso que esta vida moderna está teniendo más de moderna que
de
vida? (Mafalda)
--
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.
--
Marcelo
¿No será acaso que esta vida moderna está teniendo más de moderna que de
vida? (Mafalda)
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from
Re: [Puppet Users] Error: Could not run: failed to allocate memory
Yeah, definitely some combination of reading the entire file into memory and me not disabling backups. I disabled backups globally per your suggestion and voted on the issue you linked. Thanks, Josh On Wednesday, July 24, 2013 9:52:29 AM UTC-6, Josh Cooper wrote: On Tue, Jul 23, 2013 at 10:57 PM, Josh D joshuad...@gmail.comjavascript: wrote: I installed Cygwin on some Windows 7 x64 client nodes (v3.2.3) and was in the process of removing it. Because I cannot modify CIFS/SAMBA shares or change the puppet service to run as a domain user, I'm basically reduced to getting the installers for each package on the machine prior to installing them. I was just using simple file types for this. Therefore, as part of the uninstallation of Cygwin, I was trying to remove the installer as well. The file is quite large, clocking in close to 2GB. Is there anything i can do to increase the amount of memory available to the agent or somehow avoid this error? Error: /Stage[main]/Win7_user/File[CygwinInstaller1]/ensure: change from file to absent failed: failed to allocate memory Error: Could not run: failed to allocate memory C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/file_bucket/dipper.rb:35:in `binread' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/file_bucket/dipper.rb:35:in `backup' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/util/backups.rb:84:in `backup_file_with_filebucket' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/util/backups.rb:28:in `perform_backup_with_bucket' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/util/backups.rb:15:in `perform_backup' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/type/file.rb:817:in`backup_existing' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/type/file.rb:628:in`remove_existing' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/type/file/ensure.rb:160:in `sync' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/transaction/resource_harness.rb:114:in `apply_parameter' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/transaction/resource_harness.rb:56:in `perform_changes' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/transaction/resource_harness.rb:139:in `evaluate' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/transaction.rb:48:in `apply' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/transaction.rb:83:in `eval_resource' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/transaction.rb:103:in `block (2 levels) in evaluate' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/util.rb:351:in `block in thinmark' C:/Program Files (x86)/Puppet Labs/Puppet/sys/ruby/lib/ruby/1.9.1/benchmark.rb:295:in `realtime' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/util.rb:350:in `thinmark' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/transaction.rb:103:in `block in evaluate' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/transaction.rb:382:in `traverse' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/transaction.rb:98:in `evaluate' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/resource/catalog.rb:146:in `apply' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/configurer.rb:122:in `block in apply_catalog' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/util.rb:179:in `block in benchmark' C:/Program Files (x86)/Puppet Labs/Puppet/sys/ruby/lib/ruby/1.9.1/benchmark.rb:295:in `realtime' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/util.rb:178:in `benchmark' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/configurer.rb:121:in `apply_catalog' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/configurer.rb:179:in `run' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:45:in `block (5 levels) in run' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent/locker.rb:20:in `lock' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:45:in `block (4 levels) in run' C:/Program Files (x86)/Puppet Labs/Puppet/sys/ruby/lib/ruby/1.9.1/sync.rb:227:in `sync_synchronize' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:45:in `block (3 levels) in run' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:119:in `with_client' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:42:in `block (2 levels) in run' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:84:in `run_in_fork' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:41:in `block in run' C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/application.rb:179:in `call' C:/Program Files (x86)/Puppet
[Puppet Users] Puppet loading class that is not included?
Hi,
I have noticed a very strance problem with my current puppet setup on
one of the nodes.
This is very peculiar problem indeed.
I have class php which looks like this:
# Class: php$major
#
# This module manages php$major installation for CentOS 5
#
class php (
$major = $php::params::major,
$package_ensure = $php::params::package_ensure,
$timezone = $::timezone,
) inherits php::params {
# packages from CentOS base
package { 'php':
ensure = $package_ensure,
name = php${major},
}
package { 'php-cli':
ensure = $package_ensure,
name = php${major}-cli,
}
package { 'php-common':
ensure = $package_ensure,
name = php${major}-common,
}
file { '/etc/php.d/timezone.ini':
ensure = file,
owner = root,
group = root,
mode= '0644',
content = template('php/timezone.ini.erb'),
require = Package['php-common'],
}
}
Now, I have many subclases for php modules, like this one:
# Class: php::mod::bcmath
class php::mod::bcmath (
$major = $php::major,
$package_ensure = $php::package_ensure,
) inherits php {
package { 'php-bcmath':
ensure = $package_ensure,
name = php${major}-bcmath,
}
}
It's obvious that this class inherits class php.
Now, I have a following classes that include the php:
class system::templates::php {
include ::php
include ::php::mod::bcmath
}
But I also have a class system::php ,which only brings
/etc/php.d/system.ini :
class system::php {
file { '/etc/php.d/system.ini': }
}
Now, strange thing is, if system::php is present, puppet does automatic
include on every node that has some of the php::mod::* included...
But if I rm -f system/manifests/php.pp, not a single node reports an
error...
So, it's obvious that system::php is being pulled in catalog somehow, I
presume by the 'inherits php' code from php submodules. I have alot of
other code around, so I didn't (yet) try to code up the minimal possible
code that causes this behaviour... But sure as hell this is unintended
in my case...
I was pretty cautious in specifying top scope in numeros occasions when
including or requiring classes, but this time I thing that 'inherits'
bit me...
Has anyone had similar problems? Should I change my classes code in some
way to avoid this kind of issues in the future?
--
Jakov Sosic
www.srce.unizg.hr
--
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 loading class that is not included?
On 07/25/2013 02:13 AM, Jakov Sosic wrote: I was pretty cautious in specifying top scope in numeros occasions when including or requiring classes, but this time I thing that 'inherits' bit me... Nah, I've found it... It seems that I missed one require in another class, system::foobar, which stated 'require php', and thus included system::php if it existed! I've changed it to 'require ::php' and now it's ok, system::php is not included any more. So it's not the inherit after all :D -- Jakov Sosic www.srce.unizg.hr -- 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 loading class that is not included?
On 07/25/2013 02:13 AM, Jakov Sosic wrote: Hi, Also, just in case some else stumbles upon something like this... generating grahps, and opening .dot file in text editor and searching for incriminating classes and it's relationships really solved it for me. So that's my advice to future readers. -- Jakov Sosic www.srce.unizg.hr -- 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] mcollective puppet module: not pulling in specified parameters
Is it okay to ask questions about the mcollective puppet module by
puppetlabs here?
If so, I'm getting this error:
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Failed to parse template mcollective/server.cfg.erb:
Filepath: /usr/lib/ruby/site_ruby/1.8/puppet/parser/templatewrapper.rb
Line: 67
Detail: Could not find value for 'mc_topicprefix' at
2:/usr/local/puppet/environments/development/modules/mcollective/templates/server.cfg.erb
This is how it's defined in the server template:
templates/server.cfg.erb:
# Basic stuff
topicprefix = %= mc_topicprefix %
So, I checked to make sure it was defined in params:
manifests/params.pp
class mcollective::params {
$mc_topicprefix = '/topic/'
So I checked to make sure params was inherited:
manifests/server/config.pp
class mcollective::server::config(
$config_file,
$config,
$server_config_owner = $mcollective::params::server_config_owner,
$server_config_group = $mcollective::params::server_config_group
) inherits mcollective::params {
This is in my server's .pp file:
class { 'mcollective':
version = 'present',
server = true,
server_config= template('mcollective/server.cfg.erb'),
server_config_file = '/etc/mcollective/server.cfg',
client = 'false',
client_config= template('mcollective/client.cfg.erb'),
client_config_file = '/home/mcollective/.mcollective',
stomp_server = 'X',
mc_security_provider = 'XXX',
mc_security_psk = 'X',
}
Any thoughts on next steps for troubleshooting?
--
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] Not collecting exported resources without storeconfigs
# cat /etc/redhat-release CentOS release 6.4 (Final) # puppet --version 3.2.3 # rpm -q puppetdb puppetdb-1.3.2-1.el6.noarch I am now receiving Not collecting exported resources without storeconfigs for my opsview module. It was working fine on puppet 2.7 with Activerecord/MySQL. I am still new to puppetdb so maybe I am missing something. This is from puppet.conf: storeconfigs = true thin_storeconifgs = false storeconfigs_backend = puppetdb Any ideas? Thanks, -Larry -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] operatingsystemrelease fact on windows
Hi everyone, I've revisited one of the old facter issues for the windows hosts: implementing the 'operatingsystemrelease' (http://projects.puppetlabs.com/issues/7621). The current version is returning the kernel release, but in the windows world, a kernel release (like 6.2) can refer to different releases of the operating system (Windows 8 or Windows 2012). I've sent a pull request (https://github.com/puppetlabs/facter/pull/500) that implements this alternative behavior for the fact: returning the common windows release name, but as it changes the semantics of the current fact, I'd like to have your feedback about this change in the pull request. Cheers, Luis -- 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] is there any way to see what are the resources exported by a node?
Hello folks, Is there any way to see what are the resources exported by a node when using puppetdb and exported resources. I am running puppet 2.7.22 and puppetdb 1.3 on Ubuntu 10.4. I have tried to use e API and its not working for me(see https://groups.google.com/forum/#!topicsearchin/puppet-users/puppetdb$20API$20v2$20is$20not$20working$20for$20me/puppet-users/WFo9YEw6oRo ) Anyone know any SQL query to get this info? Thanks so much in advance Watchman -- 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: puppetdb v2 node api
Hey mate, It looks liek you got this v2 API working. How did you setup that? I spend so much time to get this working but no luck. Whenever I try the url I get 404 error in puppetdb log... If you could help me then that would be great! Thanks Watchman On Monday, April 22, 2013 1:09:08 PM UTC+10, hyde wrote: In puppetdb v2 node api, it changes behavior with GET /v2/nodeshttp://docs.puppetlabs.com/puppetdb/1.2/api/query/v2/nodes.html#get-v2nodes, which only returns active nodes now. In v1, it would return all nodes. So in puppetdb v2 node api, how is it possible to return all nodes (both active and deactivated ones)? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
