Tinydns_down.php - error messages in system log
-
The messages came back after I made some changes to the config.
Changes where made in the DHCP section & rule section.
After these changes the syslog/system-messages came back..To be continued..
Welcome back, SkyNET, you were missed…
-
I'm having the same problem. :-[
-
I've been having the same problem, and I've tracked it down as far as /usr/local/bin/ping_hosts.sh, or more accurately, /tmp/tmpHOSTS which ping_hosts reads.
I've got one line with a blank ip address in the second pipe delimited column, and when I manually remove that line those log lines go away for a while (but eventually return).
The tmpHOSTS file is generated by catting a few files together (bin/ping_hosts.sh:cat $PKGHOSTS $HOSTS $IPSECHOSTS >/tmp/tmpHOSTS) so that's the next direction I'm looking…
-
I think that makes six people so far. Welcome to the club, wlm2048 and iyanchev. So have you two installed/uninstalled the tinydns package and this created the problem? I believe that is what started it for me.
I am starting to think the only way to fix this is to format the hard drive and start over again…
-
Nope, just upgraded to the newest version.
-
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.
-
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
-
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?
-
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.
-
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| -
You're welcome, glad I could help!
-
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??
-
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".
-
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) -
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!
