On Fri, Feb 21, 2014 at 09:46:13AM +0100, Stefano Callegari wrote: > Feb 21 09:12:22.731 [22110] dbg: config: using > "/var/lib/spamassassin/3.004000" for sys rules pre files > Feb 21 09:12:22.731 [22110] dbg: config: using > "/var/lib/spamassassin/3.004000" for default rules dir > Feb 21 09:12:22.731 [22110] error: config: no rules were found! Do you need > to run 'sa-update'? > config: no rules were found! Do you need to run 'sa-update'?
It's trying to load rules from /var/lib/spamassassin/3.004000, which is where sa-update installs them. Packaged rules are installed in /usr/share/spamassassin. If bug 739373 was triggered on the first sa-update run, then /var/lib/spamassassin/3.004000 would have been created but never populated with rules. This could leave spamassassin in a situation similar to the one you're in. It would have to affect the very first run of sa-update, though, because if that succeeded, then subsequent runs would simply leave behind rules from a previous run. What I don't understand is what ran sa-update. It isn't run by postinst or any other processes that would run during a package upgrade. Is there anything else on your system that could have triggered sa-update? If you delete /var/lib/spamassassin/3.004000, you should be able to update to 3.4.0. Can you confirm this? If that works, then I'd be interested in seeing if things stay stable following a manual run of sa-update: su - debian-spamd -c "sa-update --gpghomedir /var/lib/spamassassin/sa-update-keys" Thanks noah
signature.asc
Description: Digital signature
