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

    Tinydns_down.php - error messages in system log

    Scheduled Pinned Locked Moved pfSense Packages
    27 Posts 7 Posters 5.5k 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.
    • W
      wlm2048
      last edited by

      Nope, just upgraded to the newest version.

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

        OK, I fixed it.

        Around line 431 of /usr/local/pkg/tinydns.inc, there's a line that looks like:

        if(!in_array($monitorip, $processed)) {
        

        and it needs to be:

        if(!empty($monitorip) && !in_array($monitorip, $processed)) {
        

        Additionally, around line 444, there's one that's:

        if(!in_array($row['failoverip'], $processed)) {
        

        and it also needs to check to make sure that variable is set:

        if(!empty($row['failoverip']) && !in_array($row['failoverip'], $processed)) {
        

        Really, all the places that file is written to needs a check for a null/empty value, but this worked for me. Note that I've made edits to the file, so the line numbers may be off a bit.

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

          As long as you're in there, I had to make the following change in order for it to not start axfrdns (even though my zone xfer fields were blank). Same sort of thing - it's checking to see if it's an array without checking to see if it actually contains something. Around line 300 this function needed some work (again, the file has been modified, but it should be close):

          
          function populate_zt_array() {
                  global $g, $config;
                  /* Populate Zone Transfer array */
                  if($config['installedpackages']['tinydns']['config'][0]['row']) {
                          $ztipaddress = array();
                          foreach($config['installedpackages']['tinydns']['config'][0]['row'] as $zt) {
                                  if ( !empty($zt['ztipaddress']) && !empty($zt['dnszone']) ) {
                                          $tmp = array();
                                          $tmp['ztipaddress'] = $zt['ztipaddress'];
                                          $tmp['dnszone'] = $zt['dnszone'];
                                          $ztipaddress[] = $tmp;
                                  }
                          }
                          if (!empty($ztipaddress)) {
                                  log_error("ztipaddress is not empty");
                          }
                          else {
                                  log_error("ztipaddress is empty");
                                  unset($ztipaddress);
                          }
                  }
                  return $ztipaddress;
          }
          
          

          And yes, this is horrible code, but I just wanted it to work and stop killing my DNS server  :D

          1 Reply Last reply Reply Quote 0
          • P
            pfSensible
            last edited by

            @wlm2048:

            OK, I fixed it.

            Around line 431 of /usr/local/pkg/tinydns.inc, there's a line that looks like:
            …

            OK, I wish I had the pfSense skills to do this, especially because I don't have that file.  As with others on this thread we actually do not have tinyDNS installed.  At one point I installed it, but it was a disaster and I since uninstalled it months ago.

            This is what makes this so frustrating for us - somewhere there is a code remnant that causes this issue and we don't know where it is.

            Maybe if we create this file but make it empty it will solve the problem?

            The NSA is a terrorist organization that must be stopped.

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

              See if you have "/var/db/pkgpinghosts", and if so, delete the lines in it that say anything about tinydns, and then delete the "/tmp/tmpHOSTS" file. The latter will be recreated.

              1 Reply Last reply Reply Quote 0
              • P
                pfSensible
                last edited by

                @wlm2048:

                See if you have "/var/db/pkgpinghosts", and if so, delete the lines in it that say anything about tinydns, and then delete the "/tmp/tmpHOSTS" file. The latter will be recreated.

                THAT FIXED IT!!!  THANK YOU!  It was like the pfSense box was possessed and this exorcised the demons.

                The lines that were in the files were:

                192.168.4.15|ns.admin.internal.|1|/usr/local/pkg/tinydns_down.php|/usr/local/pkg/tinydns_up.php
                192.168.4.15||1|/usr/local/pkg/tinydns_down.php|/usr/local/pkg/tinydns_up.php|

                The NSA is a terrorist organization that must be stopped.

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

                  You're welcome, glad I could help!

                  1 Reply Last reply Reply Quote 0
                  • S
                    SkyNET
                    last edited by

                    Logging in to my box via ssh and opened /var/db/pkgpinghosts with vi.
                    There were only 3 entries in there all about tinydns. (my old outside ip address)
                    Tried to remove the lines with vi but was not able to save the file. Permissions denied.

                    trying su, sudo or chmod does not work. any suggestions??

                    1 Reply Last reply Reply Quote 0
                    • BBcan177B
                      BBcan177 Moderator
                      last edited by

                      Make sure you SSH with the "account" that has admin rights. Look at the User Manager to see the accounts that are configured. You can run "whoami" in the shell and it should report "root".

                      "Experience is something you don't get until just after you need it."

                      Website: http://pfBlockerNG.com
                      Twitter: @BBcan177  #pfBlockerNG
                      Reddit: https://www.reddit.com/r/pfBlockerNG/new/

                      1 Reply Last reply Reply Quote 0
                      • S
                        SkyNET
                        last edited by

                        Thanks! I had disabled the default admin account and created a new (non-default) admin account. That one did not have sufficient privileges via ssh.
                        It did the trick for me! Everything is working like it should now. Thanks everyone!  8)

                        1 Reply Last reply Reply Quote 0
                        • I
                          IvanS
                          last edited by

                          @wlm2048:

                          See if you have "/var/db/pkgpinghosts", and if so, delete the lines in it that say anything about tinydns, and then delete the "/tmp/tmpHOSTS" file. The latter will be recreated.

                          Thank you, You made my day/week!

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