On Mon, May 3, 2010 at 11:39 PM, Yun Zhou <[email protected]> wrote:
> Giovanni Tirloni wrote: > > On Mon, May 3, 2010 at 11:07 PM, Yun Zhou <[email protected] <mailto: >> [email protected]>> wrote: >> >> Can you please preload libumem to diagnose the memory leak >> problem? I think the below should do the trick: >> >> # svcadm disable svc:/network/datalink-management:default >> # export LD_PRELOAD=libumem.so >> # export UMEM_DEBUG=default >> # /sbin/dlmgmtd -d 10 & >> # mdb -p `pgrep dlmgmtd` >> > ::findleaks >> >> >> # LD_PRELOAD=libumem.so UMEM_DEBUG=default /sbin/dlmgmtd -d 10 >> >> # while [ 1 ]; do dladm show-ether; dladm show-phys; dladm show-link; >> dladm show-aggr; sleep 1; done >> >> It iterated 100 times and then I fired up mdb (which had the effect of >> making dladm wait): >> >> # mdb -p 13859 >> Loading modules: [ ld.so.1 libumem.so.1 libavl.so.1 ] >> > ::findleaks >> findleaks: no memory leaks detected >> > Hmm, it does not report any memory leak problem. Do you still see dlmgmtd > uses a lot of memory? > No, it doesn't seem to be growing right now. We have Zabbix hammering the servers with `dladm show-ether` since a few days ago and they all stopped working between yesterday and today. I restarted dlmgmtd in a few servers and we should be able to see if they break again in a few days. -- Giovanni
_______________________________________________ networking-discuss mailing list [email protected]
