[chef] Re: Re: ERROR: No socketless chef-zero server

[Daniel DeLeo < >]

On Monday, May 18, 2015 at 12:17 AM, Ted B wrote:
>  
> > On 7 May 2015, at 11:13 am, Daniel DeLeo 
> > <
 
> >  
> > (mailto:
 )>
> >  wrote:
> > > I don't think there's a bug. Just user error. I finally figured it out.
> >  
> >  
> > Glad to hear.
> > > As an aside: is there a way to do bootstrap from knife in local mode?
> >  
> >  
> > Chef Provisioning can create machines from local mode but knife does not 
> > have this ability.
>  
>  
> I’m having the same issue - but I’m using chef-provisioning for bootstrap. 
> It only fails when the chef zero socketless mode is tried to be used by the 
> client on each node.
>  
> - [cheffrontendTEST1.int] update node cheffrontendTEST1.int at 
> chefzero://localhost:8889
> - [cheffrontendTEST1.int] add normal.aws_ha_chef = 
> {:aws_access_key_id=>”x", :aws_secret_access_key=>”y", 
> :backend1=>{:fqdn=>”chefbackendTEST1.int", :ip_address=>"172.21.1.85"}, 
> :backend2=>{:fqdn=>”chefbackendTEST2.int", :ip_address=>"172.21.1.86"}, 
> :frontends=>{:fe1=>{:fqdn=>”cheffrontendTEST1.int", 
> :ip_address=>"172.21.1.88"}, :fe2=>{:fqdn=>”cheffrontendTEST2.int", 
> :ip_address=>"172.21.1.111"}}}
> - [cheffrontendTEST1.int] remove 
> normal.aws_ha_chef[2015-05-18T17:04:41+10:00] INFO: Converging 
> cheffrontendTEST1.int because the resource was updated ...
> [2015-05-18T17:04:41+10:00] INFO: Port forwarded: local URL 
> chefzero://localhost:8889 is available to 172.21.1.88 as 
> chefzero://localhost:8889 for the duration of this SSH connection.
> [2015-05-18T17:04:41+10:00] INFO: Executing sudo chef-client -l info on 
> 
 
>  
> (mailto:
 )
> [cheffrontendTEST1.int] [2015-05-18T07:04:41+00:00] INFO: Forking chef 
> instance to converge...
> Starting Chef Client, version 12.3.0
> [2015-05-18T07:04:41+00:00] INFO: *** Chef 12.3.0 ***
> [2015-05-18T07:04:41+00:00] INFO: Chef-client pid: 1505
>  
> ================================================================================
> Chef encountered an error attempting to load the node data for 
> “cheffrontendTEST1.int"
> ================================================================================
>  
> Unexpected Error:
> -----------------
> ChefZero::ServerNotFound: No socketless chef-zero server on given port 8889
>  
> [2015-05-18T07:04:42+00:00] FATAL: Stacktrace dumped to 
> /var/chef/cache/chef-stacktrace.out
> Chef Client failed. 0 resources updated in 0.859637226 seconds
> [2015-05-18T07:04:42+00:00] ERROR: No socketless chef-zero server on given 
> port 8889
> [2015-05-18T07:04:42+00:00] FATAL: Chef::Exceptions::ChildConvergeError: 
> Chef run process exited unsuccessfully (exit code 1)
> [2015-05-18T17:04:42+10:00] INFO: Completed chef-client -l info on 
> 
 
>  
> (mailto:
 ):
>  exit status 1
>  
> Using chefDK 0.6.0 and client 12.3 as well.
This is an incompatibility between Chef 12.3 and Chef Provisioning 1.1.1. A 
fix has been committed for this and will be released in the next version of 
Chef Provisioning. We were hoping to release this with ChefDK 0.6, but 
unfortunately there are some interactions between Chef, knife-windows, Chef 
Vault, and Chef Provisioning that made the latest versions of all of these 
incompatible with each other. We’ll be implementing some changes to fix that 
also.


--  
Daniel DeLeo