I was working without problem on the host throught cockpit I disabled firewalld few seconds to test a sftp that should run but not I reboot the host and then I was unable to connect throught cockpit. I have an another host same os same update which is working fine. Reproducible: Always OS: 6.4.12-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Aug 23 17:46:49 UTC 2023 x86_64 GNU/Linux systemctl status dbus-broker × dbus-broker.service - D-Bus System Message Bus Loaded: loaded (/usr/lib/systemd/system/dbus-broker.service; enabled; preset: enabled) Drop-In: /usr/lib/systemd/system/service.d └─10-timeout-abort.conf Active: failed (Result: exit-code) since Mon 2023-09-04 10:50:41 CEST; 55s ago Duration: 6ms TriggeredBy: × dbus.socket Docs: man:dbus-broker-launch(1) Process: 3389 ExecStart=/usr/bin/dbus-broker-launch --scope system --audit (code=exited, status=1/FAILURE) Main PID: 3389 (code=exited, status=1/FAILURE) CPU: 49ms dbus-broker-launch[3389]: launcher_add_services @ ../src/launch/launcher.c +804 dbus-broker-launch[3389]: launcher_run @ ../src/launch/launcher.c +1415 dbus-broker-launch[3389]: run @ ../src/launch/main.c +152 dbus-broker-launch[3389]: main @ ../src/launch/main.c +178 dbus-broker-launch[3389]: Exiting due to fatal error: -107 systemd[1]: dbus-broker.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: dbus-broker.service: Failed with result 'exit-code'. systemd[1]: dbus-broker.service: Start request repeated too quickly. systemd[1]: dbus-broker.service: Failed with result 'exit-code'. systemd[1]: Failed to start dbus-broker.service - D-Bus System Message Bus. journalctl -eu dbus-broker systemd[1]: Starting dbus-broker.service - D-Bus System Message Bus... dbus-broker-launch[1284]: Looking up NSS group entry for 'netdev'... dbus-broker-launch[1284]: NSS returned no entry for 'netdev' dbus-broker-launch[1284]: Invalid group-name in /usr/share/dbus-1/system.d/ead-dbus.conf +20: group="netdev" dbus-broker-launch[1284]: Invalid group-name in /usr/share/dbus-1/system.d/iwd-dbus.conf +21: group="netdev" systemd[1]: Started dbus-broker.service - D-Bus System Message Bus. dbus-broker-launch[1297]: ERROR launcher_run_child @ ../src/launch/launcher.c +325: Permission denied dbus-broker-launch[1284]: ERROR service_add @ ../src/launch/service.c +1011: Transport endpoint is not connected dbus-broker-launch[1284]: launcher_add_services @ ../src/launch/launcher.c +804 dbus-broker-launch[1284]: launcher_run @ ../src/launch/launcher.c +1415 dbus-broker-launch[1284]: run @ ../src/launch/main.c +152 dbus-broker-launch[1284]: main @ ../src/launch/main.c +178 dbus-broker-launch[1284]: Exiting due to fatal error: -107 systemd[1]: dbus-broker.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: dbus-broker.service: Failed with result 'exit-code'. I created the system group netdev the message "invalid group-name" disapeared but nothing else.
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
Your machine-id file has incorrect permissions and is not readable by `dbus-broker`. The `sd_id128_get_machine()` call in `dbus-broker` fails (also see `machine-id(5)`). This is not a supported system setup and thus causes `dbus-broker` to exit. Can you check which machine-id files exist on your system and fix the permissions accordingly?
I checked the status of dbus-broker. It is running. I made an OS update. Now kernel is 6.5.10-200.fc38.x86_64 instead of 6.4.12-200.fc38.x86_64 permissions file are -r--r--r--. 1 root root 33 Oct 28 2022 /etc/machine-id
Right, so everything is working correctly? In that case, I will close the report. Thanks!
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.