cannot load such file -- chef/provider/package/freebsd

[sous-chefs]

cannot load such file -- chef/provider/package/freebsd

[svanzoest]

This seems to be caused by the chef 11.14.2 release in relation to our dependency on the 'freebsd' cookbook. This impacts both master and v1.11.0

[dkinzer]

Ah. OK, that make sense because try as I might I couldn't find a reference that would not give me this error. I think I'll just make sure to tell omnibus to checkout the 11.14.1 release for now. Thanks!

[svanzoest]

This is in the freebsd cookbook, see sous-chefs/freebsd#8

[f4tq]

Trouble is that the 11.14.1 version no longer exists see chef versions. I also ran into this as it just started yesterday. 11.14.2 coincides with the ':latest' omnibus recognized chef release. If you change your chef release to the previous one '11.12.8' then the freebsd bug goes away but reveals an apache2 bug regarding 'Lockfile'. Use this Vagrant file to see:

VAGRANTFILE_API_VERSION = "2"
Vagrant.require_version ">= 1.5.0"
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
  config.vm.hostname = "foo"
  config.omnibus.chef_version = '11.12.8' #:latest
  config.vm.box = "chef/ubuntu-14.04"
  config.vm.network :private_network, type: "dhcp"
  config.berkshelf.enabled = true
  config.vm.provision :chef_solo do |chef|
    chef.json = {
    }
    chef.run_list = [
        "recipe[apache2]"
    ]
  end
end

Here is the output from vagrant up:

=> default: 
==> default: [2014-08-02T18:05:44+00:00] INFO: Running queued delayed notifications before re-raising exception
==> default: [2014-08-02T18:05:44+00:00] INFO: template[apache2.conf] sending reload action to service[apache2] (delayed)
==> default: 
==> default: ================================================================================
==> default: Error executing action `reload` on resource 'service[apache2]'
==> default: ================================================================================
==> default: 
==> default: 
==> default: Mixlib::ShellOut::ShellCommandFailed
==> default: 
==> default: ------------------------------------
==> default: Expected process to exit with [0], but received '1'
==> default: ---- Begin output of /usr/sbin/invoke-rc.d apache2 reload && sleep 1 ----
==> default: STDOUT: * Reloading web server apache2
==> default:  *
==> default:  * The apache2 configtest failed. Not doing anything.
==> default: STDERR: Output of config test was:
==> default: AH00526: Syntax error on line 11 of /etc/apache2/apache2.conf:
==> default: Invalid command 'LockFile', perhaps misspelled or defined by a module not included in the server configuration
==> default: Action 'configtest' failed.
==> default: The Apache error log may have more information.
==> default: invoke-rc.d: initscript apache2, action "reload" failed.
==> default: ---- End output of /usr/sbin/invoke-rc.d apache2 reload && sleep 1 ----
==> default: Ran /usr/sbin/invoke-rc.d apache2 reload && sleep 1 returned 1

Is there a way for me to proceed with apache2 or should I wrap it and remove the Lockfile template?

[dkinzer]

@f4tq, yeah I finally figured that out. But in the meantime the issue got fixed for 11.14.2 so I'm happily using that. However, @svanzoest reports that it breaks for 11.12.8 which is listed as a chef version.

[svanzoest]

@f4tq are you using the v1.11.0 release of the apache2 cookbook on Ubuntu 14.04? That version does not support 14.04, however, the upcoming 2.0 version (currently on the master) will.

[f4tq]

Weird, I just tried 11.14.2-1 with the same Vagrantfile and this happened:

--snip--
==> default: Preparing to unpack .../chef_11.14.2-1_amd64.deb ...
==> default: Unpacking chef (11.14.2-1) ...
==> default: Setting up chef (11.14.2-1) ...
==> default: Thank you for installing Chef!
==> default: Running provisioner: chef_solo...
Generating chef JSON and uploading...
==> default: Running chef-solo...
==> default: stdin: is not a tty
==> default: [2014-08-02T22:17:36+00:00] INFO: Forking chef instance to converge...
==> default: [2014-08-02T22:17:36+00:00] WARN: 
==> default: * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
==> default: SSL validation of HTTPS requests is disabled. HTTPS connections are still
==> default: encrypted, but chef is not able to detect forged replies or man in the middle
==> default: attacks.
==> default: 
==> default: To fix this issue add an entry like this to your configuration file:
==> default: 
==> default: ```
==> default:   # Verify all HTTPS connections (recommended)
==> default:   ssl_verify_mode :verify_peer
==> default: 
==> default:   # OR, Verify only connections to chef-server
==> default:   verify_api_cert true
==> default: ```
==> default: 
==> default: To check your SSL configuration, or troubleshoot errors, you can use the
==> default: `knife ssl check` command like so:
==> default: 
==> default: ```
==> default:   knife ssl check -c /tmp/vagrant-chef-3/solo.rb
==> default: ```
==> default: 
==> default: * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
==> default: [2014-08-02T22:17:36+00:00] INFO: *** Chef 11.14.2 ***
==> default: [2014-08-02T22:17:36+00:00] INFO: Chef-client pid: 1598
==> default: [2014-08-02T22:17:43+00:00] INFO: Setting the run_list to ["recipe[apache2]"] from CLI options
==> default: [2014-08-02T22:17:43+00:00] INFO: Run List is [recipe[apache2]]
==> default: [2014-08-02T22:17:43+00:00] INFO: Run List expands to [apache2]
==> default: [2014-08-02T22:17:43+00:00] INFO: Starting Chef Run for foo3
==> default: [2014-08-02T22:17:43+00:00] INFO: Running start handlers
==> default: [2014-08-02T22:17:43+00:00] INFO: Start handlers complete.
==> default: 
==> default: ================================================================================
==> default: Recipe Compile Error in /tmp/vagrant-chef-3/chef-solo-1/cookbooks/freebsd/libraries/package_provider.rb
==> default: ================================================================================
==> default: 
==> default: 
==> default: LoadError
==> default: ---------
==> default: cannot load such file -- chef/provider/package/freebsd
==> default: 
==> default: 
==> default: Cookbook Trace:
==> default: ---------------
==> default:   /tmp/vagrant-chef-3/chef-solo-1/cookbooks/freebsd/libraries/package_provider.rb:20:in `<top (required)>'
==> default: 
==> default: 
==> default: Relevant File Content:
==> default: ----------------------
==> default: /tmp/vagrant-chef-3/chef-solo-1/cookbooks/freebsd/libraries/package_provider.rb:
==> default: 
==> default: 
==> default: 
==> default:  13:  # Unless required by applicable law or agreed to in writing, software
==> default: 
==> default:  14:  # distributed under the License is distributed on an "AS IS" BASIS,
==> default: 
==> default:  15:  # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
==> default: 
==> default:  16:  # See the License for the specific language governing permissions and
==> default: 
==> default:  17:  # limitations under the License.
==> default: 
==> default:  18:  #
==> default: 
==> default:  19:  
==> default: 
==> default:  20>> require 'chef/provider/package/freebsd'
==> default: 
==> default:  21:  
==> default: 
==> default:  22:  class Chef
==> default: 
==> default:  23:    class Provider
==> default: 
==> default:  24:      class Package
==> default: 
==> default:  25:        #
==> default: 
==> default:  26:        class Freebsd
==> default: 
==> default:  27:          alias_method :original_initialize, :initialize
==> default: 
==> default:  28:  
==> default: 

Are you using apache2::default like I am?

[f4tq]

@svanzoest,
I ran the above Vagrantfile with my Berksfile set as:

cookbook 'apache2', :git => 'https://github.com/onehealth-cookbooks/apache2.git'

That grabs master right? What's really weird about this is that everything worked fine until yesterday around 11am PDT...

[svanzoest]

Please update the freebsd cookbook to version 0.1.9 which now supports both ways. What broke was the release of chef 11.14.2 which was incompatible with the freebsd cookbook (because of some freebsd enhancements in chef-client broke the freebsd cookbook monkey patches).

[f4tq]

@svanzoest
Updating freebsd did the trick. Also, rm -f Berksfile.lock if you're using chef-dev.
Thanks!!!

[axonglue]

Thanks that fixed it for me as well. You might just want to update your berksfile.lock freebsd version to 0.1.9 instead of deleting it. The next time you run vagrant provision it will install and vendor in the new one

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.