sa-update.cron: env: /etc/init.d/spamassassin: Permission denied

[bluik]

(Solved/Workaround) sa-update.cron: env: /etc/init.d/spamassassin: Permission denied

---------------------------------------------------------------
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Parallels Plesk Panel, 10.2, Red Hat Enterprise Linux 6.1, x86_86

PROBLEM DESCRIPTION AND STEPS TO REPRODUCE
Install RHEL6, yum update, install Plesk 10.2 with psa-spamassassin

Every day a SpamAssassin update job is run from /etc/cron.d/sa-update, which contains the following:

# cat /etc/cron.d/sa-update
10 4 * * * root /usr/share/spamassassin/sa-update.cron 2>&1 | tee -a /var/log/sa-update.log
# /usr/share/spamassassin/sa-update.cron 2>&1 | tee -a /var/log/sa-update.log
env: /etc/init.d/spamassassin: Permission denied

This is due to following:

# ls -la /etc/init.d/spamassassin
-rw-r--r--. 1 root root 1664 Mar 17 2010 /etc/init.d/spamassassin

See, no execute bits set.

I am not sure if this whole /etc/cron.d/sa-update is required, since PSA has its own /etc/cron.daily/60sa-update that is supposed to run updates.

ACTUAL RESULT
Mail to admin mail address daily from the stock sa-update cron script, with error:

env: /etc/init.d/spamassassin: Permission denied

EXPECTED RESULT
SpamAssassin rules updated correctly without error message every day from the cron job - not two cron jobs doing same thing and one failing.

ANY ADDITIONAL INFORMATION
The RHEL stock (?) SpamAssassin update script is MUCH more complex/sophisticated than the PSA equivalent. This is completely fresh install so I have not tested if the PSA sa-update script even actually works.

Latest MU installed.
--------------------------------------------------------------

 

[IgorG]

All these scripts belongs to OS vendor's spamassassin package and not related to Plesk:

# rpm -qf /etc/init.d/spamassassin
spamassassin-3.2.5-1.el5

# rpm -qf /usr/share/spamassassin/sa-update.cron
spamassassin-3.2.5-1.el5

# rpm -qf /etc/cron.d/sa-update
spamassassin-3.2.5-1.el5

So, there is nothing from Plesk side and you can just disable /etc/cron.d/sa-update as possible workaround.

 

[bluik]

Thanks Igor, this is exactly what I expected, just wanted a confirmation & for the record if other people have this problem.

Wonder why a search did not show anyone else having this problem?