Forum Discussion

purna_256577's avatar
purna_256577
Icon for Nimbostratus rankNimbostratus
Aug 02, 2017

shared partition taking high memory of 98%, where zrd.out file consuming more data

shared partition taking high memory of 98%, where zrd.out file consuming 28GB. Please suggest how to resolve the memory high issue. f5 Os is 10.2.1

 

Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg--db--sda-set.3.root 248M 130M 106M 56% / /dev/mapper/vg--db--sda-set.3._config 496M 22M 449M 5% /config /dev/mapper/vg--db--sda-set.3._usr 1.4G 962M 317M 76% /usr /dev/mapper/vg--db--sda-set.3._var 3.0G 181M 2.7G 7% /var /dev/mapper/vg--db--sda-dat.share.1 30G 30G 0 98% /shared /dev/mapper/vg--db--sda-dat.log.1 6.9G 184M 6.4G 3% /var/log none 2.0G 408K 2.0G 1% /dev/shm none 2.0G 8.7M 2.0G 1% /var/tmstat none 2.0G 1.1M 2.0G 1% /var/run prompt 4.0M 12K 4.0M 1% /var/prompt

 

HQL7-ITRADMZ-GTM-02:Standby] tmp find /shared/ -xdev -type f | xargs du | sort -rn | head -20 27797952/shared/tmp/zrd.out 830084/shared/images/BIGIP-10.2.1.297.0.iso 11468/shared/tmp/HQL7-ITRADMZ-GTM-02.bibd.com.bn.tgz 8996/shared/core/gtmd.bld297.0.core.gz 3808/shared/bin/big3d 2496/shared/rrd.1.2/blade0cpu 1596/shared/rrd.1.2/connections 1164/shared/rrd.backup/throughput 1164/shared/rrd.1.2/throughput 1164/shared/rrd.1.2/memory 1096/shared/rrd.1.2/rollupcpu 876/shared/rrd.1.2/gtm 732/shared/rrd.1.2/ramcache 224/shared/tmp/packages/rt.pkc 156/shared/rrd.1.2/bladeconnections 48/shared/tmp/packages/tmui.pkc 20/shared/tmp/packages/schema.pkc 20/shared/log/eud.log.1 20/shared/log/eud.log 16/shared/tmp/packages/axis.pkc

 

1 Reply

  • Well the question would be is the ZRD Debug logging is enabled ? Was it enabled for some troubleshooting activity and missed to disable back.

    The ZoneRunner process debug log is located at /var/tmp/zrd.out.

    Can you check currently what's the logging level of zrd.

    tmsh list /sys db log.zrd.level value

    Notice is the default value, if you see it on debug mode, the 28GB file will continue to increase day-by-day. If its set back to notice, it means the debugging is stopped.

    Refer article.

    On a side note: Do a ls -ltr to know when this file was created, you go back and check what and when was happened.