[Bug 356971] New: beagled-helper consume 94% of cpu under havy load
https://bugzilla.novell.com/show_bug.cgi?id=356971 Summary: beagled-helper consume 94% of cpu under havy load Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Mono AssignedTo: bnc-team-mono@forge.provo.novell.com ReportedBy: pnemec@novell.com QAContact: qa@suse.de Found By: --- I run abuild application to build and rpm and I realise that my system is very irresponsible. I run top to obtain information and I realise that beagled-helper spin constantly about 90% of cpu. this is snip of top: top - 15:13:45 up 20 days, 23:38, 24 users, load average: 5.28, 3.76, 2.42 Tasks: 189 total, 4 running, 185 sleeping, 0 stopped, 0 zombie Cpu(s): 25.3%us, 3.5%sy, 47.8%ni, 0.0%id, 22.6%wa, 0.3%hi, 0.5%si, 0.0%st Mem: 2061376k total, 2052288k used, 9088k free, 133804k buffers Swap: 4225052k total, 207692k used, 4017360k free, 603600k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 19293 pavel 39 19 262m 35m 11m R 97 1.8 732:42.68 beagled-helper 12286 root 19 0 10232 8192 2048 R 52 0.4 0:05.08 rpm.bin beagled-helper should watch "load" walue and respect it. Search using kerry work normally. Spin took 5 minutes now and counting. Computer is x86_64 openSUSE 10.3. I do not index use any mounted nfs system. My fstab: /dev/disk/by-id/scsi-SATA_ST3160815AS_6RA01QN8-part1 / ext3 acl,user_xattr 1 1 /dev/disk/by-id/scsi-SATA_ST3160815AS_6RA01QN8-part5 /home ext3 defaults 1 2 /dev/disk/by-id/scsi-SATA_ST3160815AS_6RA01QN8-part8 swap swap defaults 0 0 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=356971 User pnemec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=356971#c1 Pavel Nemec <pnemec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gekker@novell.com Severity|Normal |Major --- Comment #1 from Pavel Nemec <pnemec@novell.com> 2008-06-30 03:18:31 MDT --- I successfully reproduced with openSUSE 11.0. beagled-helper occupy one my CPU core constantly at ~90 % I tried beagle-shutdown, but it do not close beagled-helper only line in log appear: 0080630 09:59:32.6995 02974 Beagle INFO: Starting Beagle Daemon (version 0.3.7) 20080630 09:59:32.7251 02974 Beagle INFO: Running on Mono 1.9.1 20080630 09:59:32.7255 02974 Beagle INFO: Command Line: /usr/lib64/beagle/BeagleDaemon.exe --replace --bg 20080630 09:59:43.3491 02974 Beagle ERROR EX: Failed to access dbus session bus. Battery monitoring will be disabled. 20080630 09:59:43.3491 02974 Beagle ERROR EX: System.Exception: Unable to open the session message bus. ---> System.ArgumentNullException: Argument cannot be null. 20080630 09:59:43.3491 02974 Beagle ERROR EX: Parameter name: address 20080630 09:59:43.3491 02974 Beagle ERROR EX: at NDesk.DBus.Bus.Open (System.String address) [0x00000] 20080630 09:59:43.3491 02974 Beagle ERROR EX: at NDesk.DBus.Bus.get_Session () [0x00000] --- End of inner exception stack trace --- 20080630 09:59:43.3491 02974 Beagle ERROR EX: 20080630 09:59:43.3491 02974 Beagle ERROR EX: at NDesk.DBus.Bus.get_Session () [0x00000] 20080630 09:59:43.3491 02974 Beagle ERROR EX: at NDesk.DBus.BusG.Init () [0x00000] 20080630 09:59:43.3491 02974 Beagle ERROR EX: at Beagle.Daemon.BatteryMonitor.Init () [0x00000] 20080630 10:01:40.8933 02974 Beagle ERROR: Indexing secure https:// URIs is not secure! 20080630 11:09:37.2572 02974 Beagle WARN: HandleAttribEvent failed: Couldn't find DirectoryModel for '/home/pavel/Desktop/ftp' 20080630 11:09:39.1390 02974 Beagle WARN: HandleAttribEvent failed: Couldn't find DirectoryModel for '/home/pavel/Desktop/tftpboot/boot/pxelinux.cfg' 20080630 11:15:26.7154 02974 Beagle INFO: Shutdown requested Rising severity. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=356971 User dbera.web@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=356971#c2 D Bera <dbera.web@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dbera.web@gmail.com --- Comment #2 from D Bera <dbera.web@gmail.com> 2008-07-06 06:17:02 MDT --- (In reply to comment #1 from Pavel Nemec)
I successfully reproduced with openSUSE 11.0.
All beagled-helper cpu load bugs are different, so if you can please provide a few information.
beagled-helper occupy one my CPU core constantly at ~90 %
I am assuming you meant 90% load for more than a few seconds ?
I tried beagle-shutdown, but it do not close beagled-helper only line in log appear:
The log file claimed that beagled-helper was shut down. You by any chance didnt have more than one instance of beagled and beagled-helper running - did you ? These bugs are usually hard to "reproduce". If you still have ~/.beagle/Log/current-IndexHelper could you attach it (it will be a symbolic link to some 2008-*-IndexHelper file). Thanks. If you encounter this anytime in the future, could you send SIGUSR1 and SIGUSR2 to beagled and attach the ~/.beagle/Log/current-* files immediately after that ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=356971 User dbera.web@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=356971#c3 --- Comment #3 from D Bera <dbera.web@gmail.com> 2008-07-06 06:23:16 MDT --- (In reply to comment #0 from Pavel Nemec)
I run abuild application to build and rpm and I realise that my system is very irresponsible. I run top to obtain information and I realise that beagled-helper spin constantly about 90% of cpu.
this is snip of top: top - 15:13:45 up 20 days, 23:38, 24 users, load average: 5.28, 3.76, 2.42 Tasks: 189 total, 4 running, 185 sleeping, 0 stopped, 0 zombie Cpu(s): 25.3%us, 3.5%sy, 47.8%ni, 0.0%id, 22.6%wa, 0.3%hi, 0.5%si, 0.0%st Mem: 2061376k total, 2052288k used, 9088k free, 133804k buffers Swap: 4225052k total, 207692k used, 4017360k free, 603600k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 19293 pavel 39 19 262m 35m 11m R 97 1.8 732:42.68 beagled-helper 12286 root 19 0 10232 8192 2048 R 52 0.4 0:05.08 rpm.bin
beagled-helper should watch "load" walue and respect it.
It actually does. I suspect this has something to do with rpm. Currently rpm files are indexed by parsing the output of "rpm -q --queryformat ..." so large rpms can be a bit costly. (The rpm process is automatically killed if it runs for too long). Or it was some file whose parser was causing the high load. Usually the file parsers are fixed if the problem can be detected. So if you spot such a file, please report and attach the file. Sending SIGUSR2 to beagled-helper will cause beagled-helper to print the name of the currently indexing file to ~/.beagle/Log/current-IndexHelper -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=356971 User pnemec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=356971#c4 Pavel Nemec <pnemec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |pnemec@novell.com --- Comment #4 from Pavel Nemec <pnemec@novell.com> 2008-07-07 01:36:47 MDT ---
beagled-helper occupy one my CPU core constantly at ~90 %
I am assuming you meant 90% load for more than a few seconds ?
No I thought 15+ minutes when beagled-helper load was more than 90%
I tried beagle-shutdown, but it do not close beagled-helper only line in log appear:
The log file claimed that beagled-helper was shut down. You by any chance didnt have more than one instance of beagled and beagled-helper running - did you ?
In past I had problem that beagle spawn childrens without killing them, so yes from my point of view; it is possible that there were more than one instance running. I will make sure to obtain this information next time.
These bugs are usually hard to "reproduce". If you still have ~/.beagle/Log/current-IndexHelper could you attach it (it will be a symbolic link to some 2008-*-IndexHelper file). Thanks.
If you encounter this anytime in the future, could you send SIGUSR1 and SIGUSR2 to beagled and attach the ~/.beagle/Log/current-* files immediately after that
Sure I will do that. (In reply to comment #3 from D Bera)
(In reply to comment #0 from Pavel Nemec)
I run abuild application to build and rpm and I realise that my system is very [...] It actually does. I suspect this has something to do with rpm. Currently rpm files are indexed by parsing the output of "rpm -q --queryformat ..." so large rpms can be a bit costly. (The rpm process is automatically killed if it runs
I understand it know. I run abuild, which install 50+ rpms into chroot environment, this will spin beagle to use rpm -q.... Anyway I will provide logs as you requested. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=356971 User pnemec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=356971#c5 Pavel Nemec <pnemec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|pnemec@novell.com | Resolution| |INVALID --- Comment #5 from Pavel Nemec <pnemec@novell.com> 2008-08-01 08:23:51 MDT --- I update to 11.0 and I can`t provide requested infromation anymore. -> INVALID -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com