Issue #5908 has been updated by Matt Robinson.
It looks like this may be a bug with debian squeeze more than puppet. For some
reason using update-rc.d service stop doesn't put in place the right symlinks.
vagrant@vagrant-debian-squeeze:~$ ls -l /etc/rc?.d/*postfix* lrwxrwxrwx
1 root root 17 Mar 21 22:37 /etc/rc0.d/K01postfix -> ../init.d/postfix
lrwxrwxrwx 1 root root 17 Mar 21 22:37 /etc/rc1.d/K01postfix ->
../init.d/postfix
lrwxrwxrwx 1 root root 17 Mar 21 22:37 /etc/rc2.d/S02postfix ->
../init.d/postfix
lrwxrwxrwx 1 root root 17 Mar 21 22:37 /etc/rc3.d/S02postfix ->
../init.d/postfix
lrwxrwxrwx 1 root root 17 Mar 21 22:37 /etc/rc4.d/S02postfix ->
../init.d/postfix
lrwxrwxrwx 1 root root 17 Mar 21 22:37 /etc/rc5.d/S02postfix ->
../init.d/postfix
lrwxrwxrwx 1 root root 17 Mar 21 22:37 /etc/rc6.d/K01postfix ->
../init.d/postfix
vagrant@vagrant-debian-squeeze:~$ sudo update-rc.d -f postfix remove
update-rc.d: using dependency based boot sequencing
vagrant@vagrant-debian-squeeze:~$ ls -l /etc/rc?.d/*postfix*
ls: cannot access /etc/rc?.d/*postfix*: No such file or directory
vagrant@vagrant-debian-squeeze:~$ sudo update-rc.d postfix stop 00 0 1 2 3
4 5 6 .
update-rc.d: using dependency based boot sequencing
update-rc.d: warning: postfix start runlevel arguments (none) do not match
LSB Default-Start values (2 3 4 5)
update-rc.d: warning: postfix stop runlevel arguments (0 1 2 3 4 5 6) do
not match LSB Default-Stop values (0 1 6)
vagrant@vagrant-debian-squeeze:~$ ls -l /etc/rc?.d/*postfix*
lrwxrwxrwx 1 root root 17 Mar 21 22:40 /etc/rc0.d/K01postfix ->
../init.d/postfix
lrwxrwxrwx 1 root root 17 Mar 21 22:40 /etc/rc1.d/K01postfix ->
../init.d/postfix
lrwxrwxrwx 1 root root 17 Mar 21 22:40 /etc/rc2.d/S02postfix ->
../init.d/postfix
lrwxrwxrwx 1 root root 17 Mar 21 22:40 /etc/rc3.d/S02postfix ->
../init.d/postfix
lrwxrwxrwx 1 root root 17 Mar 21 22:40 /etc/rc4.d/S02postfix ->
../init.d/postfix
lrwxrwxrwx 1 root root 17 Mar 21 22:40 /etc/rc5.d/S02postfix ->
../init.d/postfix
lrwxrwxrwx 1 root root 17 Mar 21 22:40 /etc/rc6.d/K01postfix ->
../init.d/postfix
I'm not seeing this problem on Ubuntu Lucid, Maverick or on Debian Lenny.
Surprisingly, using disable does work.
vagrant@vagrant-debian-squeeze:~$ ls -l /etc/rc?.d/*postfix* lrwxrwxrwx
1 root root 17 Mar 21 22:40 /etc/rc0.d/K01postfix -> ../init.d/postfix
lrwxrwxrwx 1 root root 17 Mar 21 22:40 /etc/rc1.d/K01postfix ->
../init.d/postfix
lrwxrwxrwx 1 root root 17 Mar 21 22:42 /etc/rc2.d/S02postfix ->
../init.d/postfix
lrwxrwxrwx 1 root root 17 Mar 21 22:42 /etc/rc3.d/S02postfix ->
../init.d/postfix
lrwxrwxrwx 1 root root 17 Mar 21 22:42 /etc/rc4.d/S02postfix ->
../init.d/postfix
lrwxrwxrwx 1 root root 17 Mar 21 22:42 /etc/rc5.d/S02postfix ->
../init.d/postfix
lrwxrwxrwx 1 root root 17 Mar 21 22:40 /etc/rc6.d/K01postfix ->
../init.d/postfix
vagrant@vagrant-debian-squeeze:~$ sudo update-rc.d postfix disable
update-rc.d: using dependency based boot sequencing
insserv: warning: current start runlevel(s) (empty) of script `postfix'
overwrites defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script
`postfix' overwrites defaults (0 1 6).
insserv: warning: current start runlevel(s) (empty) of script `postfix'
overwrites defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script
`postfix' overwrites defaults (0 1 6).
vagrant@vagrant-debian-squeeze:~$ ls -l /etc/rc?.d/*postfix*
lrwxrwxrwx 1 root root 17 Mar 21 22:40 /etc/rc0.d/K01postfix ->
../init.d/postfix
lrwxrwxrwx 1 root root 17 Mar 21 22:40 /etc/rc1.d/K01postfix ->
../init.d/postfix
lrwxrwxrwx 1 root root 17 Mar 21 22:45 /etc/rc2.d/K01postfix ->
../init.d/postfix
lrwxrwxrwx 1 root root 17 Mar 21 22:45 /etc/rc3.d/K01postfix ->
../init.d/postfix
lrwxrwxrwx 1 root root 17 Mar 21 22:45 /etc/rc4.d/K01postfix ->
../init.d/postfix
lrwxrwxrwx 1 root root 17 Mar 21 22:45 /etc/rc5.d/K01postfix ->
../init.d/postfix
lrwxrwxrwx 1 root root 17 Mar 21 22:40 /etc/rc6.d/K01postfix ->
../init.d/postfix
So we could special case just Debian squeeze (or higher?) to use disable
instead of stop.
----------------------------------------
Bug #5908: Service Provider on Debian unable to disable services: now uses
update-rc.d enable/disable
https://projects.puppetlabs.com/issues/5908
Author: Stig Sandbeck Mathisen
Status: Accepted
Priority: Urgent
Assignee:
Category: service
Target version: 2.6.x
Affected Puppet version: 0.25.4
Keywords: provider, debian, service, update-rc.d
Branch: http://github.com/jamtur01/puppet/tree/tickets/2.6.x/5908
The debian provider of the service type now use update-rc.d "enable" and
"disable", and lets "insserv" select which priorities to use for the symlinks.
This is also true for non-upstart init scripts on Ubuntu.
The following commit, contributed by Martin F Krafft, can be merged to fix this
issue:
Repo: git://git.debian.org/pkg-puppet/puppet.git
Commit: 83d88e218b5f8c940c4f2cc5ba33d3e976ed66bf
Gitweb:
http://git.debian.org/?p=pkg-puppet/puppet.git;a=commit;h=83d88e218b5f8c940c4f2cc5ba33d3e976ed66bf
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
