Temat: Wyciek pamięci - jak zidentyfikować
Witam,
Jak najlepiej namierzyć proces, który powoduje wyciek pamięci. Mam to na kilku routerach np. R6220 i MIR3G
Strony 1
Zaloguj się lub zarejestruj by napisać odpowiedź
Nie jesteś zalogowany. Proszę się zalogować lub zarejestrować.
eko.one.pl → Oprogramowanie / Software → Wyciek pamięci - jak zidentyfikować
Strony 1
Zaloguj się lub zarejestruj by napisać odpowiedź
Witam,
Jak najlepiej namierzyć proces, który powoduje wyciek pamięci. Mam to na kilku routerach np. R6220 i MIR3G
Zrobisz top i patrzysz co zużywa pamięć...
Nie mogę wrzucać rysunków bo w collectd ładnie pokazuje:
top:
root@NetgearR6220:~# uptime
09:54:30 up 14 days, 46 min, load average: 0.09, 0.13, 0.10
root@NetgearR6220:~# free -h
total used free shared buff/cache available
Mem: 122612 84900 29988 1724 7724 9596
Swap: 32764 1536 31228
root@NetgearR6220:~# top -n 1 -b
Mem: 92364K used, 30248K free, 1724K shrd, 2188K buff, 5532K cached
CPU: 4% usr 4% sys 0% nic 78% idle 0% io 0% irq 13% sirq
Load average: 0.10 0.10 0.09 4/86 32611
PID PPID USER STAT VSZ %VSZ %CPU COMMAND
1514 1 root S 2344 2% 4% /usr/sbin/hostapd -s -g /var/run/hostapd/global
32493 1 root SN 4732 4% 0% /usr/sbin/collectd -C /tmp/collectd.conf -f
1515 1 root S 2228 2% 0% /usr/sbin/wpa_supplicant -n -s -g /var/run/wpa_supplicant/global
1283 1 root S 2224 2% 0% /sbin/rpcd -s /var/run/ubus.sock -t 30
1251 1 root S 1872 2% 0% /sbin/logd -S 256
1553 1 root S 1804 1% 0% /sbin/netifd
4783 1 root S 1712 1% 0% /usr/sbin/uhttpd -f -h /www -r NetgearR6220 -x /cgi-bin -u /ubus -t 60 -T 30 -k 20 -A 1 -n 3 -N 100 -R -p 0.0.0.0:8001 -p [::]:80 -p 192.168.0.1:80 -q
6224 1 root SN 1644 1% 0% /usr/sbin/nlbwmon -o /var/lib/nlbwmon -b 1048576 -i 24h -r 30s -p /usr/share/nlbwmon/protocols -G 10 -I 1 -L 50000 -Z -s 192.168.0.0/16 -s 172.16.0.0/12 -s 10.0.0.0/8 -s 192.168.0.1/24
1 0 root S 1624 1% 0% /sbin/procd
12428 1 dnsmasq S 1420 1% 0% /usr/sbin/dnsmasq -C /var/etc/dnsmasq.conf.cfg01411c -k -x /var/run/dnsmasq/dnsmasq.cfg01411c.pid
26003 1553 root S 1296 1% 0% /usr/sbin/pppd nodetach ipparam wan ifname pppoe-wan lcp-echo-interval 1 lcp-echo-failure 5 lcp-echo-adaptive nodefaultroute usepeerdns maxfail 1 user ..... ip-up-script /lib/netifd/ppp-up ip-down-script /lib/netifd/ppp-down mtu 1492 mru 1492 plugin rp-pppoe.so nic-wan
723 1 root S 1292 1% 0% /sbin/ubusd
32119 32118 root S 1260 1% 0% -ash
32611 32119 root R 1256 1% 0% top -n 1 -b
1593 1 root S 1252 1% 0% /usr/sbin/crond -f -c /etc/crontabs -l 5
2781 1 root S 1252 1% 0% /bin/sh /usr/bin/watchcat.sh period 21600 30 8.8.8.8 1080
1473 1 rpc S 1252 1% 0% /usr/sbin/rpcbind -f -w
2845 1 root S< 1252 1% 0% /usr/sbin/ntpd -n -N -S /usr/sbin/ntpd-hotplug -p 0.openwrt.pool.ntp.org -p 1.openwrt.pool.ntp.org -p 2.openwrt.pool.ntp.org -p 3.openwrt.pool.ntp.org
32602 2781 root S 1248 1% 0% sleep 1080
32118 1991 root S 1208 1% 0% /usr/sbin/dropbear -F -P /var/run/dropbear.1.pid -p 192.168.0.1:22 -K 300 -T 3
1991 1 root S 1148 1% 0% /usr/sbin/dropbear -F -P /var/run/dropbear.1.pid -p 192.168.0.1:22 -K 300 -T 3
26370 1 root S 1148 1% 0% /usr/sbin/dropbear -F -P /var/run/dropbear.2.pid -p 185.170.224.165:60021 -K 300 -T 3
741 1 root S 1044 1% 0% /sbin/urngd
724 1 root S 940 1% 0% /sbin/askfirst /usr/libexec/login.sh
9 2 root SW 0 0% 0% [ksoftirqd/0]
886 2 root SW 0 0% 0% [mt76-tx phy0]
971 2 root SW 0 0% 0% [mt76-tx phy1]
10 2 root IW 0 0% 0% [rcu_sched]
15 2 root SW 0 0% 0% [ksoftirqd/1]
9884 2 root IW 0 0% 0% [kworker/0:2-eve]
29451 2 root IW 0 0% 0% [kworker/1:0-eve]
31978 2 root IW< 0 0% 0% [kworker/u5:3-na]
11 2 root SW 0 0% 0% [migration/0]
32580 2 root IW< 0 0% 0% [kworker/u5:2-na]
14 2 root SW 0 0% 0% [migration/1]
27951 2 root IW 0 0% 0% [kworker/1:1-eve]
32590 2 root IW< 0 0% 0% [kworker/u5:1-na]
32597 2 root IW< 0 0% 0% [kworker/u5:0-na]
31935 2 root IW 0 0% 0% [kworker/0:1-eve]
2 0 root SW 0 0% 0% [kthreadd]
32589 2 root IW 0 0% 0% [kworker/u4:0-ph]
199 2 root SW 0 0% 0% [kswapd0]
32595 2 root IW 0 0% 0% [kworker/u4:2-ph]
144 2 root SW 0 0% 0% [kcompactd0]
607 2 root SW 0 0% 0% [ubifs_bgt0_1]
424 2 root SW 0 0% 0% [ubi_bgt0d]
430 2 root IW< 0 0% 0% [kworker/0:1H-kb]
429 2 root IW< 0 0% 0% [kworker/1:1H-kb]
796 2 root IW< 0 0% 0% [smb3decryptd]
795 2 root IW< 0 0% 0% [cifsiod]
797 2 root IW< 0 0% 0% [cifsfileinfoput]
466 2 root SW 0 0% 0% [irq/24-keys]
465 2 root SW 0 0% 0% [irq/23-keys]
372 2 root IW< 0 0% 0% [dsa_ordered]
464 2 root SW 0 0% 0% [irq/22-keys]
798 2 root IW< 0 0% 0% [cifsoplockd]
163 2 root IW< 0 0% 0% [blkcg_punt_bio]
162 2 root IW< 0 0% 0% [kblockd]
179 2 root SW 0 0% 0% [watchdogd]
149 2 root IW< 0 0% 0% [pencrypt_serial]
142 2 root IW< 0 0% 0% [writeback]
141 2 root SW 0 0% 0% [oom_reaper]
151 2 root IW< 0 0% 0% [pdecrypt_serial]
816 2 root IW< 0 0% 0% [nfsiod]
805 2 root IW< 0 0% 0% [xprtiod]
865 2 root IW< 0 0% 0% [cfg80211]
13 2 root SW 0 0% 0% [cpuhp/1]
12 2 root SW 0 0% 0% [cpuhp/0]
17 2 root IW< 0 0% 0% [kworker/1:0H-kb]
8 2 root IW< 0 0% 0% [mm_percpu_wq]
4 2 root IW< 0 0% 0% [rcu_par_gp]
3 2 root IW< 0 0% 0% [rcu_gp]
6 2 root IW< 0 0% 0% [kworker/0:0H-kb]
18 2 root IW< 0 0% 0% [netns]
281 2 root IW< 0 0% 0% [kthrotld]
804 2 root IW< 0 0% 0% [rpciod]
32596 2 root IW 0 0% 0% [kworker/u4:1]Ty masz obserwować top, cyklicznie. Jednorazowe wykonanie top nic ci nie powie poza bieżącym zużyciem. Uruchamiaj cyklicznie i sprawdzaj co zjada zasoby.
Strony 1
Zaloguj się lub zarejestruj by napisać odpowiedź
eko.one.pl → Oprogramowanie / Software → Wyciek pamięci - jak zidentyfikować
Forum oparte o PunBB, wspierane przez Informer Technologies, Inc