blocks|key|2674170|text|Facter+2.0.1昨天被释放。这是你的问题。降级到1.7.x，你会没事的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2674171|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Facter 2.0.1 was released yesterday. That's your problem. Downgrade to 1.7.x and you should be fine.

blocks|key|2674186|text|今天发现了同样的错误，重新配置了我的傀儡主人：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2674187|Info:+Retrieving+pluginfacts
Error:+/File[/var/lib/puppet/facts.d]:+Could+not+evaluate:+Could+not+retrieve+information+from+environment+production+source(s)+puppet://puppet/pluginfacts
Info:+Retrieving+plugin
Error:+/File[/var/lib/puppet/lib]:+Could+not+evaluate:+Could+not+retrieve+information+from+environment+production+source(s)+puppet://puppet/plugins
Info:+Caching+catalog+for+puppet
Info:+Applying+configuration+version+'1405577010'|code-block|syntax|javascript|2674188|以下是我的版本：|2674189|grundic@puppet:~$+puppet+--version
3.6.2
grundic@puppet:~$+facter+--version
2.1.0|2674190|重新启动守护进程帮助我(我使用乘客背后的木偶大师)：|2674191|grundic@puppet:~$+sudo+service+apache2+restart+
+*+Restarting+web+server+apache2
+...+waiting++++...done.
grundic@puppet:~$+sudo+puppet+agent+--test+--verbose
Info:+Retrieving+pluginfacts
Info:+Retrieving+plugin
Info:+Caching+catalog+for+puppet
Info:+Applying+configuration+version+'1405607835'
Notice:+Dummy+message+for+debugging
Notice:+/Stage[main]/Main/Notify[Dummy+message+for+debugging]/message:+defined+'message'+as+'Dummy+message+for+debugging'
Notice:+Finished+catalog+run+in+0.06+seconds|2674192|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

Caught the same error today, reconfiguring my puppet master: 

<pre><code>Info: Retrieving pluginfacts
Error: /File[/var/lib/puppet/facts.d]: Could not evaluate: Could not retrieve information from environment production source(s) puppet://puppet/pluginfacts
Info: Retrieving plugin
Error: /File[/var/lib/puppet/lib]: Could not evaluate: Could not retrieve information from environment production source(s) puppet://puppet/plugins
Info: Caching catalog for puppet
Info: Applying configuration version '1405577010'
</code></pre>

Here are my versions:

<pre><code>grundic@puppet:~$ puppet --version
3.6.2
grundic@puppet:~$ facter --version
2.1.0
</code></pre>

Restarting daemon helped me (I use puppet master behind passenger):

<pre><code>grundic@puppet:~$ sudo service apache2 restart 
 * Restarting web server apache2
 ... waiting ...done.
grundic@puppet:~$ sudo puppet agent --test --verbose
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Caching catalog for puppet
Info: Applying configuration version '1405607835'
Notice: Dummy message for debugging
Notice: /Stage[main]/Main/Notify[Dummy message for debugging]/message: defined 'message' as 'Dummy message for debugging'
Notice: Finished catalog run in 0.06 seconds
</code></pre>

blocks|key|3216550|text|我有同样的埃尔斯运行傀儡3.6.2在centos+6.5。将木偶、傀儡服务器、facter和hiera降级到以前的版本(3.6.1、2.0.2、1.3.3)“解决”了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3216551|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same erorrs running puppet 3.6.2 on centos 6.5. 
Downgrading puppet,puppet-server, facter and hiera to the previous version (3.6.1, 2.0.2, 1.3.3) 'resolves' the issue..

blocks|key|388159|text|就像格伦迪奇说的，重启大师。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|388160|然后将证书清理到主程序上的傀儡代理，并移除代理上的证书。然后重新运行傀儡代理-t和傀儡证书-全部。一切都会消失的。对我起作用了。|388161|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

As Grundic said, restart master.

Then clean up certs to the puppet agent on the master and remove the certs on the agent. Then re-run puppet agent -t and puppet cert sign --all. It will all go away. That worked for me.

blocks|key|2674368|text|您在这里遇到的问题来自于facter更新，以及您在使用facter+2.X.when的3.X版本上使用私有事实的方式--您希望分发外部事实(这就是我的情况)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2674369|正如facter+2.2文档中所述，您需要将facter文件夹重新定位到模块树中：|2674370|分发外部事实的最佳方法是使用pluginsync，它在Puppet3.4/Facter+2.0.1中增加了对它们的支持。要向傀儡模块添加外部事实，只需将它们放在MODULEPATH/MODULE/facts.d/中即可。
|blockquote|2674371|2674372|因此，在旧版本中，外部事实的路径是：|2674373|MODULEPATH/MODULEPATH/
|2674374|2674375|如果将其更改为：|2674376|2674377|2674378|那么你就不会再遇到这个问题了。|2674379|问候|2674380|-锈蚀|2674381|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|11|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|A|$]]|$1|J|3|K|5|F|7|13|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|14|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|15|8|@]|9|@]|A|$]]|$1|O|3|K|5|F|7|16|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|18|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|19|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1A|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|X|$]]

The problem your encounter here comes from facter update, and the way you use private facts with puppet on version 3.X with facter 2.X.when you want to distribute external facts (that was my case).

As said in facter 2.2 documentation, you need to relocate your facter folder into module tree : 

<blockquote>
 The best way to distribute external facts is with pluginsync, which
 added support for them in Puppet 3.4/Facter 2.0.1. To add external
 facts to your puppet modules, just place them in
 MODULEPATH/MODULE/facts.d/.
</blockquote>

So, in older versions, the path for external facts was : 

<blockquote>
 MODULEPATH/MODULE/lib/facter/external_fact.rb
</blockquote>

If you change it to :

<blockquote>
 MODULEPATH/MODULE/facts.d/external_fact.rb
</blockquote>

Then you won't encounter the problem any more.

Regards

--
rustx

blocks|key|2674406|text|for+path+in+`ls+*/lib/facter+%7C+grep+:$+%7C+sed+"s,:,,"`;+
+++do+MODULE=`echo+$path+%7C+sed+"s,/lib/facter,,"`;+
+++cd+$MODULE+&&+ln++-s+lib/facter+facts.d+&&+cd+..+;
done|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|2674407|这些部分特别重要。|unstyled|2674408|`ls+*/lib/facter+%7C+grep+:$+%7C+sed+"s,:,,"`

`echo+$path+%7C+sed+"s,/lib/facter,,"`|2674409|这个代码片段应该从/etc/+run+/模块以及/etc/run/环境中的每个环境的模块/路径中运行。|2674410|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|N|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$B|C]]|$1|I|3|J|5|F|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|F|7|Q|8|@]|9|@]|A|$]]]|L|$]]

<pre><code>for path in `ls */lib/facter | grep :$ | sed "s,:,,"`; 
 do MODULE=`echo $path | sed "s,/lib/facter,,"`; 
 cd $MODULE &amp;&amp; ln -s lib/facter facts.d &amp;&amp; cd .. ;
done
</code></pre>

these parts are especially important

<pre><code>`ls */lib/facter | grep :$ | sed "s,:,,"`

`echo $path | sed "s,/lib/facter,,"`
</code></pre>

This code snippet ought to be run from /etc/puppet/modules as well as from the modules/ path for each environment at /etc/puppet/environments.

blocks|key|2674474|text|这是由于这个错误：https://tickets.puppetlabs.com/browse/PUP-3655|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2674475|问题是，要使pluginsync工作，必须在环境中至少有一个模块，它的facts.d目录直接位于模块的顶层。|style|CODE|2674476|我所做的工作是在我们的主要内部模块的顶层创建一个可执行的facts.d/README文件，其中包含以下内容：|2674477|#!/bin/bash
#+This+directory+is+where+external+fact+scripts+would+go,+if+we+had+any.++This
#+directory+exists+only+because+with+directory+environments+puppet+will
#+complain+if+there+isn't+a+single+module+in+an+environment+that+doesn't+have+a
#+facts.d+directory.
echo+"bug=https://tickets.puppetlabs.com/browse/PUP-3655"
exit+0|code-block|syntax|javascript|2674478|entityMap|0|LINK|mutability|MUTABLE|url|https://tickets.puppetlabs.com/browse/PUP-3655^0|9|1A|0|0|Z|7|0|S|E|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|6|7|10|8|@$A|11|B|12|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|13|8|@$A|14|B|15|F|G]]|9|@]|C|$]]|$1|J|3|K|5|L|7|16|8|@]|9|@]|C|$M|N]]|$1|O|3|-4|5|6|7|17|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

This is due to this bug: <a href="https://tickets.puppetlabs.com/browse/PUP-3655" rel="noreferrer">https://tickets.puppetlabs.com/browse/PUP-3655</a>

The issue is that for pluginsync to work, there must be at least one module in the environment that has a <code>facts.d</code> directory directly off of the top level of the module.

My work around for this was to create an executable <code>facts.d/README</code> file at the top level of one of our main internal modules that contained the following:

<pre><code>#!/bin/bash
# This directory is where external fact scripts would go, if we had any. This
# directory exists only because with directory environments puppet will
# complain if there isn't a single module in an environment that doesn't have a
# facts.d directory.
echo "bug=https://tickets.puppetlabs.com/browse/PUP-3655"
exit 0
</code></pre>

I've just upgraded my puppet environment from <code>3.4.2</code> to <code>3.4.3</code>. through puppetlabs' apt repos. I was upgrading agent(s) and master. Doing an agent run leads to following error:

<pre><code>Info: Retrieving pluginfacts
Debug: Failed to load library 'msgpack' for feature 'msgpack'
Debug: file_metadata supports formats: pson yaml b64_zlib_yaml raw
Debug: Failed to load library 'msgpack' for feature 'msgpack'
Debug: file_metadata supports formats: pson yaml b64_zlib_yaml raw

Error: /File[/var/lib/puppet/facts.d]: Could not evaluate: Could not retrieve information from environment production source(s) puppet://&lt;puppetserver&gt;/pluginfacts

Debug: Finishing transaction [...]
</code></pre>

Nevertheless I retrieve a catalog from master, so the agent run still works and seems to do the things it should do. (Or let's say, I acutally can't determine, if something is going wrong that is related to the error message.)

However, I want to get rid of the Error message.

I double-checked version of puppet with <code>puppet --version</code> on agent and master. I use passenger for puppetmaster. Facter has version <code>2.0.1</code>. So what did I miss?

Addition: When running an agent with the previous version <code>3.4.2</code> there will be no error message.

Any ideas? Many thanks for your support.

ITL

Facts.d - Pluginfacts could not be retrieved during puppet run

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我刚刚将我的傀儡环境从3.4.2升级到了3.4.3。通过木偶实验室的善后反应。我是升级代理和大师。执行代理运行会导致以下错误：Info: Retrieving pluginfactsDebug: Failed to load library 'msgpack' for feature 'msgpack'Debug: f...

问在木偶运行过程中无法检索Facts.d - Pluginfacts
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在木偶运行过程中无法检索Facts.d - PluginfactsEN