我在Xen dom0上运行puppet master
,并通过每小时一次的crontab puppet agent --test
同步3个domU。
大约80%的时间, puppet agent --test
成功完成:
info: Retrieving plugin info: Caching catalog for test3 info: Applying configuration version '1333319732' notice: Finished catalog run in 5.08 seconds
另外20%的时间中途中断,出现以下错误:
err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class iptables for test1 at /etc/puppet/manifests/site.pp:1 on node test1 warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run
要么
info: Retrieving plugin info: Caching catalog for test2 info: Applying configuration version '1333319732' notice: Finished catalog run in 24.73 seconds err: Could not send report: Error 500 on SERVER: Internal Server Error private method `gsub' called for WEBrick::HTTPStatus::RequestTimeout:Class WEBrick/1.3.1 (Ruby/1.8.5/2006-08-25) OpenSSL/0.9.8e-rhel5 at puppet:8140
要么
info: Retrieving plugin err: Could not retrieve catalog from remote server: execution expired warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run
要么
info: Retrieving plugin info: Caching catalog for test3 info: Applying configuration version '1333319732' notice: Finished catalog run in 9.47 seconds err: Could not send report: Error 408 on SERVER: Request Timeout
在这段时间里,我还没有对Puppetconfiguration做任何修改,只是偶尔失败。
我在CentOS上运行puppet-2.7.12,并按照http://docs.puppetlabs.com/learning/agent_master_basic.html上的设置说明进行操作。
有关如何解决这个问题的任何想法?
几个星期前,我把运行puppet master
的虚拟机的内存分配增加了几百兆,从那以后没有任何失败。
(这是一种表示内存不足的奇怪方式…)
Webrick是单线的,performance糟糕。 超过20台服务器的configuration项目数量相对较less(大约200台),则必须更换其他设备。 使用木偶机架 – 它好多了。