[BlueOnyx:20033] Re: 5209R Sendmail hanging gripe

[Larry Smith]

Chris,

  Have two 5209R servers that are doing the exact same thing.
Appears to be relative to end-of-day processing, but not certain.

On mine, both sendmail and saslauthd appear running, but are not
answering.  A systemctl restart on both clears it up, but am to
the point of having to do this daily (or reboot) to get things working.

Tried adding a systemctl restart in the end of the logrotate stuff;
did not help;  tried adding a systemctl restart at the end of the syslog
stuff (end of day) and that did not work either....

-- 
Larry Smith
lesmith at ecsis.net

On Wed August 31 2016 07:34, Chris Gebhardt - VIRTBIZ Internet wrote:
> Every so often, and usually in the early morning, we will find our 5209R
> boxes with hung Sendmail.    Typically if it happens on one, it's
> happening on the others as well.  I wonder if anyone else has had this
> happen?
>
> Sendmail will simply stop responding, so if I quiz systemctl as to its
> status:
>
> * sendmail.service - Sendmail Mail Transport Agent
>    Loaded: loaded (/usr/lib/systemd/system/sendmail.service; enabled;
> vendor preset: disabled)
>    Active: inactive (dead) since Wed 2016-08-31 06:06:43 CDT; 1h 20min ago
>  Main PID: 17176 (code=exited, status=0/SUCCESS)
>
>
> Well gosh, that's helpful.  Thanks a lot to Active Monitor for picking
> up on that and restarting the service.  <rolleyes>
>
> I'd say that it often will correlate to a YUM update (as is the case
> this morning) but that's not ALWAYS the case.
>
> Has anyone else also run into this?   And if so, ideas for getting the
> service to restart on its own?  Surely if systemctl knows it's down,
> Active Monitor should be able to pick up on it as well?    Or maybe I'll
> have to craft a script to kick the service if Nagios detects it's down.
>  That just seems like a kludge...