Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
Platform OS
-
2
-
Platform OS Kanban
-
Reviewed
-
CS doesn't know the deep deep details of this, but Zack remembers something about how SC didn't block, and that blocking is desirable even if it sometimes times out.
Description
From http://stackoverflow.com/q/33531461/18475, net.exe can timeout while waiting for a process that is in a start pending state. The Windows provider for service in Puppet uses net.exe, which returns a non-zero exit code when it times out waiting for the service, even if the service does eventually start up.
It is believed (needs research) that Service Controller (sc.exe) doesn't suffer from this issue.
Investigate using it instead. As a benefit, it can also create and destroy services.
Attachments
Issue Links
- blocks
-
PUP-6254 Windows Service start reports failures instead of success under some states
-
- Closed
-
-
PUP-6822 Windows agents should be able to apply a 'stopped' service resource even if the service doesn't exist
-
- Closed
-
-
PUP-5477 Windows Service Provider should be able to create and destroy services
-
- Accepted
-
-
PUP-1289 Ability to manage a windows service's user account and password
-
- Resolved
-
-
PCP-717 pxp-agent (stable) service_stop_start test failure (windows2008r2)
-
- Closed
-
- is duplicated by
-
PUP-5473 net.exe start reports error starting service, even though the service starts
-
- Closed
-
-
PUP-5757 Replace win32-service calls with internal API implementations that are wide-string compatibles
-
- Closed
-
- relates to
-
MCO-802 MCollective service fails to either start/stop intermittently on windows agents
-
- Closed
-
-
PUP-6254 Windows Service start reports failures instead of success under some states
-
- Closed
-
-
PUP-9113 Unable to manage services with what looks like HyperV installed on Windows
-
- Closed
-
-
PUP-6702 Windows service in Paused state cannot be managed
-
- Closed
-