简体   繁体   English

刀SSH命令启动Chef Client运行超时

[英]Knife SSH command to initiate Chef Client run times out

Per the Stackoverflow community's recommendation; 根据Stackoverflow社区的建议; I have recently moved my Chef Workstation from a VM to a machine running Ubuntu 16.04 desktop. 我最近将Chef工作站从VM移到了运行Ubuntu 16.04桌面的计算机上。 I have regenerated my .pem file as I'm using the same Hosted Chef user on the new machine. 我在新计算机上使用相同的Hosted Chef用户时,已经重新生成了.pem文件。

Knife node list returns the two managed nodes I have setup, and knife search node name:some-name yields a search result for each of the nodes. 刀节点列表返回我已设置的两个受管节点,刀搜索节点名称:some-name产生每个节点的搜索结果。 When I attempt to initiate a Chef Client run on the nodes, I receive an SSH timeout. 当我尝试启动在节点上运行的Chef Client时,我收到SSH超时。

The command I am using to initiate the chef client runs is as follows: 我用来启动Chef客户端运行的命令如下:

knife ssh 'name:managed-node1' 'sudo chef-client' --ssh-user c7-device --identity-file ~/chef/.chef/chucknorris.pem --attribute ipaddress

A bit of information that may be of particular importantance: each one of these managed nodes is a VM with a resolvable hostname. 一点信息可能特别重要:这些受管节点中的每个节点都是具有可解析主机名的VM。 Why after moving my workstation to a new machine, would I now receive an SSH timeout when attempting to initiate a Chef Client run on my managed nodes? 为什么在将工作站移动到新计算机后,尝试启动在受管节点上运行的Chef Client时,我现在会收到SSH超时?

Thanks in advance for any guidance, 预先感谢您的指导,

As noted above in comments, there is no network connectivity between the hosts in general. 如上面的注释中所述,主机之间通常没有网络连接。 This probably means you need to fix your network layout but is outside the scope of knife . 这可能意味着你需要修复您的网络布局,但范围之外的knife

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM