named-service-stopped

[Reindl Harald]

Am 15.12.19 um 09:44 schrieb MEjaz:
> We are an ISP, All of sudden during the midnight our named service was
> down, please find the below snippet of the logs  when we checked the
> logs  of “dmesg” and “/var/log/messages”
> 
> Our bind name version is =  BIND 9.12.3-P1 <id:cfdd35
> 
> Is that advisable to upgrade our bind from the above version to the
> latest stable one
> 
> We don’t fall into the same problem again. any clue would be highly
> appreciated. Thanks in advance

at least it would be a good idea to use a supported version, sespecially
if you are an ISP

every service i care about has this in the systemd unit

[Service]
Restart=always
RestartSec=1

it's somehow irresponsible "sudden during the midnight our named service
was down" requires human intervention

while the root cause of SIGABRT should be found and automatic restart is
not a proper final solution if that happens repeatly at least your
services are up in case of one-time events nobody can reproduce