chef-12.0.0/lib/chef/event_loggers/windows_eventlog.rb:25:in `block in <top (required)>': uninitialized constant Windows::Constants (NameError) #2560
Comments
|
We are working on repro-ing this issue. |
…ng win event log module to crash Fix for Issue #2560
|
Fixed with #2574. |
|
Thanks heaps :) How long until this is available on the gems list? |
|
I did repro using ruby 2.1.3 and a gem install. The patch we made fixes it, but it does not get much further. Ruby segfaults loading ohai, so just an fyi, you are going down a very unhappy path. This is why we didn't release chef with ruby 2.1. |
|
OTOH, if @pvandervelde can manage to push on this until we wind up fixing ruby 2.1.x on windows that'd be useful... But yes, the road ahead is littered with yak carcasses... |
|
I'll be more than happy to keep reporting bugs. I won't be much good at fixing them given my total lack of Ruby and Chef skills. |
|
Did you guys want me to report the segfault? I can reproduce that one if I patch my local chef install with the changes for the current issue. |
|
Yeah, it can't really hurt, and I haven't had a look at it, and it'd save me fighting with setting up a windows build to replicate it. |
|
Ok I'll put it here for now so that it's there before I leave for work but let me know if you want me to report this in another issue or another repo or anything. E:> chef-client -- Control frame information ----------------------------------------------- -- Ruby level backtrace information ---------------------------------------- -- C level backtrace information ------------------------------------------- -- Other runtime information -----------------------------------------------
[NOTE] This application has requested the Runtime to terminate it in an unusual way. |
|
This is a closed ticket, that should really have its own open issue... |
|
And what leaps out at me is that it is segfaulting in a monkeypatch to the core string class which is super lazy programming. That should be made a proper mixing which is mixed into the class that uses it and takes the string as an argument to the method. |
|
I don't think the place it is crashing is the place the problem is occurring. When I tried it, it seg faulted in wmi-lite. And in our CI, commenting out any tests that use wmi-lite seems to solve the problem. |
|
That being said, monkey patching string could be what is causing it, I just don't know |
|
I think its worth a shot of implementing that as a non-monkeypatch and seeing if the problem goes away, because we should do that anyway, because monkeypatching core ruby classes is horrible... |
|
Fair enough on the 'closed issue' comment, I just didn't have the time to figure out where the issue should be filed this morning when I ran away to work :) So if this is actually a Chef issue and not a Ruby issue then I will move the stack trace to a new issue. If it needs to go elsewhere (i.e. another repository / product / ..) then please let me know. |
|
Maybe ohai? http://github.com/opscode/ohai/issues/new |
Version:
chef 12.0.0
Environment:
Windows 8.1
Installed ruby 2.1.3 and ruby2.devkit via chocolatey
Installed gems:
bigdecimal (1.2.4)
builder (3.2.2)
chef (12.0.0)
chef-zero (3.2.1)
chefspec (4.1.1)
coderay (1.1.0)
diff-lcs (1.2.5)
erubis (2.7.0)
fauxhai (2.2.0)
ffi (1.9.6 x64-mingw32)
ffi-yajl (1.3.1)
foodcritic (4.0.0)
gherkin (2.12.2)
hashie (2.1.2)
highline (1.6.21)
io-console (0.4.2)
ipaddress (0.8.0)
json (1.8.1)
libyajl2 (1.2.0)
method_source (0.8.2)
mime-types (1.25.1)
mini_portile (0.6.1)
minitest (4.7.5)
mixlib-authentication (1.3.0)
mixlib-cli (1.5.0)
mixlib-config (2.1.0)
mixlib-log (1.6.0)
mixlib-shellout (2.0.0, 1.6.1)
multi_json (1.10.1)
net-dhcp (1.3.2)
net-scp (1.2.1)
net-ssh (2.9.1)
net-ssh-gateway (1.2.0)
net-ssh-multi (1.2.0)
nokogiri (1.6.5 x64-mingw32)
ohai (8.0.1)
plist (3.1.0)
polyglot (0.3.5)
pry (0.10.1 x64-mingw32)
psych (2.0.5)
rack (1.5.2)
rake (10.1.0)
rdoc (4.1.0)
rspec (3.1.0)
rspec-core (3.1.7)
rspec-expectations (3.1.2)
rspec-mocks (3.1.3)
rspec-support (3.1.2)
rspec_junit_formatter (0.2.0)
rubygems-update (2.4.5)
rufus-lru (1.0.5)
safe_yaml (1.0.4)
slop (3.6.0)
systemu (2.6.4)
test-kitchen (1.2.1)
test-unit (2.1.3.0)
thor (0.19.1)
treetop (1.5.3)
uuidtools (2.1.5)
win32-api (1.5.2 universal-mingw32)
win32-event (0.6.1)
win32-eventlog (0.6.2)
win32-ipc (0.6.1)
win32-nio (0.1.3)
win32-process (0.7.4)
win32-service (0.8.6)
win32console (1.3.2)
windows-api (0.4.3)
windows-pr (1.2.4)
wmi-lite (1.0.0)
yajl-ruby (1.2.1)
Scenario:
Trying to run chef-client via the chef gem. Failing with an exception.
Steps to Reproduce:
Invoke chef-client on the command line
Actual Result:
I get the following exception when invoking chef-client
Chances are that I'm missing one or more gems but given that I did
gem install chefI would expect to have everything included?The text was updated successfully, but these errors were encountered: