Package: shibboleth-sp2-utils
Version: 2.6.0+dfsg1-3+b1
Severity: important
Dear Maintainer,
In attempting to upgrade this package to the latest version, i see
repeated failures. shibd.log does not report unusual errors.
No /run/shibboleth/shibd.sock is created.
During the attempt to upgrade, shibd process starts, but seems to get
hung (ps axjf):
apt-get -f install
\_ /usr/bin/dpkg --status-fd 17 --configure --pending
\_ /bin/sh
\_ /bin/sh /var/lib/dpkg/info/shibboleth-sp2-utils.postinst conf
\_ systemctl start shibd.service
\_ /bin/systemd-tty-ask-password-agent --watch
journalctl -xe shows:
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit shibd.service has begun starting up.
Oct 07 12:24:25 epics systemd[1]: shibd.service: Start operation timed
out. Terminating.
Oct 07 12:24:31 epics systemd[1]: shibd.service: State
'stop-final-sigterm' timed out. Killing.
Oct 07 12:24:31 epics systemd[1]: shibd.service: Killing process 3910
(shibd) with signal SIGKILL.
Oct 07 12:24:31 epics systemd[1]: shibd.service: Main process exited,
code=killed, status=9/KILL
Oct 07 12:24:31 epics systemd[1]: Failed to start Shibboleth Service
Provider Daemon.
-- Subject: Unit shibd.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit shibd.service has failed.
--
-- The result is failed.
Oct 07 12:24:31 epics systemd[1]: shibd.service: Unit entered failed
state.
Oct 07 12:24:31 epics systemd[1]: shibd.service: Failed with result
'signal'.
Oct 07 12:25:01 epics systemd[1]: shibd.service: Service hold-off time
over, scheduling restart.
Oct 07 12:25:01 epics systemd[1]: Stopped Shibboleth Service Provider
Daemon.
-- Subject: Unit shibd.service has finished shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit shibd.service has finished shutting down.
Oct 07 12:25:01 epics systemd[1]: Starting Shibboleth Service Provider
Daemon...
-- Subject: Unit shibd.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit shibd.service has begun starting up.
Based on other bug reports, commands such as
systemctl stop systemd-ask-password-wall.service
and
systemctl daemon-reexec
were tried, and typically led to dpkg failing.
Manually trying to start /usr/sbin/shibd -f -F never produces the
/run/shibboleth/shibd.sock nor any other files in that dir.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.6.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages shibboleth-sp2-utils depends on:
ii adduser 3.115
ii libc6 2.24-3
ii libfcgi0ldbl 2.4.0-8.4
ii libgcc1 1:6.1.1-11
ii liblog4shib1v5 1.0.9-3
ii libsaml9 2.6.0-4
ii libshibsp-plugins 2.6.0+dfsg1-3+b1
ii libshibsp7 2.6.0+dfsg1-3+b1
ii libstdc++6 6.1.1-11
ii libsystemd0 231-9
ii libxerces-c3.1 3.1.3+debian-2.1+b1
ii libxmltooling7 1.6.0-3
Versions of packages shibboleth-sp2-utils recommends:
ii openssl 1.0.2j-1
shibboleth-sp2-utils suggests no packages.
-- no debconf information
