Issue run-parts: /etc/cron.daily/60sa-update exited with return code 4

[remy]

I get this error message in a mail with subject "Cron <root@dev2> test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )"

This file looks like this:

#!/bin/bash

### Copyright 1999-2017. Parallels IP Holdings GmbH. All Rights Reserved.


sa_update()

{

/usr/bin/sa-update

local rc="$?"

case $rc in

# Only restart spamd if sa-update returns 0, meaning it updated the rules

0) env PATH=/opt/psa/admin/sbin:/usr/local/psa/admin/sbin:$PATH spammng --condrestart ;;

# If sa-update returns 1 then there are no updates

1) exit 0 ;;

esac

return $rc

}


sa_update >> /var/log/sa-update.log 2>&1

 

[remy]

Anyone?

 

[IgorG]

What is your Plesk version? Try to run this cron script manually and check output and log:

# sh /etc/cron.daily/60sa-update
# less /var/log/sa-update.log

 

[tweitzel]

Got the same error today.

Product version: Plesk Onyx 17.5.3 Update #37
Update date: 2018/01/10 13:29
Build date: 2017/03/17 16:00
OS version: Ubuntu 16.04
Revision: 55d1b49a272f44666e1920eca8b6e4da449a38cd
Architecture: 64-bit
Wrapper version: 1.2

When started manually, there's no feedback given on the console. The last couple of lines in the log file are these:

Service condrestart was done successfully.
gpg: process '/usr/bin/gpg' finished: exit 1
error: GPG validation failed!
The update downloaded successfully, but the GPG signature verification
failed.
channel: GPG validation failed, channel failed
Service condrestart was done successfully.
Service condrestart was done successfully.
Service condrestart was done successfully.
channel: SHA1 verification failed, channel failed
Service condrestart was done successfully.
Service condrestart was done successfully.
Service condrestart was done successfully.
Service condrestart was done successfully.
channel: SHA1 verification failed, channel failed
Service condrestart was done successfully.

 

[IgorG]

The update downloaded successfully, but the GPG signature verification
failed.

You can fix it with

# wget http://spamassassin.apache.org/updates/GPG.KEY
# sa-update --import GPG.KEY

 

[nineproof]

After applying your fix

You can fix it with

# wget http://spamassassin.apache.org/updates/GPG.KEY
# sa-update --import GPG.KEY

another error arised:

2018-01-31 04:51:32] Spamassassin update started...
[2018-01-31 04:51:32] sa_update() function starting...
rules: failed to run FORGED_GMAIL_RCVD test, skipping:
(Can't locate object method "check_for_forged_gmail_received_headers" via package "Mail::SpamAssassin:erMsgStatus" at (eval 1317) line 1033.
)
channel: lint check of update failed, channel failed
rules: failed to run FORGED_GMAIL_RCVD test, skipping:
(Can't locate object method "check_for_forged_gmail_received_headers" via package "Mail::SpamAssassin:erMsgStatus" at (eval 1317) line 71.
)
channel: lint check of update failed, channel failed

This issue appeared after one of the last Plesk microupdated

 

[IgorG]

Please use this KB article for fixing this issue Plesk Help Center

 

[Richard18]

Please use this KB article for fixing this issue Plesk Help Center

I get a 404 on that link

oops 404
You're not authorized to access this page

 

[IgorG]

The issue was caused by Spam Assassin's bug #7540

Apply new rule set provided by SpamAssassin as a workaround:

[Apache-SVN] Revision 1822466

As the bug is on SpamAssassin's side, when SpamAssassin will release bugfix it will be added to repositories and issue will be fixed automatically after update.

 

[Pascal_Netenvie]

Hello,
I also have this problem on many servers.
Is the problem fixed ??

 

[MarkM]

SA appears to provide a patch;

7540 – r1822466 fails lint check (FORGED_GMAIL_RCVD)

 

[Pascal_Netenvie]

I still have this in log :

gpg: process '/usr/bin/gpg' finished: exit 1
error: GPG validation failed!
The update downloaded successfully, but the GPG signature verification
failed.
channel: GPG validation failed, channel failed
Service condrestart was done successfully.

 

[Pascal_Netenvie]

And even if i download and update GPG.key manually it still the same ...

 

[daanse]

still having this often with some Servers
any news about this?

 

[Pascal_Netenvie]

Same here.
It comed back for some days ...