| 2023-09-06 01:16:07 |
Mitchell Dzurick |
bug |
|
|
added bug |
| 2023-09-06 13:48:42 |
Mitchell Dzurick |
description |
I noticed that (at least on Lunar) that reinstalling multipath-tools leads to multipathd.socket being inactive.
I don't think this is actually an issue. It's fine for sockets to be inactive, it's just the general behavior I notice with this socket is that it's usually always active, so I wanted to start a discussion on if this behavior warrants further investigation scrutiny.
I reinstalled multipath-tools so the socket says inactive, and the multipathd utility (which communicates through the socket) is responding appropriately without errors.
ubuntu@ip-172-31-37-103:~$ sudo systemctl status multipathd.socket
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-06 00:52:14 UTC; 1min 6s ago
Until: Wed 2023-09-06 00:52:14 UTC; 1min 6s ago
Triggers: ● multipathd.service
Listen: @/org/kernel/linux/storage/multipathd (Stream)
CGroup: /system.slice/multipathd.socket
Notice: journal has been rotated since unit was started, output may be incomplete.
ubuntu@ip-172-31-37-103:~$ sudo apt install multipath-tools --reinstall
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
libintl-perl libintl-xs-perl libmodule-find-perl libmodule-scandeps-perl libproc-processtable-perl
libsort-naturally-perl libterm-readkey-perl
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 328 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://eu-north-1.ec2.archive.ubuntu.com/ubuntu lunar/main amd64 multipath-tools amd64 0.8.8-1ubuntu2 [328 kB]
Fetched 328 kB in 0s (13.5 MB/s)
(Reading database ... 65325 files and directories currently installed.)
Preparing to unpack .../multipath-tools_0.8.8-1ubuntu2_amd64.deb ...
Unpacking multipath-tools (0.8.8-1ubuntu2) over (0.8.8-1ubuntu2) ...
Setting up multipath-tools (0.8.8-1ubuntu2) ...
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145.
Processing triggers for man-db (2.11.2-1) ...
Processing triggers for libc-bin (2.37-0ubuntu2) ...
ubuntu@ip-172-31-37-103:~$ sudo systemctl status multipathd.socket
○ multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: inactive (dead) since Wed 2023-09-06 00:53:47 UTC; 5s ago
Duration: 1min 32.166s
Triggers: ● multipathd.service
Listen: @/org/kernel/linux/storage/multipathd (Stream)
Sep 06 00:53:47 ip-172-31-37-103 systemd[1]: multipathd.socket: Deactivated successfully.
Sep 06 00:53:47 ip-172-31-37-103 systemd[1]: Closed multipathd.socket - multipathd control socket.
Sep 06 00:53:47 ip-172-31-37-103 systemd[1]: multipathd.socket: Socket service multipathd.service already>
Sep 06 00:53:47 ip-172-31-37-103 systemd[1]: Failed to listen on multipathd.socket - multipathd control s>
Notice: journal has been rotated since unit was started, output may be incomplete.
ubuntu@ip-172-31-37-103:~$ sudo multipath -ll
mpatha (360000000000000000e00000000010001) dm-0 IET,VIRTUAL-DISK
size=100M features='0' hwhandler='0' wp=rw
|-+- policy='service-time 0' prio=1 status=active
| `- 1:0:0:1 sdb 8:16 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- 0:0:0:1 sda 8:0 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- 2:0:0:1 sdc 8:32 active ready running
`-+- policy='service-time 0' prio=1 status=enabled
`- 3:0:0:1 sdd 8:48 active ready running |
I noticed that (at least on Lunar) that reinstalling multipath-tools leads to multipathd.socket being inactive.
I don't think this is actually an issue. It's fine for sockets to be inactive, it's just the general behavior I notice with this socket is that it's usually always active, so I wanted to start a discussion on if this behavior warrants further investigation or scrutiny.
I reinstalled multipath-tools so the socket says inactive, and the multipathd utility (which communicates through the socket) is responding appropriately without errors.
ubuntu@ip-172-31-37-103:~$ sudo systemctl status multipathd.socket
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-06 00:52:14 UTC; 1min 6s ago
Until: Wed 2023-09-06 00:52:14 UTC; 1min 6s ago
Triggers: ● multipathd.service
Listen: @/org/kernel/linux/storage/multipathd (Stream)
CGroup: /system.slice/multipathd.socket
Notice: journal has been rotated since unit was started, output may be incomplete.
ubuntu@ip-172-31-37-103:~$ sudo apt install multipath-tools --reinstall
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
libintl-perl libintl-xs-perl libmodule-find-perl libmodule-scandeps-perl libproc-processtable-perl
libsort-naturally-perl libterm-readkey-perl
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 328 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://eu-north-1.ec2.archive.ubuntu.com/ubuntu lunar/main amd64 multipath-tools amd64 0.8.8-1ubuntu2 [328 kB]
Fetched 328 kB in 0s (13.5 MB/s)
(Reading database ... 65325 files and directories currently installed.)
Preparing to unpack .../multipath-tools_0.8.8-1ubuntu2_amd64.deb ...
Unpacking multipath-tools (0.8.8-1ubuntu2) over (0.8.8-1ubuntu2) ...
Setting up multipath-tools (0.8.8-1ubuntu2) ...
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145.
Processing triggers for man-db (2.11.2-1) ...
Processing triggers for libc-bin (2.37-0ubuntu2) ...
ubuntu@ip-172-31-37-103:~$ sudo systemctl status multipathd.socket
○ multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: inactive (dead) since Wed 2023-09-06 00:53:47 UTC; 5s ago
Duration: 1min 32.166s
Triggers: ● multipathd.service
Listen: @/org/kernel/linux/storage/multipathd (Stream)
Sep 06 00:53:47 ip-172-31-37-103 systemd[1]: multipathd.socket: Deactivated successfully.
Sep 06 00:53:47 ip-172-31-37-103 systemd[1]: Closed multipathd.socket - multipathd control socket.
Sep 06 00:53:47 ip-172-31-37-103 systemd[1]: multipathd.socket: Socket service multipathd.service already>
Sep 06 00:53:47 ip-172-31-37-103 systemd[1]: Failed to listen on multipathd.socket - multipathd control s>
Notice: journal has been rotated since unit was started, output may be incomplete.
ubuntu@ip-172-31-37-103:~$ sudo multipath -ll
mpatha (360000000000000000e00000000010001) dm-0 IET,VIRTUAL-DISK
size=100M features='0' hwhandler='0' wp=rw
|-+- policy='service-time 0' prio=1 status=active
| `- 1:0:0:1 sdb 8:16 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- 0:0:0:1 sda 8:0 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- 2:0:0:1 sdc 8:32 active ready running
`-+- policy='service-time 0' prio=1 status=enabled
`- 3:0:0:1 sdd 8:48 active ready running |
|
| 2023-09-13 14:14:16 |
Mitchell Dzurick |
description |
I noticed that (at least on Lunar) that reinstalling multipath-tools leads to multipathd.socket being inactive.
I don't think this is actually an issue. It's fine for sockets to be inactive, it's just the general behavior I notice with this socket is that it's usually always active, so I wanted to start a discussion on if this behavior warrants further investigation or scrutiny.
I reinstalled multipath-tools so the socket says inactive, and the multipathd utility (which communicates through the socket) is responding appropriately without errors.
ubuntu@ip-172-31-37-103:~$ sudo systemctl status multipathd.socket
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-06 00:52:14 UTC; 1min 6s ago
Until: Wed 2023-09-06 00:52:14 UTC; 1min 6s ago
Triggers: ● multipathd.service
Listen: @/org/kernel/linux/storage/multipathd (Stream)
CGroup: /system.slice/multipathd.socket
Notice: journal has been rotated since unit was started, output may be incomplete.
ubuntu@ip-172-31-37-103:~$ sudo apt install multipath-tools --reinstall
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
libintl-perl libintl-xs-perl libmodule-find-perl libmodule-scandeps-perl libproc-processtable-perl
libsort-naturally-perl libterm-readkey-perl
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 328 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://eu-north-1.ec2.archive.ubuntu.com/ubuntu lunar/main amd64 multipath-tools amd64 0.8.8-1ubuntu2 [328 kB]
Fetched 328 kB in 0s (13.5 MB/s)
(Reading database ... 65325 files and directories currently installed.)
Preparing to unpack .../multipath-tools_0.8.8-1ubuntu2_amd64.deb ...
Unpacking multipath-tools (0.8.8-1ubuntu2) over (0.8.8-1ubuntu2) ...
Setting up multipath-tools (0.8.8-1ubuntu2) ...
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145.
Processing triggers for man-db (2.11.2-1) ...
Processing triggers for libc-bin (2.37-0ubuntu2) ...
ubuntu@ip-172-31-37-103:~$ sudo systemctl status multipathd.socket
○ multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: inactive (dead) since Wed 2023-09-06 00:53:47 UTC; 5s ago
Duration: 1min 32.166s
Triggers: ● multipathd.service
Listen: @/org/kernel/linux/storage/multipathd (Stream)
Sep 06 00:53:47 ip-172-31-37-103 systemd[1]: multipathd.socket: Deactivated successfully.
Sep 06 00:53:47 ip-172-31-37-103 systemd[1]: Closed multipathd.socket - multipathd control socket.
Sep 06 00:53:47 ip-172-31-37-103 systemd[1]: multipathd.socket: Socket service multipathd.service already>
Sep 06 00:53:47 ip-172-31-37-103 systemd[1]: Failed to listen on multipathd.socket - multipathd control s>
Notice: journal has been rotated since unit was started, output may be incomplete.
ubuntu@ip-172-31-37-103:~$ sudo multipath -ll
mpatha (360000000000000000e00000000010001) dm-0 IET,VIRTUAL-DISK
size=100M features='0' hwhandler='0' wp=rw
|-+- policy='service-time 0' prio=1 status=active
| `- 1:0:0:1 sdb 8:16 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- 0:0:0:1 sda 8:0 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- 2:0:0:1 sdc 8:32 active ready running
`-+- policy='service-time 0' prio=1 status=enabled
`- 3:0:0:1 sdd 8:48 active ready running |
[Impact]
This issue affects the following packages:
Lunar (0.8.8-1ubuntu2.1)
Jammy (0.8.8-1ubuntu1.22.04.2)
Focal (0.8.3-1ubuntu2.2)
- On upgrade
- On first install
Mantic (0.9.4-5ubuntu3)
- On first install
On Upgrade/Install, the multipathd.socket states that it is inactive. An error is seeing during install/upgrade that says
Job failed. See "journalctl -xe" for details.
The issue is because of the order of the systemctl command and the systemd unit files.
multipathd.service has:
...
After=multipathd.socket
...
Also=multipathd.socket
/var/lib/dpkg/info/multipath-tools.postinst has:
Jammy/Lunar/Focal (added by dh_systemd_start)
deb-systemd-invoke start 'multipathd.service' 'multipathd.socket' >/dev/null || true
Mantic (added by dh_installsystemd)
if [ -n "$2" ]; then
_dh_action=restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action 'multipathd.service' 'multipathd.socket' >/dev/null || true
If we try to start the socket after the service, we get a failure. This is by design so multiple processes of the socket are not active at once.
[Reproducer]
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.service multipathd.socket
Job failed. See "journalctl -xe" for details.
root@ip-172-31-18-52:/var/lib/dpkg/info# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:07:58 UTC; 2s ago
--
○ multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: inactive (dead) since Wed 2023-09-13 14:07:42 UTC; 18s ago
Now if we start the socket and then the service, the socket no longer says it is inactive.
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.socket multipathd.service
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago
# multipath -ll
mpatha (360000000000000000e00000000010001) dm-0 IET,VIRTUAL-DISK
size=100M features='0' hwhandler='0' wp=rw
|-+- policy='service-time 0' prio=1 status=active
| `- 1:0:0:1 sdb 8:16 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- 0:0:0:1 sda 8:0 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- 2:0:0:1 sdc 8:32 active ready running
`-+- policy='service-time 0' prio=1 status=enabled
`- 3:0:0:1 sdd 8:48 active ready running |
|
| 2023-09-13 14:15:20 |
Mitchell Dzurick |
description |
[Impact]
This issue affects the following packages:
Lunar (0.8.8-1ubuntu2.1)
Jammy (0.8.8-1ubuntu1.22.04.2)
Focal (0.8.3-1ubuntu2.2)
- On upgrade
- On first install
Mantic (0.9.4-5ubuntu3)
- On first install
On Upgrade/Install, the multipathd.socket states that it is inactive. An error is seeing during install/upgrade that says
Job failed. See "journalctl -xe" for details.
The issue is because of the order of the systemctl command and the systemd unit files.
multipathd.service has:
...
After=multipathd.socket
...
Also=multipathd.socket
/var/lib/dpkg/info/multipath-tools.postinst has:
Jammy/Lunar/Focal (added by dh_systemd_start)
deb-systemd-invoke start 'multipathd.service' 'multipathd.socket' >/dev/null || true
Mantic (added by dh_installsystemd)
if [ -n "$2" ]; then
_dh_action=restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action 'multipathd.service' 'multipathd.socket' >/dev/null || true
If we try to start the socket after the service, we get a failure. This is by design so multiple processes of the socket are not active at once.
[Reproducer]
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.service multipathd.socket
Job failed. See "journalctl -xe" for details.
root@ip-172-31-18-52:/var/lib/dpkg/info# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:07:58 UTC; 2s ago
--
○ multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: inactive (dead) since Wed 2023-09-13 14:07:42 UTC; 18s ago
Now if we start the socket and then the service, the socket no longer says it is inactive.
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.socket multipathd.service
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago
# multipath -ll
mpatha (360000000000000000e00000000010001) dm-0 IET,VIRTUAL-DISK
size=100M features='0' hwhandler='0' wp=rw
|-+- policy='service-time 0' prio=1 status=active
| `- 1:0:0:1 sdb 8:16 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- 0:0:0:1 sda 8:0 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- 2:0:0:1 sdc 8:32 active ready running
`-+- policy='service-time 0' prio=1 status=enabled
`- 3:0:0:1 sdd 8:48 active ready running |
[Impact]
This issue affects the following packages:
Lunar (0.8.8-1ubuntu2.1)
Jammy (0.8.8-1ubuntu1.22.04.2)
Focal (0.8.3-1ubuntu2.2)
- On upgrade
- On first install
Mantic (0.9.4-5ubuntu3)
- On first install
On Upgrade/Install, the multipathd.socket states that it is inactive. An error is seeing during install/upgrade that says
Job failed. See "journalctl -xe" for details.
The issue is because of the order of the systemctl command and the systemd unit files.
multipathd.service has:
...
After=multipathd.socket
...
Also=multipathd.socket
/var/lib/dpkg/info/multipath-tools.postinst has:
Jammy/Lunar/Focal (added by dh_systemd_start)
deb-systemd-invoke start 'multipathd.service' 'multipathd.socket' >/dev/null || true
Mantic (added by dh_installsystemd)
if [ -n "$2" ]; then
_dh_action=restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action 'multipathd.service' 'multipathd.socket' >/dev/null || true
If we try to start the socket after the service, we get a failure. This is by design so multiple processes of the socket are not active at once.
[Reproducer]
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.service multipathd.socket
Job failed. See "journalctl -xe" for details.
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:07:58 UTC; 2s ago
--
○ multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: inactive (dead) since Wed 2023-09-13 14:07:42 UTC; 18s ago
Now if we start the socket and then the service, the socket no longer says it is inactive.
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.socket multipathd.service
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago
# multipath -ll
mpatha (360000000000000000e00000000010001) dm-0 IET,VIRTUAL-DISK
size=100M features='0' hwhandler='0' wp=rw
|-+- policy='service-time 0' prio=1 status=active
| `- 1:0:0:1 sdb 8:16 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- 0:0:0:1 sda 8:0 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- 2:0:0:1 sdc 8:32 active ready running
`-+- policy='service-time 0' prio=1 status=enabled
`- 3:0:0:1 sdd 8:48 active ready running |
|
| 2023-09-13 16:43:02 |
Mitchell Dzurick |
summary |
Reinstalling multipath-tools leads to multipathd.socket being inactive |
Installing/Upgrading multipath-tools leads to multipathd.socket being inactive |
|
| 2023-09-13 18:22:11 |
Mitchell Dzurick |
description |
[Impact]
This issue affects the following packages:
Lunar (0.8.8-1ubuntu2.1)
Jammy (0.8.8-1ubuntu1.22.04.2)
Focal (0.8.3-1ubuntu2.2)
- On upgrade
- On first install
Mantic (0.9.4-5ubuntu3)
- On first install
On Upgrade/Install, the multipathd.socket states that it is inactive. An error is seeing during install/upgrade that says
Job failed. See "journalctl -xe" for details.
The issue is because of the order of the systemctl command and the systemd unit files.
multipathd.service has:
...
After=multipathd.socket
...
Also=multipathd.socket
/var/lib/dpkg/info/multipath-tools.postinst has:
Jammy/Lunar/Focal (added by dh_systemd_start)
deb-systemd-invoke start 'multipathd.service' 'multipathd.socket' >/dev/null || true
Mantic (added by dh_installsystemd)
if [ -n "$2" ]; then
_dh_action=restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action 'multipathd.service' 'multipathd.socket' >/dev/null || true
If we try to start the socket after the service, we get a failure. This is by design so multiple processes of the socket are not active at once.
[Reproducer]
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.service multipathd.socket
Job failed. See "journalctl -xe" for details.
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:07:58 UTC; 2s ago
--
○ multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: inactive (dead) since Wed 2023-09-13 14:07:42 UTC; 18s ago
Now if we start the socket and then the service, the socket no longer says it is inactive.
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.socket multipathd.service
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago
# multipath -ll
mpatha (360000000000000000e00000000010001) dm-0 IET,VIRTUAL-DISK
size=100M features='0' hwhandler='0' wp=rw
|-+- policy='service-time 0' prio=1 status=active
| `- 1:0:0:1 sdb 8:16 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- 0:0:0:1 sda 8:0 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- 2:0:0:1 sdc 8:32 active ready running
`-+- policy='service-time 0' prio=1 status=enabled
`- 3:0:0:1 sdd 8:48 active ready running |
[Impact]
On Upgrade/Install, the multipathd.socket states that it is inactive. An error is seeing during install/upgrade that says
Job failed. See "journalctl -xe" for details.
This issue affects the following packages:
Lunar (0.8.8-1ubuntu2.1)
Jammy (0.8.8-1ubuntu1.22.04.2)
Focal (0.8.3-1ubuntu2.2)
- On upgrade
- On first install
Mantic (0.9.4-5ubuntu3)
- On first install
The issue is because of the order of the systemctl command and the systemd unit files.
multipathd.service has:
...
After=multipathd.socket
...
Also=multipathd.socket
/var/lib/dpkg/info/multipath-tools.postinst has:
Jammy/Lunar/Focal (added by dh_systemd_start)
deb-systemd-invoke start 'multipathd.service' 'multipathd.socket' >/dev/null || true
Mantic (added by dh_installsystemd)
if [ -n "$2" ]; then
_dh_action=restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action 'multipathd.service' 'multipathd.socket' >/dev/null || true
If we try to start the socket after the service, we get a failure. This is by design so multiple processes of the socket are not active at once.
[Test Case]
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.service multipathd.socket
Job failed. See "journalctl -xe" for details.
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:07:58 UTC; 2s ago
--
○ multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: inactive (dead) since Wed 2023-09-13 14:07:42 UTC; 18s ago
Now if we start the socket and then the service, the socket no longer says it is inactive.
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.socket multipathd.service
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago |
|
| 2023-09-13 18:44:01 |
Mitchell Dzurick |
description |
[Impact]
On Upgrade/Install, the multipathd.socket states that it is inactive. An error is seeing during install/upgrade that says
Job failed. See "journalctl -xe" for details.
This issue affects the following packages:
Lunar (0.8.8-1ubuntu2.1)
Jammy (0.8.8-1ubuntu1.22.04.2)
Focal (0.8.3-1ubuntu2.2)
- On upgrade
- On first install
Mantic (0.9.4-5ubuntu3)
- On first install
The issue is because of the order of the systemctl command and the systemd unit files.
multipathd.service has:
...
After=multipathd.socket
...
Also=multipathd.socket
/var/lib/dpkg/info/multipath-tools.postinst has:
Jammy/Lunar/Focal (added by dh_systemd_start)
deb-systemd-invoke start 'multipathd.service' 'multipathd.socket' >/dev/null || true
Mantic (added by dh_installsystemd)
if [ -n "$2" ]; then
_dh_action=restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action 'multipathd.service' 'multipathd.socket' >/dev/null || true
If we try to start the socket after the service, we get a failure. This is by design so multiple processes of the socket are not active at once.
[Test Case]
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.service multipathd.socket
Job failed. See "journalctl -xe" for details.
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:07:58 UTC; 2s ago
--
○ multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: inactive (dead) since Wed 2023-09-13 14:07:42 UTC; 18s ago
Now if we start the socket and then the service, the socket no longer says it is inactive.
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.socket multipathd.service
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago |
[Impact]
On Upgrade/Install, the multipathd.socket states that it is inactive. An error is seen during install/upgrade that says
Job failed. See "journalctl -xe" for details.
This issue affects the following packages:
Lunar (0.8.8-1ubuntu2.1)
Jammy (0.8.8-1ubuntu1.22.04.2)
Focal (0.8.3-1ubuntu2.2)
- On upgrade
- On first install
Mantic (0.9.4-5ubuntu3)
- On first install
The issue is because of the order of the systemctl command and the systemd unit files.
multipathd.service has:
...
After=multipathd.socket
...
Also=multipathd.socket
/var/lib/dpkg/info/multipath-tools.postinst has:
Jammy/Lunar/Focal (added by dh_systemd_start)
deb-systemd-invoke start 'multipathd.service' 'multipathd.socket' >/dev/null || true
Mantic (added by dh_installsystemd)
if [ -n "$2" ]; then
_dh_action=restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action 'multipathd.service' 'multipathd.socket' >/dev/null || true
If we try to start the socket after the service, we get a failure. This is by design so multiple processes of the socket are not active at once.
[Test Case]
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.service multipathd.socket
Job failed. See "journalctl -xe" for details.
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:07:58 UTC; 2s ago
--
○ multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: inactive (dead) since Wed 2023-09-13 14:07:42 UTC; 18s ago
Now if we start the socket and then the service, the socket no longer says it is inactive.
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.socket multipathd.service
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago |
|
| 2023-09-13 18:45:53 |
Mitchell Dzurick |
summary |
Installing/Upgrading multipath-tools leads to multipathd.socket being inactive |
[FFE] Installing/Upgrading multipath-tools leads to multipathd.socket being inactive |
|
| 2023-09-13 18:46:01 |
Mitchell Dzurick |
summary |
[FFE] Installing/Upgrading multipath-tools leads to multipathd.socket being inactive |
[FFE+SRU] Installing/Upgrading multipath-tools leads to multipathd.socket being inactive |
|
| 2023-09-13 18:59:52 |
Mitchell Dzurick |
description |
[Impact]
On Upgrade/Install, the multipathd.socket states that it is inactive. An error is seen during install/upgrade that says
Job failed. See "journalctl -xe" for details.
This issue affects the following packages:
Lunar (0.8.8-1ubuntu2.1)
Jammy (0.8.8-1ubuntu1.22.04.2)
Focal (0.8.3-1ubuntu2.2)
- On upgrade
- On first install
Mantic (0.9.4-5ubuntu3)
- On first install
The issue is because of the order of the systemctl command and the systemd unit files.
multipathd.service has:
...
After=multipathd.socket
...
Also=multipathd.socket
/var/lib/dpkg/info/multipath-tools.postinst has:
Jammy/Lunar/Focal (added by dh_systemd_start)
deb-systemd-invoke start 'multipathd.service' 'multipathd.socket' >/dev/null || true
Mantic (added by dh_installsystemd)
if [ -n "$2" ]; then
_dh_action=restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action 'multipathd.service' 'multipathd.socket' >/dev/null || true
If we try to start the socket after the service, we get a failure. This is by design so multiple processes of the socket are not active at once.
[Test Case]
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.service multipathd.socket
Job failed. See "journalctl -xe" for details.
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:07:58 UTC; 2s ago
--
○ multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: inactive (dead) since Wed 2023-09-13 14:07:42 UTC; 18s ago
Now if we start the socket and then the service, the socket no longer says it is inactive.
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.socket multipathd.service
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago |
[FFE]
This is an issue with the systemd service not stating the dependency on the socket, but stating a start order with the socket. The fix here is to add
Wants=multipathd.socket
in multipathd.service which is a weak dependency, so the chance of issues arising from it is low, but helps to solve this particular issue.
[Impact]
On Upgrade/Install, the multipathd.socket states that it is inactive. An error is seen during install/upgrade that says
Job failed. See "journalctl -xe" for details.
This issue affects the following packages:
Lunar (0.8.8-1ubuntu2.1)
Jammy (0.8.8-1ubuntu1.22.04.2)
Focal (0.8.3-1ubuntu2.2)
- On upgrade
- On first install
Mantic (0.9.4-5ubuntu3)
- On first install
The issue is because of the order of the systemctl command and the systemd unit files.
multipathd.service has:
...
After=multipathd.socket
...
Also=multipathd.socket
multipath-tools.postinst has:
Jammy/Lunar/Focal (added by dh_systemd_start)
deb-systemd-invoke start 'multipathd.service' 'multipathd.socket' >/dev/null || true
Mantic (added by dh_installsystemd)
if [ -n "$2" ]; then
_dh_action=restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action 'multipathd.service' 'multipathd.socket' >/dev/null || true
In other words,
systemctl stop multipathd.service multipathd.socket
systemctl start multipathd.service multipathd.socket
will fail
systemctl stop multipathd.service multipathd.socket
systemctl start multipathd.socket multipathd.service
will succeed
If we try to start the socket after the service, we get a failure. This is by design so multiple processes of the socket are not active at once.
[Test Case]
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.service multipathd.socket
Job failed. See "journalctl -xe" for details.
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:07:58 UTC; 2s ago
--
○ multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: inactive (dead) since Wed 2023-09-13 14:07:42 UTC; 18s ago
Now if we start the socket and then the service, the socket no longer says it is inactive.
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.socket multipathd.service
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago |
|
| 2023-09-13 19:07:15 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~mitchdz/ubuntu/+source/multipath-tools/+git/multipath-tools/+merge/451301 |
|
| 2023-09-13 19:09:57 |
Mitchell Dzurick |
summary |
[FFE+SRU] Installing/Upgrading multipath-tools leads to multipathd.socket being inactive |
Installing/Upgrading multipath-tools leads to multipathd.socket being inactive |
|
| 2023-09-13 19:10:07 |
Mitchell Dzurick |
description |
[FFE]
This is an issue with the systemd service not stating the dependency on the socket, but stating a start order with the socket. The fix here is to add
Wants=multipathd.socket
in multipathd.service which is a weak dependency, so the chance of issues arising from it is low, but helps to solve this particular issue.
[Impact]
On Upgrade/Install, the multipathd.socket states that it is inactive. An error is seen during install/upgrade that says
Job failed. See "journalctl -xe" for details.
This issue affects the following packages:
Lunar (0.8.8-1ubuntu2.1)
Jammy (0.8.8-1ubuntu1.22.04.2)
Focal (0.8.3-1ubuntu2.2)
- On upgrade
- On first install
Mantic (0.9.4-5ubuntu3)
- On first install
The issue is because of the order of the systemctl command and the systemd unit files.
multipathd.service has:
...
After=multipathd.socket
...
Also=multipathd.socket
multipath-tools.postinst has:
Jammy/Lunar/Focal (added by dh_systemd_start)
deb-systemd-invoke start 'multipathd.service' 'multipathd.socket' >/dev/null || true
Mantic (added by dh_installsystemd)
if [ -n "$2" ]; then
_dh_action=restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action 'multipathd.service' 'multipathd.socket' >/dev/null || true
In other words,
systemctl stop multipathd.service multipathd.socket
systemctl start multipathd.service multipathd.socket
will fail
systemctl stop multipathd.service multipathd.socket
systemctl start multipathd.socket multipathd.service
will succeed
If we try to start the socket after the service, we get a failure. This is by design so multiple processes of the socket are not active at once.
[Test Case]
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.service multipathd.socket
Job failed. See "journalctl -xe" for details.
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:07:58 UTC; 2s ago
--
○ multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: inactive (dead) since Wed 2023-09-13 14:07:42 UTC; 18s ago
Now if we start the socket and then the service, the socket no longer says it is inactive.
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.socket multipathd.service
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago |
[Impact]
On Upgrade/Install, the multipathd.socket states that it is inactive. An error is seen during install/upgrade that says
Job failed. See "journalctl -xe" for details.
This issue affects the following packages:
Lunar (0.8.8-1ubuntu2.1)
Jammy (0.8.8-1ubuntu1.22.04.2)
Focal (0.8.3-1ubuntu2.2)
- On upgrade
- On first install
Mantic (0.9.4-5ubuntu3)
- On first install
The issue is because of the order of the systemctl command and the systemd unit files.
multipathd.service has:
...
After=multipathd.socket
...
Also=multipathd.socket
multipath-tools.postinst has:
Jammy/Lunar/Focal (added by dh_systemd_start)
deb-systemd-invoke start 'multipathd.service' 'multipathd.socket' >/dev/null || true
Mantic (added by dh_installsystemd)
if [ -n "$2" ]; then
_dh_action=restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action 'multipathd.service' 'multipathd.socket' >/dev/null || true
In other words,
systemctl stop multipathd.service multipathd.socket
systemctl start multipathd.service multipathd.socket
will fail
systemctl stop multipathd.service multipathd.socket
systemctl start multipathd.socket multipathd.service
will succeed
If we try to start the socket after the service, we get a failure. This is by design so multiple processes of the socket are not active at once.
[Test Case]
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.service multipathd.socket
Job failed. See "journalctl -xe" for details.
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:07:58 UTC; 2s ago
--
○ multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: inactive (dead) since Wed 2023-09-13 14:07:42 UTC; 18s ago
Now if we start the socket and then the service, the socket no longer says it is inactive.
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.socket multipathd.service
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago |
|
| 2023-09-13 19:10:59 |
Mitchell Dzurick |
description |
[Impact]
On Upgrade/Install, the multipathd.socket states that it is inactive. An error is seen during install/upgrade that says
Job failed. See "journalctl -xe" for details.
This issue affects the following packages:
Lunar (0.8.8-1ubuntu2.1)
Jammy (0.8.8-1ubuntu1.22.04.2)
Focal (0.8.3-1ubuntu2.2)
- On upgrade
- On first install
Mantic (0.9.4-5ubuntu3)
- On first install
The issue is because of the order of the systemctl command and the systemd unit files.
multipathd.service has:
...
After=multipathd.socket
...
Also=multipathd.socket
multipath-tools.postinst has:
Jammy/Lunar/Focal (added by dh_systemd_start)
deb-systemd-invoke start 'multipathd.service' 'multipathd.socket' >/dev/null || true
Mantic (added by dh_installsystemd)
if [ -n "$2" ]; then
_dh_action=restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action 'multipathd.service' 'multipathd.socket' >/dev/null || true
In other words,
systemctl stop multipathd.service multipathd.socket
systemctl start multipathd.service multipathd.socket
will fail
systemctl stop multipathd.service multipathd.socket
systemctl start multipathd.socket multipathd.service
will succeed
If we try to start the socket after the service, we get a failure. This is by design so multiple processes of the socket are not active at once.
[Test Case]
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.service multipathd.socket
Job failed. See "journalctl -xe" for details.
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:07:58 UTC; 2s ago
--
○ multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: inactive (dead) since Wed 2023-09-13 14:07:42 UTC; 18s ago
Now if we start the socket and then the service, the socket no longer says it is inactive.
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.socket multipathd.service
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago |
This is an issue with the systemd service not stating the dependency on the socket, but stating a start order with the socket. The fix here is to add
Wants=multipathd.socket
in multipathd.service which is a weak dependency, so the chance of issues arising from it is low, but helps to solve this particular issue.
[Impact]
On Upgrade/Install, the multipathd.socket states that it is inactive. An error is seen during install/upgrade that says
Job failed. See "journalctl -xe" for details.
This issue affects the following packages:
Lunar (0.8.8-1ubuntu2.1)
Jammy (0.8.8-1ubuntu1.22.04.2)
Focal (0.8.3-1ubuntu2.2)
- On upgrade
- On first install
Mantic (0.9.4-5ubuntu3)
- On first install
The issue is because of the order of the systemctl command and the systemd unit files.
multipathd.service has:
...
After=multipathd.socket
...
Also=multipathd.socket
multipath-tools.postinst has:
Jammy/Lunar/Focal (added by dh_systemd_start)
deb-systemd-invoke start 'multipathd.service' 'multipathd.socket' >/dev/null || true
Mantic (added by dh_installsystemd)
if [ -n "$2" ]; then
_dh_action=restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action 'multipathd.service' 'multipathd.socket' >/dev/null || true
In other words,
systemctl stop multipathd.service multipathd.socket
systemctl start multipathd.service multipathd.socket
will fail
systemctl stop multipathd.service multipathd.socket
systemctl start multipathd.socket multipathd.service
will succeed
If we try to start the socket after the service, we get a failure. This is by design so multiple processes of the socket are not active at once.
[Test Case]
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.service multipathd.socket
Job failed. See "journalctl -xe" for details.
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:07:58 UTC; 2s ago
--
○ multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: inactive (dead) since Wed 2023-09-13 14:07:42 UTC; 18s ago
Now if we start the socket and then the service, the socket no longer says it is inactive.
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.socket multipathd.service
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago |
|
| 2023-09-13 19:19:05 |
Mitchell Dzurick |
description |
This is an issue with the systemd service not stating the dependency on the socket, but stating a start order with the socket. The fix here is to add
Wants=multipathd.socket
in multipathd.service which is a weak dependency, so the chance of issues arising from it is low, but helps to solve this particular issue.
[Impact]
On Upgrade/Install, the multipathd.socket states that it is inactive. An error is seen during install/upgrade that says
Job failed. See "journalctl -xe" for details.
This issue affects the following packages:
Lunar (0.8.8-1ubuntu2.1)
Jammy (0.8.8-1ubuntu1.22.04.2)
Focal (0.8.3-1ubuntu2.2)
- On upgrade
- On first install
Mantic (0.9.4-5ubuntu3)
- On first install
The issue is because of the order of the systemctl command and the systemd unit files.
multipathd.service has:
...
After=multipathd.socket
...
Also=multipathd.socket
multipath-tools.postinst has:
Jammy/Lunar/Focal (added by dh_systemd_start)
deb-systemd-invoke start 'multipathd.service' 'multipathd.socket' >/dev/null || true
Mantic (added by dh_installsystemd)
if [ -n "$2" ]; then
_dh_action=restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action 'multipathd.service' 'multipathd.socket' >/dev/null || true
In other words,
systemctl stop multipathd.service multipathd.socket
systemctl start multipathd.service multipathd.socket
will fail
systemctl stop multipathd.service multipathd.socket
systemctl start multipathd.socket multipathd.service
will succeed
If we try to start the socket after the service, we get a failure. This is by design so multiple processes of the socket are not active at once.
[Test Case]
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.service multipathd.socket
Job failed. See "journalctl -xe" for details.
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:07:58 UTC; 2s ago
--
○ multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: inactive (dead) since Wed 2023-09-13 14:07:42 UTC; 18s ago
Now if we start the socket and then the service, the socket no longer says it is inactive.
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.socket multipathd.service
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago |
This is an issue with the systemd service not stating the dependency on the socket, but stating a start order with the socket. The fix here is to add
Wants=multipathd.socket
in multipathd.service which is a weak dependency, so the chance of issues arising from it is low, but helps to solve this particular issue.
[Impact]
On Upgrade/Install, the multipathd.socket states that it is inactive. An error is seen during install/upgrade that says
Job failed. See "journalctl -xe" for details.
This issue affects the following packages:
Lunar (0.8.8-1ubuntu2.1)
Jammy (0.8.8-1ubuntu1.22.04.2)
Focal (0.8.3-1ubuntu2.2)
- On upgrade
- On first install
Mantic (0.9.4-5ubuntu3)
- On first install
The issue is because of the order of the systemctl command and the systemd unit files.
multipathd.service has:
...
After=multipathd.socket
...
Also=multipathd.socket
multipath-tools.postinst has:
Jammy/Lunar/Focal (added by dh_systemd_start)
deb-systemd-invoke start 'multipathd.service' 'multipathd.socket' >/dev/null || true
Mantic (added by dh_installsystemd)
if [ -n "$2" ]; then
_dh_action=restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action 'multipathd.service' 'multipathd.socket' >/dev/null || true
In other words,
systemctl stop multipathd.service multipathd.socket
systemctl start multipathd.service multipathd.socket
will fail
systemctl stop multipathd.service multipathd.socket
systemctl start multipathd.socket multipathd.service
will succeed
If we try to start the socket after the service, we get a failure. This is by design so multiple processes of the socket are not active at once.
[Test Cases]
Due to the nature of this bug/fix, multiple test cases are defined here:
1. Install multipath-tools when it is uninstalled
2. Upgrade multipath-tools to this version
3. Downgrade multipath-tools to this version
4. Reintsall multipath-tools when it is this version
5.
systemctl stop multipathd.service multipathd.socket
systemctl start multipathd.service multipathd.socket
All test cases should result in _no errors_ and both multipathd.service multipathd.socket are active
[Reproducer]
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.service multipathd.socket
Job failed. See "journalctl -xe" for details.
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:07:58 UTC; 2s ago
--
○ multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: inactive (dead) since Wed 2023-09-13 14:07:42 UTC; 18s ago
Now if we start the socket and then the service, the socket no longer says it is inactive.
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.socket multipathd.service
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago |
|
| 2023-09-13 19:19:07 |
Mitchell Dzurick |
multipath-tools (Ubuntu): assignee |
|
Mitchell Dzurick (mitchdz) |
|
| 2023-09-13 19:22:04 |
Mitchell Dzurick |
description |
This is an issue with the systemd service not stating the dependency on the socket, but stating a start order with the socket. The fix here is to add
Wants=multipathd.socket
in multipathd.service which is a weak dependency, so the chance of issues arising from it is low, but helps to solve this particular issue.
[Impact]
On Upgrade/Install, the multipathd.socket states that it is inactive. An error is seen during install/upgrade that says
Job failed. See "journalctl -xe" for details.
This issue affects the following packages:
Lunar (0.8.8-1ubuntu2.1)
Jammy (0.8.8-1ubuntu1.22.04.2)
Focal (0.8.3-1ubuntu2.2)
- On upgrade
- On first install
Mantic (0.9.4-5ubuntu3)
- On first install
The issue is because of the order of the systemctl command and the systemd unit files.
multipathd.service has:
...
After=multipathd.socket
...
Also=multipathd.socket
multipath-tools.postinst has:
Jammy/Lunar/Focal (added by dh_systemd_start)
deb-systemd-invoke start 'multipathd.service' 'multipathd.socket' >/dev/null || true
Mantic (added by dh_installsystemd)
if [ -n "$2" ]; then
_dh_action=restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action 'multipathd.service' 'multipathd.socket' >/dev/null || true
In other words,
systemctl stop multipathd.service multipathd.socket
systemctl start multipathd.service multipathd.socket
will fail
systemctl stop multipathd.service multipathd.socket
systemctl start multipathd.socket multipathd.service
will succeed
If we try to start the socket after the service, we get a failure. This is by design so multiple processes of the socket are not active at once.
[Test Cases]
Due to the nature of this bug/fix, multiple test cases are defined here:
1. Install multipath-tools when it is uninstalled
2. Upgrade multipath-tools to this version
3. Downgrade multipath-tools to this version
4. Reintsall multipath-tools when it is this version
5.
systemctl stop multipathd.service multipathd.socket
systemctl start multipathd.service multipathd.socket
All test cases should result in _no errors_ and both multipathd.service multipathd.socket are active
[Reproducer]
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.service multipathd.socket
Job failed. See "journalctl -xe" for details.
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:07:58 UTC; 2s ago
--
○ multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: inactive (dead) since Wed 2023-09-13 14:07:42 UTC; 18s ago
Now if we start the socket and then the service, the socket no longer says it is inactive.
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.socket multipathd.service
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago |
This is an issue with the systemd service not stating the dependency on the socket, but stating a start order with the socket. The fix here is to add
Wants=multipathd.socket
in multipathd.service which is a weak dependency, so the chance of issues arising from it is low, but helps to solve this particular issue.
[Impact]
On Upgrade/Install, the multipathd.socket states that it is inactive. An error is seen during install/upgrade that says
Job failed. See "journalctl -xe" for details.
This issue affects the following packages:
Lunar (0.8.8-1ubuntu2.1)
Jammy (0.8.8-1ubuntu1.22.04.2)
Focal (0.8.3-1ubuntu2.2)
- On upgrade
- On first install
Mantic (0.9.4-5ubuntu3)
- On first install
The issue is because of the order of the systemctl command and the systemd unit files.
multipathd.service has:
...
After=multipathd.socket
...
Also=multipathd.socket
multipath-tools.postinst has:
Jammy/Lunar/Focal (added by dh_systemd_start)
deb-systemd-invoke start 'multipathd.service' 'multipathd.socket' >/dev/null || true
Mantic (added by dh_installsystemd)
if [ -n "$2" ]; then
_dh_action=restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action 'multipathd.service' 'multipathd.socket' >/dev/null || true
In other words,
systemctl stop multipathd.service multipathd.socket
systemctl start multipathd.service multipathd.socket
will fail
systemctl stop multipathd.service multipathd.socket
systemctl start multipathd.socket multipathd.service
will succeed
If we try to start the socket after the service, we get a failure. This is by design so multiple processes of the socket are not active at once.
[Test Cases]
Due to the nature of this bug/fix, multiple test cases are defined here:
1. Install multipath-tools when it is uninstalled
2. Upgrade multipath-tools to this version
3. Downgrade multipath-tools to this version
4. Reinstall multipath-tools when it is this version
5.
systemctl stop multipathd.service multipathd.socket
systemctl start multipathd.service multipathd.socket
All test cases should result in _no errors_ and both multipathd.service multipathd.socket are active
[Reproducer]
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.service multipathd.socket
Job failed. See "journalctl -xe" for details.
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:07:58 UTC; 2s ago
--
○ multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: inactive (dead) since Wed 2023-09-13 14:07:42 UTC; 18s ago
Now if we start the socket and then the service, the socket no longer says it is inactive.
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.socket multipathd.service
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago |
|
| 2023-09-13 19:32:27 |
Mitchell Dzurick |
description |
This is an issue with the systemd service not stating the dependency on the socket, but stating a start order with the socket. The fix here is to add
Wants=multipathd.socket
in multipathd.service which is a weak dependency, so the chance of issues arising from it is low, but helps to solve this particular issue.
[Impact]
On Upgrade/Install, the multipathd.socket states that it is inactive. An error is seen during install/upgrade that says
Job failed. See "journalctl -xe" for details.
This issue affects the following packages:
Lunar (0.8.8-1ubuntu2.1)
Jammy (0.8.8-1ubuntu1.22.04.2)
Focal (0.8.3-1ubuntu2.2)
- On upgrade
- On first install
Mantic (0.9.4-5ubuntu3)
- On first install
The issue is because of the order of the systemctl command and the systemd unit files.
multipathd.service has:
...
After=multipathd.socket
...
Also=multipathd.socket
multipath-tools.postinst has:
Jammy/Lunar/Focal (added by dh_systemd_start)
deb-systemd-invoke start 'multipathd.service' 'multipathd.socket' >/dev/null || true
Mantic (added by dh_installsystemd)
if [ -n "$2" ]; then
_dh_action=restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action 'multipathd.service' 'multipathd.socket' >/dev/null || true
In other words,
systemctl stop multipathd.service multipathd.socket
systemctl start multipathd.service multipathd.socket
will fail
systemctl stop multipathd.service multipathd.socket
systemctl start multipathd.socket multipathd.service
will succeed
If we try to start the socket after the service, we get a failure. This is by design so multiple processes of the socket are not active at once.
[Test Cases]
Due to the nature of this bug/fix, multiple test cases are defined here:
1. Install multipath-tools when it is uninstalled
2. Upgrade multipath-tools to this version
3. Downgrade multipath-tools to this version
4. Reinstall multipath-tools when it is this version
5.
systemctl stop multipathd.service multipathd.socket
systemctl start multipathd.service multipathd.socket
All test cases should result in _no errors_ and both multipathd.service multipathd.socket are active
[Reproducer]
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:03:16 UTC; 45s ago
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.service multipathd.socket
Job failed. See "journalctl -xe" for details.
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:07:58 UTC; 2s ago
--
○ multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: inactive (dead) since Wed 2023-09-13 14:07:42 UTC; 18s ago
Now if we start the socket and then the service, the socket no longer says it is inactive.
# systemctl stop multipathd.service multipathd.socket
# systemctl start multipathd.socket multipathd.service
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago
--
● multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 14:09:37 UTC; 3s ago |
This is an issue with the systemd service not stating the dependency on the socket, but stating a start order with the socket. The fix here is to add
Wants=multipathd.socket
in multipathd.service which is a weak dependency, so the chance of issues arising from it is low, but helps to solve this particular issue.
[Impact]
On Upgrade/Install, the multipathd.socket states that it is inactive. An error is seen during install/upgrade that says
Job failed. See "journalctl -xe" for details.
This issue affects the following packages:
Lunar (0.8.8-1ubuntu2.1)
Jammy (0.8.8-1ubuntu1.22.04.2)
Focal (0.8.3-1ubuntu2.2)
- On upgrade
- On first install
Mantic (0.9.4-5ubuntu3)
- On first install
The issue is because of the order of the systemctl command and the systemd unit files.
multipathd.service has:
...
After=multipathd.socket
...
Also=multipathd.socket
multipath-tools.postinst has:
Jammy/Lunar/Focal (added by dh_systemd_start)
deb-systemd-invoke start 'multipathd.service' 'multipathd.socket' >/dev/null || true
Mantic (added by dh_installsystemd)
if [ -n "$2" ]; then
_dh_action=restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action 'multipathd.service' 'multipathd.socket' >/dev/null || true
In other words,
systemctl stop multipathd.service multipathd.socket
systemctl start multipathd.service multipathd.socket
will fail
systemctl stop multipathd.service multipathd.socket
systemctl start multipathd.socket multipathd.service
will succeed
If we try to start the socket after the service, we get a failure. This is by design so multiple processes of the socket are not active at once.
[Test Cases]
Due to the nature of this bug/fix, multiple test cases are defined here:
1. Install multipath-tools when it is uninstalled
2. Upgrade multipath-tools to this version
3. Downgrade multipath-tools to this version
4. Reinstall multipath-tools when it is this version
5.
systemctl stop multipathd.service multipathd.socket
systemctl start multipathd.service multipathd.socket
All test cases should result in _no errors_ and both multipathd.service multipathd.socket are active
[Reproducer]
$ lxc launch ubuntu-daily:mantic m --vm
$ lxc shell m
# apt purge -y multipath-tools
# apt update -y
# apt install -y multipath-tools
# systemctl status multipathd.service multipathd.socket | grep Active -B2
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-13 19:30:56 UTC; 47s ago
--
○ multipathd.socket - multipathd control socket
Loaded: loaded (/lib/systemd/system/multipathd.socket; enabled; preset: enabled)
Active: inactive (dead) |
|
| 2023-09-15 14:35:31 |
Mitchell Dzurick |
tags |
|
ubuntu-server |
|
| 2023-09-15 14:36:24 |
Mitchell Dzurick |
tags |
ubuntu-server |
server-todo |
|
| 2023-09-18 15:00:44 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~mitchdz/ubuntu/+source/multipath-tools/+git/multipath-tools/+merge/451558 |
|
| 2023-10-06 18:51:55 |
Andreas Hasenack |
nominated for series |
|
Ubuntu Jammy |
|
| 2023-10-06 18:51:55 |
Andreas Hasenack |
bug task added |
|
multipath-tools (Ubuntu Jammy) |
|
| 2023-10-06 18:51:55 |
Andreas Hasenack |
nominated for series |
|
Ubuntu Mantic |
|
| 2023-10-06 18:51:55 |
Andreas Hasenack |
bug task added |
|
multipath-tools (Ubuntu Mantic) |
|
| 2023-10-06 18:51:55 |
Andreas Hasenack |
nominated for series |
|
Ubuntu Lunar |
|
| 2023-10-06 18:51:55 |
Andreas Hasenack |
bug task added |
|
multipath-tools (Ubuntu Lunar) |
|
