-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dbus-broker-launch[9179]: ERROR listener_dispatch @ ../src/bus/listener.c +42: Bad file descriptor #330
Comments
What version of dbus-broker are you running? |
[root@host ~]# dbus-broker --v [root@host ~]# dbus-broker-launch --version I saw the latest version is 35, how to properly update? |
Apparently |
No the system is round about 2 month 24/7 in use. I also had the same problem 2 month ago and then had to reinstall. Now it's time to find the cause. It happend out of nowhere. So do you recommend update kernel? |
How long had the old system been running, also around two months? Do you have any custom config of either systemd or dbus? |
Yes, it's about the same duration the server lasted. I just use DirectAdmin on it for Webhosting and Docker, with no custom configuration of the system itself. |
This is really strange, especially given that you are the only one hitting this so far. I really suspect that some other component is at fault here, but that is always easy to say. The thing is, the error indicates that the socket that is created by systemd and then passed in as D-Bus listener socket to I would expect this error to go away with a clean install of an up-to-date Fedora/Alma/..., but you are saying it does not, right? |
I'm having the same issue on Arch linux after upgrade, but only on my Cloud vserver. $ dbus-broker --v $ systemctl status dbus Jan 18 20:59:33 vs0101 systemd[1]: Starting D-Bus System Message Bus... $ journalctl --since 18:00 | grep Unexpected Jan 18 20:59:33 vs0101 systemd[1]: systemd-logind.service: Unexpected error response from GetNameOwner(): Connection terminated $ pacman -Qikk dbus-broker dbus-broker-units Name : dbus-broker dbus-broker: 18 total files, 0 altered files dbus-broker-units: 7 total files, 0 altered files |
@jstrausd @DimeOne I am trying to trace this down. On an affected machine, can you clone the Something like this: git clone https://github.com/bus1/dbus-broker.git
cd dbus-broker
make meson-setup
make meson-build
make meson-test
cd ./build/meson
./test/dbus/test-matches
strace -f ./test/dbus/test-matches (You might have to install |
Also experiencing this on an Arch VM running on Hetzner Cloud. I ran the tests above on the affected VM, here's output from both the test and strace: https://gist.github.com/rafaelwastaken/2582a88888330243a5ea25207ae5fe48 |
Thanks a lot for submitting the information! Unfortunately, I picked the wrong directory to run the test from (it runs
|
Sorry for the delayed response. Re-ran the new commands, output here: https://gist.github.com/rafaelwastaken/7d1e097aa56e15a8632c0e05957378a9 |
Thanks a lot for the trace! I think the relevant piece is this:
If we sanitize this, it becomes: accept4(8, NULL, NULL, SOCK_CLOEXEC|SOCK_NONBLOCK) = -1 EAGAIN (Resource temporarily unavailable)
getsockopt(-1, SOL_SOCKET, SO_TYPE, 0x7ffda8d59b70, [4]) = -1 EBADF (Bad file descriptor)
write(2, "ERROR listener_dispatch @ ../../"..., 76) = 76 I have no clue where this A few followup questions:
|
There is a lot of suspicious activity in that strace. There is access on Can you look into |
Hello, since a few days my server with AlmaLinux 9 randomly started making problems. After a reboot NetworkManager and systemd-login and d-bus can't start or logged some errors.
Dec 20 11:25:59 host systemd[1]: Starting D-Bus System Message Bus...
Dec 20 11:25:59 host systemd[1]: Started D-Bus System Message Bus.
Dec 20 11:25:59 host dbus-broker-launch[9179]: ERROR listener_dispatch @ ../src/bus/listener.c +42: Bad file descriptor
Dec 20 11:25:59 host dbus-broker-launch[9179]: dispatch_context_dispatch @ ../src/util/dispatch.c +344
Dec 20 11:25:59 host dbus-broker-launch[9179]: broker_run @ ../src/broker/broker.c +225
Dec 20 11:25:59 host dbus-broker-launch[9179]: run @ ../src/broker/main.c +261
Dec 20 11:25:59 host dbus-broker-launch[9179]: main @ ../src/broker/main.c +295
Dec 20 11:25:59 host dbus-broker-lau[9178]: Ready
Dec 20 11:25:59 host dbus-broker[9179]: Dispatched 0 messages @ 0(±0)μs / message.
Dec 20 11:25:59 host systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated
Dec 20 11:25:59 host systemd[1]: polkit.service: Unexpected error response from GetNameOwner(): Connection terminated
Dec 20 11:25:59 host systemd[1]: tuned.service: Unexpected error response from GetNameOwner(): Connection terminated
Dec 20 11:25:59 host dbus-broker-launch[9178]: Caught SIGCHLD of broker.
Is there any way to fix my problem with dbus/dbus-broker?
I tried several things I found online, but nothing seemed to help...
The text was updated successfully, but these errors were encountered: