This is most commonly due to a mail routing loop and messages are stuck in the mail queue. There are instruction on docs.astaro.org on how to clear the mail queue.
The system is a PII 400 /128 I have pptp running but no connections, and I am not running smtp proxie, turned off accounting as well as pptp but no change, I have not rebooted and this is day 3. at 99%.
I thin tccoggs didn't mean the SMTP proxy, he meant the notification system on the firewall.
Anyway, there are severl possibilities which could cause this bad cpu usage.
1. Notification system: Have a look at WEBADMIN:REPORTING/SMTP
if there are no messages in the queue check step 2 (in the current Beta you find that directly under Proxies)
2. Access the comand line interface as usr root and enter "ps axwfu" to find out which process eats up cpu time. - If you find named as cpu time eater, make sure that your internal nameservers you maybe run, are configured correctly - nacctd or snmpd could be the problem, if your firewall is under heavy load - If you find any other process - post again :-)
Well its back again system runs fine for a few hrs and bang 99% cpu usage, the system will not reboot from webmin I have to log into the console and reboot the box, I logged in from outside says the pppoe is down yet I'm logged in through that port... seems know one else is experienceing these problems ?
I have upgraded to the RC astaro and the CPU problem has come back the system also drops all info regarding the PPPOE interface, come up red and says not connected even though I have connection. The WAN selection disapears from all configuration options. It does not reboot from webmin or SSH and the box hangs and needs a hardware reset to get back up and going. As in the prior posts cpu usage is the middleware.
I have the same problem, the firewall goes well during a couple of days and after that is going in the roof at 99% of CPU process. The mdw_daemon.pl is running at 80%. I send to the support some files to help them to diagnose the problem. I'm still waiting the answer.
