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

    Unbound errors after upgrade to 23.09. Unbound fails to start

    Scheduled Pinned Locked Moved General pfSense Questions
    2 Posts 1 Posters 428 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.
    • P
      pfBo
      last edited by

      Hi all,

      After upgrading to pfSense 23.09 I see the following errors in the logs:

      2023-11-07 15:47:02.374257+01:00 unbound 32496 [32496:0] fatal error: failed to setup modules
      2023-11-07 15:47:02.374248+01:00 unbound 32496 [32496:0] error: module init for module validator failed
      2023-11-07 15:47:02.374238+01:00 unbound 32496 [32496:0] error: validator: could not apply configuration settings.
      2023-11-07 15:47:02.374228+01:00 unbound 32496 [32496:0] error: validator: error in trustanchors config
      2023-11-07 15:47:02.374210+01:00 unbound 32496 [32496:0] error: error reading auto-trust-anchor-file: /var/unbound/root.key
      2023-11-07 15:47:02.374186+01:00 unbound 32496 [32496:0] error: failed to read /root.key
      2023-11-07 15:47:02.372190+01:00 unbound 32496 [32496:0] notice: init module 0: validator

      Unbound creates a new empty root.key:

      -rw-r--r-- 1 unbound unbound 0 Nov 7 15:47 root.key

      Also when changing the config I'm seeing errors in the GUI:

      *The following input errors were detected:

      The generated config file cannot be parsed by unbound. Please correct the following errors:
      /var/unbound/test/unbound_server.pem: No such file or directory
      [1699368775] unbound-checkconf[76221:0] fatal error: server-cert-file: "/var/unbound/test/unbound_server.pem" does not exist*
      

      If I copy the missing file from /var/unbound to /var/unbound/test it gets deleted (same as root.key).

      Has anyone seen this error before? And if so how did you fix it?

      Best regards,

      Bo

      P 1 Reply Last reply Reply Quote 0
      • P
        pfBo @pfBo
        last edited by

        Problem solved. Disk was full....

        Took me a few minutes to figure that one out...

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