Featured Post

Directory environments in Puppet

Environments are individual groups of Puppet agents each environment have there own completely different manifests and module-paths. This basically is useful for testing changes to our Puppet code before implementing them on production machines. There are two types of implementation of environments structure in Puppet one if directory based and another is config file based here we will see bit of an insight about directory based. As usual for more information about this you can visit puppetlabs official website. On the master node: Append following details in puppet.conf which is placed under /etc/puppet or /etc/puppetlabs/puppet:     Under [main] section add a variable called confdir with value as /etc/puppet or /etc/puppetlabs/puppet     confdir=/etc/puppet Then add information regarding environments/manifests and modulepath in it.      #environments     environmentpath = $confdir/environments     default_manfiest = $confdir/manifests     basemodulepath =
Post a Comment

puppet master???

*Master daemon in Puppet "puppet master"*

Puppet master is the central puppet server. Firing this command "puppet master" starts an instance of puppet master and runs as a daemon by default.

[root@puppet ~]# /etc/init.d/puppetmaster status
puppetmasterd is stopped
[root@puppet ~]# puppet master
[root@puppet ~]# /etc/init.d/puppetmaster status
puppetmasterd (pid  31281) is running...
[root@puppet ~]#

If you want to enable full debugging mode while executing puppet master you can use the option --debug while firing it.

[root@puppet ~]# puppet master --debug --no-daemonize
debug: Puppet::Type::User::ProviderPw: file pw does not exist
debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist
debug: Puppet::Type::User::ProviderLdap: true value when expecting false
debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not exist
debug: Failed to load library 'rubygems' for feature 'rubygems'
debug: /File[/var/lib/puppet/reports]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/ssl/private]: Autorequiring File[/var/lib/puppet/ssl]
debug: /File[/var/lib/puppet/server_data]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/yaml]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring File[/var/lib/puppet/ssl]
debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/fileserver.conf]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring File[/var/lib/puppet/ssl/certs]
..........
..........
..........
debug: Using cached certificate for ca
debug: Using cached certificate for puppet.sunny.com
notice: Starting Puppet master version 2.7.25
debug: Finishing transaction 70212603728220
Using --no-daemonize option will get all your information on the foreground as stated above.

If you want to keep this information in a log kind of a thing at a custom location you can use the option --logdest while using it.

[root@puppet ~]# puppet master --debug --logdest /tmp/puppet_master_log
[root@puppet ~]#

Now if you will cat this file /tmp/puppet_master_log you can see all information regarding puppet master startup.

To see the version of puppet master you can use --version option.

[root@puppet ~]# puppet master --version
2.7.25
[root@puppet ~]#


To see the configuration parameters of the puppet master you can fire this command.

[root@puppet ~]# puppet master --genconfig > /tmp/puppet_conf

This command will create a sample configuration file in /tmp directory as puppet_conf.

To see what is the path of ssldir:

[root@puppet ~]# puppet master --genconfig | grep ssldir
    # The default value is '$ssldir/crl.pem'.
    ssldir = /var/lib/puppet/ssl
    # The default value is '$ssldir/private_keys'.

Comments

  1. UnknownNovember 24, 2016 at 11:51 PM

    thank you for this marvellous post. Puppet master can also be managed by other application servers; when this is the case, this executable is not used.

    ReplyDelete
  2. UnknownJune 24, 2018 at 10:25 PM

    The information you provided in this Blog is very useful and The information is worth and very useful for the beginners. UiPath automation platform enables global enterprises to design, deploy and manage a full fledged robotic workforce that mimics employees in administering rules-based tasks and frees them from the daily routine of rote work. Know more Details About Uipath Click here.

    ReplyDelete

Post a Comment

Popular posts from this blog

Exec in Puppet

Exec is a very useful resource type present in Puppet which is used to executes external commands. Puppet basically runs as a daemon in which it executes every 30 mins. So while writing an exec resource type make sure that the exec resource must be able to run multiple times without causing any harm to the machine i.e. it must be idempotent. Suppose you just want to run a command like reload a service for that what you can do is? exec { "reload httpd": command => "service httpd reload", path => "/usr/local/bin/:/bin/:/sbin/", } Lets break this line by line: exec { "reload httpd": This specifies that the resource type is exec type and has a human readable name as "reload httpd". command => "service httpd reload", This specified which command to execute when puppet is executed. path => "/usr/local/bin/:/bin/:/sbin/", This specifies where the binary service can be found in your mac
Read more

Un-revoke the revoked certificate in Puppet

If you revoked or deleted the puppet agent’s certificate accidentally. Basically it is nearly impossible un-revoke a certificate. The solution is to recover all revoked certificates then revoke other certificates which don’t need to be recovered. But if in-case you have thousands of revoked certificates then its a bit lengthy process. Second one is to generate a new certificate for the client/agent and get that signed by the puppet master.  List of all the certificates which are signed at the moment:  [root@puppet requests]# puppet cert list --all + "fedora20"            (AE:57:40:F6:FC:E1:CD:DD:ED:EE:1E:8C:A7:81:0D:76) + "kubuntu14.sunny.com" (20:6B:A1:E2:A3:DE:B1:95:C8:80:4C:B4:27:2B:C0:A2) + "puppet.sunny.com"    (68:12:76:3C:D0:F8:0D:2D:8B:2B:40:E7:49:2D:55:5B) (alt names: "DNS:puppet", "DNS:puppet.sunny.com") + "rhel6.sunny.com"     (DC:6E:B1:FC:27:1D:7A:2A:85:E7:3E:3A:24:8B:64:D3) [root@puppet requests]# N
Read more

Dry run in Puppet --noop

 Dry run in puppet is a powerful feature given by puppet. This basically is used to test your Puppet manifests on any of the environment without actually making any changes to the machine. To dry-run Puppet, --noop flag needs to be used. Puppet’s ‘noop’ (no-operation) mode shows you what would happen, but actually doesn’t do anything :) This basically helps us for debugging stuff. For instance: [root@puppet manifests]# puppet apply site.pp --noop notice: /Stage[main]/Sudo/File[/etc/sudoers]/content: current_value {md5}e81452ad78198a79772447b1f2b3b614, should be {md5}e2d690ebe349d93efa84146eb854c987 (noop) notice: Class[Sudo]: Would have triggered 'refresh' from 1 events notice: /Stage[main]/Ssh::Service/Service[sshd]/ensure: current_value stopped, should be running (noop) notice: Class[Ssh::Service]: Would have triggered 'refresh' from 1 events notice: Stage[main]: Would have triggered 'refresh' from 2 events notice: Finished catalog run in 2.75 seco
Read more