@cyphermox @paelzer
This patch resolves the systemd multipathd.socket unit problem.
It just waits a while until the socket closes.
The error message is gone, and the unit state is OK after booting.
# systemctl status multipathd.socket
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; static; vendor
preset: enabled)
Active: active (running) since Thu 2017-03-30 11:39:51 CDT; 18min ago
...
In my system, I added an echo debug statement to check it, and it took ~4
seconds.
Weird, but obviously that with such delay, the socket would be still open by
the time the unit was started.
while [ $seconds -gt 0 ]; do
+ echo WAITING FOR SOCKET :: seconds $seconds
grep -q '@/org/kernel/linux/storage/multipathd' /proc/net/unix || break
Begin: Running /scripts/local-bottom ... Begin: Stopping multipathd ... done.
WAIT FOR SOCKET :: seconds 10
WAIT FOR SOCKET :: seconds 9
WAIT FOR SOCKET :: seconds 8
WAIT FOR SOCKET :: seconds 7
done.
** Patch added: "multipath-tools_wait-socket.debdiff"
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1670811/+attachment/4850667/+files/multipath-tools_wait-socket.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670811
Title:
Multipath services fails to start on Ubuntu 17.04 on boot and kdump
(initramfs)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1670811/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
