Jira (PUP-8433) PXP fails to start after a Puppet Agent upgrade with SSL library errors
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8433 PXP fails to start after a Puppet Agent upgrade with SSL library errors Change By: Craig Gomes Reporter: James Stocks Glenn Sarti Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8433) PXP fails to start after a Puppet Agent upgrade with SSL library errors
Title: Message Title Michael Smith commented on PUP-8433 Re: PXP fails to start after a Puppet Agent upgrade with SSL library errors We already do the 1st with Ruby, I think that sounds fine until we restructure. If we wanted to do 3 on a small scale, we could just move pxp-agent files, which would be unlikely to break anything people use. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8433) PXP fails to start after a Puppet Agent upgrade with SSL library errors
Title: Message Title Ethan Brown commented on PUP-8433 Re: PXP fails to start after a Puppet Agent upgrade with SSL library errors So I think we have 3 options for addressing this problem. 1. Copy the OpenSSL DLL files into the same directory as pxp-agent.exe, by making changes to the MSI installer. This is the most direct solution and carries a small penalty of including extra files in the installer - but is the least complicated solution (presuming no additional libraries must be copied there). 2. Modify how pxp-agent.exe and the OpenSSL dlls are compiled, so that the win32 loader uses the SxS mechanism to find the libraries by relative path. https://stackoverflow.com/a/1973332 has a good explanation of using resource manifests for precisely this situation, but note that it requires multiple steps from what I can tell: Compile manifests into each of the OpenSSL dlls (requires using mt.exe) that specify the library versions Compile a manifest into pxp-agent.exe that references the OpenSSL dlls Add a pxp-agent.exe.config that lives alongside This requires making some changes to CMake build scripts to include embedded resources. CMake 3.4 added support for manifest resources, but our current CMake 3.2 doesn't understand them natively, though they're straightforward to add https://stackoverflow.com/a/9611396 3. Redo the internals of the installer to move around files so that all binaries are colocated. I'm reluctant to go down this path considering it may cause breaking changes for end users. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-8433) PXP fails to start after a Puppet Agent upgrade with SSL library errors
Title: Message Title Ethan Brown updated an issue Puppet / PUP-8433 PXP fails to start after a Puppet Agent upgrade with SSL library errors Change By: Ethan Brown Sprint: Windows Kanban Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8433) PXP fails to start after a Puppet Agent upgrade with SSL library errors
Title: Message Title Ethan Brown updated an issue Puppet / PUP-8433 PXP fails to start after a Puppet Agent upgrade with SSL library errors Change By: Ethan Brown Labels: customer-escalation manage-service Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8433) PXP fails to start after a Puppet Agent upgrade with SSL library errors
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-8433 PXP fails to start after a Puppet Agent upgrade with SSL library errors Change By: Ethan Brown Assignee: Glenn Sarti Ethan Brown Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8433) PXP fails to start after a Puppet Agent upgrade with SSL library errors
Title: Message Title Ethan Brown updated an issue Puppet / PUP-8433 PXP fails to start after a Puppet Agent upgrade with SSL library errors Change By: Ethan Brown Team: Platform OS Windows Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8433) PXP fails to start after a Puppet Agent upgrade with SSL library errors
Title: Message Title Glenn Sarti commented on PUP-8433 Re: PXP fails to start after a Puppet Agent upgrade with SSL library errors I don't think https://puppetlabs.zendesk.com/agent/tickets/26386 is relevant for this ticket Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8433) PXP fails to start after a Puppet Agent upgrade with SSL library errors
Title: Message Title Glenn Sarti commented on PUP-8433 Re: PXP fails to start after a Puppet Agent upgrade with SSL library errors Repro'd the issue. Some steps may not be required but it's how I did it. Spin up a Puppet Master and Windows 2012R2 client. Fully connect them and ensure the "Run Puppet" functionality is working (Use your own tools for this. For my repro I used the Learning VM from SLICE and a Windows 2012R2 client with the Puppet 5.3.1 x64 Agent Stop the PXP-Agent Service copy the C:\Windows\System32\lltdapi.dll to C:\Windows\System32\libeay32.dll (This is basically using a valid DLL file but it does not have the same functions exported etc. so it should break if used) Start the PXP-Agent Service It Should error and then NSSM will put the service into a Pause state Delete the "bad" C:\Windows\System32\libeay32.dll file and restart the PXP agent service and it will run correctly. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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
Jira (PUP-8433) PXP fails to start after a Puppet Agent upgrade with SSL library errors
Title: Message Title Glenn Sarti commented on PUP-8433 Re: PXP fails to start after a Puppet Agent upgrade with SSL library errors Interesting - https://community.ivanti.com/docs/DOC-61035 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8433) PXP fails to start after a Puppet Agent upgrade with SSL library errors
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-8433 PXP fails to start after a Puppet Agent upgrade with SSL library errors Change By: Glenn Sarti This issue was created from PUP-6702 --- — Steps to reproduce;Unknown at this stage. Looks like it could be made to happen after the puppet_agent module does an agent upgrade. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8433) PXP fails to start after a Puppet Agent upgrade with SSL library errors
Title: Message Title
Glenn Sarti updated an issue
Puppet / PUP-8433
PXP fails to start after a Puppet Agent upgrade with SSL library errors
Change By:
Glenn Sarti
When a service is in the Paused state; it's 'ensure' property cannot be managed by Puppet Note that for our own services that use nssm; nssm has a characteristic that it uses the "Paused" service state for a service that has reached a fault state (see https://nssm.cc/usage )*To reproduce:* * Install puppet-agent * Ensure pxp-agent service is stopped in services.msc * Ensure the ProgramData/PuppetLabs/pxp-agent/etc/pxp-agent.conf file is renamed or deleted * Run _puppet resource service pxp-agent ensure=running_The service will now be in the paused state. Attempting _puppet resource service pxp-agent ensure=stopped_ will echo back ensure=stopped , but services.msc will show the service as still paused. Attempting _puppet resource service pxp-agent ensure=running_ will return an error:{noformat}C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Puppet>puppet resource service pxp-agent ensure=runningError: Cannot start pxp-agent, error This issue was : Execution of 'C:/Windows/system32/net.exe start pxp created from PUP - agent' returned 2: The requested service has already been started. 6702 More help is available by typing NET HELPMSG 2182.Wrapped exception:Execution of 'C:/Windows/system32/net.exe start pxp - agent' returned 2: The requested service has already been started.More help is available by typing NET HELPMSG 2182.Error: /Service[pxp - agent]/ensure: change from stopped to running failed: Cannot start pxp - agent, error was: Execution of 'C:/Windows/system32/net.exe start pxp -agent' returned 2: The requested service has already been started. More help is available by typing NET HELPMSG 2182.{noformat}Outside of Puppet, the service can be stopped by simply using the Stop option in services.msc*Expected behaviour:* * The "Paused" state should be understood by Puppet for a Windows service resource. Or at least; Puppet should actually stop a service in the "Paused" state when ensure=stopped is applied.
Add Comment
Jira (PUP-8433) PXP fails to start after a Puppet Agent upgrade with SSL library errors
Title: Message Title James Stocks created an issue Puppet / PUP-8433 PXP fails to start after a Puppet Agent upgrade with SSL library errors Issue Type: Bug Affects Versions: PUP 4.10.4 Assignee: Glenn Sarti Attachments: screenshot-1.png Components: Windows Created: 2018/02/06 5:46 PM Environment: TEST_TARGET=windows2008r2-64a SUITE_VERSION=1.6.2.135.g8a48f21 SUITE_COMMIT=8a48f210f6901be0edba16eb49c1bfbfb07d338b Labels: manage-service Priority: Major Reporter: James Stocks When a service is in the Paused state; it's 'ensure' property cannot be managed by Puppet Note that for our own services that use nssm; nssm has a characteristic that it uses the "Paused" service state for a service that has reached a fault state (see https://nssm.cc/usage ) To reproduce: Install puppet-agent Ensure pxp-agent service is stopped in services.msc Ensure the ProgramData/PuppetLabs/pxp-agent/etc/pxp-agent.conf file is renamed or deleted
