Posts by batZen

    hm my problem is that they should run according to crontab file in the morning hours between 5 and 6 am.... but as you see in the logs they run at 0:00...

    Hallo zusammen,


    ich nutze aktuell


    imscp 1.3.0
    auf debian jessie


    Ich habe immer von der Nacht von Samstag auf Sonntag mit sehr hoher Serverlast zu kämpfen und zwar genau um 0:00 Uhr.... wenn das um 5 Uhr passieren würde wäre das kein Problem, aber so schon. Problem scheint zu sein das alle weekly Cronjobs zu der Zeit starten:


    Code
    1. Aug 14 00:00:02 menkisyscloudsrv33 CRON[25844]: (root) CMD (nice -n 15 ionice -c2 -n5 perl /var/www/imscp/gui/plugins/LetsEncrypt/cronjobs/pending.pl > /dev/null 2>&1)Aug 14 00:00:03 menkisyscloudsrv33 CRON[25847]: (root) CMD (nice -n 15 ionice -c2 -n5 perl /var/www/imscp/gui/plugins/SpamAssassin/cronjobs/cronjob_clean_bayes_db.pl >/dev/null 2>&1)Aug 14 00:00:05 menkisyscloudsrv33 CRON[25850]: (root) CMD (nice -n 15 ionice -c2 -n5 bash chkrootkit -e > /var/log/chkrootkit.log 2>&1)Aug 14 00:00:06 menkisyscloudsrv33 CRON[25851]: (root) CMD (nice -n 15 ionice -c2 -n5 perl /var/www/imscp/gui/plugins/SpamAssassin/cronjobs/cronjob_bayes_sa-learn.pl >/dev/null 2>&1)Aug 14 00:00:14 menkisyscloudsrv33 CRON[25860]: (root) CMD (nice -n 15 ionice -c2 -n5 perl /var/www/imscp/gui/plugins/SpamAssassin/cronjobs/cronjob_discover_razor.pl >/dev/null 2>&1)Aug 14 00:00:14 menkisyscloudsrv33 CRON[25862]: (root) CMD (find /var/www/imscp/backups -type f -mtime +7 -exec rm -- {} +)Aug 14 00:00:14 menkisyscloudsrv33 CRON[25863]: (root) CMD (nice -n 15 ionice -c2 -n5 perl /var/www/imscp/engine/PerlLib/Package/AntiRootkits/Rkhunter/Cron.pl > /dev/null 2>&1)Aug 14 00:00:14 menkisyscloudsrv33 CRON[25865]: (root) CMD (nice -n 15 ionice -c2 -n5 perl /var/www/imscp/engine/backup/imscp-backup-imscp > /var/log/imscp/imscp-backup-imscp-mngr.log 2>&1)Aug 14 00:00:15 menkisyscloudsrv33 CRON[25867]: (root) CMD (nice -n 15 ionice -c2 -n5 perl /var/www/imscp/gui/plugins/RoundcubePlugins/cronjob/cronjob_pop3fetcher.pl >/dev/null 2>&1)Aug 14 00:00:15 menkisyscloudsrv33 CRON[25869]: (root) CMD (nice -n 15 ionice -c2 -n5 perl /var/www/imscp/engine/tools/imscp-disable-accounts >/dev/null 2>&1)Aug 14 00:00:15 menkisyscloudsrv33 CRON[25870]: (root) CMD (nice -n 15 ionice -c2 -n5 perl /var/www/imscp/engine/quota/imscp-dsk-quota > /var/log/imscp/imscp-dsk-quota.log 2>&1)Aug 14 00:00:15 menkisyscloudsrv33 CRON[25871]: (root) CMD (find /etc/imscp/*/backup -type f -mtime +7 -regextype sed -regex '.*/.*[0-9]\{10\}$' -exec rm -- {} +)Aug 14 00:00:15 menkisyscloudsrv33 CRON[25861]: (root) CMD (nice -n 15 ionice -c2 -n5 perl /var/www/imscp/gui/plugins/LetsEncrypt/cronjobs/renew.pl > /dev/null 2>&1)Aug 14 00:00:15 menkisyscloudsrv33 CRON[25880]: (root) CMD (find /var/log/imscp -type f -mtime +7 -exec rm -- {} +)Aug 14 00:00:15 menkisyscloudsrv33 CRON[25882]: (root) CMD (perl /var/www/imscp/engine/traffic/imscp-vrl-traff > /var/log/imscp/imscp-vrl-traff.log 2>&1)Aug 14 00:00:16 menkisyscloudsrv33 CRON[25891]: (root) CMD (perl /var/www/imscp/engine/traffic/imscp-srv-traff > /var/log/imscp/imscp-srv-traff.log 2>&1)Aug 14 00:01:07 menkisyscloudsrv33 CRON[25902]: (root) CMD (nice -n 15 ionice -c2 -n5 perl /var/www/imscp/gui/plugins/SpamAssassin/cronjobs/cronjob_bayes_sa-learn.pl >/dev/null 2>&1)


    ich würde diese ganzen Backups cronjobs lieber zwischen 5 und 6 laufen lassen dementsprechend ist auch der eintrag in etc/crontab




    leider scheint dies wie man an der o. g. log sehen kann nicht zu funktionieren. Hat jemand ne Idee was ich übersehe?

    Not my plugin so I'll take care when I'll have time. Anyway, you can ignore those messages ATM. Google a bit to know why ;)


    thank you, i did some google. Seems that rules are loaded only some rules are not used... here is a good explain:



    Quote

    antidebug_antivm.yar contains 12 rules which uses the pe module (pe.imports), so only these 12 rules will be skipped/ignored, the rest of the rules will be loaded (113 loaded rules)


    malicious_document.yar contains 5 rules which uses uint32be, so only these 5 rules will be skipped/ignored, the rest of the rules will be loaded (15 loaded rules)

    Source


    So a new Clamav need to fix the problem and support the skipped rules.

    Code
    1. -rw------- 1 postfix postfix 33 Jul 24 21:25 master.lock-rw------- 1 postfix postfix 8192 Jul 24 21:27 postscreen_cache.db-rw------- 1 postfix postfix 1024 Jul 24 21:27 prng_exch-rw------- 1 postfix postfix 8192 Jul 24 21:27 smtpd_scache.db

    and


    Code
    1. drwxr-xr-x 2 postfix postfix 4096 Jul 24 21:27 postfix

    Did that, file was created but still getting the error message? I think it's safe to just ignore it?


    Code
    1. menkisyscloudsrv33 postfix/postscreen[29379]: close database /var/lib/postfix/postscreen_cache.db: No such file or directory (possible Berkeley DB bug)

    I Use Postscreen Plugin Version 1.1.0


    After checking Mail Logs i found this error:

    Code
    1. Jul 24 21:00:31 menkisyscloudsrv33 postfix/postscreen[28206]: close database /var/lib/postfix/postscreen_cache.db: No such file or directory (possible Berkeley DB bug)

    I think postscreen is working, but maybe this have some effect?