Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-1368

Puppet on Windows segfaulting

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: PUP 3.3.1, PUP 3.4.1
    • Fix Version/s: PUP 3.4.3, PUP 3.5.0
    • Component/s: Types and Providers
    • Labels:
    • Environment:

      Windows 2008 R2 64-bit, Windows 2008 R2 SP1 64-bit
      One agent with Puppet 3.3.1 and another with 3.4.1

    • Template:
    • Story Points:
      3
    • Sprint:
      Week 2014-1-15 to 2014-1-21, Week 2014-1-22 to 2014-1-29, Week 2014-1-29 to 2014-2-05

      Description

      In the past day I've implemented some scheduled tasks which invoke an MSSQL stored procedure via SQLCMD. Today I've found that these scheduled tasks are causing a segfault on any agent which they run.

      In almost all tests, I've been able to run the agent via "puppet agent --test --debug --trace". The first run will correctly create the scheduled task; but the second run will produce a segfault of the puppet agent, causing the catalog run to never finish. Sometimes a third run was needed to get a segfault.

      The affected nodes so far are both Windows 2008 R2, but running different sets of updates (eg one is not SP1). Both were originally running Puppet 3.3.1, but I upgraded one of them to 3.4.1, which no effect.

      I've created a new 'test' module to simplify reproducing the bug. To test this bug I am simply adding "include test" to the node definition for chosen nodes.

      I've included the test module manifest for reproduction, as well as the stack strace I get when the segfault occurs.

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  kylo Kylo Ginsberg
                  Reporter:
                  geekman Geek Man
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  6 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Zendesk Support