-
Notifications
You must be signed in to change notification settings - Fork 23.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Module 'service' error on Debian Lenny with svc_cmd #3533
Comments
First I've heard of this one so I'm a little unsure whether this is across Will take a look, thanks. On Mon, Jul 15, 2013 at 9:21 AM, psvo notifications@github.com wrote:
|
Can you share the line from your ansible playbook you were using? |
Following is enough to trigger this error (but happens with ansible-playbook too):
|
Interesting. Haven't heard this reported before and am quite surprised why that would be. On Mon, Jul 15, 2013 at 10:15 AM, psvo notifications@github.com wrote:
|
I looked at it in more detail... Actual status on Lenny is:
And on Squeeze:
And that seems correct, because on Lenny none of searched binaries exists (except for update-rc.d, but that is irrelevant here). In Lenny "service" binary is installed by "admin/sysvconfig" or "admin/chkconfig" but none of them is installed on our systems. AFAIK native binary used by Debian systems is (or at least was) "invoke-rc.d", but it is not detected at all. |
I can confirm the problem, it happened to me recently on a Lenny host. Younger debians (squeeze etc.) are not affected |
When service module is used on unsupported Linux system where init script is used directly, LinuxService.svc_cmd is None so .endswith() fails. Fixes issue #3533
When service module is used on unsupported Linux system where init script is used directly, LinuxService.svc_cmd is None so .endswith() fails. This extends fix from e2f20db also for state=restarted. Fixes issue ansible#3533
When service module is used on unsupported Linux system where init script is used directly, LinuxService.svc_cmd is None so .endswith() fails. This extends fix from e2f20db also for state=restarted. Fixes issue ansible#3533
Module service dies with exception - see below. Problem is caused probably by commit bcca609 which references
'svc_cmd' object attribute that can be None.
Error is triggered at least on Debian Lenny but probably other distributions could be affected too. Debian Squeeze works OK.
Same problem also on another places:
The text was updated successfully, but these errors were encountered: