Hi,

in the last months I have an issue on some servers where spamdyke processes use the 100% of the CPU when connections are coming from specific remote host. When this happens the load on the server increase and the only way to solve is to kill the processes. We are running spamdyke 5.0.1 on CentOS 6.10.

Here is an example where there are 2 spamdyke process (22218 and 22957) at 100%CPU:

[root@srv-2 ~]# netstat -natpu | grep 22218
udp        0      0 0.0.0.0:45298 0.0.0.0:*                               22218/spamdyke


[root@srv-2 ~]# netstat -natpu | grep 22957
tcp   200592      0 78.45.67.31:25 154.16.116.187:32320        CLOSE_WAIT  22957/spamdyke udp        0      0 0.0.0.0:60265 0.0.0.0:*                               22957/spamdyke


[root@srv-2 ~]# lsof -n | grep 22957
spamdyke  22957 vpopmail  cwd       DIR              253,0 4096    9830479 /var/qmail/supervise/qmail-smtpd
spamdyke  22957 vpopmail  rtd       DIR              253,0 4096          2 /
spamdyke  22957 vpopmail  txt       REG              253,0 325376    6557448 /usr/local/bin/spamdyke-5.0.1 spamdyke  22957 vpopmail  mem       REG              253,0 122056   13631570 /lib64/libselinux.so.1 spamdyke  22957 vpopmail  mem       REG              253,0 143280   13631527 /lib64/libpthread-2.12.so spamdyke  22957 vpopmail  mem       REG              253,0 111440   13631529 /lib64/libresolv-2.12.so spamdyke  22957 vpopmail  mem       REG              253,0 10192   13631671 /lib64/libkeyutils.so.1.3 spamdyke  22957 vpopmail  mem       REG              253,0 43728   13631681 /lib64/libkrb5support.so.0.1 spamdyke  22957 vpopmail  mem       REG              253,0 88600   13631554 /lib64/libz.so.1.2.3 spamdyke  22957 vpopmail  mem       REG              253,0 20024   13631509 /lib64/libdl-2.12.so spamdyke  22957 vpopmail  mem       REG              253,0 174840   13631677 /lib64/libk5crypto.so.3.1 spamdyke  22957 vpopmail  mem       REG              253,0 14664   13631562 /lib64/libcom_err.so.2.1 spamdyke  22957 vpopmail  mem       REG              253,0 946048   13631679 /lib64/libkrb5.so.3.3 spamdyke  22957 vpopmail  mem       REG              253,0 277704   13631673 /lib64/libgssapi_krb5.so.2.2 spamdyke  22957 vpopmail  mem       REG              253,0 1971488    6555384 /usr/lib64/libcrypto.so.1.0.1e spamdyke  22957 vpopmail  mem       REG              253,0 1924768   13631503 /lib64/libc-2.12.so spamdyke  22957 vpopmail  mem       REG              253,0 443416    6555386 /usr/lib64/libssl.so.1.0.1e spamdyke  22957 vpopmail  mem       REG              253,0 159312   13631897 /lib64/ld-2.12.so spamdyke  22957 vpopmail    0u     IPv4         1188469288 0t0        TCP 78.45.67.31:smtp->154.16.116.187:32320 (CLOSE_WAIT) spamdyke  22957 vpopmail    1u     IPv4         1188469288 0t0        TCP 78.45.67.31:smtp->154.16.116.187:32320 (CLOSE_WAIT) spamdyke  22957 vpopmail    2w     FIFO                0,8 0t0      10454 pipe spamdyke  22957 vpopmail    3u     IPv4         1188469320 0t0        UDP *:60265 spamdyke  22957 vpopmail    4u     unix 0xffff88085f6e33c0      0t0 1188505138 socket spamdyke  22957 vpopmail    6r     FIFO                0,8      0t0 1188469325 pipe


[root@srv-2 ~]# lsof -n | grep 22218
spamdyke  22218 vpopmail  cwd       DIR              253,0 4096    9830479 /var/qmail/supervise/qmail-smtpd
spamdyke  22218 vpopmail  rtd       DIR              253,0 4096          2 /
spamdyke  22218 vpopmail  txt       REG              253,0 325376    6557448 /usr/local/bin/spamdyke-5.0.1 spamdyke  22218 vpopmail  mem       REG              253,0 122056   13631570 /lib64/libselinux.so.1 spamdyke  22218 vpopmail  mem       REG              253,0 143280   13631527 /lib64/libpthread-2.12.so spamdyke  22218 vpopmail  mem       REG              253,0 111440   13631529 /lib64/libresolv-2.12.so spamdyke  22218 vpopmail  mem       REG              253,0 10192   13631671 /lib64/libkeyutils.so.1.3 spamdyke  22218 vpopmail  mem       REG              253,0 43728   13631681 /lib64/libkrb5support.so.0.1 spamdyke  22218 vpopmail  mem       REG              253,0 88600   13631554 /lib64/libz.so.1.2.3 spamdyke  22218 vpopmail  mem       REG              253,0 20024   13631509 /lib64/libdl-2.12.so spamdyke  22218 vpopmail  mem       REG              253,0 174840   13631677 /lib64/libk5crypto.so.3.1 spamdyke  22218 vpopmail  mem       REG              253,0 14664   13631562 /lib64/libcom_err.so.2.1 spamdyke  22218 vpopmail  mem       REG              253,0 946048   13631679 /lib64/libkrb5.so.3.3 spamdyke  22218 vpopmail  mem       REG              253,0 277704   13631673 /lib64/libgssapi_krb5.so.2.2 spamdyke  22218 vpopmail  mem       REG              253,0 1971488    6555384 /usr/lib64/libcrypto.so.1.0.1e spamdyke  22218 vpopmail  mem       REG              253,0 1924768   13631503 /lib64/libc-2.12.so spamdyke  22218 vpopmail  mem       REG              253,0 443416    6555386 /usr/lib64/libssl.so.1.0.1e spamdyke  22218 vpopmail  mem       REG              253,0 159312   13631897 /lib64/ld-2.12.so spamdyke  22218 vpopmail    0u     sock                0,6      0t0 1188462010 can't identify protocol spamdyke  22218 vpopmail    1u     sock                0,6      0t0 1188462010 can't identify protocol spamdyke  22218 vpopmail    2w     FIFO                0,8 0t0      10454 pipe spamdyke  22218 vpopmail    3u     IPv4         1188462061 0t0        UDP *:45298 spamdyke  22218 vpopmail    4u     unix 0xffff88016244f840      0t0 1188500514 socket spamdyke  22218 vpopmail    6r     FIFO                0,8      0t0 1188462067 pipe

The protocol is UDP, could be a DNS problem? The problem start recentelly, apparently suddenly and without changing anything.

Do you have any suggestions on how to solve it?

Thanks

--
Alessio Cecchi
Postmaster @ http://www.qboxmail.it
https://www.linkedin.com/in/alessice

_______________________________________________
spamdyke-users mailing list
spamdyke-users@spamdyke.org
https://spamdyke.org/mailman/listinfo/spamdyke-users

Reply via email to