Skip to content

reduce parallelism on publish nodes from 2 to 1 #188

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 14, 2016

Conversation

SethTisue
Copy link
Member

in a desperate attempt to fix the "There is insufficient memory for
the Java Runtime Environment to continue" crashes, see
#181

@SethTisue SethTisue self-assigned this Sep 22, 2016
in a desperate attempt to fix the "There is insufficient memory for
the Java Runtime Environment to continue" crashes, see
scala#181
@SethTisue SethTisue force-pushed the one-executor-only-on-publisher branch from 47e617e to be99e9d Compare September 22, 2016 02:09
@SethTisue
Copy link
Member Author

wtf. when I run chef-client on jenkins-master:

================================================================================
Recipe Compile Error in /var/chef/cache/cookbooks/compat_resource/libraries/autoload.rb
================================================================================

RuntimeError
------------
This resource is written with Chef 12.5 custom resources, and requires at least Chef 12.0 used with the compat_resource cookbook, it will not work with Chef 11.x clients, and those users must pin their cookbooks to older versions or upgrade.

Cookbook Trace:
---------------
  /var/chef/cache/cookbooks/compat_resource/libraries/autoload.rb:2:in `<top (required)>'

Relevant File Content:
----------------------
/var/chef/cache/cookbooks/compat_resource/libraries/autoload.rb:

  1:  unless Gem::Requirement.new(">= 12.0").satisfied_by?(Gem::Version.new(Chef::VERSION))
  2>>   raise "This resource is written with Chef 12.5 custom resources, and requires at least Chef 12.0 used with the compat_resource cookbook, it will not work with Chef 11.x clients, and those users must pin their cookbooks to older versions or upgrade."
  3:  end
  4:  
  5:  # If users are on old verisons of ChefDK which activates an (old) gem via cheffish before this cookbook loads, then
  6:  # we just try to monkeypatch over the top of a monkeypatch.  Its possible that we have checks in this cookbook which
  7:  # will defeat that purpose and fail to monkeypatch on top of monkeypatches -- in which case those checks should be
  8:  # removed -- this cookbook needs to win when it gets into a fight with the old gem versions.
  9:  if Gem.loaded_specs["compat_resource"]
 10:    Chef.log_deprecation "using compat_resource as a gem is deprecated;  please update cheffish and chef-provisioning gems (or use the latest Chef/ChefDK packages) or else manually pin your compat_resource cookbook version to the same version as the gem you are using to remove this warning"
 11:  end


Running handlers:
[2016-09-22T02:07:44+00:00] ERROR: Running exception handlers
Running handlers complete
[2016-09-22T02:07:44+00:00] ERROR: Exception handlers complete
[2016-09-22T02:07:44+00:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
Chef Client failed. 0 resources updated in 2.780832854 seconds
[2016-09-22T02:07:44+00:00] ERROR: This resource is written with Chef 12.5 custom resources, and requires at least Chef 12.0 used with the compat_resource cookbook, it will not work with Chef 11.x clients, and those users must pin their cookbooks to older versions or upgrade.
[2016-09-22T02:07:44+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

@adriaanm
Copy link
Contributor

I'm going to level up all instance types instead.

@adriaanm
Copy link
Contributor

FYI, I just fixed this with knife cookbook delete compat_resource :-) No idea where that cookbook came from?

@SethTisue SethTisue reopened this Oct 14, 2016
@SethTisue SethTisue merged commit d379818 into scala:master Oct 14, 2016
@SethTisue SethTisue deleted the one-executor-only-on-publisher branch October 14, 2016 20:23
@SethTisue
Copy link
Member Author

SethTisue commented Oct 14, 2016

the leveling up of instance types is postponed

(the deploy step can wait until the next time we're doing something else)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants