jonj1 wrote:6GB mail to root seems to be really a lot, as a normal root mail is under 1KB, this would account of millions of mail...
There were about 75,000! Basically the problem arose because I'd added a database to MySQL and in the process broken horde. Since I don't use horde I just left it, not realising the '/etc/cron.d/bubba-horde' cron job was then sending error emails of 232K each, every 5 minutes! Here's an example:
Subject: Cron <root@bubba> test -x /usr/bin/php && /usr/bin/php /usr/share/horde3/scripts/alarms.php
A fatal error has occurred
DB Error: connect failed
[line 723 of /usr/share/horde3/lib/Horde/Group/sql.php]
Details:
The full error message is logged in Horde's log file, and is shown below only to administrators. Non-administrative users will not see error details.
DB_Error Object
(
[error_message_prefix] =>
[mode] => 1
[level] => 1024
code] => -24
[message] => DB Error: connect failed
[userinfo] => [nativecode=Access denied for user 'root'@'localhost' (using password: NO)] ** Array
[backtrace] => Array
(
[0] => Array
.......
232K of code...
There were also error emails like
[userinfo] => [nativecode=Access denied for user 'horde'@'localhost' (using password: YES)] ** Array
[4] => [nativecode=Access denied for user 'horde'@'localhost' (using password: YES)]
[3] => [nativecode=Access denied for user 'horde'@'localhost' (using password: YES)]
I've commented out the cron job now and, with the help of Rene, redirected system mail to my user so / won't fill up again so it's fixed as far as I'm concerned.
I don't know anything about MySQL so I'm not sure what broke horde. Admittedly I set up a database for the 'Bibus' reference manager and had to change something to give me remote access - it's probably that. Not worth our time at the moment to get into ...