INFO exited: clamd (terminated by SIGKILL; not expected)

[Stephan Krebernik]

I tried the free version of poste.io on a vultr-server but the clamd terminates permanently:

2016-01-27 10:51:32,368 INFO exited: clamd (terminated by SIGKILL; not expected) 2016-01-27 10:51:33,413 INFO spawned: 'clamd' with pid 405 2016-01-27 10:51:34,416 INFO success: clamd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2016-01-27 10:51:47,886 INFO exited: clamd (terminated by SIGKILL; not expected) 2016-01-27 10:51:48,928 INFO spawned: 'clamd' with pid 406 2016-01-27 10:51:49,931 INFO success: clamd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2016-01-27 10:52:03,499 INFO exited: clamd (terminated by SIGKILL; not expected) 2016-01-27 10:52:04,603 INFO spawned: 'clamd' with pid 407 2016-01-27 10:52:05,607 INFO success: clamd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2016-01-27 10:52:21,946 INFO exited: clamd (terminated by SIGKILL; not expected) 2016-01-27 10:52:23,000 INFO spawned: 'clamd' with pid 408 2016-01-27 10:52:24,004 INFO success: clamd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2016-01-27 10:54:28,557 INFO exited: clamd (terminated by SIGKILL; not expected) 2016-01-27 10:54:29,590 INFO spawned: 'clamd' with pid 409 2016-01-27 10:54:30,592 INFO success: clamd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2016-01-27 10:55:20,311 INFO exited: clamd (terminated by SIGKILL; not expected) 2016-01-27 10:55:21,350 INFO spawned: 'clamd' with pid 410 2016-01-27 10:55:22,352 INFO success: clamd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2016-01-27 10:55:31,392 INFO exited: clamd (terminated by SIGKILL; not expected) 2016-01-27 10:55:32,414 INFO spawned: 'clamd' with pid 417 2016-01-27 10:55:33,417 INFO success: clamd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2016-01-27 10:58:25,016 INFO exited: clamd (terminated by SIGKILL; not expected) 2016-01-27 10:58:26,059 INFO spawned: 'clamd' with pid 418 2016-01-27 10:58:27,061 INFO success: clamd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2016-01-27 10:59:35,709 INFO exited: clamd (terminated by SIGKILL; not expected) 2016-01-27 10:59:36,772 INFO spawned: 'clamd' with pid 461 2016-01-27 10:59:37,775 INFO success: clamd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2016-01-27 11:01:37,246 INFO exited: clamd (terminated by SIGKILL; not expected) 2016-01-27 11:01:37,439 INFO spawned: 'clamd' with pid 463 2016-01-27 11:01:38,442 INFO success: clamd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2016-01-27 11:02:21,460 INFO exited: clamd (terminated by SIGKILL; not expected) 2016-01-27 11:02:21,779 INFO spawned: 'clamd' with pid 466 2016-01-27 11:02:23,107 INFO success: clamd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2016-01-27 11:02:56,990 INFO exited: clamd (terminated by SIGKILL; not expected) 2016-01-27 11:02:58,031 INFO spawned: 'clamd' with pid 487 2016-01-27 11:02:59,035 INFO success: clamd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2016-01-27 11:05:58,050 INFO exited: clamd (terminated by SIGKILL; not expected) 2016-01-27 11:05:59,093 INFO spawned: 'clamd' with pid 488 2016-01-27 11:06:00,095 INFO success: clamd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2016-01-27 11:07:10,340 INFO exited: clamd (terminated by SIGKILL; not expected) 2016-01-27 11:07:11,398 INFO spawned: 'clamd' with pid 493 2016-01-27 11:07:12,401 INFO success: clamd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2016-01-27 11:07:39,687 INFO exited: clamd (terminated by SIGKILL; not expected) 2016-01-27 11:07:40,750 INFO spawned: 'clamd' with pid 494 2016-01-27 11:07:41,754 INFO success: clamd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2016-01-27 11:08:06,150 INFO exited: clamd (terminated by SIGKILL; not expected) 2016-01-27 11:08:07,207 INFO spawned: 'clamd' with pid 495 2016-01-27 11:08:08,211 INFO success: clamd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2016-01-27 11:08:14,448 INFO exited: clamd (terminated by SIGKILL; not expected) 2016-01-27 11:08:15,484 INFO spawned: 'clamd' with pid 496 2016-01-27 11:08:16,487 INFO success: clamd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2016-01-27 11:08:34,209 INFO exited: clamd (terminated by SIGKILL; not expected) 2016-01-27 11:08:35,257 INFO spawned: 'clamd' with pid 497 2016-01-27 11:08:36,261 INFO success: clamd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

any Idea what's the problem is or how to debug?

cheers

stephan

[SH]

Log of supervisor process is at .../log/supervisor/spamd-... Please paste here content.

[Stephan Krebernik]

spamd-stderr---supervisor-yEg1WN.log:

Jan 27 10:46:34.605 [268] info: spamd: server started on IO::Socket::INET6 [127.0.0.1]:783, IO::Socket::INET6 [::1]:783 (running version 3.4.0) Jan 27 10:46:34.606 [268] info: spamd: server pid: 268 Jan 27 10:46:34.609 [268] info: spamd: server successfully spawned child process, pid 301 Jan 27 10:46:34.622 [268] info: spamd: server successfully spawned child process, pid 302 Jan 27 10:46:34.625 [268] info: prefork: child states: IS Jan 27 10:46:34.626 [268] info: prefork: child states: II Jan 27 11:01:43.171 [301] info: spamd: connection from localhost [127.0.0.1]:54190 to port 783, fd 5 Jan 27 11:01:43.173 [301] info: spamd: setuid to smtpd succeeded Jan 27 11:01:43.194 [301] info: spamd: checking message [e-mail] for smtpd:107 Jan 27 11:02:21.760 [301] info: spamd: clean message (-0.7/5.0) for smtpd:107 in 38.6 seconds, 7006 bytes. Jan 27 11:02:21.762 [301] info: spamd: result: . 0 - HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS scantime=38.6,size=7006,user=smtpd,uid=107,required_score=5.0,rhost=localhost,raddr=127.0.0.1,rport=54190,mid=[e-mail],autolearn=ham autolearn_force=no Jan 27 11:02:21.876 [268] info: prefork: child states: II Jan 27 11:11:52.909 [301] info: spamd: connection from localhost [127.0.0.1]:54192 to port 783, fd 5 Jan 27 11:11:52.912 [301] info: spamd: setuid to smtpd succeeded Jan 27 11:11:52.957 [301] info: spamd: checking message [e-mail] for smtpd:107 Jan 27 11:11:53.267 [301] info: spamd: clean message (-0.7/5.0) for smtpd:107 in 0.4 seconds, 7004 bytes. Jan 27 11:11:53.268 [301] info: spamd: result: . 0 - HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H2,SPF_HELO_PASS scantime=0.4,size=7004,user=smtpd,uid=107,required_score=5.0,rhost=localhost,raddr=127.0.0.1,rport=54192,mid=[e-mail],autolearn=ham autolearn_force=no Jan 27 11:11:53.358 [268] info: prefork: child states: II Jan 27 12:17:22.431 [268] info: spamd: server killed by SIGTERM, shutting down Jan 27 12:17:22.447 [268] info: spamd: cannot send SIGINT to child process [301]: No such process Jan 27 12:17:22.447 [268] info: spamd: cannot send SIGINT to child process [302]: No such process

[Stephan Krebernik]

sorry, no idea why this editor kills the text format...

[Stephan Krebernik]

data/log/clamav/freshclam.log:

[SH]

It seems unrelated to spamassassin processing itself. There was external process terminating spamd - did you do anything at Jan 27 12:17:22 with server settings? Have your server enough free memory? There might be other logs at log/syslog or log/supervisor/supervisord.log

[Stephan Krebernik]

do you think it's a memory issue? the server has 512MB, as can be seen in the screenshot. the clamd takes a really high CPU usage..

[Stephan Krebernik]

okay, just increased the swap to 2GB and it works like a charme.

maybe you should put some more info on your website about the minimum requirements? ;)

and thanks for help!

[SH]

Please inspect your syslog logs - there should be message about insuficient memory (if this was the case). Its kind of tricky to define minimum requirements, but i'll try...

[SH]

Very old issue, closing