warning: already initialized constant Lucene::SEP

Question

warning: already initialized constant Lucene::SEP

NikolayMurha opened this issue 10 years ago · 10 comments

Hello.

I have warning:

  /tmp/vagrant-chef-3/chef-solo-1/cookbooks/chef-solo-search/libraries/vendor/chef/solr_query/lucene_nodes.rb:22: warning: already initialized constant Lucene::SEP`

Chef 12.0.3

Answer 1 · 2015-02-07T13:46:04.000Z

*** Chef 12.0.3 ***
==> default: /tmp/vagrant-chef-3/chef-solo-1/cookbooks/chef-solo-search/libraries/vendor/chef/solr_query/lucene_nodes.rb:22: warning: already initialized constant Lucene::SEP
==> default: /tmp/vagrant-chef-3/chef-solo-1/cookbooks/chef-solo-search/libraries/vendor/chef/solr_query/lucene_nodes.rb:22: warning: previous definition of SEP was here

Answer 2 · 2015-02-09T03:33:24.000Z

as far as I know -- chef 12 in local mode has search without needing chef-solo-search.

Part of upgrading to --local-mode instead of chef-solo should be migrating away from chef-solo-search.

have not used --local-mode but that's my understanding

see:
https://www.chef.io/blog/2014/06/24/from-solo-to-zero-migrating-to-chef-client-local-mode/

Answer 3 · 2015-05-07T22:12:41.000Z

I am trying to track this down as well. Using in conjunction with the user cookbook. With chef 12 it seems to be including the library twice...

Answer 4 · 2015-05-07T23:01:49.000Z

curious about why anyone would use chef-solo with chef 12?

Answer 5 · 2015-05-08T13:10:27.000Z

@michaelglass @sigil66 i make use of the https://supermarket.chef.io/cookbooks/users cookbook which will only present a warning when using chef-solo without chef-solo-search.
Although i use chef-zero, the config value "Chef::Config[:solo]" is set to true.

Answer 6 · 2015-05-08T14:30:59.000Z

"Local mode behaves exactly like Chef Solo except that, during a run, it starts up a local Chef Zero server bound to localhost, uploads all local cookbooks & recipes to it, runs Chef Client, and then terminates the Chef Zero server. The end user experience is identical to Solo."

I see no reason to bother starting a chef server, local or remote, when our chef code is distributed with packages. I really only use the search for the users cookbook.

Answer 7 · 2015-05-08T18:06:58.000Z

@sigil66 fwiw, this repo is mostly unmaintained now that chef zero supports search

Answer 8 · 2015-05-08T19:37:56.000Z

Understood. I just pulled it down internally and:

SEP ||= "="

Because after an hour of digging I still couldn't figure out why 'search/parser' was being loaded twice...

Answer 9 · 2015-06-18T17:42:31.000Z

I'm having same issue as @Rud5G. I use chef_zero but Chef::Config[:solo] is true. And the users mdoule basically forces us to use this cookbook. @Rud5G did you find a work around for this issue?

Answer 10 · 2015-06-19T12:19:04.000Z

@Rud5G part of this is a vagrant issue, see: hashicorp/vagrant#5619

Once that get's fix then I think we wont need to use this cookbook to make users work.