[chef] Re: Re: Re: Re: fatal:Mixlib::ShellOut::ShellCommandFailed:expectedprocess to exit with [0] but received 1


Chronological Thread 
  • From: Daniel DeLeo < >
  • To:
  • Subject: [chef] Re: Re: Re: Re: fatal:Mixlib::ShellOut::ShellCommandFailed:expectedprocess to exit with [0] but received 1
  • Date: Thu, 9 Jan 2014 08:34:10 -0800


On Thursday, January 9, 2014 at 3:52 AM, seema khalkar wrote:

Can you Please give me solution on below issue:-

c:/opscode/chef/bin/chef-solo:23:in `<main>'
Chef Client failed. 0 resources updated←[0m
[2014-01-09T03:15:56-08:00] FATAL: Mixlib::ShellOut::ShellCommandFailed: gem_pac
kage[tiny_tds] (sql_server::client line 45) had an error: Mixlib::ShellOut::Shel
lCommandFailed: Expected process to exit with [0], but received '2'
---- Begin output of C:\opscode\chef\embedded\bin\gem install tiny_tds -q --no-r
doc --no-ri -v "" ----
STDOUT:
STDERR: ERROR:  Could not find a valid gem 'tiny_tds' (>= 0), here is why:
          Unable to download data from https://rubygems.org/ - Errno::ECONNREFUS
ED: No connection could be made because the target machine actively refused it.
- connect(2) (https://api.rubygems.org/latest_specs.4.8.gz)
---- End output of C:\opscode\chef\embedded\bin\gem install tiny_tds -q --no-rdo
c --no-ri -v "" ----
Ran C:\opscode\chef\embedded\bin\gem install tiny_tds -q --no-rdoc --no-ri -v ""
 returned 2



ECONNREFUSED means that some device sent a TCP reset packet when you tried to initiate the connection. This can happen infrequently with rubygems.org if they or their CDN are down for a while, or you could have a firewall that’s preventing you from connecting.

-- 
Daniel DeLeo




Archive powered by MHonArc 2.6.16.

§