I think it's imrest. This is the cronjob that causes queries of all registered devices.
$ cat /var/spool/cron/crontabs/root
# Have the monitor retrieve device states for all registered devices once a minute.
0-59 * * * * wget -O /dev/null --header="Accept-Version: 1.0" -q http://127.0.0.1:8165/query/devices 2>&1 >/dev/null
The logs show this to stop after a long run.
$ ps | grep wget
28760 root 0 Z [wget]
Apr 25 03:46:00 (none) cron.info crond[650]: USER root pid 9008 cmd wget -O /dev/null --header="Accept-Version: 1.0" -q http:
//127.0.0.1:8165/query/devices 2>&1 >/dev/null
Apr 25 03:47:00 (none) cron.info crond[650]: USER root pid 9033 cmd wget -O /dev/null --header="Accept-Version: 1.0" -q http:
//127.0.0.1:8165/query/devices 2>&1 >/dev/null
Apr 25 03:47:52 (none) daemon.info hostapd: uap0: STA b8:27:eb:a2:35:ff IEEE 802.11: disassociated
Apr 25 03:47:52 (none) daemon.info hostapd: uap0: STA b8:27:eb:a2:35:ff IEEE 802.11: associated
Apr 25 03:47:52 (none) daemon.info hostapd: uap0: STA b8:27:eb:a2:35:ff RADIUS: starting accounting session ABFA1BC6EF10FC5D
Apr 25 03:47:52 (none) daemon.info hostapd: uap0: STA b8:27:eb:a2:35:ff IEEE 802.11: disassociated
So I think the uap0 goes down and then the crontab has stopped running. imrest is still running and memory/cpu usage is not out of hand yet.
Mem: 212488K used, 731988K free, 1696K shrd, 8104K buff, 127396K cached
CPU: 0.1% usr 0.9% sys 0.0% nic 98.9% idle 0.0% io 0.0% irq 0.0% sirq
Load average: 0.01 0.03 0.00 3/142 28729
PID PPID USER STAT VSZ %VSZ CPU %CPU COMMAND
843 1 root S 96528 10.1 0 0.3 /usr/bin/piboxd
1117 1 root S 29356 3.0 1 0.3 /usr/bin/appmgr
1124 1117 nobody S 97672 10.2 0 0.0 /usr/bin/launcher
734 1 root S 8796 0.9 1 0.0 /usr/sbin/ntpd -g -p /var/run/ntpd.pid
29 2 root SW 0 0.0 3 0.0 [ksoftirqd/3]
860 1 root S 66664 7.0 0 0.0 /usr/bin/imrest
The system is not locked yet, but the uap going down and cron stopped running is concerning.
Updated by