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

    Unbound TCP buffer settings not sticky

    Scheduled Pinned Locked Moved pfSense Packages
    85 Posts 5 Posters 23.8k 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.
    • M
      markn62
      last edited by

      States get reset on reboot, no?  Don't think it's states unless only a state reset will do.  So I should console ipkg list then ipkg remove package.name?  Or is more cleanup needed?

      1 Reply Last reply Reply Quote 0
      • W
        wagonza
        last edited by

        Check your config.xml for multiple entries for Unbound.
        Look between <installedpackages>xml tags.</installedpackages>

        Follow me on twitter http://twitter.com/wagonza
        http://www.thepackethub.co.za

        1 Reply Last reply Reply Quote 0
        • M
          markn62
          last edited by

          ./conf.default/config.xml or ./cf/conf/config.xml?

          1 Reply Last reply Reply Quote 0
          • W
            wagonza
            last edited by

            The latter one.

            Follow me on twitter http://twitter.com/wagonza
            http://www.thepackethub.co.za

            1 Reply Last reply Reply Quote 0
            • B
              bryan.paradis
              last edited by

              @markn62:

              ./conf.default/config.xml or ./cf/conf/config.xml?

              Same thing /conf is a link of /cf/conf

              mark62 are you running pfsense 2.1 that has been upgraded? Likely you need to manually clean out unbound.

              Uninstall unbound
              Turn on rw
              Find / -name *unbound*
              Delete everything you can find
              /conf/config.XML clear out all everything to do with unbound. Backup first maybe.
              Once you are sure you have killed everything reinstall.
              If you have problems with internet try adding a DNS to resolv.conf

              1 Reply Last reply Reply Quote 0
              • W
                wagonza
                last edited by

                @bryan.paradis:

                @markn62:

                ./conf.default/config.xml or ./cf/conf/config.xml?

                Same thing /conf is a link of /cf/conf

                Yeah but /conf.default is not the same thing thats used, as an example, for reverting to factory defaults.

                Follow me on twitter http://twitter.com/wagonza
                http://www.thepackethub.co.za

                1 Reply Last reply Reply Quote 0
                • B
                  bryan.paradis
                  last edited by

                  @wagonza:

                  @bryan.paradis:

                  @markn62:

                  ./conf.default/config.xml or ./cf/conf/config.xml?

                  Same thing /conf is a link of /cf/conf

                  Yeah but /conf.default is not the same thing thats used for factory defaults.

                  Haha whoops Justin woke UP didn't notice default

                  1 Reply Last reply Reply Quote 0
                  • M
                    markn62
                    last edited by

                    Thanks guys.  Where are the firmware upgrades and package upgrades hosted to do a DNS resolve on?  Same for both?  Do I just need pfsense.com.  Suppose a netstat during a temp pkg install might answer for one of the two.  Hope the host IP doesn't change often.  Good suggestion to locally resolve should happen to scramble Unbound again.

                    I find one unbound install in the xml after I had uninstalled the pkg by GUI this morning.  As well, two unbound files remain.  I'll clean these up tonight, cron a reboot, and report back.

                    Really appreciate your help…

                    1 Reply Last reply Reply Quote 0
                    • B
                      bryan.paradis
                      last edited by

                      @markn62:

                      Thanks guys.  Where are the firmware upgrades and package upgrades hosted to do a DNS resolve on?  Same for both?  Do I just need pfsense.com.  Suppose a netstat during a temp pkg install might answer for one of the two.  Hope the host IP doesn't change often.  Good suggestion to locally resolve should happen to scramble Unbound again.

                      I find one unbound install in the xml after I had uninstalled the pkg by GUI this morning.  As well, two unbound files remain.  I'll clean these up tonight, cron a reboot, and report back.

                      Really appreciate your help…

                      files.pfsense.org - pbi
                      www.pfsense.com - config

                      1 Reply Last reply Reply Quote 0
                      • M
                        markn62
                        last edited by

                        Cleaned the XML of remnant Unbound package info.  The reinstall went well and seems to be working normally now.  Odd though, the install reported 21_1 rather than 21_3.  After install the "Installed Packages" reports 21_3.  And the Unbound Status reports 21_3.  Looks like outgoing-num-tcp: 0 & incoming-num-tcp: 0 are still making it from GUI to XML.

                        –-------------------

                        Checking for package installation...
                        Downloading http://files.pfsense.org/packages/amd64/8/All/unbound-1.4.21_1-amd64.pbi


                        version: 1.4.21
                        verbosity: 1
                        threads: 2
                        modules: 2 [ validator iterator ]
                        uptime: 51 seconds
                        unbound (pid 34067) is running…


                        Unbound  Services  1.4.21_3
                        Unbound is a validating, recursive, and caching DNS resolver. This package is a drop in replacement for Services: DNS Forwarder and also supports DNSSEC extensions. Once installed please configure the Unbound service by visiting Services: Unbound DNS.

                        1 Reply Last reply Reply Quote 0
                        • B
                          bryan.paradis
                          last edited by

                          @markn62:

                          Cleaned the XML of remnant Unbound package info.  The reinstall went well and seems to be working normally now.  Odd though, the install reported 21_1 rather than 21_3.  After install the "Installed Packages" reports 21_3.  And the Unbound Status reports 21_3.  Looks like outgoing-num-tcp: 0 & incoming-num-tcp: 0 are still making it from GUI to XML.

                          –-------------------

                          Checking for package installation...
                          Downloading http://files.pfsense.org/packages/amd64/8/All/unbound-1.4.21_1-amd64.pbi


                          version: 1.4.21
                          verbosity: 1
                          threads: 2
                          modules: 2 [ validator iterator ]
                          uptime: 51 seconds
                          unbound (pid 34067) is running…


                          Unbound  Services  1.4.21_3
                          Unbound is a validating, recursive, and caching DNS resolver. This package is a drop in replacement for Services: DNS Forwarder and also supports DNSSEC extensions. Once installed please configure the Unbound service by visiting Services: Unbound DNS.

                          Great! Wagonza updated the file already so the configuration should be working properly as you see.

                          As far as I can see its just the packages list xml has the newer version number and the unbound package xml has the older version number still. Wagonza just needs to update that line.

                          1 Reply Last reply Reply Quote 0
                          • W
                            wagonza
                            last edited by

                            Yup that's all. Package just needs a rebuild on the package servers as well. Glad to hear all ok markn62.

                            Follow me on twitter http://twitter.com/wagonza
                            http://www.thepackethub.co.za

                            1 Reply Last reply Reply Quote 0
                            • M
                              markn62
                              last edited by

                              Not what I was hoping to report.  Thought all was well after the reinstall.  Watched for about an hour and everything appeared normal.  Bout 30 minutes after I walked away Unbound died and would not restart.  Pointed back to the stand-alone unbound service AGAIN.  This is getting so frustrating!

                              1 Reply Last reply Reply Quote 0
                              • W
                                wagonza
                                last edited by

                                Any logs (both system and package logs) giving an indication as to why?

                                Follow me on twitter http://twitter.com/wagonza
                                http://www.thepackethub.co.za

                                1 Reply Last reply Reply Quote 0
                                • B
                                  bryan.paradis
                                  last edited by

                                  @markn62:

                                  Not what I was hoping to report.  Thought all was well after the reinstall.  Watched for about an hour and everything appeared normal.  Bout 30 minutes after I walked away Unbound died and would not restart.  Pointed back to the stand-alone unbound service AGAIN.  This is getting so frustrating!

                                  You will need to be much clearer and specific.

                                  What do you mean it died? Still running but not responding? Crashed/No process?
                                  What do you see in system.log? Or any other pertinent logs. Better yet pastebin the log so we can look.
                                  Am I assuming correctly you mean a separate box running unbound when you say stand-alone unbound service?

                                  Is this a fresh 2.1 installation or a upgrade from prior versions to 2.1?
                                  If an upgrade what packages do you have installed using pkg_info on the shell?

                                  1 Reply Last reply Reply Quote 0
                                  • M
                                    markn62
                                    last edited by

                                    By died I mean the unbound service stopped on it's own after about an hour of normal operation and the watchdog or manual restart wouldn't get it started again.  Yes, stand-alone means a separate box.  It is an upgrade from 2.0 to 2.1.  Pkg_Info reports no packages installed even though there are.  I'm not certain the name and location of the system and package log. I could binpaste the SNMP log if I knew how.  Is that the insert code button?  Bout 100 lines of text probably best not pasted in this post.

                                    1 Reply Last reply Reply Quote 0
                                    • B
                                      bryan.paradis
                                      last edited by

                                      @markn62:

                                      By died I mean the unbound service stopped on it's own after about an hour of normal operation and the watchdog or manual restart wouldn't get it started again.  Yes, stand-alone means a separate box.  It is an upgrade from 2.0 to 2.1.  Pkg_Info reports no packages installed even though there are.  I'm not certain the name and location of the system and package log. I could binpaste the SNMP log if I knew how.  Is that the insert code button?  Bout 100 lines of text probably best not pasted in this post.

                                      http://pastebin.com/

                                      /var/log

                                      system.log
                                      unbound.log? Is there one?
                                      /tmp/php_errors.txt

                                      what happens when you try to start unbound manually?

                                      1 Reply Last reply Reply Quote 0
                                      • M
                                        markn62
                                        last edited by

                                        Forum access is with a PC other than what has access to the router logs so it would take me a bit to transfer files around and post here.  For now here is the SNMP; http://pastebin.com/embed_js.php?i=kTkuRnzX  I hope I binpasted correctly using a hyperlink. As mentioned, a manual restart would do nothing.  The service would remain unstarted.

                                        A quick look via the GUI edit file I find php_errors.txt is empty even though the SNMP shows some.  The router was rebooted early AM by cron.  The unbound log only has CLOG and some odd symbol after the word.  The system log has plenty and isn't cooperative by remote login.  Large file I suppose.  May have to post the system log this evening.

                                        1 Reply Last reply Reply Quote 0
                                        • M
                                          markn62
                                          last edited by

                                          Forgot to mention installed packages.  Installed and running fine for a few months other than Unbound are;

                                          • Cron

                                          • PhpSysInfo

                                          • Service Watchdog

                                          • SipProxD

                                          • Unbound

                                          1 Reply Last reply Reply Quote 0
                                          • B
                                            bryan.paradis
                                            last edited by

                                            Just grab Winscp and use same credentials as ssh. Just like using a FTP server. Unbound should be complaining somewhere about something.

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