a lot of files total 83264 drwxr-xr-x 2 clamscan clamscan 4096 Aug 7 16:35 . drwxr-xr-x. 16 root root 4096 Aug 7 17:53 .. -rw-r----- 1 clamscan clamscan 1041589 Aug 7 19:54 clamd.log -rw-r----- 1 clamscan clamscan 2097213 Oct 3 2019 clamd.log-20191003_100947 -rw-r----- 1 clamscan clamscan 2097218 Oct 11 2019 clamd.log-20191011_141430 -rw-r----- 1 clamscan clamscan 2097186 Oct 22 2019 clamd.log-20191022_081523 -rw-r----- 1 clamscan clamscan 2097243 Oct 31 2019 clamd.log-20191031_023746 -rw-r----- 1 clamscan clamscan 2097195 Nov 7 2019 clamd.log-20191107_114249 -rw-r----- 1 clamscan clamscan 2097179 Nov 15 2019 clamd.log-20191115_003226 -rw-r----- 1 clamscan clamscan 2097187 Nov 25 2019 clamd.log-20191125_095345 -rw-r----- 1 clamscan clamscan 2097248 Dec 1 2019 clamd.log-20191201_194116 -rw-r----- 1 clamscan clamscan 2097192 Dec 6 2019 clamd.log-20191206_145032 -rw-r----- 1 clamscan clamscan 2097206 Dec 13 2019 clamd.log-20191213_151511 -rw-r----- 1 clamscan clamscan 2097208 Dec 23 2019 clamd.log-20191223_073104 -rw-r----- 1 clamscan clamscan 2097232 Jan 2 2020 clamd.log-20200102_134420 -rw-r----- 1 clamscan clamscan 2097163 Jan 10 2020 clamd.log-20200110_153545 -rw-r----- 1 clamscan clamscan 2097201 Jan 20 2020 clamd.log-20200120_124235 -rw-r----- 1 clamscan clamscan 2097178 Jan 29 2020 clamd.log-20200129_043739 -rw-r----- 1 clamscan clamscan 2097155 Feb 6 2020 clamd.log-20200206_094540 -rw-r----- 1 clamscan clamscan 2097200 Feb 14 12:18 clamd.log-20200214_121849 -rw-r----- 1 clamscan clamscan 2097245 Feb 23 13:38 clamd.log-20200223_133808 -rw-r----- 1 clamscan clamscan 2097216 Mar 3 18:16 clamd.log-20200303_181644 -rw-r----- 1 clamscan clamscan 2097184 Mar 10 20:09 clamd.log-20200310_200931 -rw-r----- 1 clamscan clamscan 2097255 Mar 18 12:27 clamd.log-20200318_122742 -rw-r----- 1 clamscan clamscan 2097225 Mar 28 16:06 clamd.log-20200328_160600 -rw-r----- 1 clamscan clamscan 2097232 Apr 7 11:19 clamd.log-20200407_111914 -rw-r----- 1 clamscan clamscan 2097203 Apr 15 09:34 clamd.log-20200415_093400 -rw-r----- 1 clamscan clamscan 2097195 Apr 22 15:58 clamd.log-20200422_155848 -rw-r----- 1 clamscan clamscan 2097209 Apr 30 09:38 clamd.log-20200430_093920 -rw-r----- 1 clamscan clamscan 2097216 May 7 22:20 clamd.log-20200507_222017 -rw-r----- 1 clamscan clamscan 2097153 May 14 10:00 clamd.log-20200514_100043 -rw-r----- 1 clamscan clamscan 2097219 May 20 19:35 clamd.log-20200520_193509 -rw-r----- 1 clamscan clamscan 2097244 May 28 13:06 clamd.log-20200528_130631 -rw-r----- 1 clamscan clamscan 2097154 Jun 4 14:00 clamd.log-20200604_140037 -rw-r----- 1 clamscan clamscan 2097153 Jun 11 04:00 clamd.log-20200611_040933 -rw-r----- 1 clamscan clamscan 2097180 Jun 17 19:14 clamd.log-20200617_191508 -rw-r----- 1 clamscan clamscan 2097187 Jun 24 13:33 clamd.log-20200624_133356 -rw-r----- 1 clamscan clamscan 2097171 Jun 30 22:59 clamd.log-20200630_225940 -rw-r----- 1 clamscan clamscan 2097202 Jul 7 09:54 clamd.log-20200707_095401 -rw-r----- 1 clamscan clamscan 2097182 Jul 14 18:14 clamd.log-20200714_181456 -rw-r----- 1 clamscan clamscan 2097210 Jul 21 10:49 clamd.log-20200721_104950 -rw-r----- 1 clamscan clamscan 2097250 Jul 28 11:50 clamd.log-20200728_115012 -rw-r----- 1 clamscan clamscan 2097234 Aug 4 10:52 clamd.log-20200804_105240
El vie., 7 ago. 2020 a las 19:24, Eric Broch (<[email protected]>) escribió: > what's this yield > > # ls -la /var/log/clamd > On 8/7/2020 4:19 PM, Diego Piñon Conde wrote: > > Same error > > systemctl start clamd@scan > Job for [email protected] failed because a timeout was exceeded. See > "systemctl status [email protected]" and "journalctl -xe" for details. > > El vie., 7 ago. 2020 a las 19:08, Eric Broch (<[email protected]>) > escribió: > >> run the following and try to restart clamd@scan >> >> curl -o /etc/clamd.d/scan.conf >> https://raw.githubusercontent.com/qmtoaster/scripts/master/scan.conf >> >> On 8/7/2020 4:05 PM, Diego Piñon Conde wrote: >> >> systemctl start clamd@scan Job for [email protected] >> failed because a timeout was exceeded. See "systemctl status >> [email protected]" and "journalctl -xe" for details. >> >> Did Not start >> >> El vie., 7 ago. 2020 a las 18:44, Eric Broch (<[email protected]>) >> escribió: >> >>> don't stop it. allow it to go until it starts. sometimes it takes quite >>> a while. >>> On 8/7/2020 3:39 PM, Diego Piñon Conde wrote: >>> >>> systemctl start clamd@scan >>> >>> freeze and do nothing >>> >>> # ls -ld /var/log/dspam >>> >>> *drwxrwx--- 2 dspam mail 81 Feb 18 03:57 /var/log/dspam* >>> >>> # ls -la /var/log/dspam >>> >>> >>> >>> >>> >>> >>> *total 10256 drwxrwx--- 2 dspam mail 81 Feb 18 03:57 . >>> drwxr-xr-x. 16 root root 4096 Aug 7 17:53 .. -rw-r--r-- 1 dspam >>> mail 0 Feb 18 03:57 sql.errors -rw-rw---- 1 vpopmail mail >>> 10493507 Feb 18 01:53 sql.errors-20200218 -rw------- 1 dspam mail >>> 0 Feb 18 03:57 sql.errors-20200218.gz* >>> >>> >>> >>> >>> >>> >>> El vie., 7 ago. 2020 a las 18:31, Eric Broch (<[email protected]>) >>> escribió: >>> >>>> What's the output of the following commands? >>>> >>>> # ls -ld /var/log/dspam >>>> >>>> and >>>> >>>> # ls -la /var/log/dspam >>>> On 8/7/2020 2:46 PM, Diego Piñon Conde wrote: >>>> >>>> This is the only weird message i can repeated times see from now >>>> [00 ]Aug 7 17:40:54 pegasus dspam[19962]: Unable to open file for >>>> writing: /var/log/dspam/sql.errors: Permission denied >>>> [00]Aug 7 17:40:55 pegasus dspam[19962]: bailing on error -2 >>>> [00]Aug 7 17:40:55 pegasus dspam[19962]: received invalid result >>>> (!DSR_ISSPAM && !DSR_ISINNOCENT): -2 >>>> [00]Aug 7 17:40:55 pegasus dspam[19962]: process_message returned >>>> error -5. delivering. >>>> >>>> I 'm still looking >>>> >>>> El vie., 7 ago. 2020 a las 17:06, Philip Nix Guru (<[email protected]>) >>>> escribió: >>>> >>>>> Hello >>>>> >>>>> a bit hard to debug without checking system >>>>> >>>>> if you got multitail >>>>> >>>>> create a file with : >>>>> >>>>> multitail -Z red,black,inverse -T -S -x "%m %u@%h %f (%t) [%l]" \ >>>>> -m 0 -n 49 -cS qmail-send -l "qmlog -f send" \ >>>>> -m 0 -n 49 -cS qmail-smtp3 -em "policy_check" -em "CHKUSER" -em >>>>> "simscan" -em "spamdyke" -em "qmail-smtpd: " -l "qmlog -f smtp" \ >>>>> -m 0 -n 49 -cS qmtspamassassin -ev "prefork" -ev "(connection from >>>>> localhost)" -l "tail -f /var/log/maillog" \ >>>>> # -m 0 -n 49 -cS qmail-smtp -em "policy_check" -em "CHKUSER" -em >>>>> "simscan" -em "spamdyke" -em "qmail-smtpd: " -em "spf-reject" -l "qmlog >>>>> -f >>>>> submission" \ >>>>> # -m 0 -n 49 -cS qmtspamassassin -ev "prefork" -ev "(connection from >>>>> localhost)" -l "tail -f /var/log/maillog" >>>>> >>>>> and just sh it, and check if you see anything weird/strange, delay ... >>>>> >>>>> in the mail transaction >>>>> >>>>> The amount of messages in the local queue is still descending but I >>>>> don't know why so slow! >>>>> >>>>> >>>>> >>>>> >>>>> El vie., 7 ago. 2020 a las 15:48, Philip Nix Guru (<[email protected]>) >>>>> escribió: >>>>> >>>>>> Hello >>>>>> >>>>>> But the mail does get delivered just with a very long delay ? >>>>>> >>>>>> and you disabled clamd but it still running ? >>>>>> >>>>>> >>>>>> Check a delivered mail, look at the headers, make sure clamd is >>>>>> really not running >>>>>> >>>>>> anything suspicous in /var/log/clamd/clamd.log ? >>>>>> >>>>>> >>>>>> qmHandle -s shows what ? >>>>>> >>>>>> >>>>>> On 8/7/20 8:34 PM, Diego Piñon Conde wrote: >>>>>> >>>>>> 2 hs has passed and the local queue has 3530 msg (it was 3700 at some >>>>>> point). Beside clamd that it is still running and time to time take 100% >>>>>> cpu usage (I don't understand why because qmailtoaster it's supoust that >>>>>> not use it anymore), cpu usage is normally below 20% and memory is the >>>>>> same. So why does it take so long to deliver local msg! >>>>>> >>>>>> I'm in UTC -3, so probably all of you are snoring. I will keep >>>>>> working til qmailtoaster works normally, I hope when you wake up you can >>>>>> give me a hand. >>>>>> >>>>>> I will really appreciate that. Thanks in advance! >>>>>> >>>>>> El vie., 7 ago. 2020 a las 12:29, Philip Nix Guru (<[email protected]>) >>>>>> escribió: >>>>>> >>>>>>> Hello >>>>>>> >>>>>>> what you could start by doing is disabling >>>>>>> >>>>>>> idle-timeout-secs=xx in /etc/spamdyke/spamdyke.conf >>>>>>> >>>>>>> just comment the line >>>>>>> >>>>>>> check in a few hours if your TIMEOUT drastically decreased >>>>>>> >>>>>>> then you can adapt the idle-timeout delay >>>>>>> >>>>>>> >>>>>>> If not then, we can check other things >>>>>>> >>>>>>> >>>>>>> Cheers >>>>>>> >>>>>>> >>>>>>> On 8/7/20 4:40 PM, Diego Piñon Conde wrote: >>>>>>> >>>>>>> Hi Philip >>>>>>> this is the tail of /var/log/maillog >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> *Aug 7 11:31:01 pegasus spamdyke[2968]: TIMEOUT from: >>>>>>> [email protected] <[email protected]> to: >>>>>>> [email protected] <[email protected]> origin_ip: >>>>>>> 209.85.215.175 origin_rdns: mail-pg1-f175.google.com >>>>>>> <http://mail-pg1-f175.google.com> auth: (unknown) encryption: TLS >>>>>>> reason: >>>>>>> TIMEOUT Aug 7 11:31:03 pegasus spamdyke[2970]: TIMEOUT from: >>>>>>> [email protected] <[email protected]> to: >>>>>>> [email protected] <[email protected]> origin_ip: >>>>>>> 209.167.231.144 origin_rdns: mail01.messages.sonicwall.com >>>>>>> <http://mail01.messages.sonicwall.com> auth: (unknown) encryption: TLS >>>>>>> reason: TIMEOUT Aug 7 11:31:03 pegasus spamdyke[2969]: TIMEOUT from: >>>>>>> v-cjcdika_pmnlhikcme_gmicmlkp_gmicmlk...@bounce.info.bancopatagonia.com.ar >>>>>>> <v-cjcdika_pmnlhikcme_gmicmlkp_gmicmlk...@bounce.info.bancopatagonia.com.ar> >>>>>>> to: [email protected] <[email protected]> origin_ip: >>>>>>> 192.156.219.80 origin_rdns: mail7756.info.bancopatagonia.com.ar >>>>>>> <http://mail7756.info.bancopatagonia.com.ar> auth: (unknown) encryption: >>>>>>> TLS reason: TIMEOUT Aug 7 11:31:06 pegasus spamdyke[2974]: TIMEOUT >>>>>>> from: >>>>>>> bounce-10710_html-121882056-2177875-6399888-...@bounce.mail.bbva.com.ar >>>>>>> <bounce-10710_html-121882056-2177875-6399888-...@bounce.mail.bbva.com.ar> >>>>>>> to: [email protected] <[email protected]> origin_ip: >>>>>>> 13.111.6.12 origin_rdns: mta.mail.bbva.com.ar >>>>>>> <http://mta.mail.bbva.com.ar> >>>>>>> auth: (unknown) encryption: TLS reason: TIMEOUT Aug 7 11:31:24 pegasus >>>>>>> vpopmail[3225]: vchkpw-submission: (PLAIN) login success >>>>>>> [email protected]:10.10.10.8 >>>>>>> <[email protected]:10.10.10.8> >>>>>>> Aug 7 11:31:27 pegasus spamdyke[3004]: TIMEOUT from: >>>>>>> [email protected] <[email protected]> to: >>>>>>> [email protected] <[email protected]> origin_ip: >>>>>>> 91.211.241.9 origin_rdns: pmta41009.emsmtp.com >>>>>>> <http://pmta41009.emsmtp.com> auth: (unknown) encryption: TLS reason: >>>>>>> TIMEOUT Aug 7 11:31:32 pegasus spamdyke[3006]: TIMEOUT from: >>>>>>> [email protected] <[email protected]> to: >>>>>>> [email protected] <[email protected]> origin_ip: >>>>>>> 40.107.76.91 origin_rdns: >>>>>>> mail-eopbgr760091.outbound.protection.outlook.com >>>>>>> <http://mail-eopbgr760091.outbound.protection.outlook.com> auth: >>>>>>> (unknown) >>>>>>> encryption: TLS reason: TIMEOUT Aug 7 11:31:34 pegasus spamdyke[3050]: >>>>>>> TIMEOUT from: [email protected] <[email protected]> >>>>>>> to: >>>>>>> [email protected] <[email protected]> origin_ip: >>>>>>> 190.210.19.10 origin_rdns: webmail.provinciaseguros.com >>>>>>> <http://webmail.provinciaseguros.com> auth: (unknown) encryption: TLS >>>>>>> reason: TIMEOUT Aug 7 11:31:38 pegasus spamdyke[3074]: TIMEOUT from: >>>>>>> [email protected] <[email protected]> to: >>>>>>> [email protected] <[email protected]> origin_ip: >>>>>>> 209.85.210.45 origin_rdns: mail-ot1-f45.google.com >>>>>>> <http://mail-ot1-f45.google.com> auth: (unknown) encryption: TLS reason: >>>>>>> TIMEOUT Aug 7 11:31:42 pegasus spamdyke[3158]: TIMEOUT from: >>>>>>> [email protected] <[email protected]> to: >>>>>>> [email protected] <[email protected]> origin_ip: >>>>>>> 200.41.224.100 origin_rdns: mail.mardelplata.gov.ar >>>>>>> <http://mail.mardelplata.gov.ar> auth: (unknown) encryption: (none) >>>>>>> reason: >>>>>>> TIMEOUT* >>>>>>> >>>>>>> I've checked scan.conf and logverbose = yes >>>>>>> >>>>>>> >>>>>>> El vie., 7 ago. 2020 a las 11:27, Philip Nix Guru (<[email protected]>) >>>>>>> escribió: >>>>>>> >>>>>>>> Hello >>>>>>>> >>>>>>>> can you check if you got any >>>>>>>> >>>>>>>> TIMEOUT in /var/log/maillog log file >>>>>>>> >>>>>>>> since you did your update >>>>>>>> >>>>>>>> >>>>>>>> Check also your scan.conf file >>>>>>>> >>>>>>>> /etc/clamd.d/scan.conf >>>>>>>> >>>>>>>> Enable Log (verbose) , >>>>>>>> >>>>>>>> LogVerbose yes >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On 8/7/20 4:12 PM, Diego Piñon Conde wrote: >>>>>>>> >>>>>>>> Hi all >>>>>>>> >>>>>>>> I'm running qmail toaster on CentOS 7. >>>>>>>> >>>>>>>> Because I had problems with freshclam (terrible slow db update), >>>>>>>> yesterday I changed clamAV to Epel version. >>>>>>>> >>>>>>>> I don't know if it's relevant, but after that local delivery was >>>>>>>> too slow. >>>>>>>> >>>>>>>> Local queue was increasing in size and every email received by >>>>>>>> clients was received 5 or 6 times. >>>>>>>> >>>>>>>> I thinked maybe clamd it's the culprit, so I've changed clamd=no in >>>>>>>> simcontrol and did qmailctl cdb but nothing has changed. >>>>>>>> >>>>>>>> My knowledge is limited and I will appreciate any help >>>>>>>> >>>>>>>>
