[systemd-devel] Help! iSCSI based file systems with "_netdev" causing ordering cycles to occur (random services and mounts fail)

Tony Rodriguez unixpro1970 at gmail.com
Sat Oct 28 03:46:15 UTC 2023


On 10/27/23 07:06, Lennart Poettering wrote:
> On Do, 26.10.23 19:03, Tony Rodriguez (unixpro1970 at gmail.com) wrote:
>
>> Experiencing this same issue with iSCSI and systemd-239 for RH8/Rocky8 and
>> RH9/Rocky9 system-252. Nothing was done on my end to create this issue.  In
>> other words, no custom mount/unit files or services, just your typical ISO
>> install and rpm updates.
>>
>> An ordering cycle occurs, when "_netdev" is specified within /etc/fstab for
>> systemd.  This happens with systemd-239-14 and systemd-239-18 using iSCSI
>> based file systems.    Seems others are experiencing this as well (see link
>> below).  I can also confirm this happens with systemd-252 (RH9/Rocky9)l.
>> Especially if "_netdev" is used with either "/var" or "/usr" iSCSI based
>> devices/file systems.  The system may not boot, may not mount file systems,
>> may not start services/unit files, and the system becomes slow during system
>> boot.
>>
>> Does anyone know of a fix/patch and root cause for this?
>>
>> Please see this link:
>> https://issues.redhat.com/browse/RHEL-12987?jql=project%20%3D%20RHEL%20AND%20affectedVersion%20%3D%20rhel-9.2.0%20AND%20text%20~%20%22iscsi%22
>>
>> # cat /etc/fstab
>> [...]
>> /dev/mapper/rhel-root /                       xfs defaults,_netdev 0 0
>> UUID=2177a7fc-bc41-43e4-bdc1-d231a5eb4680 /boot xfs defaults,_netdev 0 0
>> /dev/mapper/rhel-tmp /tmp                    xfs defaults,_netdev 0 0
>> /dev/mapper/rhel-var /var                    xfs
>> defaults,_netdev,x-initrd.mount 0 0
>> /dev/mapper/rhel-var_log /var/log                xfs defaults,_netdev 0 0
>> /dev/mapper/rhel-var_tmp /var/tmp                xfs defaults,_netdev 0 0
>>
>> # journalctl -b | grep deleted
>> Oct 13 08:15:35 vm-isci8 systemd[1]: basic.target: Job tmp.mount/start
>> deleted to break ordering cycle starting with basic.target/start
>> Oct 13 08:15:35 vm-isci8 systemd[1]: network.target: Job
>> network-pre.target/start deleted to break ordering cycle starting with
>> network.target/start
>> Oct 13 08:15:35 vm-isci8 systemd[1]: NetworkManager.service: Job
>> dbus.socket/start deleted to break ordering cycle starting with
>> NetworkManager.service/start
> /tmp must be available during early boot already, and your
> NetworkManager service is apparently a late boot service. Hence you
> have a cycle: you want that /tmp/ is mounted after the network, but
> your network is configured really late. But /tmp is necessary during
> early boot. BOOM!
>
> Two ways out:
>
> 1. Don't make /tmp an iscsi mount. Bad idea anyway. Just use tmpfs for
>     it, like everyone else.
>
> 2. Upgrade to a better network management solution that has no
>     problems with running in early boot, for example systemd-networkd.
>
> Lennart
>
> --
> Lennart Poettering, Berlin

Thank you Lennart and Andrei,

Andrea asked for more details so I have provide this verbose output.

1) Lennart's recommendation of removing "/tmp" within /etc/fstab and 
using tmpfs for "/tmp" appears to stop the dependency issue for 
systemd-239 for systemd-252.  However, RH8 and RH9 don't support 
systemd-networkd, I am wondering how this can be overcome if removing 
"/tmp" and using "tmpfs" aren't options?  Would I have to modify various 
services and targets? What would I need to add or remove within services 
and targets to avoid these dependencies?

2) On another note, with RH9 systemd-252-14/systemd-252-18 and iscsi, 
new dependency issues occur if "_netdev" within /etc/fstab is specified 
for "/var" or "/usr".  My system will not reach a graphical state and 
will take a very long time to boot. The dbus related error is also 
strange as well.  Have to ssh into the system, since the GUI doesn't 
start, and manually "init 5" to make things work.  Only way I can boot, 
(without any issues), is by omitting "_netdev" for "/tmp", "/usr", and 
"/var".   This doesn't make sense because "_netdev" is the recommended 
way of telling systemd to treat file systems as remote-fs targets. RH9 
dependency errors are listed below:

/etc/fstab
UID=d21b12c1-0d2b-435d-bdf9-fb327a484539 /boot xfs     defaults        0 0
UUID=C1FC-48AC          /boot/efi               vfat 
umask=0077,shortname=winnt 0 2

/dev/mapper/rh9--iscsi4--mp-root          / xfs       defaults,_netdev 0 0
/dev/mapper/rh9--iscsi4--mp-home      /home           xfs 
defaults,_netdev 0 0
#/dev/mapper/rh9--iscsi4--mp-tmp       /tmp xfs        defaults,_netdev 0 0
/dev/mapper/rh9--iscsi4--mp-var           /var xfs       
defaults,_netdev,x-initrd.mount 0 0
/dev/mapper/rh9--iscsi4--mp-usr          /usr xfs       defaults,_netdev 
0  0
/dev/mapper/rh9--iscsi4--mp-swap       none              swap 
defaults        0 0

---------------------------
/var/log/messages (short -- longer one is listed below)
------------------------------
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Dependency failed for Power 
Profiles daemon.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: power-profiles-daemon.service: 
Job power-profiles-daemon.service/start failed with result 'dependency'.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Dependency failed for 
firewalld - dynamic firewall daemon.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: firewalld.service: Job 
firewalld.service/start failed with result 'dependency'.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Dependency failed for GNOME 
Display Manager.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: gdm.service: Job 
gdm.service/start failed with result 'dependency'.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: gdm.service: Triggering 
OnFailure= dependencies.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Dependency failed for Network 
Manager.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Dependency failed for Network 
Manager Wait Online.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: 
NetworkManager-wait-online.service: Job 
NetworkManager-wait-online.service/start failed with result 'dependency'.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: NetworkManager.service: Job 
NetworkManager.service/start failed with result 'dependency'.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Dependency failed for User 
Login Management.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: systemd-logind.service: Job 
systemd-logind.service/start failed with result 'dependency'.

systemctl status power-profiles-daemon.service
○ power-profiles-daemon.service - Power Profiles daemon
      Loaded: loaded 
(/usr/lib/systemd/system/power-profiles-daemon.service; enabled; preset: 
enabled)
      Active: inactive (dead) (Result: exit-code) since Fri 2023-10-27 
20:00:24 PDT; 3min 53s ago
     Process: 1749 ExecStart=/usr/libexec/power-profiles-daemon 
(code=exited, status=1/FAILURE)
    Main PID: 1749 (code=exited, status=1/FAILURE)
         CPU: 59ms

Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: power-profiles-daemon.service: 
Scheduled restart job, restart counter is at 5.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Stopped Power Profiles daemon.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Dependency failed for Power 
Profiles daemon.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: power-profiles-daemon.service: 
Job power-profiles-daemon.service/start failed with res>

systemctl status firewalld
○ firewalld.service - firewalld - dynamic firewall daemon
      Loaded: loaded (/usr/lib/systemd/system/firewalld.service; 
enabled; preset: enabled)
      Active: inactive (dead) since Fri 2023-10-27 20:00:24 PDT; 5min ago
        Docs: man:firewalld(1)
     Process: 1716 ExecStart=/usr/sbin/firewalld --nofork --nopid 
$FIREWALLD_ARGS (code=exited, status=0/SUCCESS)
    Main PID: 1716 (code=exited, status=0/SUCCESS)
         CPU: 481ms

Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Starting firewalld - dynamic 
firewall daemon...
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Dependency failed for 
firewalld - dynamic firewall daemon.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: firewalld.service: Job 
firewalld.service/start failed with result 'dependency'.
** Oct 27 20:00:24 rh9-iscsi4-mp firewalld[1716]: ERROR: Exception 
DBusException: org.freedesktop.DBus.Error.NoServer: Failed to connect to 
socket /ru>
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: firewalld.service: Deactivated 
successfully.

systemctl status gdm.service
○ gdm.service - GNOME Display Manager
      Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; 
preset: enabled)
      Active: inactive (dead)

Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Dependency failed for GNOME 
Display Manager.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: gdm.service: Job 
gdm.service/start failed with result 'dependency'.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: gdm.service: Triggering 
OnFailure= dependencies.

systemctl status NetworkManager-wait-online.service
○ NetworkManager-wait-online.service - Network Manager Wait Online
      Loaded: loaded 
(/usr/lib/systemd/system/NetworkManager-wait-online.service; enabled; 
preset: disabled)
      Active: inactive (dead)
        Docs: man:nm-online(1)

Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Dependency failed for Network 
Manager Wait Online.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: 
NetworkManager-wait-online.service: Job 
NetworkManager-wait-online.service/start failed with result 'dep

systemctl status NetworkManager.service
○ NetworkManager.service - Network Manager
      Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; 
enabled; preset: enabled)
      Active: inactive (dead)
        Docs: man:NetworkManager(8)

Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Dependency failed for Network 
Manager.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: NetworkManager.service: Job 
NetworkManager.service/start failed with result 'dependency'.

systemctl status systemd-logind.service
● systemd-logind.service - User Login Management
      Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; 
static)
     Drop-In: /usr/lib/systemd/system/systemd-logind.service.d
              └─10-grub2-logind-service.conf
      Active: active (running) since Fri 2023-10-27 20:01:54 PDT; 9min ago
        Docs: man:sd-login(3)
              man:systemd-logind.service(8)
              man:logind.conf(5)
              man:org.freedesktop.login1(5)
    Main PID: 6849 (systemd-logind)
      Status: "Processing requests..."
       Tasks: 1 (limit: 47287)
      Memory: 2.6M
         CPU: 94ms
      CGroup: /system.slice/systemd-logind.service
              └─6849 /usr/lib/systemd/systemd-logind


Oct 27 20:01:54 rh9-iscsi4-mp systemd[1]: Starting User Login Management...
Oct 27 20:01:54 rh9-iscsi4-mp systemd-logind[6849]: New seat seat0.
Oct 27 20:01:54 rh9-iscsi4-mp systemd-logind[6849]: Watching system 
buttons on /dev/input/event0 (Power Button)


Oct 27 20:00:23 rh9-iscsi4-mp avahi-daemon[1640]: Found user 'avahi' 
(UID 70) and group 'avahi' (GID 70).
Oct 27 20:00:24 rh9-iscsi4-mp iscsiadm[1755]: iscsiadm: No records found
Oct 27 20:00:24 rh9-iscsi4-mp firewalld[1716]: ERROR: Exception 
DBusException: org.freedesktop.DBus.Error.NoServer: Failed to connect to 
socket /run/dbus/system_bus_socket: Connection
  refused
Oct 27 20:00:27 rh9-iscsi4-mp dracut[2212]: dracut module 
'systemd-networkd' will not be installed, because command 'networkctl' 
could not be found!
Oct 27 20:00:27 rh9-iscsi4-mp dracut[2212]: dracut module 
'systemd-networkd' will not be installed, because command 
'/usr/lib/systemd/systemd-networkd' could not be found!
Oct 27 20:00:27 rh9-iscsi4-mp dracut[2212]: dracut module 
'systemd-networkd' will not be installed, because command 
'/usr/lib/systemd/systemd-networkd-wait-online' could not be found!
Oct 27 20:00:27 rh9-iscsi4-mp dracut[2212]: dracut module 
'systemd-resolved' will not be installed, because command 'resolvectl' 
could not be found!
Oct 27 20:00:28 rh9-iscsi4-mp dracut[2212]: dracut module 
'systemd-resolved' will not be installed, because command 
'/usr/lib/systemd/systemd-resolved' could not be found!
Oct 27 20:00:28 rh9-iscsi4-mp dracut[2212]: dracut module 
'systemd-timesyncd' will not be installed, because command 
'/usr/lib/systemd/systemd-timesyncd' could not be found!
Oct 27 20:00:28 rh9-iscsi4-mp dracut[2212]: dracut module 
'systemd-timesyncd' will not be installed, because command 
'/usr/lib/systemd/systemd-time-wait-sync' could not be found!
Oct 27 20:00:28 rh9-iscsi4-mp dracut[2212]: dracut module 'modsign' will 
not be installed, because command 'keyctl' could not be found!
Oct 27 20:00:28 rh9-iscsi4-mp dracut[2212]: dracut module 'busybox' will 
not be installed, because command 'busybox' could not be found!
Oct 27 20:00:28 rh9-iscsi4-mp dracut[2212]: dracut module 'rngd' will 
not be installed, because command 'rngd' could not be found!
Oct 27 20:00:28 rh9-iscsi4-mp dracut[2212]: dracut module 'connman' will 
not be installed, because command 'connmand' could not be found!
Oct 27 20:00:28 rh9-iscsi4-mp dracut[2212]: dracut module 'connman' will 
not be installed, because command 'connmanctl' could not be found!
Oct 27 20:00:28 rh9-iscsi4-mp dracut[2212]: dracut module 'connman' will 
not be installed, because command 'connmand-wait-online' could not be found!
Oct 27 20:00:28 rh9-iscsi4-mp dracut[2212]: dracut module 
'network-legacy' will not be installed, because command 'dhclient' could 
not be found!
Oct 27 20:00:28 rh9-iscsi4-mp dracut[2212]: dracut module 
'network-wicked' will not be installed, because command 'wicked' could 
not be found!


Oct 27 20:01:54 rh9-iscsi4-mp systemd-logind[6849]: Watching system 
buttons on /dev/input/event1 (AT Translated Set 2 keyboard)
Oct 27 20:01:54 rh9-iscsi4-mp systemd[1]: Started User Login Management.

systemctl status dbus.service
● dbus-broker.service - D-Bus System Message Bus
      Loaded: loaded (/usr/lib/systemd/system/dbus-broker.service; 
enabled; preset: enabled)
      Active: active (running) since Fri 2023-10-27 20:01:54 PDT; 10min ago
TriggeredBy: ● dbus.socket
        Docs: man:dbus-broker-launch(1)
    Main PID: 6850 (dbus-broker-lau)
       Tasks: 2 (limit: 47287)
      Memory: 2.1M
         CPU: 83ms
      CGroup: /system.slice/dbus-broker.service
              ├─6850 /usr/bin/dbus-broker-launch --scope system --audit
              └─6851 dbus-broker --log 4 --controller 9 --machine-id 
4e8cf1330530419797c5d503ca1cd85d --max-bytes 536870912 --max-fds 4096 
--max-mat>

Oct 27 20:01:54 rh9-iscsi4-mp systemd[1]: Starting D-Bus System Message 
Bus...
Oct 27 20:01:54 rh9-iscsi4-mp systemd[1]: Started D-Bus System Message Bus.
Oct 27 20:01:54 rh9-iscsi4-mp dbus-broker-lau[6850]: Ready

----------------------------------------------------------------------------------------------
grep -iE "delete|found|error|depend|fail" /var/log/messages (long version )
----------------------------------------------------------------------------------------------

Oct 27 19:58:39 rh9-iscsi4-mp kernel: No NUMA configuration found
Oct 27 19:58:39 rh9-iscsi4-mp kernel: pnp: PnP ACPI: found 5 devices
Oct 27 19:58:39 rh9-iscsi4-mp kernel: usb usb1: New USB device found, 
idVendor=1d6b, idProduct=0002, bcdDevice= 5.15
Oct 27 19:58:39 rh9-iscsi4-mp kernel: hub 1-0:1.0: USB hub found
Oct 27 19:58:39 rh9-iscsi4-mp kernel: usb usb2: New USB device found, 
idVendor=1d6b, idProduct=0003, bcdDevice= 5.15
Oct 27 19:58:39 rh9-iscsi4-mp kernel: hub 2-0:1.0: USB hub found
Oct 27 19:58:39 rh9-iscsi4-mp kernel: usb 1-1: New USB device found, 
idVendor=0627, idProduct=0001, bcdDevice= 0.00
Oct 27 19:58:39 rh9-iscsi4-mp kernel: ima: No TPM chip found, activating 
TPM-bypass!
Oct 27 19:58:39 rh9-iscsi4-mp kernel: ima: No architecture policies found
Oct 27 19:58:39 rh9-iscsi4-mp kernel: RAS: Correctable Errors collector 
initialized.
Oct 27 19:58:41 rh9-iscsi4-mp NetworkManager[464]: <warn> 
[1698461921.8466] ifcfg-rh: dbus: couldn't acquire D-Bus service: 
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Request
  to own name refused by policy
Oct 27 19:58:42 rh9-iscsi4-mp dracut-initqueue[683]: iscsiadm: Could not 
execute operation on all records: encountered iSCSI database failure
Oct 27 19:58:42 rh9-iscsi4-mp dracut-initqueue[684]: iscsiadm: Could not 
execute operation on all records: encountered iSCSI database failure
Oct 27 19:58:43 rh9-iscsi4-mp dracut-initqueue[806]: iscsiadm: Could not 
execute operation on all records: encountered iSCSI database failure
Oct 27 19:58:43 rh9-iscsi4-mp dracut-initqueue[807]: iscsiadm: Could not 
execute operation on all records: encountered iSCSI database failure
Oct 27 19:58:44 rh9-iscsi4-mp dracut-initqueue[912]: iscsiadm: Could not 
execute operation on all records: encountered iSCSI database failure
Oct 27 19:58:44 rh9-iscsi4-mp dracut-initqueue[913]: iscsiadm: Could not 
execute operation on all records: encountered iSCSI database failure
Oct 27 19:58:44 rh9-iscsi4-mp dracut-initqueue[1005]: iscsiadm: Could 
not execute operation on all records: encountered iSCSI database failure
Oct 27 19:58:44 rh9-iscsi4-mp dracut-initqueue[1006]: iscsiadm: Could 
not execute operation on all records: encountered iSCSI database failure
Oct 27 19:58:44 rh9-iscsi4-mp systemd[1]: Found device 
/dev/mapper/rh9--iscsi4--mp-root.
Oct 27 19:58:45 rh9-iscsi4-mp systemd[1]: Found device 
/dev/mapper/rh9--iscsi4--mp-swap.
Oct 27 20:00:19 rh9-iscsi4-mp systemd[1]: Failed to deserialized tracked 
clients, ignoring: Transport endpoint is not connected
Oct 27 20:00:20 rh9-iscsi4-mp kernel: iTCO_wdt iTCO_wdt.1.auto: Found a 
ICH9 TCO device (Version=2, TCOBASE=0x0660)
Oct 27 20:00:21 rh9-iscsi4-mp systemd[1]: dbus-broker.service: Main 
process exited, code=exited, status=1/FAILURE
Oct 27 20:00:21 rh9-iscsi4-mp systemd[1]: dbus-broker.service: Failed 
with result 'exit-code'.
Oct 27 20:00:21 rh9-iscsi4-mp systemd[1]: Failed to start D-Bus System 
Message Bus.
Oct 27 20:00:21 rh9-iscsi4-mp systemd[1]: dbus-broker.service: Main 
process exited, code=exited, status=1/FAILURE
Oct 27 20:00:21 rh9-iscsi4-mp systemd[1]: dbus-broker.service: Failed 
with result 'exit-code'.
Oct 27 20:00:21 rh9-iscsi4-mp systemd[1]: Failed to start D-Bus System 
Message Bus.
Oct 27 20:00:21 rh9-iscsi4-mp augenrules[1615]: failure 1
Oct 27 20:00:21 rh9-iscsi4-mp augenrules[1615]: failure 1
Oct 27 20:00:21 rh9-iscsi4-mp augenrules[1615]: failure 1
Oct 27 20:00:21 rh9-iscsi4-mp systemd[1]: dbus-broker.service: Main 
process exited, code=exited, status=1/FAILURE
Oct 27 20:00:21 rh9-iscsi4-mp systemd[1]: dbus-broker.service: Failed 
with result 'exit-code'.
Oct 27 20:00:21 rh9-iscsi4-mp systemd[1]: Failed to start D-Bus System 
Message Bus.

Oct 27 20:00:21 rh9-iscsi4-mp systemd[1]: dbus-broker.service: Main 
process exited, code=exited, status=1/FAILURE
Oct 27 20:00:21 rh9-iscsi4-mp systemd[1]: dbus-broker.service: Failed 
with result 'exit-code'.
Oct 27 20:00:21 rh9-iscsi4-mp systemd[1]: Failed to start D-Bus System 
Message Bus.
Oct 27 20:00:21 rh9-iscsi4-mp systemd[1]: dbus-broker.service: Main 
process exited, code=exited, status=1/FAILURE
Oct 27 20:00:21 rh9-iscsi4-mp systemd[1]: dbus-broker.service: Failed 
with result 'exit-code'.
Oct 27 20:00:21 rh9-iscsi4-mp systemd[1]: Failed to start D-Bus System 
Message Bus.
Oct 27 20:00:21 rh9-iscsi4-mp systemd[1]: dbus-broker.service: Failed 
with result 'exit-code'.
Oct 27 20:00:21 rh9-iscsi4-mp systemd[1]: Failed to start D-Bus System 
Message Bus.
Oct 27 20:00:21 rh9-iscsi4-mp systemd[1]: dbus.socket: Failed with 
result 'service-start-limit-hit'.
Oct 27 20:00:23 rh9-iscsi4-mp systemd[1]: Auto-connect to subsystems on 
FC-NVME devices found during boot was skipped because of an unmet 
condition check 
(ConditionPathExists=/sys/class/fc/fc_udev_device/nvme_discovery).

Oct 27 20:00:23 rh9-iscsi4-mp avahi-daemon[1640]: Found user 'avahi' 
(UID 70) and group 'avahi' (GID 70).
Oct 27 20:00:23 rh9-iscsi4-mp rtkit-daemon[1658]: Failed to connect to 
system bus: Failed to connect to socket /run/dbus/system_bus_socket: 
Connection refused
Oct 27 20:00:23 rh9-iscsi4-mp systemd[1]: power-profiles-daemon.service: 
Main process exited, code=exited, status=1/FAILURE
Oct 27 20:00:23 rh9-iscsi4-mp systemd[1]: power-profiles-daemon.service: 
Failed with result 'exit-code'.
Oct 27 20:00:23 rh9-iscsi4-mp systemd[1]: Failed to start Power Profiles 
daemon.
Oct 27 20:00:23 rh9-iscsi4-mp systemd[1]: rtkit-daemon.service: Main 
process exited, code=exited, status=1/FAILURE
Oct 27 20:00:23 rh9-iscsi4-mp systemd[1]: rtkit-daemon.service: Failed 
with result 'exit-code'.
Oct 27 20:00:23 rh9-iscsi4-mp systemd[1]: Failed to start RealtimeKit 
Scheduling Policy Service.
Oct 27 20:00:23 rh9-iscsi4-mp avahi-daemon[1640]: 
dbus_bus_get_private(): Failed to connect to socket 
/run/dbus/system_bus_socket: Connection refused
Oct 27 20:00:23 rh9-iscsi4-mp avahi-daemon[1640]: WARNING: Failed to 
contact D-Bus daemon.
Oct 27 20:00:23 rh9-iscsi4-mp systemd[1]: avahi-daemon.service: Failed 
with result 'exit-code'.
Oct 27 20:00:23 rh9-iscsi4-mp systemd[1]: Failed to start Avahi 
mDNS/DNS-SD Stack.
Oct 27 20:00:23 rh9-iscsi4-mp journal[1666]: Failed to connect to the 
system message bus
Oct 27 20:00:23 rh9-iscsi4-mp journal[1667]: 
g_dbus_proxy_get_connection: assertion 'G_IS_DBUS_PROXY (proxy)' failed
Oct 27 20:00:23 rh9-iscsi4-mp journal[1667]: 
g_dbus_connection_signal_subscribe: assertion 'G_IS_DBUS_CONNECTION 
(connection)' failed
Oct 27 20:00:23 rh9-iscsi4-mp journal[1667]: 
g_dbus_proxy_call_sync_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed
Oct 27 20:00:23 rh9-iscsi4-mp journal[1667]: 
g_dbus_proxy_get_connection: assertion 'G_IS_DBUS_PROXY (proxy)' failed
Oct 27 20:00:23 rh9-iscsi4-mp journal[1667]: 
g_dbus_connection_signal_unsubscribe: assertion 'G_IS_DBUS_CONNECTION 
(connection)' failed
Oct 27 20:00:23 rh9-iscsi4-mp systemd-logind[1665]: Failed to connect to 
system bus: Connection refused
Oct 27 20:00:23 rh9-iscsi4-mp systemd-logind[1665]: Failed to fully 
start up daemon: Connection refused
Oct 27 20:00:23 rh9-iscsi4-mp systemd[1]: systemd-logind.service: Main 
process exited, code=exited, status=1/FAILURE
Oct 27 20:00:23 rh9-iscsi4-mp systemd[1]: systemd-logind.service: Failed 
with result 'exit-code'.
Oct 27 20:00:23 rh9-iscsi4-mp systemd[1]: Failed to start User Login 
Management.
Oct 27 20:00:23 rh9-iscsi4-mp dbus-daemon[1642]: Failed to start message 
bus: No socket received.
Oct 27 20:00:23 rh9-iscsi4-mp systemd[1]: dbus-daemon.service: Main 
process exited, code=exited, status=1/FAILURE

Oct 27 20:00:23 rh9-iscsi4-mp systemd[1]: dbus-daemon.service: Failed 
with result 'exit-code'.
Oct 27 20:00:23 rh9-iscsi4-mp systemd[1]: dbus-broker.service: Failed 
with result 'exit-code'.
Oct 27 20:00:23 rh9-iscsi4-mp systemd[1]: Failed to start D-Bus System 
Message Bus.
Oct 27 20:00:23 rh9-iscsi4-mp systemd[1]: dbus.socket: Failed with 
result 'service-start-limit-hit'.
Oct 27 20:00:24 rh9-iscsi4-mp systemd-logind[1711]: Failed to connect to 
system bus: Connection refused
Oct 27 20:00:24 rh9-iscsi4-mp systemd-logind[1711]: Failed to fully 
start up daemon: Connection refused
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: systemd-logind.service: Main 
process exited, code=exited, status=1/FAILURE
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: systemd-logind.service: Failed 
with result 'exit-code'.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Failed to start User Login 
Management.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: power-profiles-daemon.service: 
Main process exited, code=exited, status=1/FAILURE
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: power-profiles-daemon.service: 
Failed with result 'exit-code'.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Failed to start Power Profiles 
daemon.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: dbus-broker.service: Failed 
with result 'exit-code'.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Failed to start D-Bus System 
Message Bus.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: dbus.socket: Failed with 
result 'service-start-limit-hit'.
Oct 27 20:00:24 rh9-iscsi4-mp systemd-logind[1725]: Failed to connect to 
system bus: Connection refused
Oct 27 20:00:24 rh9-iscsi4-mp systemd-logind[1725]: Failed to fully 
start up daemon: Connection refused
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: systemd-logind.service: Main 
process exited, code=exited, status=1/FAILURE
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: systemd-logind.service: Failed 
with result 'exit-code'.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Failed to start User Login 
Management.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: dbus-broker.service: Failed 
with result 'exit-code'.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Failed to start D-Bus System 
Message Bus.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: dbus.socket: Failed with 
result 'service-start-limit-hit'.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: power-profiles-daemon.service: 
Main process exited, code=exited, status=1/FAILURE
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: power-profiles-daemon.service: 
Failed with result 'exit-code'.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Failed to start Power Profiles 
daemon.
Oct 27 20:00:24 rh9-iscsi4-mp systemd-logind[1734]: Failed to connect to 
system bus: Connection refused
Oct 27 20:00:24 rh9-iscsi4-mp systemd-logind[1734]: Failed to fully 
start up daemon: Connection refused
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: systemd-logind.service: Main 
process exited, code=exited, status=1/FAILURE
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: systemd-logind.service: Failed 
with result 'exit-code'.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Failed to start User Login 
Management.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: dbus-broker.service: Failed 
with result 'exit-code'.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Failed to start D-Bus System 
Message Bus.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: dbus.socket: Failed with 
result 'service-start-limit-hit'.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: power-profiles-daemon.service: 
Main process exited, code=exited, status=1/FAILURE
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: power-profiles-daemon.service: 
Failed with result 'exit-code'.

Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Failed to start Power Profiles 
daemon.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: dbus-broker.service: Failed 
with result 'exit-code'.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Failed to start D-Bus System 
Message Bus.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: dbus.socket: Failed with 
result 'service-start-limit-hit'.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: power-profiles-daemon.service: 
Main process exited, code=exited, status=1/FAILURE
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: power-profiles-daemon.service: 
Failed with result 'exit-code'.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Failed to start Power Profiles 
daemon.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: dbus.socket: Failed with 
result 'service-start-limit-hit'.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Failed to listen on D-Bus 
System Message Bus Socket.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Dependency failed for Power 
Profiles daemon.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: power-profiles-daemon.service: 
Job power-profiles-daemon.service/start failed with result 'dependency'.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Dependency failed for 
firewalld - dynamic firewall daemon.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: firewalld.service: Job 
firewalld.service/start failed with result 'dependency'.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Dependency failed for GNOME 
Display Manager.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: gdm.service: Job 
gdm.service/start failed with result 'dependency'.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: gdm.service: Triggering 
OnFailure= dependencies.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Dependency failed for Network 
Manager.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Dependency failed for Network 
Manager Wait Online.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: 
NetworkManager-wait-online.service: Job 
NetworkManager-wait-online.service/start failed with result 'dependency'.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: NetworkManager.service: Job 
NetworkManager.service/start failed with result 'dependency'.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: Dependency failed for User 
Login Management.
Oct 27 20:00:24 rh9-iscsi4-mp systemd[1]: systemd-logind.service: Job 
systemd-logind.service/start failed with result 'dependency'.
Oct 27 20:00:24 rh9-iscsi4-mp iscsiadm[1755]: iscsiadm: No records found
Oct 27 20:00:24 rh9-iscsi4-mp firewalld[1716]: ERROR: Exception 
DBusException: org.freedesktop.DBus.Error.NoServer: Failed to connect to 
socket /run/dbus/system_bus_socket: Connection refused
Oct 27 20:00:27 rh9-iscsi4-mp dracut[2212]: dracut module 
'systemd-networkd' will not be installed, because command 'networkctl' 
could not be found!
Oct 27 20:00:27 rh9-iscsi4-mp dracut[2212]: dracut module 
'systemd-networkd' will not be installed, because command 
'/usr/lib/systemd/systemd-networkd' could not be found!
Oct 27 20:00:27 rh9-iscsi4-mp dracut[2212]: dracut module 
'systemd-networkd' will not be installed, because command 
'/usr/lib/systemd/systemd-networkd-wait-online' could not be found!
Oct 27 20:00:27 rh9-iscsi4-mp dracut[2212]: dracut module 
'systemd-resolved' will not be installed, because command 'resolvectl' 
could not be found!
Oct 27 20:00:28 rh9-iscsi4-mp dracut[2212]: dracut module 
'systemd-resolved' will not be installed, because command 
'/usr/lib/systemd/systemd-resolved' could not be found!
Oct 27 20:00:28 rh9-iscsi4-mp dracut[2212]: dracut module 
'systemd-timesyncd' will not be installed, because command 
'/usr/lib/systemd/systemd-timesyncd' could not be found!
Oct 27 20:00:28 rh9-iscsi4-mp dracut[2212]: dracut module 
'systemd-timesyncd' will not be installed, because command 
'/usr/lib/systemd/systemd-time-wait-sync' could not be found!
Oct 27 20:00:28 rh9-iscsi4-mp dracut[2212]: dracut module 'modsign' will 
not be installed, because command 'keyctl' could not be found!
Oct 27 20:00:28 rh9-iscsi4-mp dracut[2212]: dracut module 'busybox' will 
not be installed, because command 'busybox' could not be found!
Oct 27 20:00:28 rh9-iscsi4-mp dracut[2212]: dracut module 'rngd' will 
not be installed, because command 'rngd' could not be found!
Oct 27 20:00:28 rh9-iscsi4-mp dracut[2212]: dracut module 'connman' will 
not be installed, because command 'connmand' could not be found!

Oct 27 20:00:28 rh9-iscsi4-mp dracut[2212]: dracut module 'busybox' will 
not be installed, because command 'busybox' could not be found!
Oct 27 20:00:28 rh9-iscsi4-mp dracut[2212]: dracut module 'rngd' will 
not be installed, because command 'rngd' could not be found!
Oct 27 20:00:28 rh9-iscsi4-mp dracut[2212]: dracut module 'connman' will 
not be installed, because command 'connmand' could not be found!
Oct 27 20:00:28 rh9-iscsi4-mp dracut[2212]: dracut module 'connman' will 
not be installed, because command 'connmanctl' could not be found!
Oct 27 20:00:28 rh9-iscsi4-mp dracut[2212]: dracut module 'connman' will 
not be installed, because command 'connmand-wait-online' could not be found!
Oct 27 20:00:28 rh9-iscsi4-mp dracut[2212]: dracut module 
'network-legacy' will not be installed, because command 'dhclient' could 
not be found!
Oct 27 20:00:28 rh9-iscsi4-mp dracut[2212]: dracut module 
'network-wicked' will not be installed, because command 'wicked' could 
not be found!
Oct 27 20:00:28 rh9-iscsi4-mp dracut[2212]: dracut module 'dmraid' will 
not be installed, because command 'dmraid' could not be found!
Oct 27 20:00:28 rh9-iscsi4-mp dracut[2212]: dracut module 'pcsc' will 
not be installed, because command 'pcscd' could not be found!
Oct 27 20:00:28 rh9-iscsi4-mp dracut[2212]: dracut module 'cifs' will 
not be installed, because command 'mount.cifs' could not be found!
Oct 27 20:00:29 rh9-iscsi4-mp dracut[2212]: dracut module 'biosdevname' 
will not be installed, because command 'biosdevname' could not be found!
Oct 27 20:00:30 rh9-iscsi4-mp dracut[2212]: dracut module 'memstrack' 
will not be installed, because command 'memstrack' could not be found!
Oct 27 20:00:30 rh9-iscsi4-mp dracut[2212]: dracut module 
'systemd-resolved' will not be installed, because command 'resolvectl' 
could not be found!
Oct 27 20:00:30 rh9-iscsi4-mp dracut[2212]: dracut module 
'systemd-resolved' will not be installed, because command 
'/usr/lib/systemd/systemd-resolved' could not be found!
Oct 27 20:00:30 rh9-iscsi4-mp dracut[2212]: dracut module 
'systemd-timesyncd' will not be installed, because command 
'/usr/lib/systemd/systemd-timesyncd' could not be found!
Oct 27 20:00:30 rh9-iscsi4-mp dracut[2212]: dracut module 
'systemd-timesyncd' will not be installed, because command 
'/usr/lib/systemd/systemd-time-wait-sync' could not be found!
Oct 27 20:00:30 rh9-iscsi4-mp dracut[2212]: dracut module 'modsign' will 
not be installed, because command 'keyctl' could not be found!
Oct 27 20:00:30 rh9-iscsi4-mp dracut[2212]: dracut module 'busybox' will 
not be installed, because command 'busybox' could not be found!
Oct 27 20:00:30 rh9-iscsi4-mp dracut[2212]: dracut module 'rngd' will 
not be installed, because command 'rngd' could not be found!
Oct 27 20:00:30 rh9-iscsi4-mp dracut[2212]: dracut module 'connman' will 
not be installed, because command 'connmand' could not be found!
Oct 27 20:00:30 rh9-iscsi4-mp dracut[2212]: dracut module 'connman' will 
not be installed, because command 'connmanctl' could not be found!
Oct 27 20:00:30 rh9-iscsi4-mp dracut[2212]: dracut module 'connman' will 
not be installed, because command 'connmand-wait-online' could not be found!
Oct 27 20:00:30 rh9-iscsi4-mp dracut[2212]: dracut module 
'network-legacy' will not be installed, because command 'dhclient' could 
not be found!
Oct 27 20:00:30 rh9-iscsi4-mp dracut[2212]: dracut module 
'network-wicked' will not be installed, because command 'wicked' could 
not be found!
Oct 27 20:00:30 rh9-iscsi4-mp dracut[2212]: dracut module 'dmraid' will 
not be installed, because command 'dmraid' could not be found!
Oct 27 20:00:30 rh9-iscsi4-mp dracut[2212]: dracut module 'pcsc' will 
not be installed, because command 'pcscd' could not be found!
Oct 27 20:00:30 rh9-iscsi4-mp dracut[2212]: dracut module 'cifs' will 
not be installed, because command 'mount.cifs' could not be found!
Oct 27 20:00:31 rh9-iscsi4-mp dracut[2212]: dracut module 'memstrack' 
will not be installed, because command 'memstrack' could not be found!
Oct 27 20:00:40 rh9-iscsi4-mp dracut[2212]: Found iscsi component 
/sys/devices/platform/host6/session1
Oct 27 20:00:41 rh9-iscsi4-mp dracut[2212]: Found iscsi component 
/sys/devices/platform/host6/session1
Oct 27 20:00:41 rh9-iscsi4-mp kdumpctl[4977]: Error: Could not create 
NMClient object: Could not connect: Connection refused.
Oct 27 20:00:42 rk9-iscsi4-mp dracut[2212]: *** Installing kernel module 
dependencies ***
Oct 27 20:00:43 rh9-iscsi4-mp dracut[2212]: *** Installing kernel module 
dependencies done ***
Oct 27 20:00:43 rh9-iscsi4-mp dracut[2212]: *** Resolving executable 
dependencies ***
Oct 27 20:00:47 rh9-iscsi4-mp dracut[2212]: *** Resolving executable 
dependencies done ***
Oct 27 20:01:54 rh9-iscsi4-mp systemd[1]: systemd-logind.service: Failed 
with result 'timeout'.
















More information about the systemd-devel mailing list