sa-update issue

I noticed the following issue (fresh vm 4.11 gpl install):

channel: could not find working mirror, channel failed
sa-update failed for unknown reasons

Other virtualmin users seem to have the same issue

But I couldn't find any solution. Just FYI.



Howdy -- that actually sounds like a problem with SpamAssassin or the servers that host the SpamAssassin rules. That isn't something Virtualmin configures.

However, what are the contents of your "/usr/bin/sa-update" file? Could you either paste that in here, or attach it as a .txt file?

Here you go

PS I started the file manually (as root) and the update went through (just a problem with cron job?)

Oh nuts, I paste in the wrong filename.

I'm actually interested in the file "/etc/cron.daily/spamassassin".

Also, what are the contents of "/etc/default/spamassassin"?


Here you go :-)


OPTIONS="--create-prefs --max-children 5 --helper-home-dir"

Cron: see attachment

Thanks for the info! I did a little digging, and found a variety of other Ubuntu users experiencing this problem in 14.04.

Can you try the solution mentioned in this Ubuntu forum post here:

It's sounding like a packaging bug in the Ubuntu SpamAssassin package though.

I tried this on the folder /var/lib/spamassassin/3.004000 a


su - debian-spamd -c "sa-update --gpghomedir /var/lib/spamassassin/sa-update-keys"

run successfully.

Although that's a little odd, since Debian (and Centos) has the same folder with the same permis and there is no problem.

There is a difference though. Debian runs the command without the --login parameter.

su debian-spamd -c "sa-update --gpghomedir /var/lib/spamassassin/sa-update-keys"

That could be the bug, but don't want to mess with that :-)

Thinking about it again ... Actually I don't think that "--login" is a bug.

I believe now it is a virtualmin bug. I guess sa-update is not supposed to be run as root, right? Probably that is exactly what Virtualmin does during the installation. This theory would also explain that mostly virtualmin users complain about this issue :-)