• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Anacron job 'cron.daily'

IsmaeelA

Basic Pleskian
Hello guys,

Why am I getting this email:
=============================================================
/etc/cron.daily/dnsquery:
./popauth: error while loading shared libraries: libdb.so.3: cannot open shared object file: No such file or directory
send-mail: invalid option -- 's'
send-mail: invalid option -- 's'
send-mail: fatal: usage: send-mail [options]
send-mail: invalid option -- 's'
send-mail: invalid option -- 's'
send-mail: fatal: usage: send-mail [options]
popauth: no process killed
popauth: error while loading shared libraries: libdb.so.3: cannot open shared object file: No such file or directory

/etc/cron.daily/drweb-update:
Dr.Web update details:
Update server: http://update.fr1.drweb.com/plesk/700/unix
Update has begun at Mon Nov 10 04:00:29 2014 Update has finished at Mon Nov 10 04:00:39 2014

Following files have been updated:
/var/drweb/bases/drwtoday.vdb
/var/drweb/bases/dwmtoday.vdb
/var/drweb/bases/dwntoday.vdb
/var/drweb/bases/dwrtoday.vdb
/var/drweb/bases/timestamp
/var/drweb/updates/timestamp
=============================================================

What should I do?

Note:
We are using CentOS 6.5 and Plesk Panel 11.5

Thanks.
 
Hi IsmaeelA,

first you should consider installing the current "compat-db" library for your system, in order to get rid of the "missing libdb.so.3" - failure. ( or update to the most current version, depending on your used repos ).

DrWeb updates quite often and on days with heavy usage, the DrWeb - servers can sometimes be unreachable for some moments. You could always try to update DrWeb manually with:

/etc/cron.daily/drweb-update

or on other systems use:
/etc/cron.d/drweb-update


But these eMails shouldn't fill your eMail - account, as this really could be very annoying on some days. DrWeb will try to update with the next configured cronjob anyway and so there is no need to read such stuff. If you would like to get rid of these notifications, consider modifying the cronjob by adding this:

>/dev/null 2>&1

after the existing "/etc/cron.d/drweb-update" in the cronjob ( Full example will look like: "/etc/cron.d/drweb-update >/dev/null 2>&1" )
 
Back
Top