Hi Neale, are you also able to reproduce this problem on RHEL-8.3? If yes, could you please report it via https://bugzilla.redhat.com against anaconda for further review? Please, attach log files from /tmp (you can ssh as root to the installation environment). Such problems (Anaconda DBus modules failed to start on time) usually happen on very slow systems.
Regards, Jan On Tue, Dec 22, 2020 at 5:12 AM Neale Ferguson <ne...@sinenomine.net> wrote: > When installing RHEL8 on my z/VM 7.1 system I get to the part where I am > asked to ssh inst...@xx.xx.xx.xx<mailto:inst...@xx.xx.xx.xx> where it > then hangs before > > > > anaconda 29.19.2.17-1.el8 for Red Hat Enterprise Linux 8.2 started. > > * installation log files are stored in /tmp during the installation > > * shell is available in second TMUX pane (ctrl+b, then press 2) > > * when reporting a bug add logs from /tmp as separate text/plain > attachments > > > > After several minutes the next message appears: > > > > 04:05:19 Anaconda DBus modules failed to start on time. > > > > Syslog shows that during this time… > > > > 04:05:29,355 INFO systemd:anaconda-shell@hvc1.service: Service has no > hold-off time (RestartSec=0), scheduling restart. > > 04:05:29,365 INFO systemd:anaconda-shell@hvc1.service: Scheduled restart > job, restart counter is at 90. > > 04:05:29,381 INFO systemd:Stopped Shell on hvc1. > > 04:05:29,424 INFO systemd:Started Shell on hvc1. > > 04:05:31,889 INFO dbus-daemon:Reloaded configuration > > 04:05:39,620 NOTICE kernel:audit: type=1131 audit(1608609939.607:315): > pid=1 uid=0 auid=4294967295 ses=4294967295 > subj=system_u:system_r:kernel_t:s0 msg='unit=anaconda-shell@hvc1 > comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? > res=success' > > 04:05:39,644 INFO systemd:anaconda-shell@hvc1.service: Service has no > hold-off time (RestartSec=0), scheduling restart. > > 04:05:39,657 INFO systemd:anaconda-shell@hvc1.service: Scheduled restart > job, restart counter is at 91. > > 04:05:39,677 INFO systemd:Stopped Shell on hvc1. > > 04:05:39,680 NOTICE kernel:audit: type=1130 audit(1608609939.667:316): > pid=1 uid=0 auid=4294967295 ses=4294967295 > subj=system_u:system_r:kernel_t:s0 msg='unit=anaconda-shell@hvc1 > comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? > res=success' > > 04:05:39,681 NOTICE kernel:audit: type=1131 audit(1608609939.667:317): > pid=1 uid=0 auid=4294967295 ses=4294967295 > subj=system_u:system_r:kernel_t:s0 msg='unit=anaconda-shell@hvc1 > comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? > res=success' > > 04:05:39,732 INFO systemd:Started Shell on hvc1. > > : > > : > > > > I am not sure what it’s complaining about or expecting. > > > > Neale > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www2.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
