Hello,

Yesterday I finally got the rrdtool configured on my R5E50 system. This morning I figured I'd take a look at the graphs to see what my utilization was like yesterday when I was watching and recording some HD shows. At about 9:20a this morning my CPU utilization jumped to 100% and stayed there. I checked the status through MythWeb and nothing was recording, so I remoted (ssh) in to the system to see what was going on. Top showed two running mbmon processes using 100% utilization.

I killed those two processes, but was wondering if anyone else had noticed that behavior after configuring rrdtool.

Thanks,

_________________
Tim

LinHES 8.4
HDHR3
BioStar A770, AMD X2 4050e, 2GB RAM
GigaByte GeForce 8400, Chaintech AV710
USB-UIRT

I havnt even configured rrdtool or anything like that -- I'm on a fresh install of KnoppMyth R5E50 and mbmon is right now taking up 68% cpu and slowly rising. If I kill the process, it just comes back! Right now my TV is on really old hardware as I had to use the box Myth was previously on for something else... and this is virtually bringing the box to a complete halt.

Would love to know how to get rid of this! I dont need/and/or/want to do any temperature monitoring.


--Eric

Hello,

Out of the box, KM R5E50 should run the rrd update process hourly as the command to start it is in the /etc/cron.hourly directory. You should be able to remove the rrd_km file from that directory to keep it from running.

However, I'm in the situation where I would like it to run, at least for the time being while I get my HD stuff set up. I want to keep track of processor utilization and the eth0 traffic. The rest I could probably do without. However, I just had to kill a dozen or so (lost count) mbmon processes, some of which had been running for over 4 hours. I have removed my rrd configuration from my crontab, but would really like to know why this is happening as I would like to have the information rrd_tool provides.

_________________
Tim

LinHES 8.4
HDHR3
BioStar A770, AMD X2 4050e, 2GB RAM
GigaByte GeForce 8400, Chaintech AV710
USB-UIRT

While waiting for a response, I just did an "apt-get remove mbmon", since I couldnt find out where it was spawning from. I cant believe I didnt think to check cron. Sheesh.


Thanks for the tip. If I decide to reinstall it, now I'll know.

--Eric

Well, I just wound up removing all of the *temp options from the script that run rrd. So now mbmon never runs, but I still get all of the other stats.

Is that the only fix for this? I am having the same problem...

top - 15:23:30 up 19:48, 1 user, load average: 21.27, 21.06, 20.64
Tasks: 204 total, 21 running, 183 sleeping, 0 stopped, 0 zombie
Cpu(s): 98.7%us, 1.0%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.3%hi, 0.0%si, 0.0%st
Mem: 480768k total, 472072k used, 8696k free, 106484k buffers
Swap: 730948k total, 232860k used, 498088k free, 94560k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
4673 root 39 0 1620 344 276 R 9.0 0.1 17:49.21 mbmon
3944 root 29 0 1620 340 276 R 6.6 0.1 56:45.66 mbmon
3429 root 39 0 1620 340 276 R 5.3 0.1 148:57.31 mbmon
3294 root 39 0 1616 344 284 R 4.7 0.1 204:03.11 mbmon
3599 root 39 0 1616 340 276 R 4.7 0.1 101:47.46 mbmon
3684 root 39 0 1620 344 276 R 4.7 0.1 86:58.50 mbmon
3777 root 39 0 1620 344 276 R 4.7 0.1 75:06.40 mbmon
3860 root 39 0 1616 340 276 R 4.7 0.1 65:13.28 mbmon
4110 root 39 0 1620 340 276 R 4.7 0.1 42:45.54 mbmon
4433 root 39 0 1620 340 276 R 4.7 0.1 31:31.01 mbmon
4592 root 39 0 1620 344 276 R 4.7 0.1 22:02.27 mbmon
4754 root 39 0 1616 340 276 R 4.7 0.1 13:52.02 mbmon
4842 root 39 0 1616 340 276 R 4.7 0.1 10:10.60 mbmon
4919 root 39 0 1620 344 276 R 4.7 0.1 6:41.85 mbmon
4998 root 39 0 1620 344 276 R 4.7 0.1 3:24.94 mbmon
5093 root 39 0 1616 336 276 R 4.7 0.1 0:18.27 mbmon
3515 root 39 0 1616 340 276 R 4.3 0.1 121:15.51 mbmon
4027 root 39 0 1620 344 276 R 4.3 0.1 49:21.02 mbmon
4207 root 39 0 1620 344 276 R 4.3 0.1 36:51.79 mbmon
4513 root 39 0 1620 344 276 R 4.3 0.1 26:35.57 mbmon

If anyone has another fix for this, let me know.

thanks.

Well, this had been an interesting academic discussion for me, until yesterday, when I found mbmon had taken over 50% of processor cycles and had been doing so for 6 hours when I discovered it (by rrd tool graph)

HD live TV now was pegging the processor at 100% and stuttering. I went into webmin and turned off all the rrd tool processes, but the stuttering continued (probably needed re-boot) so I ssh-ed into the rrd_km file in /etc/cron.hourly and commented out all the lines in the file UFN..

After a re-boot the pvr function was OK, but rrd tools is disabled.

Anyone know why this would work OK for two weeks and then suddenly turn on like that ?