使用命令生成puppet.conf无法启动puppet master问题解决
2016-07-11 16:56
381 查看
最近对puppet比较感兴趣,然后就在虚拟机上装了puppet。一台当server,一台当agent。因为默认的puppet默认配置文件只有main和agent两个选项,并没有master。所以我使用了命令puppet –genmaster > /etc/puppet/puppet.conf,之后使用init.d下的脚本启动puppet master就起不来了。。。具体如下:
一、 环境:
1. 系统: CentOS 6.5
2. puppet版本:puppet-server-2.7.26-2.el6.noarch puppet-2.7.26-2.el6.noarch
二、问题现象:
使用/etc/init.d/puppetmasterd start启动时,在命令行会出现如下的错误:
Starting puppetmaster: /usr/lib/ruby/site_ruby/1.8/puppet/util/pidlock.rb:39:in
from /usr/lib/ruby/site_ruby/1.8/puppet/util/pidlock.rb:39:in
from /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:44:in
from /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:44:in
from /usr/lib/ruby/site_ruby/1.8/puppet/daemon.rb:21:in
from /usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:146:in
from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:416:in
from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:407:in
from /usr/sbin/puppetmasterd:4
三、解决方法:
因为使用puppetmasterd –genconfig命令生成的puppet.conf当中,rundir为/var/lib/puppet/run,将其改为
rundir =/var/lib/puppet/run
即可。
(PS: pidfile改为$rundir/master.pid)
一、 环境:
1. 系统: CentOS 6.5
2. puppet版本:puppet-server-2.7.26-2.el6.noarch puppet-2.7.26-2.el6.noarch
二、问题现象:
使用/etc/init.d/puppetmasterd start启动时,在命令行会出现如下的错误:
Starting puppetmaster: /usr/lib/ruby/site_ruby/1.8/puppet/util/pidlock.rb:39:in
initialize': Permission denied - /var/lib/puppet/run/master.pid (Errno::EACCES) from /usr/lib/ruby/site_ruby/1.8/puppet/util/pidlock.rb:39:inopen’
from /usr/lib/ruby/site_ruby/1.8/puppet/util/pidlock.rb:39:in
lock' from /usr/lib/ruby/site_ruby/1.8/puppet/daemon.rb:46:increate_pidfile’
from /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:44:in
synchronize_on' from /usr/lib/ruby/1.8/sync.rb:230:insynchronize’
from /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:44:in
synchronize_on' from /usr/lib/ruby/site_ruby/1.8/puppet/daemon.rb:45:increate_pidfile’
from /usr/lib/ruby/site_ruby/1.8/puppet/daemon.rb:21:in
daemonize' from /usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:193:inmain’
from /usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:146:in
run_command' from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:309:inrun’
from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:416:in
hook' from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:309:inrun’
from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:407:in
exit_on_fail' from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:309:inrun’
from /usr/sbin/puppetmasterd:4
三、解决方法:
因为使用puppetmasterd –genconfig命令生成的puppet.conf当中,rundir为/var/lib/puppet/run,将其改为
rundir =/var/lib/puppet/run
即可。
(PS: pidfile改为$rundir/master.pid)
相关文章推荐
- maven异常
- Ubuntu 14.04 Trusty安装java环境
- Linus的redHat在root出现错误:-bash: addgroup: command not found
- Spring管理 hibernate 事务配置的五种方式
- 关于VSAN 6.x版本里一个针对SSD性能不足时的写入保护导致强行Unmount VSAN磁盘问题
- 获取本机的全部环境属性
- php.ini参数调优
- 百度逆地址解析
- Processing Bitmaps Off the UI Thread
- C++中重载、重写(覆盖)和隐藏的区别实例分析
- JS函数的定义与调用方法
- 个推+DCLOUD,推送消息和透传消息
- Start My JS Road:3
- CodeForces - 342A
- mac os You don't have permission to access / on this server.
- “互联网+”运营新媒体,那些不得不知道的策略!
- 双向广搜模版(360百科)
- Mybatis 万能的map来接收值
- Java Override和@Override
- swiper教程——swiper的基础使用(十九)