High CPU dataskq "service named didn't start"

sephen

Verified User
Joined
Nov 12, 2019
Messages
15
Hi,

My /var/log/directadmin/errortaskq.log is flooded with:
2022:01:23-03:33:01: service named wasn't running, starting named
2822:01:23-03:33:01: Error starting service named : uid o gid 0 : /usr/bin/systemctl start named.service >/dev/null 2>/dev/null : returned 1
2022:01:23-03:33:06: service named didn't start, re-starting named
2022:01:23-03:33:06: Error restarting service named : uid a gid 0 : /usr/bin/systemctl restart named.service >/dev/null 2>/dev/null : returned 1

Resulting in a +200% CPU load

Does any body know how to solve this?
 
Did you check the named logs? They usually log to /var/log/messages on CentOS systems.

What happens when you run `service named restart`? Can you provide the output?
 
Check the reason why named does not restart in the logfiles.

It might be related to this, seems to happen a lot at the moment:
 
Back
Top