Opened on 09/08/2015 at 03:00:55 AM
Last modified on 09/08/2015 at 03:02:42 AM
#3006 new defect
Service spawn-fcgi reports inconsistent status codes
| Reported by: | matze | Assignee: | matze |
|---|---|---|---|
| Priority: | P4 | Milestone: | |
| Module: | Infrastructure | Keywords: | |
| Cc: | fred, matze | Blocked By: | |
| Blocking: | Platform: | Unknown / Cross platform | |
| Ready: | yes | Confidential: | no |
| Tester: | Unknown | Verified working: | no |
| Review URL(s): | |||
Description
When provisioning a web::server box with a custom sitescripts backend for the first time, the spawn-fcgi service is not running after Puppet has finished. In fact not even a subsequent Puppet run will start the service, one must do this by hand. When rebooting, however, the service is running as expected.
Background
This seems to be caused by the init-script not reporting LSB compliant status codes - as expected by Puppet -, but printing a status message and returning 0 afterwards - as usual with Debian derivates.
The reason for this being unnoticed most of the time is that development boxes use to become halted but not destroyed between sessions, in which case the next system boot includes starting the spawn-fcgi service.
Note that at this point it is unclear whether this issue is caused by a change in the behavior of Package['spawn-fcgi'] or if it occurred when introducing module spawn::fcgi already.
In both production and development the workaround is quite trivial: Start the service from hand after the first Puppet run on a new host.