Control: reassign -1 nslcd 0.9.4-3
On Thu, 05 Feb 2015 11:15:32 +0100 Hermann Lauer
<hermann.la...@iwr.uni-heidelberg.de> wrote:
> Package: sysvinit-utils
> Version: 2.88dsf-58
> Severity: normal
>
> Dear Maintainer,
>
> during some "service {start,stop,restart,status} nslcd" usage
> there are for unknown reasons two instances of nslcd running:
>
> # service nslcd status
> â— nslcd.service - LSB: LDAP connection daemon
> Loaded: loaded (/etc/init.d/nslcd)
> Active: active (running) since Mon 2015-02-02 14:56:16 CET; 2 days ago
> Process: 42551 ExecStop=/etc/init.d/nslcd stop (code=exited,
> status=0/SUCCESS)
> Process: 45654 ExecStart=/etc/init.d/nslcd start (code=exited,
> status=0/SUCCESS)
> CGroup: /system.slice/nslcd.service
> ├─30826 /usr/sbin/nslcd
> └─45662 /usr/sbin/nslcd
>
> # service nslcd stop
> # service nslcd status
> â— nslcd.service - LSB: LDAP connection daemon
> Loaded: loaded (/etc/init.d/nslcd)
> Active: inactive (dead) since Thu 2015-02-05 10:47:23 CET; 7s ago
> Process: 40938 ExecStop=/etc/init.d/nslcd stop (code=exited,
> status=0/SUCCESS)
> Process: 45654 ExecStart=/etc/init.d/nslcd start (code=exited,
> status=0/SUCCESS)
>
> Feb 05 10:25:12 quadxeon5 nslcd[45662]: [072b28] <passwd="*"> request denied
> by validnames option
> Feb 05 10:34:19 quadxeon5 nslcd[45662]: [5af992] <passwd="*"> request denied
> by validnames option
> Feb 05 10:34:54 quadxeon5 nslcd[45662]: [e1da79] <passwd="*"> request denied
> by validnames option
> Feb 05 10:36:22 quadxeon5 nslcd[45662]: [2949ad] <passwd="*"> request denied
> by validnames option
> Feb 05 10:39:47 quadxeon5 nslcd[45662]: [6ee0c4] <passwd="*"> request denied
> by validnames option
> Feb 05 10:43:27 quadxeon5 nslcd[45662]: [9a820e] <passwd="..."> (re)loading
> /etc/nsswitch.conf
> Feb 05 10:45:30 quadxeon5 nslcd[45662]: [7708e0] <passwd="*"> request denied
> by validnames option
> Feb 05 10:47:23 quadxeon5 nslcd[45662]: caught signal SIGTERM (15), shutting
> down
> Feb 05 10:47:23 quadxeon5 nslcd[40938]: Stopping LDAP connection daemon:
> nslcd.
> Feb 05 10:47:23 quadxeon5 nslcd[45662]: version 0.9.4 bailing out
>
> As can be seen, stop seems to have worked.
>
> But pstree still shows one nslcd running:
> # pstree -paul | fgrep nslcd
> |-nslcd,30826,nslcd
> | |-{nslcd},30924
> | |-{nslcd},30925
> | |-{nslcd},30926
> | |-{nslcd},30927
> | `-{nslcd},30928
>
> I would expect "service stop" to stop all daemons listed in status.
That would have been a bug in the nslcd init script, and thus am
reassigning with the version in testing at the time of the report. The
changelog for nslcd mentions a related bug report though: #814881.
This was fixed in 0.9.6-4, so maybe this issue is fixed as part of the
same change. I cannot determine that (I don't use nslcd) so I'm not
marking the bug as closed.
Saludos
