Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    BIND named died

    Scheduled Pinned Locked Moved DHCP and DNS
    namednamed dieddns serverdns server diedbind
    1 Posts 1 Posters 376 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B
      BlankMan
      last edited by BlankMan

      Today named died on me. I noticed my email server was not receiving emails. I tracked it down to my domain was not resolving. I tracked that down to named having died on my pfSense router.

      named has been running on it DNS'ing my domain for years, this is the first ever problem. Found this in the log:

      Aug 28 00:03:23 <myDomain>.com named[85894]: general: critical: message.c:4496: REQUIRE(msg->state == (-1)) failed, back trace
      Aug 28 00:03:23 <myDomain>.com named[85894]: general: critical: #0 0x438e30 in ??
      Aug 28 00:03:23 <myDomain>s.com named[85894]: general: critical: #1 0x6133ea in ??
      Aug 28 00:03:23 <myDomain>.com named[85894]: general: critical: #2 0x4f83d3 in ??
      Aug 28 00:03:23 <myDomain>.com named[85894]: general: critical: #3 0x56e0de in ??
      Aug 28 00:03:23 <myDomain>.com named[85894]: general: critical: #4 0x630002 in ??
      Aug 28 00:03:23 <myDomain>.com named[85894]: general: critical: #5 0x8020c40b6 in ??
      Aug 28 00:03:23 <myDomain>.com named[85894]: general: critical: exiting (due to assertion failure)

      Anyone seen this or know why what causes it? I just started digging on this so this is my first stop attempting to find answers.

      Dare to think and do outside the conventional box…

      1 Reply Last reply Reply Quote 0
      • First post
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.