• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

60sa-update error message every night

xxx

Basic Pleskian
Hello!

I'm running Plesk 10.2.0 on Ubuntu 10.04 TLS.
Since first day the administrator gets the following email from 60sa-update:
Cron <root@your_server> test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )

/etc/cron.daily/60sa-update:
[: 13: 1: unexpected operator
[: 18: 1: unexpected operator
run-parts: /etc/cron.daily/60sa-update exited with return code 1
I've found only this possible solution
http://www.codarbyte.de/2011/01/ple...n-daily60sa-update-exited-with-return-code-1/
but it doesn't match with my problem.

My 60sa-update looks like this:
#!/bin/sh

/usr/bin/sa-update
ERR=$?

# Only restart spamd if sa-update returns 0, meaning it updated the rules
if [ $ERR == 0 ]; then

/usr/bin/sa-update && { /etc/init.d/psa-spamassassin restart >> /var/log/sa-update.log; } \
|| { rc=$?; [ $rc -eq 1 ] && exit 0 || exit $rc; };

# /etc/init.d/psa-spamassassin restart | tee -a /var/log/sa-update.log;
fi

# if sa-update returns 1 when there are no updates
if [ $ERR == 1 ]; then
exit 0;
fi

exit $ERR

Is there anyone who understand this error and has a solution for me?! It would be great!

Thanks!
 
Good morning, Igor.
Thanks for your reply. I've searched before posting and I've also found your KB article. But for me it seems that this is not the same error. I have changed the first line of 60--update to bin/bash and will se what happens.
Thanks!
 
Back
Top