# chef verify is failing

**URL:** <https://discourse.chef.io/t/chef-verify-is-failing/12454>\
**Category:** Chef Infra (archive)\
**Created:** [January 18, 2018, 7:51pm UTC](https://discourse.chef.io/t/chef-verify-is-failing/12454 "2018-01-18T19:51:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Neerajjh](https://avatars.discourse-cdn.com/v4/letter/n/dc4da7/32.png) [@Neerajjh](https://discourse.chef.io/u/Neerajjh)\
**Post date:** [January 18, 2018, 7:51pm UTC](https://discourse.chef.io/t/chef-verify-is-failing/12454/1 "2018-01-18T19:51:04Z")

</div>

[root@oralinws3 ~]# chef verify  
[WARN] This is an internal command used by the ChefDK development team. If you are a ChefDK user, please do not run it.  
Running verification for component 'berkshelf’  
Running verification for component 'test-kitchen’  
Running verification for component 'tk-policyfile-provisioner’  
Running verification for component 'chef-client’  
Running verification for component 'chef-dk’  
Running verification for component 'chef-provisioning’  
Running verification for component 'chefspec’  
Running verification for component 'generated-cookbooks-pass-chefspec’  
Running verification for component 'fauxhai’  
Running verification for component 'knife-spork’  
Running verification for component 'kitchen-vagrant’  
Running verification for component 'package installation’  
Running verification for component 'openssl’  
Running verification for component 'inspec’  
Running verification for component 'delivery-cli’  
Running verification for component 'git’  
Running verification for component 'opscode-pushy-client’  
Running verification for component ‘chef-sugar’  
…/opt/chefdk/embedded/lib/ruby/gems/2.4.0/gems/mixlib-shellout-2.3.2/lib/mixlib/shellout.rb:293:in `invalid!': Expected process to exit with [0], but received '101' (Mixlib::ShellOut::ShellCommandFailed) ---- Begin output of delivery setup --user=shipit --server=delivery.shipit.io --ent=chef --org=squirrels ---- STDOUT: STDERR: thread 'main' panicked at 'called`Result::unwrap()`on an`Err`value: ColorOutOfRange', /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libcore/result.rs:837 note: Run with`RUST\_BACKTRACE=1`for a backtrace. thread 'main' panicked at 'called`Result::unwrap()`on an`Err`value: ColorOutOfRange', /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libcore/result.rs:837 ---- End output of delivery setup --user=shipit --server=delivery.shipit.io --ent=chef --org=squirrels ---- Ran delivery setup --user=shipit --server=delivery.shipit.io --ent=chef --org=squirrels returned 101 from /opt/chefdk/embedded/lib/ruby/gems/2.4.0/gems/mixlib-shellout-2.3.2/lib/mixlib/shellout.rb:280:in`error!‘  
from /opt/chefdk/embedded/lib/ruby/gems/2.4.0/gems/chef-dk-2.4.17/lib/chef-dk/component\_test.rb:128:in `block in sh!' from /opt/chefdk/embedded/lib/ruby/gems/2.4.0/gems/chef-dk-2.4.17/lib/chef-dk/component_test.rb:128:in`tap’  
from /opt/chefdk/embedded/lib/ruby/gems/2.4.0/gems/chef-dk-2.4.17/lib/chef-dk/component\_test.rb:128:in `sh!' from /opt/chefdk/embedded/lib/ruby/gems/2.4.0/gems/chef-dk-2.4.17/lib/chef-dk/command/verify.rb:445:in`block (3 levels) in class:Verify’  
from /opt/chefdk/embedded/lib/ruby/gems/2.4.0/gems/chef-dk-2.4.17/lib/chef-dk/component\_test.rb:165:in `block in tmpdir' from /opt/chefdk/embedded/lib/ruby/2.4.0/tmpdir.rb:89:in`mktmpdir’  
from /opt/chefdk/embedded/lib/ruby/gems/2.4.0/gems/chef-dk-2.4.17/lib/chef-dk/component\_test.rb:164:in `tmpdir' from /opt/chefdk/embedded/lib/ruby/gems/2.4.0/gems/chef-dk-2.4.17/lib/chef-dk/command/verify.rb:444:in`block (2 levels) in class:Verify’  
from /opt/chefdk/embedded/lib/ruby/gems/2.4.0/gems/chef-dk-2.4.17/lib/chef-dk/component\_test.rb:99:in `instance_eval' from /opt/chefdk/embedded/lib/ruby/gems/2.4.0/gems/chef-dk-2.4.17/lib/chef-dk/component_test.rb:99:in`run\_smoke\_test’  
from /opt/chefdk/embedded/lib/ruby/gems/2.4.0/gems/chef-dk-2.4.17/lib/chef-dk/command/verify.rb:570:in `block (2 levels) in invoke\_tests’

---

<div class="post-metadata">

**Author:** ![thommay](https://avatars.discourse-cdn.com/v4/letter/t/f08c70/32.png) [@thommay](https://discourse.chef.io/u/thommay)\
**Post date:** [January 19, 2018, 10:59am UTC](https://discourse.chef.io/t/chef-verify-is-failing/12454/2 "2018-01-19T10:59:08Z")

</div>

Like the first line says, don’t run that command :).

But I assume there was a reason you did? Is there a problem that you’re actually trying to solve?

---

<div class="post-metadata">

**Author:** ![Neerajjh](https://avatars.discourse-cdn.com/v4/letter/n/dc4da7/32.png) [@Neerajjh](https://discourse.chef.io/u/Neerajjh)\
**Post date:** [January 19, 2018, 11:27am UTC](https://discourse.chef.io/t/chef-verify-is-failing/12454/3 "2018-01-19T11:27:14Z")

</div>

I am from development Team. I am running this command to verify successful installation of all chef components on workstation. I did it after chefDk installation. For other workstations it worked, but failing here.