lookup-domain-d uses cpu 100% and 3.4%RAM (on a linode with 1.5GB RAM), constantly, for each of one or two process started.
The problem appeared suddenly for the first time after doing an aptitude upgrade, which upgraded Debian mysql packages from 5.5.22 to 5.5.23. (Not that I have any other reason to think the problem and the upgrade are related.)
Websites on the server were still working, but I noticed the problem from ‘top’ and from viewing the Linode graphs.
For now I have disabled Spamassasin for all accounts, turned it off, and stopped the lookup service, but I do need a spam filter. I will be grateful for any suggestions about the cause or cure of this problem.
Same problem here. The problem started to appear after the MySQL update on my Debian server. But I’m not sure that the root problem is MySQL because a lot of package were updated at the same time as MySQL.
Jamie asked this in the bug report as well, but are you both using the new Virtualmin version – 3.91?
There was a change made to the lookup-daemon in that version that should have resolved that. But if you’re both using 3.91, Jamie may need to dig deeper into that.
Yes virtualmin 3.91, 64 bit. Kernel 3, not upgraded at this time. uname outputs:
3.0.18-x86_64-linode24 #1 SMP Mon Jan 30 14:25:46 EST 2012 x86_64 GNU/Linux
Aptitude log for the problem upgrade shows only upgrades to mysql and :
webmin-virtual-server 3.90.gpl-2 -> 3.91.gpl
webmin-virtual-server-theme 8.2 -> 8.4
After updating to Virtualmin 3.91GPL, I have been noticing this same problem. The lookup-domain-daemons bring my CPU usage all the way up. The server doesn’t have that much mail coming in, and it hasn’t had this problem prior to this upgrade.
It’s a VPS with Ubuntu 10.04 x64 server, 1GB of RAM and a single core/CPU.
Normal load levels are 0.3 or so, with about 50% of RAM used. When lookup service is active, the load goes up to 20 constant (5 minute average) and RAM usage to 80-90%.
