Installation and Client Certificate --- puppet series

Introduction puppet Puppet configuration ruby language development tool based automation system, can C / S mode or stand-alone operation, and supports configuration management for all UNIX and UNIX-like systems, have begun to support the latest version of the Windows operating system for a limited number of management. Puppet tube applies to the entire server process, such as initial installation, system configuration updates, and offline. Puppet installation support for source code installation, yum install ruby of gem and installation. Official website recommended to use yum to install puppet, future aspects of the upgrade, manage and maintain. Centos yum may be employed to install, but not in the default source Centos puppet package, it is necessary to install the package epel. Epel is an acronym for Enterprise Linux add-on package (Extra Packages for Enterprise Linux) is created by a special interest group, maintenance and management for Red Hat Enterprise Linux (RHEL) and its derivative distributions (such as CentOS, Scientific Linux) is a high-quality add-on package projects. First, the installation 1, the installation puppet source, (Server and client-end had to be installed)
#rpm -Uvh http://yum.puppetlabs.com/el/6/products/i386/puppetlabs-release-6-6.noarch.rpm
2, install puppet Server:
# yum install  -y puppet-server
# /etc/init.d/puppetmaster start
Client:
# yum install  -y puppet
# /etc/init.d/puppet start
Installation: Perhaps many people will forget to install puppet sources, direct yum pro, practice tells us that the source is not installed, very sad reminder encounter various problems. One problem: Error: Package: ruby-libs -1.8.7.374-1.el5.x86_64 (puppetlabs-deps) Requires: libtk8.4.so () (64bit) Error: Package: ruby-libs-1.8.7.374-1 .el5.x86_64 (puppetlabs-deps) Requires: libtcl8.4.so () (64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles -nodigest question two : Error: Package: puppet-2.7.20-1.el6.rf.noarch (rpmforge) Requires: ruby-augeas You could try using --skip-broken to work around the problem You could try running: rpm -Va - nofiles -nodigest Second, a certificate, configure the hostname 03 2, client application for a certificate [vmclient63 the root @ ~] # puppetd --server vmserver62 -test 01 . 3, Server certificates #puppetca -s vmclient63 02 Note that often occur certificates failed first: [root @ vmserver62 ~] # puppetca -s vmclient63 err: Could not call sign: Could not find certificate request for vmclient63 second: [root @ vmclient63 ~] # puppetd - server vmserver62 --test info: Caching certificate for ca info: Creating a new SSL certificate request for vmclient63 info: Certificate Request fingerprint (md5): 99: 32: 9E: 78: 69: 55: 0D: AD: 1A: E5: 25: 60: FB: 95: 8A: 22 Exiting; no certificate found and waitforcert is disabled solution:
#puppetca --clean  vmclient63(服务端)或者 #puppetca -c -a
#/etc/init.d/puppetmaster restart (服务端)
#rm -rf /var/lib/puppet  (客户端)
#/etc/init.d/puppet restart(客户端)
# puppetd --server vmserver62 --test (客户端)
#puppetca --list ?(服务端)
For reprint please indicate the source: http://www.ttlsa.com/html/2734.html

Reproduced in: https: //my.oschina.net/766/blog/210989

Guess you like

Origin blog.csdn.net/weixin_33674976/article/details/91493004