erl_call closed stream


#1

Now that I’m using erl_call on 0.9.8 I’ve run into this:
http://tickets.opscode.com/browse/CHEF-1781

Being on CentOS (stuck on that version) I was wondering if there was a work
around I could do in the recipe itself?

Thanks,
Tristan


#2

On Feb 16, 2011, at 11:07 AM, Tristan Sloughter wrote:

Now that I’m using erl_call on 0.9.8 I’ve run into this: http://tickets.opscode.com/browse/CHEF-1781

Being on CentOS (stuck on that version) I was wondering if there was a work around I could do in the recipe itself?

You can try the ignore_failure meta attribute since even though you may get this error the code will likely still run on the erlang node, ie the failure happens after erl_call executes the code.

As noted in the bug ticket it will be fixed in 0.9.14, as well as some other improvements (CHEF-2040).

Hope this helps.

-Joe

Name: Joseph A. Williams
Email: joe@joetify.com
Blog: http://www.joeandmotorboat.com/
Twitter: http://twitter.com/williamsjoe


#3

Cool, thanks. I’m hoping to go the route of getting a non-CentOS server to
run the newest Chef, but that’ll be my backup.

On Wed, Feb 16, 2011 at 3:27 PM, Joe Williams joe@joetify.com wrote:

On Feb 16, 2011, at 11:07 AM, Tristan Sloughter wrote:

Now that I’m using erl_call on 0.9.8 I’ve run into this:
http://tickets.opscode.com/browse/CHEF-1781

Being on CentOS (stuck on that version) I was wondering if there was a work
around I could do in the recipe itself?

You can try the ignore_failure meta attribute since even though you may get
this error the code will likely still run on the erlang node, ie the failure
happens after erl_call executes the code.

As noted in the bug ticket it will be fixed in 0.9.14, as well as some
other improvements (CHEF-2040).

Hope this helps.

-Joe

Name: Joseph A. Williams
Email: joe@joetify.com
Blog: http://www.joeandmotorboat.com/
Twitter: http://twitter.com/williamsjoe