openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Fran Hsu (徐誌謙)" <Fran.Hsu@quantatw.com>
To: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: dbus-broker caused the system OOM issue.
Date: Tue, 2 Feb 2021 01:38:56 +0000	[thread overview]
Message-ID: <TYZPR04MB43666E803D310720362F0CD4F3B59@TYZPR04MB4366.apcprd04.prod.outlook.com> (raw)

Hello,
	Sometimes my BMC will run out of memory so that I try to find out which process caused the OOM issue.
From the htop information, it looks like the dbus-broker uses huge memory space.
What I'm doing is to send the ipmi sdr list command from Host OS thru the kcs interface every 2 seconds.
In the begging, I could see the dbus-broker uses up to 400MB and then reduced to less than 100MB.
But after some hours I could see the memory usage keep increasing and the dbus-broker caused system OOM eventually.

  1  [||||||||||||||||||||||||||||||||          67.1%]   Tasks: 104, 20 thr; 2 running
  2  [||||||||||||||||||||||||||||||            60.4%]   Load average: 3.12 3.34 3.54
  Mem[|||||||||||||||||||||||||||||||||||||969M/1003M]   Uptime: 12:59:12
  Swp[                                          0K/0K]

  PID USER      PRI  NI  VIRT   RES   SHR S CPU% MEM%   TIME+  Command
  281 messagebu  20   0  870M  868M   376 S  0.6 86.6 40:54.32 dbus-broker --log 4 --controller 9 --machine-id 932c
  265 messagebu  20   0  259M   284     4 S  0.0  0.0  0:00.34 /usr/bin/dbus-broker-launch --scope system --audit

Version:
	dbus-broker :25-r0

I'd appreciate any comments or feedback.

Thanks,
Fran Hsu
E-Mail : Fran.Hsu@QuantaTW.com
Tel: +886-3-327-2345 Ext: 16935



             reply	other threads:[~2021-02-02  1:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-02  1:38 Fran Hsu (徐誌謙) [this message]
2021-02-03 17:24 ` dbus-broker caused the system OOM issue Sui Chen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=TYZPR04MB43666E803D310720362F0CD4F3B59@TYZPR04MB4366.apcprd04.prod.outlook.com \
    --to=fran.hsu@quantatw.com \
    --cc=openbmc@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).