Somehow my DNS is not starting up

[Blason R]

Well it just loads fine when I run from command line i.e. named -u named -n
4 -c /etc/named.conf

On Wed, Apr 18, 2018 at 2:25 PM, Reindl Harald <h.reindl at thelounge.net>
wrote:

> named.service start operation timed out
> 362086 zones
>
> well, it may take too long to load them
>
> TimeoutStartSec defaults to DefaultTimeoutStartSec
> on Fedora: DefaultTimeoutStartSec=90s
>
> https://www.freedesktop.org/software/systemd/man/systemd.service.html
> TimeoutStartSec=
> Configures the time to wait for start-up. If a daemon service does not
> signal start-up completion within the configured time, the service will
> be considered failed and will be shut down again. Takes a unit-less
> value in seconds, or a time span value such as "5min 20s". Pass
> "infinity" to disable the timeout logic. Defaults to
> DefaultTimeoutStartSec= from the manager configuration file, except when
> Type=oneshot is used, in which case the timeout is disabled by default
> (see systemd-system.conf(5)).
>
> Am 18.04.2018 um 09:47 schrieb Blason R:
> > Not sure what is gone wrong but my DNS is not starting up. and I am
> > getting below error. I have around  362086 zones with 4 core CPU and 8
> > GB RAM.
> >
> > This is a sinkhole DNS server
> >
> > Apr 18 13:09:02 dnsfw named[1644]: command channel listening on
> > 127.0.0.1#953
> > Apr 18 13:09:02 dnsfw named[1644]: command channel listening on ::1#953
> >
> >
> > Apr 18 13:10:01 dnsfw systemd: named.service start operation timed out.
> > Terminating.
> > Apr 18 13:10:01 dnsfw systemd: Failed to start Berkeley Internet Name
> > Domain (DNS).
> > Apr 18 13:10:01 dnsfw systemd: Unit named.service entered failed state.
> > Apr 18 13:10:01 dnsfw systemd: named.service failed
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20180418/d7a3a868/attachment.html>