# RE: Strange error - knife ssh "name:node\_name" "pwd" -x root -P password returns FATAL: No nodes returned from search!

**URL:** <https://discourse.chef.io/t/re-strange-error-knife-ssh-name-node-name-pwd-x-root-p-password-returns-fatal-no-nodes-returned-from-search/6008>\
**Category:** Chef Infra (archive)\
**Created:** [November 5, 2014, 6:52pm UTC](https://discourse.chef.io/t/re-strange-error-knife-ssh-name-node-name-pwd-x-root-p-password-returns-fatal-no-nodes-returned-from-search/6008 "2014-11-05T18:52:17Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chris\_F](https://avatars.discourse-cdn.com/v4/letter/c/fbc32d/32.png) [@Chris\_F](https://discourse.chef.io/u/Chris_F)\
**Post date:** [November 5, 2014, 6:52pm UTC](https://discourse.chef.io/t/re-strange-error-knife-ssh-name-node-name-pwd-x-root-p-password-returns-fatal-no-nodes-returned-from-search/6008/1 "2014-11-05T18:52:17Z")

</div>

knife ssh “name:node\_name” “pwd” -x root -P password -a ipaddress

Shows the same error.

Chris

From: Fouts, Chris  
Sent: Wednesday, November 05, 2014 1:41 PM  
To: [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
Subject: Strange error - knife ssh “name:node\_name” “pwd” -x root -P password returns FATAL: No nodes returned from search!

I successfully bootstrapped my node, which run an empty run list

knife bootstrap node\_name -N node\_name -E my\_env -x root -P password  
Connecting to node\_name  
Node\_name Starting first Chef Client run…  
Node\_name [2014-11-05T13:22:04-05:00] WARN:  
Node\_name \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \*  
Node\_name SSL validation of HTTPS requests is disabled. HTTPS connections are still  
Node\_name encrypted, but chef is not able to detect forged replies or man in the middle  
Node\_name attacks.  
Node\_name To fix this issue add an entry like this to your configuration file:  
Node\_name `Node_name # Verify all HTTPS connections (recommended) Node_name ssl_verify_mode :verify_peer Node_name # OR, Verify only connections to chef-server Node_name verify_api_cert true Node_name`  
Node\_name To check your SSL configuration, or troubleshoot errors, you can use the  
Node\_name `knife ssl check` command like so:  
Node\_name `Node_name knife ssl check -c /etc/chef/client.rb Node_name`  
Node\_name  
Node\_name \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \*  
Node\_name Starting Chef Client, version 11.12.2  
Node\_name Creating a new client identity for node\_name using the validator key.  
Node\_name resolving cookbooks for run list: []  
Node\_name Synchronizing Cookbooks:  
Node\_name Compiling Cookbooks…  
Node\_name [2014-11-05T13:22:07-05:00] WARN: Node node\_name has an empty run list.  
Node\_name Converging 0 resources  
Node\_name Running handlers:  
Node\_name Running handlers complete  
Node\_name Chef Client finished, 0/0 resources updated in 2.479062 seconds

knife node show node\_name  
Node Name: node\_name  
Environment: my\_env  
FQDN: node\_name  
IP:   
Run List:  
Roles:  
Recipes:  
Platform: redhat 5.11  
Tags:

knife ssh “name:node\_name” “pwd” -x root -P password  
FATAL: No nodes returned from search!

I CAN go to the node, node\_name, and run chef-client from it.

I’ve done the process repeatedly to no avail.

Why?  
How can I fix it?

Chris

---

<div class="post-metadata">

**Author:** ![Morgan\_Blackthorne](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/morgan_blackthorne/32/100_2.png) [@Morgan\_Blackthorne](https://discourse.chef.io/u/Morgan_Blackthorne)\
**Post date:** [November 5, 2014, 7:07pm UTC](https://discourse.chef.io/t/re-strange-error-knife-ssh-name-node-name-pwd-x-root-p-password-returns-fatal-no-nodes-returned-from-search/6008/2 "2014-11-05T19:07:22Z")

</div>

Odd. That looks to be a search failure. What about:

knife search node "name:node\_name"

--  
~_~ StormeRider ~_~

"Every world needs its heroes [...] They inspire us to be better than we  
are. And they protect from the darkness that's just around the corner."

(from Smallville Season 6x1: "Zod")

On why I hate the phrase "that's so lame"... [http://bit.ly/Ps3uSS](http://bit.ly/Ps3uSS)

On Wed, Nov 5, 2014 at 10:52 AM, Fouts, Chris [Chris.Fouts@sensus.com](mailto:Chris.Fouts@sensus.com)  
wrote:

> knife ssh "name:node\_name" "pwd" -x root -P password –a ipaddress
> 
> Shows the same error.
> 
> Chris
> 
> _From:_ Fouts, Chris  
> _Sent:_ Wednesday, November 05, 2014 1:41 PM  
> _To:_ [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
> _Subject:_ Strange error - knife ssh "name:node\_name" "pwd" -x root -P  
> password returns FATAL: No nodes returned from search!
> 
> I successfully bootstrapped my node, which run an empty run list
> 
> knife bootstrap node\_name -N node\_name -E my\_env -x root -P password
> 
> Connecting to _node\_name_
> 
> Node\_name Starting first Chef Client run...
> 
> Node\_name [2014-11-05T13:22:04-05:00] WARN:
> 
> Node\_name \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \*
> 
> * * *
> 
> Node\_name SSL validation of HTTPS requests is disabled. HTTPS connections  
> are still
> 
> Node\_name encrypted, but chef is not able to detect forged replies or man  
> in the middle
> 
> Node\_name attacks.
> 
> Node\_name To fix this issue add an entry like this to your configuration  
> file:
> 
> Node\_name ```
> 
> Node\_name # Verify all HTTPS connections (recommended)
> 
> Node\_name ssl\_verify\_mode :verify\_peer
> 
> Node\_name # OR, Verify only connections to chef-server
> 
> Node\_name verify\_api\_cert true
> 
> Node\_name ```
> 
> Node\_name To check your SSL configuration, or troubleshoot errors, you  
> can use the
> 
> Node\_name `knife ssl check` command like so:
> 
> Node\_name ```
> 
> Node\_name knife ssl check -c /etc/chef/client.rb
> 
> Node\_name ```
> 
> Node\_name
> 
> Node\_name \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \*
> 
> * * *
> 
> Node\_name Starting Chef Client, version 11.12.2
> 
> Node\_name Creating a new client identity for node\_name using the  
> validator key.
> 
> Node\_name resolving cookbooks for run list:
> 
> Node\_name Synchronizing Cookbooks:
> 
> Node\_name Compiling Cookbooks...
> 
> Node\_name [2014-11-05T13:22:07-05:00] WARN: Node node\_name has an empty  
> run list.
> 
> Node\_name Converging 0 resources
> 
> Node\_name Running handlers:
> 
> Node\_name Running handlers complete
> 
> Node\_name Chef Client finished, 0/0 resources updated in 2.479062 seconds
> 
> knife node show node\_name
> 
> _Node Name:__node\_name_
> 
> Environment: my\_env
> 
> FQDN: node\_name
> 
> IP:
> 
> Run List:
> 
> Roles:
> 
> Recipes:
> 
> Platform: redhat 5.11
> 
> Tags:
> 
> knife ssh "name:node\_name" "pwd" -x root -P password
> 
> FATAL: No nodes returned from search!
> 
> I CAN go to the node, node\_name, and run chef-client from it.
> 
> I’ve done the process repeatedly to no avail.
> 
> Why?
> 
> How can I fix it?
> 
> Chris

---

<div class="post-metadata">

**Author:** ![Chris\_F](https://avatars.discourse-cdn.com/v4/letter/c/fbc32d/32.png) [@Chris\_F](https://discourse.chef.io/u/Chris_F)\
**Post date:** [November 5, 2014, 7:10pm UTC](https://discourse.chef.io/t/re-strange-error-knife-ssh-name-node-name-pwd-x-root-p-password-returns-fatal-no-nodes-returned-from-search/6008/3 "2014-11-05T19:10:41Z")

</div>

knife search node "name:node\_name"  
0 items found

From: Morgan Blackthorne [[mailto:stormerider@gmail.com](mailto:stormerider@gmail.com)]  
Sent: Wednesday, November 05, 2014 2:07 PM  
To: [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
Subject: [chef] Re: RE: Strange error - knife ssh “name:node\_name” “pwd” -x root -P password returns FATAL: No nodes returned from search!

Odd. That looks to be a search failure. What about:

knife search node “name:node\_name”

–  
~_~ StormeRider ~_~  
“Every world needs its heroes […] They inspire us to be better than we are. And they protect from the darkness that’s just around the corner.”

(from Smallville Season 6x1: “Zod”)

On why I hate the phrase “that’s so lame”… [http://bit.ly/Ps3uSS](http://bit.ly/Ps3uSS)

On Wed, Nov 5, 2014 at 10:52 AM, Fouts, Chris \<[Chris.Fouts@sensus.com](mailto:Chris.Fouts@sensus.com)[mailto:Chris.Fouts@sensus.com](mailto:Chris.Fouts@sensus.com)\> wrote:  
knife ssh “name:node\_name” “pwd” -x root -P password –a ipaddress

Shows the same error.

Chris

From: Fouts, Chris  
Sent: Wednesday, November 05, 2014 1:41 PM  
To: [chef@lists.opscode.com](mailto:chef@lists.opscode.com)[mailto:chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
Subject: Strange error - knife ssh “name:node\_name” “pwd” -x root -P password returns FATAL: No nodes returned from search!

I successfully bootstrapped my node, which run an empty run list

knife bootstrap node\_name -N node\_name -E my\_env -x root -P password  
Connecting to node\_name  
Node\_name Starting first Chef Client run…  
Node\_name [2014-11-05T13:22:04-05:00] WARN:  
Node\_name \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \*  
Node\_name SSL validation of HTTPS requests is disabled. HTTPS connections are still  
Node\_name encrypted, but chef is not able to detect forged replies or man in the middle  
Node\_name attacks.  
Node\_name To fix this issue add an entry like this to your configuration file:  
Node\_name `Node_name # Verify all HTTPS connections (recommended) Node_name ssl_verify_mode :verify_peer Node_name # OR, Verify only connections to chef-server Node_name verify_api_cert true Node_name`  
Node\_name To check your SSL configuration, or troubleshoot errors, you can use the  
Node\_name `knife ssl check` command like so:  
Node\_name `Node_name knife ssl check -c /etc/chef/client.rb Node_name`  
Node\_name  
Node\_name \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \*  
Node\_name Starting Chef Client, version 11.12.2  
Node\_name Creating a new client identity for node\_name using the validator key.  
Node\_name resolving cookbooks for run list: []  
Node\_name Synchronizing Cookbooks:  
Node\_name Compiling Cookbooks…  
Node\_name [2014-11-05T13:22:07-05:00] WARN: Node node\_name has an empty run list.  
Node\_name Converging 0 resources  
Node\_name Running handlers:  
Node\_name Running handlers complete  
Node\_name Chef Client finished, 0/0 resources updated in 2.479062 seconds

knife node show node\_name  
Node Name: node\_name  
Environment: my\_env  
FQDN: node\_name  
IP:   
Run List:  
Roles:  
Recipes:  
Platform: redhat 5.11  
Tags:

knife ssh “name:node\_name” “pwd” -x root -P password  
FATAL: No nodes returned from search!

I CAN go to the node, node\_name, and run chef-client from it.

I’ve done the process repeatedly to no avail.

Why?  
How can I fix it?

Chris

---

<div class="post-metadata">

**Author:** ![Morgan\_Blackthorne](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/morgan_blackthorne/32/100_2.png) [@Morgan\_Blackthorne](https://discourse.chef.io/u/Morgan_Blackthorne)\
**Post date:** [November 5, 2014, 7:14pm UTC](https://discourse.chef.io/t/re-strange-error-knife-ssh-name-node-name-pwd-x-root-p-password-returns-fatal-no-nodes-returned-from-search/6008/4 "2014-11-05T19:14:13Z")

</div>

I'd play around with search to see if other options (like  
"name:node\_name\*") return results. If not, it sounds like the search  
service might be broken on your server. On 10 that was Solr, but I have no  
idea how things are compartmentalized under 11/12... I would expect that  
the service is running, otherwise you'd get the error about the 5 retry  
attempts, but I'm not sure beyond that. #Chef Infra (archive) in IRC might be able to help  
as well.

--  
~_~ StormeRider ~_~

"Every world needs its heroes [...] They inspire us to be better than we  
are. And they protect from the darkness that's just around the corner."

(from Smallville Season 6x1: "Zod")

On why I hate the phrase "that's so lame"... [http://bit.ly/Ps3uSS](http://bit.ly/Ps3uSS)

On Wed, Nov 5, 2014 at 11:10 AM, Fouts, Chris [Chris.Fouts@sensus.com](mailto:Chris.Fouts@sensus.com)  
wrote:

> knife search node "name:node\_name"
> 
> 0 items found
> 
> _From:_ Morgan Blackthorne [[mailto:stormerider@gmail.com](mailto:stormerider@gmail.com)]  
> _Sent:_ Wednesday, November 05, 2014 2:07 PM  
> _To:_ [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
> _Subject:_ [chef] Re: RE: Strange error - knife ssh "name:node\_name"  
> "pwd" -x root -P password returns FATAL: No nodes returned from search!
> 
> Odd. That looks to be a search failure. What about:
> 
> knife search node "name:node\_name"
> 
> --
> 
> ~_~ StormeRider ~_~
> 
> "Every world needs its heroes [...] They inspire us to be better than we  
> are. And they protect from the darkness that's just around the corner."
> 
> (from Smallville Season 6x1: "Zod")
> 
> On why I hate the phrase "that's so lame"... [http://bit.ly/Ps3uSS](http://bit.ly/Ps3uSS)
> 
> On Wed, Nov 5, 2014 at 10:52 AM, Fouts, Chris [Chris.Fouts@sensus.com](mailto:Chris.Fouts@sensus.com)  
> wrote:
> 
> knife ssh "name:node\_name" "pwd" -x root -P password –a ipaddress
> 
> Shows the same error.
> 
> Chris
> 
> _From:_ Fouts, Chris  
> _Sent:_ Wednesday, November 05, 2014 1:41 PM  
> _To:_ [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
> _Subject:_ Strange error - knife ssh "name:node\_name" "pwd" -x root -P  
> password returns FATAL: No nodes returned from search!
> 
> I successfully bootstrapped my node, which run an empty run list
> 
> knife bootstrap node\_name -N node\_name -E my\_env -x root -P password
> 
> Connecting to _node\_name_
> 
> Node\_name Starting first Chef Client run...
> 
> Node\_name [2014-11-05T13:22:04-05:00] WARN:
> 
> Node\_name \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \*
> 
> * * *
> 
> Node\_name SSL validation of HTTPS requests is disabled. HTTPS connections  
> are still
> 
> Node\_name encrypted, but chef is not able to detect forged replies or man  
> in the middle
> 
> Node\_name attacks.
> 
> Node\_name To fix this issue add an entry like this to your configuration  
> file:
> 
> Node\_name ```
> 
> Node\_name # Verify all HTTPS connections (recommended)
> 
> Node\_name ssl\_verify\_mode :verify\_peer
> 
> Node\_name # OR, Verify only connections to chef-server
> 
> Node\_name verify\_api\_cert true
> 
> Node\_name ```
> 
> Node\_name To check your SSL configuration, or troubleshoot errors, you  
> can use the
> 
> Node\_name `knife ssl check` command like so:
> 
> Node\_name ```
> 
> Node\_name knife ssl check -c /etc/chef/client.rb
> 
> Node\_name ```
> 
> Node\_name
> 
> Node\_name \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \*
> 
> * * *
> 
> Node\_name Starting Chef Client, version 11.12.2
> 
> Node\_name Creating a new client identity for node\_name using the  
> validator key.
> 
> Node\_name resolving cookbooks for run list:
> 
> Node\_name Synchronizing Cookbooks:
> 
> Node\_name Compiling Cookbooks...
> 
> Node\_name [2014-11-05T13:22:07-05:00] WARN: Node node\_name has an empty  
> run list.
> 
> Node\_name Converging 0 resources
> 
> Node\_name Running handlers:
> 
> Node\_name Running handlers complete
> 
> Node\_name Chef Client finished, 0/0 resources updated in 2.479062 seconds
> 
> knife node show node\_name
> 
> _Node Name:__node\_name_
> 
> Environment: my\_env
> 
> FQDN: node\_name
> 
> IP:
> 
> Run List:
> 
> Roles:
> 
> Recipes:
> 
> Platform: redhat 5.11
> 
> Tags:
> 
> knife ssh "name:node\_name" "pwd" -x root -P password
> 
> FATAL: No nodes returned from search!
> 
> I CAN go to the node, node\_name, and run chef-client from it.
> 
> I’ve done the process repeatedly to no avail.
> 
> Why?
> 
> How can I fix it?
> 
> Chris

---

<div class="post-metadata">

**Author:** ![Peter\_Burkholder1](https://avatars.discourse-cdn.com/v4/letter/p/7ea924/32.png) [@Peter\_Burkholder1](https://discourse.chef.io/u/Peter_Burkholder1)\
**Post date:** [November 5, 2014, 7:45pm UTC](https://discourse.chef.io/t/re-strange-error-knife-ssh-name-node-name-pwd-x-root-p-password-returns-fatal-no-nodes-returned-from-search/6008/5 "2014-11-05T19:45:21Z")

</div>

Hi Chris:

What chef-server are you using? Hosted? Or one of your own?

Try 'knife raw /search/node' to get everything from the API, see if your  
node is there.

P

On Wed, Nov 5, 2014 at 2:14 PM, Morgan Blackthorne [stormerider@gmail.com](mailto:stormerider@gmail.com)  
wrote:

> I'd play around with search to see if other options (like  
> "name:node\_name\*") return results. If not, it sounds like the search  
> service might be broken on your server. On 10 that was Solr, but I have no  
> idea how things are compartmentalized under 11/12... I would expect that  
> the service is running, otherwise you'd get the error about the 5 retry  
> attempts, but I'm not sure beyond that. #Chef Infra (archive) in IRC might be able to help  
> as well.
> 
> --  
> ~_~ StormeRider ~_~
> 
> "Every world needs its heroes [...] They inspire us to be better than we  
> are. And they protect from the darkness that's just around the corner."
> 
> (from Smallville Season 6x1: "Zod")
> 
> On why I hate the phrase "that's so lame"... [http://bit.ly/Ps3uSS](http://bit.ly/Ps3uSS)
> 
> On Wed, Nov 5, 2014 at 11:10 AM, Fouts, Chris [Chris.Fouts@sensus.com](mailto:Chris.Fouts@sensus.com)  
> wrote:
> 
> > knife search node "name:node\_name"
> > 
> > 0 items found
> > 
> > _From:_ Morgan Blackthorne [[mailto:stormerider@gmail.com](mailto:stormerider@gmail.com)]  
> > _Sent:_ Wednesday, November 05, 2014 2:07 PM  
> > _To:_ [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
> > _Subject:_ [chef] Re: RE: Strange error - knife ssh "name:node\_name"  
> > "pwd" -x root -P password returns FATAL: No nodes returned from search!
> > 
> > Odd. That looks to be a search failure. What about:
> > 
> > knife search node "name:node\_name"
> > 
> > --
> > 
> > ~_~ StormeRider ~_~
> > 
> > "Every world needs its heroes [...] They inspire us to be better than we  
> > are. And they protect from the darkness that's just around the corner."
> > 
> > (from Smallville Season 6x1: "Zod")
> > 
> > On why I hate the phrase "that's so lame"... [http://bit.ly/Ps3uSS](http://bit.ly/Ps3uSS)
> > 
> > On Wed, Nov 5, 2014 at 10:52 AM, Fouts, Chris [Chris.Fouts@sensus.com](mailto:Chris.Fouts@sensus.com)  
> > wrote:
> > 
> > knife ssh "name:node\_name" "pwd" -x root -P password –a ipaddress
> > 
> > Shows the same error.
> > 
> > Chris
> > 
> > _From:_ Fouts, Chris  
> > _Sent:_ Wednesday, November 05, 2014 1:41 PM  
> > _To:_ [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
> > _Subject:_ Strange error - knife ssh "name:node\_name" "pwd" -x root -P  
> > password returns FATAL: No nodes returned from search!
> > 
> > I successfully bootstrapped my node, which run an empty run list
> > 
> > knife bootstrap node\_name -N node\_name -E my\_env -x root -P password
> > 
> > Connecting to _node\_name_
> > 
> > Node\_name Starting first Chef Client run...
> > 
> > Node\_name [2014-11-05T13:22:04-05:00] WARN:
> > 
> > Node\_name \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \*
> > 
> > * * *
> > 
> > Node\_name SSL validation of HTTPS requests is disabled. HTTPS  
> > connections are still
> > 
> > Node\_name encrypted, but chef is not able to detect forged replies or  
> > man in the middle
> > 
> > Node\_name attacks.
> > 
> > Node\_name To fix this issue add an entry like this to your configuration  
> > file:
> > 
> > Node\_name ```
> > 
> > Node\_name # Verify all HTTPS connections (recommended)
> > 
> > Node\_name ssl\_verify\_mode :verify\_peer
> > 
> > Node\_name # OR, Verify only connections to chef-server
> > 
> > Node\_name verify\_api\_cert true
> > 
> > Node\_name ```
> > 
> > Node\_name To check your SSL configuration, or troubleshoot errors, you  
> > can use the
> > 
> > Node\_name `knife ssl check` command like so:
> > 
> > Node\_name ```
> > 
> > Node\_name knife ssl check -c /etc/chef/client.rb
> > 
> > Node\_name ```
> > 
> > Node\_name
> > 
> > Node\_name \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \* \*
> > 
> > * * *
> > 
> > Node\_name Starting Chef Client, version 11.12.2
> > 
> > Node\_name Creating a new client identity for node\_name using the  
> > validator key.
> > 
> > Node\_name resolving cookbooks for run list:
> > 
> > Node\_name Synchronizing Cookbooks:
> > 
> > Node\_name Compiling Cookbooks...
> > 
> > Node\_name [2014-11-05T13:22:07-05:00] WARN: Node node\_name has an empty  
> > run list.
> > 
> > Node\_name Converging 0 resources
> > 
> > Node\_name Running handlers:
> > 
> > Node\_name Running handlers complete
> > 
> > Node\_name Chef Client finished, 0/0 resources updated in 2.479062 seconds
> > 
> > knife node show node\_name
> > 
> > _Node Name:__node\_name_
> > 
> > Environment: my\_env
> > 
> > FQDN: node\_name
> > 
> > IP:
> > 
> > Run List:
> > 
> > Roles:
> > 
> > Recipes:
> > 
> > Platform: redhat 5.11
> > 
> > Tags:
> > 
> > knife ssh "name:node\_name" "pwd" -x root -P password
> > 
> > FATAL: No nodes returned from search!
> > 
> > I CAN go to the node, node\_name, and run chef-client from it.
> > 
> > I’ve done the process repeatedly to no avail.
> > 
> > Why?
> > 
> > How can I fix it?
> > 
> > Chris