There have been various problems with spam assassin starting. The latest is: child process [1027] exited or timed out without signaling production of a PID file: exit 255 at /usr/sbin/spamd line 2590. There appears to be a suggested fix here: http://translate.google.com/translate?js=n&prev=_t&hl=en&ie=UTF-8&layout=2&eotf=1&sl=auto&tl=en&u=http%3A%2F%2Funixforum.org%2Findex.php%3Fs%3D7ebf0c1b004ff269f358d25650f3d3bc%26showtopic%3D118514%26st%3D0%26p%3D1106043%26%23entry1106043&act=url [base URL in case the Google translate link doesn't work:] http://unixforum.org/index.php?s=7ebf0c1b004ff269f358d25650f3d3bc&showtopic=118514&st=0&p=1106043&#entry1106043 Reproducible: Always Steps to Reproduce: 1./etc/init.d/spamd start 2. 3. Actual Results: child process [1027] exited or timed out without signaling production of a PID file: exit 255 at /usr/sbin/spamd line 2590. Expected Results: [OK] The potential fix above makes me think that I should include that I am using syslog-ng.
This is usually the result of no rules for SA to parse. Please make sure you run sa-update before starting spamassassin for the first time. Ebuild gives you a warning for this reason. Please reopen if running sa-update does not solve the problem.
