Control: severity -1 serious
On Fri, Aug 17, 2018 at 9:57 AM Valentin Vidic <valentin.vi...@carnet.hr>
wrote:
> On Fri, Aug 17, 2018 at 02:40:53PM +0200, Michael Biebl wrote:
> > Could you add "set -x" to /usr/sbin/invoke-rc.d, then re-install the
> > lldapd package and attach the output please.
>
> Sure, here it goes:
>
> Preparing to unpack .../lldpad_1.0.1+git20150824.036e314-4_amd64.deb ...
> Unpacking lldpad (1.0.1+git20150824.036e314-4) ...
> Setting up lldpad (1.0.1+git20150824.036e314-4) ...
> + RUNLEVELHELPER=/sbin/runlevel
> + POLICYHELPER=/usr/sbin/policy-rc.d
> + INITDPREFIX=/etc/init.d/
> + RCDPREFIX=/etc/rc
> + BEQUIET=
> + MODE=
> + ACTION=
> + FALLBACK=
> + NOFALLBACK=
> + FORCE=
> + RETRY=
> + RETURNFAILURE=
> + RC=
> + is_systemd=
> + is_openrc=
> + SKIP_SYSTEMD_NATIVE=
> + set +e
> + test 2 -eq 0
> + state=I
> + test 2 -gt 0
> + test I '!=' III
> + case "$1" in
> + case ${state} in
> + verifyparameter lldpad
> + test 1 -eq 0
> + test 1 -ne 1
> + return
> + INITSCRIPTID=lldpad
> + state=II
> + shift
> + test 1 -gt 0
> + test II '!=' III
> + case "$1" in
> + case ${state} in
> + verifyparameter start
> + test 1 -eq 0
> + test 1 -ne 1
> + return
> + ACTION=start
> + state=III
> + shift
> + test 0 -gt 0
> + test III '!=' III
> + test -d /run/systemd/system
> + is_systemd=1
> + UNIT=lldpad.service
> + '[' '!' -x /sbin/runlevel ']'
> ++ /sbin/runlevel
> + RL='N 5'
> + RL=5
> + test x5 = x0
> + test x5 = x6
> + test x5 = x0
> + test x5 = x6
> + RC=
> + '[' -n 1 ']'
> + case ${ACTION} in
> + systemctl --quiet is-enabled lldpad.service
> + systemctl --quiet is-active lldpad.service
> + RC=101
>
Hmm. Commit 6f95680ffc9b1605841eb7d3d8eb92c790e6c73a looks like the culprit
of the regression. But I'd like to understand why this happens. Shouldn't
update-rc.d have enabled the service?
This looks like the same as #906051.
Setting severity to serious. I'll revert the change, until I find some time
to fully investigate the issue.
--
Saludos,
Felipe Sateler
