Jira (FACT-1164) facter crashes with sqlserver_instances

Michael Smith (JIRA) Tue, 18 Aug 2015 17:29:37 -0700

Title: Message Title

FACT-1164

This one's weird... the custom fact below, as long as we call CoInitialize in Facter itself, fails.

Facter.add(:sqlserver_instances) do

  setcode do

    require 'win32ole'

    context = WIN32OLE.new('WbemScripting.SWbemNamedValueSet')

    context.Add("__ProviderArchitecture", 64)

    locator = WIN32OLE.new('WbemScripting.SWbemLocator')

    puts locator.ConnectServer('', "root/Microsoft/SqlServer/ComputerManagement12", '', '', nil, nil, nil, context)

    puts "Resolved"

end

end

If I have wmi::wmi throw right after creating the _coInit resource (meaning we call CoInitialize, then almost immediately call CoUninitialize), Facter hangs. If I throw before that so that we never call CoInitialize, it doesn't hang.

There's some interaction between Facter's CoInitialize and using Ruby's WIN32OLE to connect to a server that's causing us to hang on WaitForMultipleObjects. Not sure what it is yet.

Rob Reynolds or Ethan Brown, either of you have experience with this that'd be helpful?

Add Comment

This message was sent by Atlassian JIRA

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (FACT-1164) facter crashes with sqlserver_instances

Reply via email to