Unbound -never- starts on a reboot



  • any time I reboot my pfsense, whether due to update or just because I had to, the unbound service doesn't start, I have to go into the web UI and start it manually.

    i have NO idea why this is happening. its been doing this for the past half dozen updates, probably longer. I just installed 2.4.5 and boom, again.

    fyi, after this 2.4.5 upgrade, here's the console log ...

    Welcome to pfSense 2.4.5-RELEASE...
    
    No core dumps found.
    ...ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/ipsec /usr/local/lib/perl5/5.30/mach/CORE
    32-bit compatibility ldconfig path: /usr/lib32
    done.
    External config loader 1.0 is now starting... ada0s1 ada0s1a ada0s1b
    Launching the init system...Updating CPU Microcode...
    CPU: AMD GX-412TC SOC                                (998.15-MHz K8-class CPU)
      Origin="AuthenticAMD"  Id=0x730f01  Family=0x16  Model=0x30  Stepping=1
      Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
      Features2=0x3ed8220b<SSE3,PCLMULQDQ,MON,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AESNI,XSAVE,OSXSAVE,AVX,F16C>
      AMD Features=0x2e500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM>
      AMD Features2=0x1d4037ff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,SKINIT,WDT,Topology,PNXC,DBE,PTSC,PL2I>
      Structured Extended Features=0x8<BMI1>
      XSAVE Features=0x1<XSAVEOPT>
      SVM: NP,NRIP,AFlush,DAssist,NAsids=8
      TSC: P-state invariant, performance statistics
    Done.
    ...... done.
    Initializing.................. done.
    Starting device manager (devd)...done.
    Loading configuration......done.
    Updating configuration...done.
    Checking config backups consistency.................................done.
    Setting up extended sysctls...done.
    padlock0: No ACE support.
    aesni0: <AES-CBC,AES-XTS,AES-GCM,AES-ICM> on motherboard
    amdtemp0: <AMD CPU On-Die Thermal Sensors> on hostb5
    Setting timezone...done.
    Configuring looplo0: link state changed to UP
    back interface...done.
    Starting syslog...done.
    Starting Secure Shell Services...done.
    Setting up interfaces microcode...done.
    Configuring loopback interface...done.
    Creating wireless clone interfaces...done.
    Configuring LAGG interfaces...done.
    Configuring VLAN interfaces...done.
    Configuring QinQ interfaces...done.
    Configuring IPsec VTI interfaces...done.
    Configuring WAN interface...done.
    Configuring LAN interface...done.
    Configuring CARP settings...done.
    Syncing OpenVPN settings...done.
    Configuring firewall......done.
    Starting PFLOG...done.
    Setting up gateway monitors...done.
    Setting up static routes...done.
    Setting up DNSs...
    Starting DNS Resolver...done.
    Synchronizing user settings...done.
    Starting webConfigurator...done.
    Configuring CRON...done.
    Starting NTP time client...done.
    Starting DHCP service...done.
    Starting DHCPv6 service...done.
    Configuring firewall......done.
    Generating RRD graphs...done.
    Starting UPnP service... done.
    Starting syslog...done.
    Starting CRON... done.
    >>> Upgrading necessary packages... 
    Checking for upgrades (1 candidates): . done
    Processing candidates (1 candidates): . done
    Checking integrity... done (0 conflicting)
    The following 1 package(s) will be affected (of 0 checked):
    
    Installed packages to be UPGRADED:
            pfSense-pkg-iperf: 3.0.2_2 -> 3.0.2_4 [pfSense]
    
    Number of packages to be upgraded: 1
    [1/1] Upgrading pfSense-pkg-iperf from 3.0.2_2 to 3.0.2_4...
    [1/1] Extracting pfSense-pkg-iperf-3.0.2_4: ......... done
    Removing iperf components...
    Menu items... done.
    Services... done.
    Saving updated package information...
    overwrite!
    Loading package configuration... done.
    Configuring package components...
    Custom commands...
    Menu items... done.
    Services... done.
    Writing configuration... done.
    >>> Removing unnecessary packages... done.
    >>> Cleanup pkg cache... done.
     Starting package OpenVPN Client Export Utility...done.
     Starting package iperf...done.
     Starting package acme...done.
    pfSense 2.4.5-RELEASE amd64 Tue Mar 24 15:25:50 EDT 2020
    Bootup complete
    


  • @LeftCoastGeek said in Unbound -never- starts on a reboot:

    Starting DNS Resolver...done.

    It started.

    Check the DNS logs to find out why/when it stopped, was restarted, and what was pfSense doing a couple of seconds just before that. What happened when it restarted. etc.



  • @Gertjan said in Unbound -never- starts on a reboot:

    @LeftCoastGeek said in Unbound -never- starts on a reboot:

    Starting DNS Resolver...done.

    It started.

    Check the DNS logs to find out why/when it stopped, was restarted, and what was pfSense doing a couple of seconds just before that. What happened when it restarted. etc.

    I've looked at that stuff before and not found anything out of the ordinary



  • So you're say it's just dying ?

    Go to console ssh option 8 and type :

    ps ax | grep unbound
    
    ....
    68283  -  Ss     0:23.59 /usr/local/sbin/unbound -c /var/unbound/unbound.conf
    ...
    

Log in to reply