Late to the game, but seeing this on 1.14.3 too with dhcp.yaml..   on a 
centos 6.6 box.  Is this another centos ruby 1.8.7 error?

On Wednesday, February 8, 2017 at 12:15:45 PM UTC-6, Daniel Helgenberger 
wrote:
>
> Hello foreman-users, 
>
> I am running smart proxy on windows and was updating it along with 
> foreman to 1.14.1. 
>
> However, dhcpsapi fails to load for some reason and I am out of ideas why: 
>
> > W, [2017-02-08T18:44:27.153727 ]  WARN -- : Couldn't find settings file 
> C:/TheForeman/smart-proxy/config/settings.d/dhcp_native_ms.yml. Using 
> default settings. 
> > E, [2017-02-08T18:44:27.169390 ] ERROR -- : Disabling all modules in the 
> group ['dhcp_native_ms', 'dhcp'] due to a failure in one of them: cannot 
> load such file -- dhcpsapi 
> > D, [2017-02-08T18:44:27.169390 ] DEBUG -- : 
> ["C:/TheForeman/smart-proxy/modules/dhcp_native_ms/plugin_configuration.rb:5:in
>  
> `require'", 
> "C:/TheForeman/smart-proxy/modules/dhcp_native_ms/plugin_configuration.rb:5:in
>  
> `load_classes'", 
> "C:/TheForeman/smart-proxy/lib/proxy/plugin_initializer.rb:294:in 
> `load_classes'", 
> "C:/TheForeman/smart-proxy/lib/proxy/plugin_initializer.rb:243:in 
> `load_settings'", 
> "C:/TheForeman/smart-proxy/lib/proxy/plugin_initializer.rb:81:in `block in 
> load_provider_settings'", 
> "C:/TheForeman/smart-proxy/lib/proxy/plugin_initializer.rb:80:in `each'", 
> "C:/TheForeman/smart-proxy/lib/proxy/plugin_initializer.rb:80:in 
> `load_provider_settings'", 
> "C:/TheForeman/smart-proxy/lib/proxy/plugin_initializer.rb:155:in `block in 
> initialize_plugins'", 
> "C:/TheForeman/smart-proxy/lib/proxy/plugin_initializer.rb:155:in `each'", 
> "C:/TheForeman/smart-proxy/lib/proxy/plugin_initializer.rb:155:in 
> `initialize_plugins'", "C:/TheForeman/smart-proxy/lib/launcher.rb:134:in 
> `launch'", "C:/TheForeman/smart-proxy/bin/smart-proxy:6:in `<main>'"] 
>
> I ran bundle update as usual: 
>
> > $ bundle update 
> > Your Gemfile lists the gem single_test (>= 0) more than once. 
> > You should probably keep only one of them. 
> > While it's not a problem now, it could cause errors if you change the 
> version of                                                                 
>                                                                             
>   just one of them later. 
> > Your Gemfile lists the gem rdoc (>= 0) more than once. 
> > You should probably keep only one of them. 
> > While it's not a problem now, it could cause errors if you change the 
> version of                                                                 
>                                                                             
>   just one of them later. 
> > Fetching gem metadata from http://rubygems.org/............ 
> > Fetching version metadata from http://rubygems.org/.. 
> > Resolving dependencies....... 
> > Using concurrent-ruby 1.0.4 
> > Using ffi 1.9.17 
> > Using dhcpsapi 0.0.11 
> > Using highline 1.7.8 
> > Using json 2.0.3 
> > Using rack 1.5.5 
> > Using rack-protection 1.5.3 
> > Using rb-inotify 0.9.8 
> > Using rb-kqueue 0.2.4 
> > Using tilt 2.0.6 
> > Using sinatra 1.4.8 
> > Using smart_proxy 1.14.1 from source at . 
> > Using win32-service 0.8.8 
> > Using bundler 1.10.6 
> > Bundle updated! 
> > Gems in the groups development, test, krb5, puppet_proxy_legacy, bmc, 
> libvirt, p                                                                 
>                                                                             
>  uppet and puppetca were not installed. 
>
> Also, dhcpsapi loads without trouble: 
> > [1] pry(main)> require 'dhcpsapi' 
> > => true 
>
> I can only think of an load path issue; all other gems seem to load 
> correctly however. For the time being I reverted back to 1.13-stable 
>
> Suggestions welcome ... 
>
> Thanks, 
> -- 
> Daniel Helgenberger (helge000) 
> [email protected] <javascript:> 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to