On 12/19/23 21:31, Robert McBroom via users wrote:
On 12/19/23 01:53, Samuel Sieb wrote:
This is the problem you need to resolve.
I don't know why. You'll need to find out why the dbus broker can't
run. I would have expected more details in the log.
--
I'm not sure what to look for in the journal. Does this section show the
problem? Sequence repeats several times
Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: *** Warning
-- SELinux targeted policy relabel is required.
Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: ***
Relabeling could take a very long time, depending on file
Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: *** system
size and speed of hard drives.
Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: Running:
/sbin/fixfiles -T 0 restore
Dec 18 09:27:08 dv7t.attlocal.net dbus-broker-launch[866]: Looking up
NSS user entry for 'systemd-oom'...
Dec 18 09:27:08 dv7t.attlocal.net dbus-broker-launch[866]: NSS returned
no entry for 'systemd-oom'
Dec 18 09:27:08 dv7t.attlocal.net dbus-broker-launch[866]: Invalid
user-name in /usr/share/dbus-1/system.d/org.freedesktop.oom1.conf +9:
user="systemd-oom"
Dec 18 09:27:11 dv7t.attlocal.net systemd[1]: Started
dbus-broker.service - D-Bus System Message Bus.
Dec 18 09:27:11 dv7t.attlocal.net audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=dbus-broker comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
Dec 18 09:27:11 dv7t.attlocal.net kernel: kauditd_printk_skb: 15
callbacks suppressed
Dec 18 09:27:11 dv7t.attlocal.net kernel: audit: type=1130
audit(1702909631.147:131): pid=1 uid=0 auid=4294967295 ses=4294967295
subj=system_u:system_r:init_t:s0 msg='unit=dbus-broker comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[1191]: ERROR
launcher_run_child @ ../src/launch/launcher.c +347: Permission denied
Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: ERROR
service_add @ ../src/launch/service.c +1011: Transport endpoint is not
connected
What have you done to your system?
For some reason it's doing a relabel. It should be done, you can try
rebooting and see if things go better. But things look quite broken.
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
