.
$ /opt/puppetlabs/bin/puppet agent -t
Info: Using configured environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Language validation logged 2 errors. Giving up in /etc/puppetlabs/code/environments/production/modules/dspace/manifests/install.pp on node agent2
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
↧
Am tring to create a dspace module but when updating the node I get this error.. Kindly help.
↧
How do I install Python 2.6.x on a CentOS 7 machine using Puppet/yum/EPEL?
Hello,
I'm working on writing a puppet file that can be included that installs Python 2.6 on a CentOS7 remote VM. This file is being written so that Python apps that run on v2.6 can be cloned from Git onto the VM and then run immediately. The VM is running Puppet v3.8.7, yum v3.4.3, and EPEL 7.
Snippet of the relevant code that I have so far:
package { 'python26':
ensure => 'installed',
provider => 'yum',
}
package {
[
'python-devel',
'python-virtualenv',
'python-lxml',
'libxml2',
'libxml2-python',
'libxml2-devel',
'libxslt',
'libxslt-devel',
'gcc-c++',
'gcc'
]:
ensure => 'installed',
}
However, when that snippet gets run on the VM, it errors as follows:
Error: Execution of '/usr/bin/yum -d 0 -e 0 -y install python26' returned 1: Error: Nothing to do
Error: /Stage[main]/.../Python2_6/Package[python26]/ensure: change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install python26' returned 1: Error: Nothing to do
I did a little bit of research and it appears that EPEL 7 doesn't have the python26 package referenced [here](https://stackoverflow.com/a/4122184) (an old article, back when people were trying to upgrade from v2.4 to v2.6), and EPEL7's default python package installs v2.7 now. I spent about 2 hours searching through forums and documentation looking for ways to install v2.6 instead of the default v2.7 (even made it all the way to the 3rd result page of Google), and the best answer I've found so far is [this article](https://tecadmin.net/install-python-2-7-on-centos-rhel/#) which would require me to essentially run a Bash script through Puppet's exec statements, which doesn't sound like a good solution right now.
I've also tried running this on the VM :
yum list all | grep python
and looking for a 2.6 version, but I didn't see any that looked like what I want.
Do any of you have experience with a similar situation that might provide an answer? Is there a yum/EPEL package that I've overlooked that would install Python 2.6?
Thank you in advance for any help or advice that you can offer! :-)
↧
↧
puppet agent without pe-puppet possible?
Hi all,
I would like to know if there is a possibility to change the default username "pe-puppet" for the agent to something shorter ?
Kind Regards,
Marcel
↧
Apache 2 virtual hosting
Hey, i have tried what you had suggested but still isn't working
node "puppetagent" {
include tomcat
include apache
include apache::mod::jk
}
iapache::vhost { 'tomcat.dddke.net':
port => '80',
docroot => '/var/www/html',
}
apache::vhost { 'tomcat1.dddke.net':
port => '80',
docroot => '/var/www/html',
}
apache::vhost { 'tomcat2.dddke.net':
port => '80',
docroot => '/var/www/html',
}
apache::vhost { 'tomcat3.dddke.net':
port => '80',
docroot => '/var/www/html',
}
apache::vhost { 'tomcat4.dddke.net':
port => '80',
docroot => '/var/www/html',
}
class { '::apache::mod::jk':
ip => '54.172.8.127',
workers_file => 'conf/workers.properties',
mount_file => 'conf/uriworkermap.properties',
shm_file => 'run/jk.shm',
shm_size => '50M',
$workers_file_content = {
worker_lists => ['status', 'some_name,other_name'],
worker_mantain => '60',
some_name => {
comment => 'Optional comment',
type => 'ajp13',
socket_keepalive => 'true',
},
other_name => {
comment => 'I just like comments',
type => 'ajp12',
socket_keepalive => 'false',
},
}
class {'tomcat':
service_ensure => 'running',
service_enable => true
}
tomcat::instance { 'instance1':
server_control_port => 8005,
http_port => 8080,
ajp_connector => 8009,
}
tomcat::instance { 'instance2':
server_control_port => 8105,
http_port => 8081,
ajp_connector => 8109,
manage_firewall => true,
}
tomcat::instance { 'instance3':
server_control_port => 8205,
http_port => 8082,
ajp_connector => 8209,
}
tomcat::instance { 'instance4':
server_control_port => 8305,
http_port => 8083,
ajp_connector => 8309,
}
tomcat::instance { 'instance5':
server_control_port => 8405,
http_port => 8084,
ajp_connector => 8409,
}
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Could not parse for environment production: Syntax error at 'workers_file_content' at /etc/puppetlabs/code/environments/production/manifests/site.pp:42:1 on node puppetagent
when I test the same changes using the agent this is the error
↧
If condition not working
I have written the script :
class test
{
if ($admin=='false')
{
notice("Non Admin user")
}
if ($admin=='true')
{
notice("Admin User")
}
}
I am setting the value of 'admin' variable using Facter as "set Facter_ admin=true" or "set Facter_ admin=false". When I run this script, the message is not being displayed on the console; control it is not going inside the if condition. Any idea what I am doing wrong? I am calling this class from a manifest :
node default
{
include test
}
↧
↧
Environment from ldap not used/set.
I want to migrate/rebuild our exisiting puppet 3.8 environment to be more up-to-date and have it more structured without too much impact on the existing environment. This old environment uses ldap-stored environment settings, and for some machines also some puppetclasses. However getting ldap to work within the new setup is challenging as the official documentation (link:[here](https://puppet.com/docs/puppet/5.3/nodes_ldap.html"version 5")) is limited and basicly incorrect. The old version works with the current ldap data, and according to various other resources that data is complete. No doubt to question that, as I checked it with ldapsearch.
I installed puppetserver 5.1.4 and the agent 5.3.3 onto a fresh machine. And made the following changes:
* pointed the cert.pem to the system one as it also contains the certificate for our proxy, otherwise module-actions would be impossible.
* installed jruby-ldap-patched (puppetserver gem install jruby-ldap-patched) The documentation refers to the 12 year old ruby-ldap, which won't work with the java based puppetserver. The jruby-ldap is able to query the ldapserver, but can't handle the results properly. (I saw the query in the ldap logs, but didn't get a sensible response) What I do expect to see is: (old client to old server) # puppet agent -t --noop Warning: Local environment: "production" doesn't match server specified node environment "lab", switching agent to "lab". Info: Retrieving pluginfacts Info: Retrieving plugin ... What I see: (new server and agent) # puppet agent -t --noop Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Cannot reassign variable '$environment' on node myhost.mydomain.lab Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run I'm testing my agent on the same machine as my puppetserver, so the config is combined: # cat puppet.conf [master] vardir = /opt/puppetlabs/server/data/puppetserver logdir = /var/log/puppetlabs/puppetserver rundir = /var/run/puppetlabs/puppetserver pidfile = /var/run/puppetlabs/puppetserver/puppetserver.pid codedir = /etc/puppetlabs/code autosign = true pluginsync = true # ldap config node_terminus = ldap ldapserver = ldap.mydomain.lab ldapbase = ou=Servers,dc=my-securedomain,dc=net ldapstring = (&(objectclass=puppetClient)(cn=%s)) ldapclassattrs = puppetClass ldapattrs = all [main] certname = myhost.mydomain.lab dns_alt_names = puppet,puppet.mydomain.lab,myhost.mydomain.lab,myhost run_interval = 3600 [agent] pluginsync=true server = myhost.mydomain.lab What did I miss, or did I stumble upon a bug?
Any good links on how to accomplish this task using an hiera-ldap ENC are also welcomed.
* pointed the cert.pem to the system one as it also contains the certificate for our proxy, otherwise module-actions would be impossible.
* installed jruby-ldap-patched (puppetserver gem install jruby-ldap-patched) The documentation refers to the 12 year old ruby-ldap, which won't work with the java based puppetserver. The jruby-ldap is able to query the ldapserver, but can't handle the results properly. (I saw the query in the ldap logs, but didn't get a sensible response) What I do expect to see is: (old client to old server) # puppet agent -t --noop Warning: Local environment: "production" doesn't match server specified node environment "lab", switching agent to "lab". Info: Retrieving pluginfacts Info: Retrieving plugin ... What I see: (new server and agent) # puppet agent -t --noop Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Cannot reassign variable '$environment' on node myhost.mydomain.lab Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run I'm testing my agent on the same machine as my puppetserver, so the config is combined: # cat puppet.conf [master] vardir = /opt/puppetlabs/server/data/puppetserver logdir = /var/log/puppetlabs/puppetserver rundir = /var/run/puppetlabs/puppetserver pidfile = /var/run/puppetlabs/puppetserver/puppetserver.pid codedir = /etc/puppetlabs/code autosign = true pluginsync = true # ldap config node_terminus = ldap ldapserver = ldap.mydomain.lab ldapbase = ou=Servers,dc=my-securedomain,dc=net ldapstring = (&(objectclass=puppetClient)(cn=%s)) ldapclassattrs = puppetClass ldapattrs = all [main] certname = myhost.mydomain.lab dns_alt_names = puppet,puppet.mydomain.lab,myhost.mydomain.lab,myhost run_interval = 3600 [agent] pluginsync=true server = myhost.mydomain.lab What did I miss, or did I stumble upon a bug?
Any good links on how to accomplish this task using an hiera-ldap ENC are also welcomed.
↧
I want to start Puppet agent I have been already installed Puppet agent
I want to start Puppet agent I have been already installed Puppet agent but when I write this command for start sudo /opt/puppetlabs/bin/puppet resource service puppet ensure=running enable=true this gives the following error Error: /Service[puppet]: Could not evaluate: Could not find init script or upstart conf file for 'puppet' Error: Could not run: Could not find init script or upstart conf file for 'puppet'.
I am trying to install puppet agent 14.04
↧
Puppet First install - Could not find class ::ntp
Hello, team!
I'm very new on this puppet universe and i'm trying to get together a small PoC so see if puppet would be able to manage my infrastructer.
I followed a couple of receipes, installing a puppet master server and a puppet node, and right now i'm not able apply a new module on the node. The error that i get is:
puppet agent -t
Info: Using configured environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Function Call, Could not find class ::ntp for cn23.mycorporatedomain.com at /etc/puppetlabs/code/environments/production/manifests/site.pp:2:4 on node cn23.mycorporatedomain.com
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
Even with the debug option on the error itself is not clear. I've attached the following files for help:
puppetAgent.conf
[main]
certname = cn23.mycorporatedomain.com
server = sp218.mycorporatedomain.com
environment = production
[agent]
report = true
[master]
always_cache_features = true
Puppet master tree organization
/etc/puppetlabs/
├── code/
│ ├── environments/
│ │ └── production/
│ │ ├── data/
│ │ ├── manifests/
│ │ │ └── site.pp*
│ │ ├── modules/
│ │ │ ├── ntp/
│ │ │ │ └── manifests/
│ │ │ │ └── init.pp*
│ │ │ ├── manifests/
│ │ │ │ ├── init.pp
│ │ │ │ └── stages.pp
│ │ │ ├── readmes/
│ │ │ │ └── README_ja_JP.md
│ │ ├── environment.conf
│ │ └── hiera.yaml
│ └── modules/
├── mcollective/
│ ├── client.cfg
│ ├── data-help.erb
│ ├── discovery-help.erb
│ ├── facts.yaml
│ ├── metadata-help.erb
│ ├── rpc-help.erb
│ └── server.cfg
├── puppet/
│ ├── ssl/
│ │ ├── ca/
│ │ │ ├── private/
│ │ │ ├── requests/
│ │ │ ├── signed/
│ │ │ │ ├── cn23.mycorporatedomain.com.pem*
│ │ │ │ ├── sp218.mycorporatedomain.com.pem
│ │ │ │ └── sp227.mycorporatedomain.com.pem*
│ │ │ ├── ca_crl.pem
│ │ │ ├── ca_crt.pem
│ │ │ ├── ca_key.pem
│ │ │ ├── ca_pub.pem
│ │ │ ├── inventory.txt
│ │ │ └── serial
│ │ ├── certificate_requests/
│ │ ├── certs/
│ │ │ ├── ca.pem
│ │ │ └── sp218.mycorporatedomain.com.pem
│ │ ├── private/
│ │ ├── private_keys/
│ │ │ └── sp218.mycorporatedomain.com.pem
│ │ ├── public_keys/
│ │ │ └── sp218.mycorporatedomain.com.pem
│ │ └── crl.pem
├── puppetserver/
│ ├── conf.d/
│ │ ├── auth.conf
│ │ ├── global.conf
│ │ ├── metrics.conf
│ │ ├── puppetserver.conf
│ │ ├── web-routes.conf
│ │ └── webserver.conf
│ ├── services.d/
│ │ └── ca.cfg
│ ├── logback.xml
│ └── request-logging.xml
└── pxp-agent/
└── modules/
Puppet node tree organization
/etc/puppetlabs/
├── code/
│ ├── environments/
│ │ └── production/
│ │ ├── data/
│ │ ├── manifests/
│ │ ├── modules/
│ │ ├── environment.conf
│ │ └── hiera.yaml
│ └── modules/
├── mcollective/
│ ├── client.cfg
│ ├── data-help.erb
│ ├── discovery-help.erb
│ ├── facts.yaml
│ ├── metadata-help.erb
│ ├── rpc-help.erb
│ └── server.cfg
├── puppet/
│ ├── ssl/
│ │ ├── ca/
│ │ │ ├── private/
│ │ │ ├── requests/
│ │ │ ├── signed/
│ │ │ ├── ca_key.pem
│ │ │ └── ca_pub.pem
│ │ ├── certificate_requests/
│ │ │ └── cn23.mycorporatedomain.com.pem
│ │ ├── certs/
│ │ │ ├── ca.pem
│ │ │ └── cn23.mycorporatedomain.com.pem
│ │ ├── private/
│ │ ├── private_keys/
│ │ │ └── cn23.mycorporatedomain.com.pem
│ │ ├── public_keys/
│ │ │ └── cn23.mycorporatedomain.com.pem
│ │ └── crl.pem
│ ├── auth.conf
│ ├── hiera.yaml
│ └── puppet.conf
└── pxp-agent/
└── modules/
ini.pp
class ntp {
package{'ntp':
ensure => installed,
}
service{'ntpd':
ensure => running,
enable => true,
require => Package['ntp'],
}
}
site.pp
node 'cn23.mycorporatedomain.com'{
include ntp
}
Tks in advance!
↧
Mounting. the files
Hey. thanks a lot for your help, I have successfully done everything apart from mounting, kindly help me how I can do it. regards.
node "puppetagent" {
include tomcat
include apache
include apache::mod::jk
}
apache::vhost { 'tomcat.dddke.net':
port => '80',
docroot => '/var/www/html',
}
apache::vhost { 'tomcat1.dddke.net':
port => '80',
docroot => '/var/www/html',
}
apache::vhost { 'tomcat2.dddke.net':
port => '80',
docroot => '/var/www/html',
}
apache::vhost { 'tomcat3.dddke.net':
port => '80',
docroot => '/var/www/html',
}
apache::vhost { 'tomcat4.dddke.net':
port => '80',
docroot => '/var/www/html',
}
file { '/usr/lib/apache2/modules/mod_jk.so':
ensure => 'file',
}
file { '/etc/apache2/mods-enabled/load':
ensure => 'directory',
}
class { '::apache::mod::jk':
ip => '34.227.150.91',
workers_file => 'conf.d/workers.properties',
mount_file => 'conf.d/uriworkermap.properties',
shm_file => 'run/jk.shm',
shm_size => '50M',
workers_file_content => {
worker_lists => ['tomcat8', 'instance1', 'instance2', 'instance3', 'instance4', 'instance5'],
worker_mantain => '60',
some_name => {
comment => 'Optional comment',
type => 'ajp13',
socket_keepalive => 'true',
},
other_name => {
comment => 'I just like comments',
type => 'ajp12',
socket_keepalive => 'false',
},
}
}
class {'tomcat':
service_ensure => 'running',
service_enable => true
}
tomcat::instance { 'instance1':
server_control_port => 8005,
http_port => 8080,
ajp_connector => 8009,
}
tomcat::instance { 'instance2':
server_control_port => 8105,
http_port => 8081,
ajp_connector => 8109,
manage_firewall => true,
}
tomcat::instance { 'instance3':
server_control_port => 8205,
http_port => 8082,
ajp_connector => 8209,
}
tomcat::instance { 'instance4':
server_control_port => 8305,
http_port => 8083,
ajp_connector => 8309,
}
tomcat::instance { 'instance5':
server_control_port => 8405,
http_port => 8084,
ajp_connector => 8409,
}
↧
↧
How to configure single Puppet Master with Multiple Puppet Agents
I have the knowledge of configuring one puppet master with one puppet agent. But if i need to have multiple agents configured with single master puppet ,then how can it be done
↧
Make a different exec for diferents Windows O.S.
I want to execute a command if the OS is Windows 7 and another command if is another Windows OS. How can i make this?
↧
application orchestration: consuming services
Hi,
I've declared a very simple application and I'm trying to consume/export services in order to share configuration parameters. Unfortunately I'm geting an error that says a parameter hadn't been set.
/opt/puppetlabs/client-tools/bin/puppet-app show --environment production
Failed to retrieve application instances: puppetlabs.orchestrator/unknown-error: java.io.IOException: HTTP GET to https://vm-lab-linux-1.msc.es:8140/puppet/v3/environment/production:500: Server Error: Arqjeer02::Pe::Mdw::Cmpt2[cmptapp1]: expects a value for parameter 'port' in environment production
Can anybody help me with this error?
The application is the next:
site {
create_component_app('arqjeer02::pe::cmptapp', 'cmptapp1', {
'components' => {
'Arqjeer02::Pe::Mdw::Cmpt1' => ['wl02-pub-t01-p0.msc.com'],
'Arqjeer02::Pe::Mdw::Cmpt2' => ['wl02-pub-t01-p0.msc.com'],
}
})
arqjeer02/manifests/pe/cmptapp.pp:
application arqjeer02::pe::cmptapp (
) {
arqjeer02::pe::mdw::cmpt1 {$name:
port => 22,
export => Arqjeer02::Pe::Mdw::Cmpt1[$name],
}
arqjeer02::pe::mdw::cmpt2 {$name:
export => Arqjeer02::Pe::Mdw::Cmpt2[$name],
consume => Arqjeer02::Pe::Mdw::Cmpt1[$name],
}
}
arqjeer02/manifests/pe/mdw/cmpt1.pp:
define arqjeer02::pe::mdw::cmpt1 (
$port, ) { notify {"${name} -
port: ${port}":} }
Arqjeer02::Pe::Mdw::Cmpt1 produces
Cmpt1 { cmpt1_port => "81", }
arqjeer02/manifests/pe/mdw/cmpt2.pp:
define arqjeer02::pe::mdw::cmpt2 (
$port,
) {
notify {"${name} - port: ${port}":}
}
Arqjeer02::Pe::Mdw::Cmpt2 produces Dependency{}
Arqjeer02::Pe::Mdw::Cmpt2 consumes Cmpt1 {
port => $cmpt1_port,
}
arqjeer02/lib/puppet/type/cmpt1.rb:
Puppet::Type.newtype :cmpt1, :is_capability => true do
newparam :cmpt1_port
end
↧
puppetlabs-accounts in PE v2017.3.1
Install this module but the drop-down list from "add new class" does not show this module. I can only see pe_accounts* from PE installation.
document said:
To use this module, add this declaration to your Puppetfile:
mod 'puppetlabs-accounts', '1.2.1'
I created a file : /etc/puppetlabs/code/environments/production/Puppetfile
with one line:
mod 'puppetlabs-accounts', '1.2.1'
Still not see this module (class) from drop-down, I cant add/use this class in PE ?
↧
↧
Mounting the File contents.
Hey,
how do i file the file contents? i am not understanding this part,
mount_file_content
Each directive has the format = . This maps as a hash of hashes, where the outer hash specifies workers, and each inner hash contains two items: uri_list - an array with URIs to be mapped to the worker - and comment - an optional string with a comment for the worker.
For example, the mount file below:
1
2
3
4
5
6
7
8
# Worker 1
/context_1/ = worker_1
/context_1/* = worker_1
# Worker 2
/ = worker_2
/context_2/ = worker_2
/context_2/* = worker_2
Should be parameterized as:
1
2
3
4
5
6
7
8
9
10
$mount_file_content = {
worker_1 => {
uri_list => ['/context_1/', '/context_1/*'],
comment => 'Worker 1',
},
worker_2 => {
uri_list => ['/context_2/', '/context_2/*'],
comment => 'Worker 2',
},
},
node "puppetagent" {
include tomcat
include apache
include apache::mod::jk
}
apache::vhost { 'tomcat.dddke.net':
port => '80',
docroot => '/var/www/html',
}
apache::vhost { 'tomcat1.dddke.net':
port => '80',
docroot => '/var/www/html',
}
apache::vhost { 'tomcat2.dddke.net':
port => '80',
docroot => '/var/www/html',
}
apache::vhost { 'tomcat3.dddke.net':
port => '80',
docroot => '/var/www/html',
}
apache::vhost { 'tomcat4.dddke.net':
port => '80',
docroot => '/var/www/html',
}
file { '/usr/lib/apache2/modules/mod_jk.so':
ensure => 'file',
}
file { '/etc/apache2/mods-enabled/load':
ensure => 'directory',
}
class { '::apache::mod::jk':
ip => '34.227.150.91',
workers_file => 'conf.d/workers.properties',
mount_file => 'conf.d/uriworkermap.properties',
shm_file => 'run/jk.shm',
shm_size => '50M',
workers_file_content => {
worker_lists => ['tomcat8', 'instance1', 'instance2', 'instance3', 'instance4', 'instance5'],
worker_mantain => '60',
some_name => {
comment => 'Optional comment',
type => 'ajp13',
socket_keepalive => 'true',
},
other_name => {
comment => 'I just like comments',
type => 'ajp12',
socket_keepalive => 'false',
},
}
}
i want to mount tomcat8, instance1, instance2, instance3, instance4 and instance5 as shown above in the file... your help will be greatly appreciated.
regards.
↧
Mount Example
just have a look at this, is it the correct way of mounting the worker.properties file? kindly assistnode "puppetagent" {
include tomcat
include apache
include apache::mod::jk
}
apache::vhost { 'tomcat.dddke.net':
port => '80',
docroot => '/var/www/html',
}
apache::vhost { 'tomcat1.dddke.net':
port => '80',
docroot => '/var/www/html',
}
apache::vhost { 'tomcat2.dddke.net':
port => '80',
docroot => '/var/www/html',
}
apache::vhost { 'tomcat3.dddke.net':
port => '80',
docroot => '/var/www/html',
}
apache::vhost { 'tomcat4.dddke.net':
port => '80',
docroot => '/var/www/html',
}
class { '::apache::mod::jk':
ip => '34.227.150.91',
workers_file => 'conf.d/workers.properties',
mount_file =>'conf.d/uriworkermap.properties',
shm_file => 'run/jk.shm',
shm_size => '50M',
workers_file_content => {
worker_lists => ['tomcat8', 'instance1', 'instance2', 'instance3' ,'instance4', 'instance5'],
worker_mantain => '60',
some_name => {
comment => 'Optional comment',
type => 'ajp13',
socket_keepalive => 'true',
},
other_name => {
comment => 'I just like comments',
type => 'ajp12',
socket_keepalive => 'false',
},
}
mount_file_content => {
worker_1 => {
uri_list => ['/context_1/', '/context_1/*'],
comment => 'Worker 1',
},
worker_2 => {
uri_list => ['/context_2/', '/context_2/*'],
comment => 'Worker 2',
},
worker_3 => {
uri_list => ['/context_3/', '/context_3/*'],
comment => 'Worker 3',
},
worker_4 => {
uri_list => ['/context_4/', '/context_4/*'],
comment => 'Worker 4',
},
worker_5 => {
uri_list => ['/context_5/', '/context_5/*'],
comment => 'Worker 5',
},
}
↧
mcollective certificates are unable to get their certificate CRL (with use of an external CA)
Hi,
First some background info... Me and some colleagues at work are trying out Puppet Enterprise 2017.3 (free edition for 10 nodes) because we are interested in getting Puppet as our new linux desired state configtool. We already have an internal intermediate CA from Microsoft in place which we want to use instead of the build-in CA of Puppet for security reasons/policies..
Followed documentation: (which we ran over 6 times already, always from a clean install on RedHat Enterprise Linux 7.3)
https://puppet.com/docs/pe/2017.3/ssl_and_certificates/using_an_external_certificate_authority_with_pe.html
For testing purposes we just used one 1 certificate(that comes from our internal intermediate CA) that we tried to implement for all PE-services.. (=puppet01.domainname.com)
External CA Generated File Location on Host Name of File
CA's certificate /etc/puppetlabs/puppet/ssl/certs ca.pem = **here we use a .pem file that contains the root CA+intermediate CA**
CA's CRL /etc/puppetlabs/puppet/ssl crl.pem = **here we use the CRL of the intermediate CA**
CA's CRL /etc/puppetlabs/puppet/ssl/ca ca_crl.pem = **here we use the CRL of the intermediate CA again**
Host's Cert /etc/puppetlabs/puppet/ssl/certs .pem = **here we used puppet01.domainname.com**
Host's Public Key etc/puppetlabs/puppet/ssl/public_keys .pem =**here we used puppet01.domainname.com**
Host's Private Key etc/puppetlabs/puppet/ssl/private_keys .pem = **here we used the private key of puppet01.domainname.com**
When we run "puppet agent -t" on the end, we get the following error:
> [root@puppet01 ssl]# puppet agent -t
Warning: Unable to fetch my node definition, but the agent run will continue:
Warning: SSL_connect returned=1 errno=0 state=unknown state: sslv3 alert certificate unknown
Info: Retrieving pluginfacts
Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': SSL_connect returned=1 errno=0 state=unknown state: sslv3 alert certificate unknown
Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Could not evaluate: Could not retrieve file metadata for puppet:///pluginfacts: SSL_connect returned=1 errno=0 state=unknown state: sslv3 alert certificate unknown
Info: Retrieving plugin
Error: /File[/opt/puppetlabs/puppet/cache/lib]: Failed to generate additional resources using 'eval_generate': SSL_connect returned=1 errno=0 state=unknown state: sslv3 alert certificate unknown
Error: /File[/opt/puppetlabs/puppet/cache/lib]: Could not evaluate: Could not retrieve file metadata for puppet:///plugins: SSL_connect returned=1 errno=0 state=unknown state: sslv3 alert certificate unknown
Info: Loading facts
Error: Could not retrieve catalog from remote server: SSL_connect returned=1 errno=0 state=unknown state: sslv3 alert certificate unknown
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
Error: Could not send report: SSL_connect returned=1 errno=0 state=unknown state: sslv3 alert certificate unknown
And when we run a "puppet cert list --all"
> [root@puppet01 ssl]# puppet cert list --all
- "pe-internal-mcollective-servers" (SHA256) 3B:24:BD:01:28:0C:7F:30:D1:33:E1:C4:A5:B8:A0:1F:3C:FF:66:AB:6A:B6:44:54:30:5C:C3:03:FA:3C:15:02 (unable to get certificate CRL)
- "pe-internal-peadmin-mcollective-client" (SHA256) F6:AB:74:B9:B4:D7:83:BE:7F:F7:BC:71:9D:CF:B8:22:55:03:5D:9C:2B:BD:36:C3:7C:CE:7A:FA:5D:EF:BF:F6 (unable to get certificate CRL)
- "puppet01.domainname.no" (SHA256) 41:22:04:63:5F:8D:C5:D1:11:5C:B4:DF:4C:2C:B5:83:8C:03:21:4C:B8:F1:8D:69:2A:04:3C:09:BF:11:56:5C (unable to get certificate CRL)
When I do a "openssl x509 -in "pe-internal-mcollective-servers.pem" -text" after awhile to check out the mcollective-certificates, then i see that something has overwritten our certificates again. This is because the issuer of the certificate has been set back to "Puppet Enterprise CA"...I presume that the internal CA of Puppet somehow has been reactivated???
We are really clueless at the moment, can someone please help us out?
Friendly regards,
Jonas
↧
Simple top-level yaml hash not merging
I have the following hiera definitions:
# hiera.yaml
:backends:
- yaml
:yaml:
:datadir: /home/supermathie/puppettest
:hierarchy:
- local
- global
# global.yaml
containers:
auth-proxy:
image: 'devel/auth-proxy'
kibana:
image: 'devel/kibana'
elasticsearch:
image: 'devel/elasticsearch'
logstash:
image: 'devel/logstash'
# local.yaml
containers:
kibana:
image: 'devel/kibana-local'
I'm trying to override a single item in the `containers` hash, but I don't understand why it isn't merging the contents from both yaml files - everything I've read so far says that this is *supposed* to work:
$ puppet apply --hiera_config hiera.yaml <<<"notice(hiera('containers'))"
Notice: Scope(Class[main]): {"kibana"=>{"image"=>"devel/kibana-local"}}
Expected output:
$ puppet apply --hiera_config hiera.yaml <<<"notice(hiera('containers'))"
Notice: Scope(Class[main]): {"auth-proxy"=>{"image"=>"devel/auth-proxy"}, "kibana"=>{"image"=>"devel/kibana-local"}, "elasticsearch"=>{"image"=>"devel/elasticsearch"}, "logstash"=>{"image"=>"devel/logstash"}}
What's going wrong?
---
Versions:
$ puppet -V
3.8.7
$ hiera -V
1.3.4
↧
↧
Install tomcat on windows server 2012 agent from Centos linux master
Hi,
I am very new to puppet and trying to install tomcat on my windows agent server 2012 and my master server is Centos linux.
I am installing tomcat module on centos but that is not made up for windows and so when i am writing a manifest to install tomcat on windows it certainly gives an error of unsupported family type.
Please can you brief me the process of doing this.
↧
How do you deploy Hadoop to Ubuntu with Puppet when there is an "Error: Execution of ... hadoop-hdfs-namenode"?
I want to install Hadoop with Puppet. I am using Puppet 5.x on Ubuntu 16.x in AWS. On Puppet Master, I ran this: "puppet module install cesnet-hadoop --version 2.4.3" to use the module from https://forge.puppet.com/cesnet/hadoop/.
This is my site.pp file:
class{"hadoop":
hdfs_hostname => $::fqdn,
yarn_hostname => $::fqdn,
slaves => [ $::fqdn ],
frontends => [ $::fqdn ],
properties => {
'dfs.replication' => 1,
}
}
I ran the puppet agent command from a node client, but I got this error:
> Error: Execution of '/usr/bin/apt-get> -q -y -o DPkg::Options::=--force-confold> install hadoop-hdfs-namenode' returned> 100: Reading package lists... Building> dependency tree... Reading state> information... E: Unable to locate> package hadoop-hdfs-namenode Error:> /Stage[main]/Hadoop::Namenode::Install/Package[hadoop-hdfs-namenode]/ensure:> change from 'purged' to 'present'> failed: Execution of '/usr/bin/apt-get> -q -y -o DPkg::Options::=--force-confold> install hadoop-hdfs-namenode' returned> 100: Reading package lists... Building> dependency tree... Reading state> information... E: Unable to locate> package hadoop-hdfs-namenode
I ran puppet apply from the Puppet Master server, but I got this:
> Error: Execution of '/usr/bin/apt-get> -q -y -o DPkg::Options::=--force-confold> install hadoop-hdfs-namenode' returned> 100: Re Building dependency tree...> Reading state information... E: Unable> to locate package hadoop-hdfs-namenode> Error:> /Stage[main]/Hadoop::Namenode::Install/Package[hadoop-hdfs-namenode]/ensure:> change from 'purged' to 'present'> failed:100: Reading package lists...> Building dependency tree... Reading> state information... E: Unable to> locate package hadoop-hdfs-namenode> Error: Could not set 'file' on ensure:> No such file or directory @> dir_s_mkdir -> /etc/hadoop/conf/slaves20171201-9273-xuym37.> Error: Could not set 'file' on ensure
I cannot get Hadoop to be deployed (on a puppet agent node or a Puppet Master server). Other manifests work. How do I deploy Hadoop to Ubuntu servers? I tried this https://github.com/viirya/puppet-hadoop but I had a different problem. I just want to deploy Hadoop via Puppet to Ubuntu Linux servers.
↧
unable to update PE2017.3 on ubuntu 16.04
I have Puppet Enterprise 2017.3 installed and working but when updating Ubuntu 16.04 it fail at
Get:8 file:/opt/puppetlabs/server/data/packages/public/2017.3.0/ubuntu-16.04-amd64-5.3.2 ./ Packages [6,638 B]
Reading package lists... Done
W: Invalid 'Date' entry in Release file /var/lib/apt/lists/partial/_opt_puppetlabs_server_data_packages_public_2017.3.0_ubuntu-16.04-amd64-5.3.2_._Release
I've tried to delete the file /var/lib/apt/lists/partial/_opt_puppetlabs_server_data_packages_public_2017.3.0_ubuntu-16.04-amd64-5.3.2_._Release but doesn't help.
Any ideas on how to fix?
Thanks
↧