Question

spamd: server killed by SIGTERM, shutting down

Posted September 28, 2020 200 views
SecurityEmail

Hi,

I’m receiving this warning every day: spamd: server killed by SIGTERM, shutting down

I searched in google and saw that more people have same warning, but I not found any solution.

Why happen this?; this is a error/problem?.

Thank you very much. Have a nice day.

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
1 answer

Hi @computereleon,

SIGTERM is used to kill a process. Usually, when a droplet is under load it will start killing processes that take a lot of Memory(RAM) or CPU so that it doesn’t die. In your case it seems the reason for the high load was soo big the droplet didn’t manage to kill everything it shutdown.

In these cases, I’ll recommend you to either find the source of the issue or upgrade your droplet.

About finding the source of the issue, it would mean you’ll need to track what exactly is happening, what is causing this load spikes. The best way would be from inside the droplet itself.

Regards,
KFSys

  • Thank you very much for this information.

    Where can I check logs for know why SIGTERM killed spamd?.

    Thank you again. Have a nice day!

    • Hi @computereleon,

      If you are on a CentOS droplet, you should be able to find these in the /var/log/messages. If you are on an Ubuntu OS, you should be able to check those messages in /var/log/syslog.

      You can grep for messages like oom, kill etc. Example:

      grep -i oom /var/log/syslog
      

      You can also grep for spamd to see the exact message.

      regards,
      KFsys

      • Thank you very much.

        I have CentOS 7. I checked the file “/var/log/messages” and have this:

        Sep 29 01:34:33 systemd: Stopping System Logging Service...
        Sep 29 01:34:33 rsyslogd: [origin software="rsyslogd" swVersion="8.24.0-52.el7_8.2" x-pid="16754" x-info="http://www.rsyslog.com"] exiting on signal 15.
        Sep 29 01:34:33 systemd: Stopped System Logging Service.
        Sep 29 01:34:33 systemd: Starting System Logging Service...
        Sep 29 01:34:33 rsyslogd: [origin software="rsyslogd" swVersion="8.24.0-52.el7_8.2" x-pid="22235" x-info="http://www.rsyslog.com"] start
        Sep 29 01:34:33 systemd: Started System Logging Service.
        Sep 29 01:34:33 systemd: Stopping Apache SpamAssassin™ deferral daemon...
        Sep 29 01:34:33 systemd: Stopped Apache SpamAssassin™ deferral daemon.
        Sep 29 01:34:33 systemd: Starting Apache SpamAssassin™ deferral daemon...
        Sep 29 01:34:36 systemd: Removed slice User Slice of root.
        

        I searched information in google but not found useful steps. You have any idea what happens and how solve him?.

        Thank you again. Have a nice day.

        • The information provided from the log does not seem to be related to spamd being killed. Maybe you couldn’t find the relevant lines. Anyway, I would suggest to try and monitor your droplet. If you ever experience a killed service, you can check whether it’s high load or anything related to that then you can act upon it.

Submit an Answer