Skip to content

Instantly share code, notes, and snippets.

ec2-54-205-89-86.compute-1.amazonaws.com * apt_package[ncurses-dev] action install (up to date)
ec2-54-205-89-86.compute-1.amazonaws.com
ec2-54-205-89-86.compute-1.amazonaws.com ================================================================================
ec2-54-205-89-86.compute-1.amazonaws.com Recipe Compile Error in /var/chef/cache/cookbooks/packages/recipes/default.rb
ec2-54-205-89-86.compute-1.amazonaws.com ================================================================================
ec2-54-205-89-86.compute-1.amazonaws.com
ec2-54-205-89-86.compute-1.amazonaws.com TypeError
ec2-54-205-89-86.compute-1.amazonaws.com ---------
ec2-54-205-89-86.compute-1.amazonaws.com can't convert Chef::Node::VividMash to String (Chef::Node::VividMash#to_str gives Chef::Node::VividMash)
ec2-54-205-89-86.compute-1.amazonaws.com
ec2-54-205-89-86.compute-1.amazonaws.com Compiling Cookbooks...
ec2-54-205-89-86.compute-1.amazonaws.com [2016-05-05T17:26:15+00:00] WARN: You declared a new resource #<Class:0x000000049585b8> for resource ingredient_config, but it comes alph
abetically after Chef::Resource::IngredientConfig and has the same filters ({}), so it will not be used. Use override: true if you want to use it for ingredient_config.
ec2-54-205-89-86.compute-1.amazonaws.com
ec2-54-205-89-86.compute-1.amazonaws.com ================================================================================
ec2-54-205-89-86.compute-1.amazonaws.com Recipe Compile Error in /var/chef/cache/cookbooks/chef-ingredient/resources/ingredient_config.rb
ec2-54-205-89-86.compute-1.amazonaws.com ================================================================================
ec2-54-205-89-86.compute-1.amazonaws.com
ec2-54-205-89-86.compute-1.amazonaws.com NoMethodError
ec2-54-205-89-86.compute-1.amazonaws.com -------------
/opt/supermarket/embedded/lib/ruby/2.2.0/irb/input-method.rb:150: [BUG] Segmentation fault at 0x007fe388fa3ff8
ruby 2.2.3p173 (2015-08-18 revision 51636) [x86_64-linux]
-- Control frame information -----------------------------------------------
c:0029 p:---- s:0108 e:000107 CFUNC :readline
c:0028 p:0042 s:0103 e:000102 METHOD /opt/supermarket/embedded/lib/ruby/2.2.0/irb/input-method.rb:150
c:0027 p:0011 s:0099 e:000098 BLOCK /opt/supermarket/embedded/lib/ruby/2.2.0/irb.rb:469
c:0026 p:0040 s:0096 e:000095 METHOD /opt/supermarket/embedded/lib/ruby/2.2.0/irb.rb:623
c:0025 p:0009 s:0091 e:000090 BLOCK /opt/supermarket/embedded/lib/ruby/2.2.0/irb.rb:468 [FINISH]
c:0024 p:---- s:0089 e:000088 CFUNC :call
# In recipes/default.rb of a Supermarket Wrapper Cookbook
node.set['supermarket_omnibus']['features'] = "tools,no_crawl,announcement,github"
# 2015-10-05
## Meeting
1. This is a blameless Post Mortem.
2. We will not focus on the past events as they pertain to "could've", "should've", etc.
3. All follow up action items will be assigned to a team/individual before the end of the meeting. If the item is not going to be top priority leaving the meeting, don't make it a follow up item.
### Incident Leader: Nell Shamrell-Harrington
## Description
Greetings!
I am happy to report that we have just released Supermarket 2.0.0! The Supermarket - both the public and private versions - continues to evolve to the needs of the Chef community.
As you might guess from the major version bump, this version contains a potentally breaking change. This only occurs on private Supermarkets - those that use the supermarket-omnibus package for their installs. We have added in the ability to to disable ssl through a new environmental attribute: [‘ssl’][‘enabled’].
New Supermarket installs will have [‘ssl’][‘enabled’] set to true by default. However, if you are using an existing Supermarket install and wish to continue using ssl when you upgrade to Supermarket 2.0.0, you will need to explicitly set [‘ssl’][‘enabled’] to true.
With this change, we are now using the Supermarket omnibus install to run the public Supermarket site as well as private Supermarkets. The Supermarket omnibus install is the only officially supported way to run a private Supermarket. Irv
Let's say you have a working, running Chef Server. And let's also say you have a working, running, brand new Supermarket you just spun up. Everything appears to be working fine.
BUT - when you click the "Sign In" link in the upper right hand corner of your Supermarket view in your browser, you suddenly see an error that looks like this:
502 Bad Gateway
openresty/1.17.10.1
Oh noes!!!!
This is due to a known issue with the latest version of Chef Server (https://github.com/chef/chef-server/issues/375). A patch has been merged into the main code base for Chef Server, but it has not yet been released. Until then, here is a workaround.
@nellshamrell
nellshamrell / gist:6502904fa35cc9534ac9
Created June 12, 2015 19:02
Setting up Supermarket Manually
## Setting up a private Supermarket manually
### Provision a Supermarket server
Go ahead and spin up a new Ubuntu 14-04 server for your Supermarket install. (This will work with other Operating Systems as well, but these examples will for Ubuntu).
### SSH into your Private Supermarket Server
```bash
$ ssh root@your_private_supermarket_server_ip
@nellshamrell
nellshamrell / gist:0745564772c4d0454c9d
Created May 27, 2015 18:40
Omnibus install error
[Software: version-manifest] I | Resolving manifest entry for version-manifest
[NullFetcher: version-manifest] I | Fetching `version-manifest' (nothing to fetch)
/home/vagrant/.gem/ruby/2.1.5/gems/ruby-progressbar-1.7.5/lib/ruby-progressbar/progress.rb:58:in `progress=': You can't set the item's current value to be greater than
the total. (ProgressBar::InvalidProgressError)
from /home/vagrant/.gem/ruby/2.1.5/gems/ruby-progressbar-1.7.5/lib/ruby-progressbar/base.rb:156:in `block in update_progress'
from /home/vagrant/.gem/ruby/2.1.5/gems/ruby-progressbar-1.7.5/lib/ruby-progressbar/output.rb:38:in `with_refresh'
from /home/vagrant/.gem/ruby/2.1.5/gems/ruby-progressbar-1.7.5/lib/ruby-progressbar/base.rb:155:in `update_progress'
from /home/vagrant/.gem/ruby/2.1.5/gems/ruby-progressbar-1.7.5/lib/ruby-progressbar/base.rb:99:in `progress='
from /home/vagrant/.gem/ruby/2.1.5/bundler/gems/omnibus-9d387525a335/lib/omnibus/fetchers/net_fetcher.rb:173:in `block in downloa
" Configuration file for vim
set nocompatible " be iMproved, required
filetype off " required
"set the runtime path to include Vundle and initialize
set rtp+=~/.vim/bundle/Vundle.vim
call vundle#begin()
" alternatively, pass a path where Vundle should install plugins
" "call vundle#begin('~/some/path/here')