[opensuse] dbus-daemon 100% CPU. Constant disk access.
I have suddenly started to see very strange things in my openSuse 10.1 installation on my laptop. I was up to date with updates/patches, until about a month ago, but have done no updates lately, and the only new software I installed is the Novell linux client. First problem I have is that there is a process called dbus-daemon that is taking up 100% CPU, all the time. I don't know what this process is, or if I could kill it safely, and why is it doing what it is doing. When I do kill this process, CPU time is freed, but some process is writing/reading from the hard disk constantly (i.e. the hard disk light is constantly on). How can I find out which process is accessing the hard disk? Thanks Marius Roets -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Am Mittwoch, 6. Dezember 2006 08:59 schrieb Marius Roets:
I have suddenly started to see very strange things in my openSuse 10.1 installation on my laptop. I was up to date with updates/patches, until about a month ago, but have done no updates lately, and the only new software I installed is the Novell linux client.
First problem I have is that there is a process called dbus-daemon that is taking up 100% CPU, all the time. I don't know what this process is, or if I could kill it safely, and why is it doing what it is doing.
When I do kill this process, CPU time is freed, but some process is writing/reading from the hard disk constantly (i.e. the hard disk light is constantly on). How can I find out which process is accessing the hard disk?
Thanks Marius Roets
Not long ago i had some strange issues just because my harddrive (the root partition) was completly full. Please check youre drive with KDiskFree (Alt+F2 kdf), or with df -h on a console. Greets Michael -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi Marius, On Wed, 2006-12-06 at 09:59 +0200, Marius Roets wrote:
I have suddenly started to see very strange things in my openSuse 10.1 installation on my laptop. I was up to date with updates/patches, until about a month ago, but have done no updates lately, and the only new software I installed is the Novell linux client.
First problem I have is that there is a process called dbus-daemon that is taking up 100% CPU, all the time. I don't know what this process is, or if I could kill it safely, and why is it doing what it is doing.
Can you please check whether it was the D-Bus system bus or the D-Bus session bus? When you run `ps axu | grep dbus-daemon` you should get something like this: thoenig@nouse:~> ps axu |grep dbus-daemon 100 3122 0.0 0.2 5160 2636 ? Ss Dec05 0:33 /usr/bin/dbus-daemon --system thoenig 5050 0.0 0.0 3772 872 ? Ss Dec05 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session Then run `top` to identify which of the processes is the CPU hog. This all sounds very scary and I've never seen it before. It might be that an application misbehaves and causes a lot of traffic on the D-Bus daemon process. This in return may cause the D-Bus daemon to suck all of the CPU cycles. In any way, please file a bug against SUSE Linux 10.1 on [1] in order to solve this issue. Thanks, Timo [1] Novell Bugzilla https://bugzilla.novell.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 12/6/06, Timo Hoenig <thoenig@suse.de> wrote:
Hi Marius,
On Wed, 2006-12-06 at 09:59 +0200, Marius Roets wrote:
I have suddenly started to see very strange things in my openSuse 10.1 installation on my laptop. I was up to date with updates/patches, until about a month ago, but have done no updates lately, and the only new software I installed is the Novell linux client.
First problem I have is that there is a process called dbus-daemon that is taking up 100% CPU, all the time. I don't know what this process is, or if I could kill it safely, and why is it doing what it is doing.
Can you please check whether it was the D-Bus system bus or the D-Bus session bus? When you run `ps axu | grep dbus-daemon` you should get something like this:
thoenig@nouse:~> ps axu |grep dbus-daemon 100 3122 0.0 0.2 5160 2636 ? Ss Dec05 0:33 /usr/bin/dbus-daemon --system thoenig 5050 0.0 0.0 3772 872 ? Ss Dec05 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
Then run `top` to identify which of the processes is the CPU hog.
This all sounds very scary and I've never seen it before. It might be that an application misbehaves and causes a lot of traffic on the D-Bus daemon process. This in return may cause the D-Bus daemon to suck all of the CPU cycles.
In any way, please file a bug against SUSE Linux 10.1 on [1] in order to solve this issue.
Thanks,
Timo
[1] Novell Bugzilla https://bugzilla.novell.com/
Hi Timo, Thanks for the reply. Here is the output of the commands you mentioned. :~> ps axu |grep dbus-daemon 100 2517 0.0 0.0 3396 988 ? Ss 09:33 0:00 /usr/bin/dbus-daemon --system mroets 4513 99.0 0.0 3288 572 ? Rs 09:34 148:11 dbus-daemon --fork --print-pid 7 --print-address 5 --session :~> top top - 12:02:35 up 2:30, 6 users, load average: 2.36, 2.39, 2.24 Tasks: 128 total, 2 running, 126 sleeping, 0 stopped, 0 zombie Cpu(s): 11.5% us, 41.1% sy, 0.0% ni, 43.1% id, 3.8% wa, 0.2% hi, 0.3% si Mem: 1033840k total, 1004916k used, 28924k free, 266376k buffers Swap: 1052248k total, 52k used, 1052196k free, 265556k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 4513 mroets 25 0 3288 572 440 R 100 0.1 146:51.06 dbus-daemon 4802 mroets 15 0 171m 70m 25m S 5 7.0 2:07.68 firefox-bin 2479 root 18 0 1892 812 576 D 1 0.1 1:11.21 syslog-ng 4508 mroets 15 0 4392 956 660 S 0 0.1 0:16.41 ssh-agent 1 root 16 0 720 280 244 S 0 0.0 0:01.35 init It definitely seems to be the "session bus", though I'm not sure what this means, since I don't know what dbus is :) I will file the bug. Thanks Marius -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2006-12-06 at 12:03 +0200, Marius Roets wrote (shortened):
It definitely seems to be the "session bus", though I'm not sure what this means, since I don't know what dbus is :)
Yes, it is the session bus. That's actually good news ;-)
I will file the bug.
Thanks for that. Please assign the bug directly to me and I will give further instructions. Thank you, Timo -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Marius Roets -
Michael Schueller -
Timo Hoenig