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.
    • I
      IvanS
      last edited by

      As expected issue still there in 2.1.3

      $ grep tinydns *
      help.php: 'tinydns.xml' => 'https://doc.pfsense.org/index.php/Tinydns_package',
      help.php: 'tinydns_domains.xml' => 'https://doc.pfsense.org/index.php/Tinydns_package',
      help.php: 'tinydns_sync.xml' => 'https://doc.pfsense.org/index.php/Tinydns_package',

      grep tiny_dns * - nothing
      grep PingMonitor * - nothing

      Tinydns section

      <tinydns><config><temp><ipaddress>127.0.0.1</ipaddress>
      <enableforwarding>on</enableforwarding>
      <interface>lan,wan,lo0</interface>
      <dnscache_listen>192.168.2 10</dnscache_listen>
      <regdhcpstatic>on</regdhcpstatic>
      <regdhcp>on</regdhcp>
      <enableipmonitoring><refreshinterval><syncxmlrpc><row><ztipaddress></ztipaddress></row></syncxmlrpc></refreshinterval></enableipmonitoring></temp></config></tinydns>

      removed from the config.xml, however, same error as before after the restart even when monitor is down. Any other thoughts where to dig further  :o ?

      This is beyond the abilities of this noob too

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

        I spent a few more hours this morning trying to sort this out without success.  It turns out the grep command is not recursing through the subdirectories as it should be (even with the -r switch or the -d recurse switch) so the results cannot be trusted.  Basically I am looking for any file that contains the words tinydns, tiny_dns or pingmonitor.

        My lack of success most likely has more to do with my lack of Linux skills.

        My last attempts this morning involved variations on the following commands:
        grep -d recurse -i -s pingmonitor /.
        grep -r -i -s pingmonitor /.

        These never worked, it would go one directory deep, find stuff and then terminate.  I verified this when I ran this command:
        grep -r -i the /.

        So then I decided to try specifying the directory each time, like so:
        grep -r -i -s pingmonitor /etc/.

        Finally I realized the futility of this.  So, people who KNOW Linux, how is this done?  How do we recursively search through the entire pfSense directory structure to (hopefully) locate the file that is causing this issue?

        What baffles me is SkyNET claims to have never installed TinyDNS yet he still has this problem.

        The NSA is a terrorist organization that must be stopped.

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

          Don't know why but I don't receive the thinydns messages anymore. I just upgraded to 2.1.3.

          What baffles me is SkyNET claims to have never installed TinyDNS yet he still has this problem.

          In response, I might have installed tunydns once for testing on my first pfsense box a long time ago.
          But I used the same config on my second box where the messages did not show up.

          Anyway.. no more system- or syslog messages regarding tinydns for me.. Cheers!

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

            Well, I upgraded to 2.1.3 yesterday and this is my current system log:

            
May 3 21:20:18	PingMonitor[85407]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 21:16:15	PingMonitor[73885]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 21:12:13	PingMonitor[68062]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 21:08:11	PingMonitor[63013]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 21:04:08	PingMonitor[57246]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 21:00:06	PingMonitor[52366]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 20:56:04	PingMonitor[42580]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 20:52:01	PingMonitor[31987]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 20:47:59	PingMonitor[27585]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 20:43:57	PingMonitor[19427]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 20:39:55	PingMonitor[14145]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 20:35:52	PingMonitor[7688]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 20:31:50	PingMonitor[2121]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 20:27:48	PingMonitor[96916]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 20:23:46	PingMonitor[8735]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 20:19:43	PingMonitor[9184]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 20:15:41	PingMonitor[1501]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 20:11:39	PingMonitor[96525]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 20:07:37	PingMonitor[93542]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 20:03:34	PingMonitor[82721]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 19:59:32	PingMonitor[73384]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 19:55:30	PingMonitor[67955]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 19:51:28	PingMonitor[63591]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 19:47:25	PingMonitor[59850]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 19:43:23	PingMonitor[48230]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 19:39:21	PingMonitor[43821]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 19:35:19	PingMonitor[37274]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 19:31:16	PingMonitor[28361]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 19:27:14	PingMonitor[22147]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 19:23:12	PingMonitor[14490]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 19:19:10	PingMonitor[9828]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 19:15:07	PingMonitor[3091]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 19:11:05	PingMonitor[97216]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 19:07:03	PingMonitor[90969]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 19:03:00	PingMonitor[81577]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 18:58:58	PingMonitor[73676]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 18:54:56	PingMonitor[86736]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 18:50:54	PingMonitor[81240]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 18:46:50	PingMonitor[74112]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 18:42:48	PingMonitor[61890]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 18:38:46	PingMonitor[56128]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 18:34:43	PingMonitor[51565]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 18:30:40	PingMonitor[45812]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 18:26:38	PingMonitor[38134]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 18:22:36	PingMonitor[33420]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 18:18:34	PingMonitor[27538]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 18:14:31	PingMonitor[19573]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 18:10:29	PingMonitor[16853]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 18:06:27	PingMonitor[12765]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 18:02:24	PingMonitor[2399]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 17:58:22	PingMonitor[93196]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 17:54:20	PingMonitor[89548]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 17:50:18	PingMonitor[89244]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 17:46:12	PingMonitor[82103]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 17:42:10	PingMonitor[72057]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 17:38:08	PingMonitor[67590]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 17:34:06	PingMonitor[58746]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 17:30:02	PingMonitor[55917]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 17:26:00	PingMonitor[44683]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 17:21:56	PingMonitor[36749]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 17:17:54	PingMonitor[32298]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 17:13:52	PingMonitor[24903]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 17:09:49	PingMonitor[38603]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 17:05:47	PingMonitor[32899]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 17:01:45	PingMonitor[27208]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 16:57:43	PingMonitor[18561]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 16:53:40	PingMonitor[9440]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 16:49:38	PingMonitor[888]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 16:45:36	PingMonitor[95167]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 16:41:34	PingMonitor[89598]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 16:37:31	PingMonitor[81755]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 16:33:29	PingMonitor[73738]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 16:29:27	PingMonitor[65641]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 16:25:24	PingMonitor[58342]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 16:21:22	PingMonitor[55112]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 16:17:20	PingMonitor[52513]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 16:13:18	PingMonitor[46934]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 16:09:14	PingMonitor[37539]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 16:05:12	PingMonitor[29664]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 16:01:07	PingMonitor[24842]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 15:57:05	PingMonitor[10929]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 15:53:03	PingMonitor[6656]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 15:49:01	PingMonitor[1618]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 15:44:58	PingMonitor[95298]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 15:40:56	PingMonitor[92006]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 15:36:54	PingMonitor[1122]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 15:32:52	PingMonitor[97949]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 15:28:49	PingMonitor[94154]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 15:24:47	PingMonitor[92766]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 15:20:45	PingMonitor[89899]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 15:16:43	PingMonitor[84124]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 15:12:40	PingMonitor[79058]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 15:08:38	PingMonitor[75909]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 15:04:36	PingMonitor[71500]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 15:00:32	PingMonitor[69678]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 14:56:30	PingMonitor[56496]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 14:52:26	PingMonitor[47062]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 14:48:24	PingMonitor[43528]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 14:44:21	PingMonitor[39344]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 14:40:19	PingMonitor[33843]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 14:36:17	PingMonitor[24506]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 14:32:15	PingMonitor[18194]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 14:28:12	PingMonitor[9147]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 14:24:10	PingMonitor[5423]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 14:20:08	PingMonitor[3110]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 14:16:05	PingMonitor[94796]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 14:12:03	PingMonitor[87278]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 14:08:01	PingMonitor[83460]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 14:03:59	PingMonitor[75720]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 13:59:56	PingMonitor[92004]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 13:55:54	PingMonitor[87714]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 13:51:52	PingMonitor[84459]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 13:47:50	PingMonitor[77491]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 13:43:46	PingMonitor[71754]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 13:39:44	PingMonitor[66806]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 13:35:41	PingMonitor[63054]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 13:31:39	PingMonitor[54225]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 13:27:37	PingMonitor[47318]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 13:23:35	PingMonitor[40247]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 13:19:32	PingMonitor[35337]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 13:15:30	PingMonitor[32681]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 13:11:28	PingMonitor[26064]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 13:07:26	PingMonitor[19752]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 13:03:23	PingMonitor[9252]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 12:59:21	PingMonitor[98386]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 12:55:19	PingMonitor[90237]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 12:51:16	PingMonitor[83225]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 12:47:14	PingMonitor[81056]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 12:43:12	PingMonitor[76920]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 12:39:10	PingMonitor[71260]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 12:35:07	PingMonitor[72437]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 12:31:04	PingMonitor[68603]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 12:27:02	PingMonitor[79844]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 12:23:00	PingMonitor[76325]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 12:18:58	PingMonitor[70701]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 12:14:55	PingMonitor[63845]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 12:10:53	PingMonitor[58575]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 12:06:51	PingMonitor[7854]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 12:02:48	PingMonitor[4994]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 11:58:46	PingMonitor[25217]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 11:54:44	PingMonitor[18530]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 11:50:42	PingMonitor[10433]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 11:46:39	PingMonitor[4086]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 11:42:37	PingMonitor[99296]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 11:38:35	PingMonitor[67591]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 11:34:32	PingMonitor[86810]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 11:30:30	PingMonitor[6953]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 11:26:28	PingMonitor[30448]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 11:22:26	PingMonitor[51574]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 11:18:23	PingMonitor[65455]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 11:14:20	PingMonitor[82616]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 11:10:18	PingMonitor[92249]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 11:06:16	PingMonitor[12074]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 11:02:14	PingMonitor[31230]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 10:58:11	PingMonitor[68294]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 10:54:09	PingMonitor[81580]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
May 3 10:50:07	PingMonitor[96706]: is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php

            The NSA is a terrorist organization that must be stopped.

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

              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..

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

                @SkyNET:

                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…

                The NSA is a terrorist organization that must be stopped.

                1 Reply Last reply Reply Quote 0
                • I
                  iyanchevgtbuglaria.com
                  last edited by

                  I'm having the same problem. :-[

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

                    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…

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

                      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…

                      The NSA is a terrorist organization that must be stopped.

                      1 Reply Last reply Reply Quote 0
                      • 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.