{"id":236,"date":"2017-01-17T23:07:35","date_gmt":"2017-01-17T14:07:35","guid":{"rendered":"http:\/\/daimlars.jp\/blog\/?p=236"},"modified":"2017-01-17T23:07:35","modified_gmt":"2017-01-17T14:07:35","slug":"%e8%ab%a6%e3%82%81%e3%81%a6el-capitan%e3%81%abgraphite","status":"publish","type":"post","link":"http:\/\/daimlars.jp\/blog\/?p=236","title":{"rendered":"\u8ae6\u3081\u3066El capitan\u306bGraphite"},"content":{"rendered":"<p>\u8ae6\u3081\u3066\u3001\u304a\u3046\u3061\u306eEl capitan\u3067\u305b\u3081\u3066\u3082\u306e\u753b\u9762\u3060\u3051\u306f\u898b\u3088\u3046\u3068\u3057\u3066\u307f\u308b\u3002\u3044\u304d\u306a\u308a\u3064\u307e\u305a\u304f\u3002<\/p>\n<pre class=\"lang:sh decode:true\">$vagrant plugin install vagrant-vbguest\nInstalling the 'vagrant-vbguest' plugin. This can take a few minutes...\nBundler, the underlying system Vagrant uses to install plugins,\nreported an error. The error is shown below. These errors are usually\ncaused by misconfigured plugin installations or transient network\nissues. The error from Bundler is:\n\nAn error occurred while installing ffi (1.9.14), and Bundler cannot continue.\nMake sure that `gem install ffi -v '1.9.14'` succeeds before bundling.<\/pre>\n<p>gem\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u3082NG\u3002<\/p>\n<pre class=\"lang:sh decode:true \">$gem install ffi -v '1.9.14'\nFetching: ffi-1.9.14.gem (100%)\nBuilding native extensions.  This could take a while...\nERROR:  Error installing ffi:\n\tERROR: Failed to build gem native extension.\n\n    \/System\/Library\/Frameworks\/Ruby.framework\/Versions\/2.0\/usr\/bin\/ruby extconf.rb\nmkmf.rb can't find header files for ruby at \/System\/Library\/Frameworks\/Ruby.framework\/Versions\/2.0\/usr\/lib\/ruby\/include\/ruby.h\n\n\nGem files will remain installed in \/Library\/Ruby\/Gems\/2.0.0\/gems\/ffi-1.9.14 for inspection.\nResults logged to \/Library\/Ruby\/Gems\/2.0.0\/gems\/ffi-1.9.14\/ext\/ffi_c\/gem_make.out<\/pre>\n<p>Xcode\u306e\u30b3\u30de\u30f3\u30c9\u30e9\u30a4\u30f3\u30c4\u30fc\u30eb\u3092\u5165\u308c\u3066\u307f\u308b\u3002\u524d\u3082\u3084\u3063\u305f\u6c17\u304c\u3059\u308b\u304c\u3002<\/p>\n<pre class=\"lang:default decode:true \">$ xcode-select --install\n$ sudo xcodebuild -license\n\uff04 gem install ffi -v '1.9.14'\nBuilding native extensions.  This could take a while...\nSuccessfully installed ffi-1.9.14\nParsing documentation for ffi-1.9.14\nInstalling ri documentation for ffi-1.9.14\n1 gem installed<\/pre>\n<p>vagrant up\u3057\u305f\u3089\u6012\u3089\u308c\u305f<\/p>\n<pre class=\"lang:sh decode:true \">$vagrant up\nBringing machine 'default' up with 'virtualbox' provider...\n==&gt; default: Box 'mayflower\/trusty64-puppet3' could not be found. Attempting to find and install...\n    default: Box Provider: virtualbox\n    default: Box Version: &gt;= 0\n==&gt; default: Loading metadata for box 'mayflower\/trusty64-puppet3'\n    default: URL: https:\/\/atlas.hashicorp.com\/mayflower\/trusty64-puppet3\n==&gt; default: Adding box 'mayflower\/trusty64-puppet3' (v0.7.2) for provider: virtualbox\n    default: Downloading: https:\/\/atlas.hashicorp.com\/mayflower\/boxes\/trusty64-puppet3\/versions\/0.7.2\/providers\/virtualbox.box\n==&gt; default: Box download is resuming from prior download progress\n==&gt; default: Successfully added box 'mayflower\/trusty64-puppet3' (v0.7.2) for 'virtualbox'!\n==&gt; default: Importing base box 'mayflower\/trusty64-puppet3'...\n==&gt; default: Matching MAC address for NAT networking...\n==&gt; default: Checking if box 'mayflower\/trusty64-puppet3' is up to date...\n==&gt; default: Setting the name of the VM: synthesize-master_default_1484155138036_88827\nVagrant cannot forward the specified ports on this VM, since they\nwould collide with some other application that is already listening\non these ports. The forwarded port to 8443 is already in use\non the host machine.\n\nTo fix this, modify your current project's Vagrantfile to use another\nport. Example, where '1234' would be replaced by a unique host port:\n\n  config.vm.network :forwarded_port, guest: 443, host: 1234\n\nSometimes, Vagrant will attempt to auto-correct this for you. In this\ncase, Vagrant was unable to. This is usually because the guest machine\nis in a state which doesn't allow modifying port forwarding. You could\ntry 'vagrant reload' (equivalent of running a halt followed by an up)\nso vagrant can attempt to auto-correct this upon booting. Be warned\nthat any unsaved work might be lost.<\/pre>\n<p>Vagrantfile\u3092\u4fee\u6b63\u3002\u3072\u3068\u307e\u305a8445\u306b\u3002<\/p>\n<pre class=\"lang:sh decode:true \">config.vm.network :forwarded_port, guest: 443, host: 8445<\/pre>\n<p>\u8d77\u52d5\u3067\u304d\u305f\uff01<\/p>\n<p class=\"p1\">\u00a0<img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-large wp-image-239\" src=\"http:\/\/54.188.22.29\/blog\/wp-content\/uploads\/2017\/01\/graphite-1024x526.png\" alt=\"\" width=\"750\" height=\"385\" srcset=\"http:\/\/daimlars.jp\/blog\/wp-content\/uploads\/2017\/01\/graphite-1024x526.png 1024w, http:\/\/daimlars.jp\/blog\/wp-content\/uploads\/2017\/01\/graphite-300x154.png 300w, http:\/\/daimlars.jp\/blog\/wp-content\/uploads\/2017\/01\/graphite-768x394.png 768w, http:\/\/daimlars.jp\/blog\/wp-content\/uploads\/2017\/01\/graphite-1536x788.png 1536w, http:\/\/daimlars.jp\/blog\/wp-content\/uploads\/2017\/01\/graphite-1568x805.png 1568w, http:\/\/daimlars.jp\/blog\/wp-content\/uploads\/2017\/01\/graphite.png 1689w\" sizes=\"auto, (max-width: 750px) 100vw, 750px\" \/><\/p>\n","protected":false},"excerpt":{"rendered":"<p>\u8ae6\u3081\u3066\u3001\u304a\u3046\u3061\u306eEl capitan\u3067\u305b\u3081\u3066\u3082\u306e\u753b\u9762\u3060\u3051\u306f\u898b\u3088\u3046\u3068\u3057\u3066\u307f\u308b\u3002\u3044\u304d\u306a\u308a\u3064\u307e\u305a\u304f\u3002 $vagrant plugin install vagrant-vbguest Installing the &#8216;vagran [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-236","post","type-post","status-publish","format-standard","hentry","category-engineering"],"_links":{"self":[{"href":"http:\/\/daimlars.jp\/blog\/index.php?rest_route=\/wp\/v2\/posts\/236","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/daimlars.jp\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/daimlars.jp\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/daimlars.jp\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/daimlars.jp\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=236"}],"version-history":[{"count":0,"href":"http:\/\/daimlars.jp\/blog\/index.php?rest_route=\/wp\/v2\/posts\/236\/revisions"}],"wp:attachment":[{"href":"http:\/\/daimlars.jp\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=236"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/daimlars.jp\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=236"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/daimlars.jp\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=236"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}