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

    Strange state table bug since 2.1.5 to 2.2 RC nanobsd alix

    2.2 Snapshot Feedback and Problems - RETIRED
    2
    29
    4.4k
    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.
    • C
      cmb
      last edited by

      Does something else happen in the event of power failure, like the modem also losing power and potentially not being up when the firewall boots so it has no Internet connectivity initially? Seems likely there is something other than just power failure happening that's making a difference. I can yank the plug on a system with the same alias configured and it's fine. No difference in behavior than a clean shut down.

      All 4 of those hostnames resolve to the same 4 IPs. Not sure if that's somehow related, but doesn't seem to be an issue for me.

      The dnsmasq logs are probably so verbose you're missing any logging from filterdns. Try disabling query logging now that we know where the queries are coming from, and then try to replicate. Once you can replicate, what logs do you have in the resolver log from filterdns?

      1 Reply Last reply Reply Quote 0
      • X
        xbipin
        last edited by

        ill try to do that and get back to to u, meanwhile i also have this rule under floating tab relating to that alias as a match

        no the modem remains on and pfsense connects as soon as it reboots

        CropperCapture[2].jpg
        CropperCapture[2].jpg_thumb

        1 Reply Last reply Reply Quote 0
        • X
          xbipin
          last edited by

          tried it and got this in log

          Jan 1 04:01:55 	filterdns: adding entry 37.58.52.31 to table ExpressVPN2 on host germany-cluster.expressnetwork.net
Jan 1 04:01:55 	filterdns: adding entry 46.165.208.224 to table ExpressVPN2 on host germany-cluster.expressnetwork.net
Jan 1 04:01:55 	filterdns: adding entry 46.165.251.70 to table ExpressVPN2 on host germany-cluster.expressnetwork.net
Jan 1 04:01:55 	filterdns: adding entry 46.165.251.82 to table ExpressVPN2 on host germany-cluster.expressnetwork.net
Jan 1 04:01:55 	filterdns: adding entry 46.165.251.70 to table ExpressVPN2 on host germany-cluster3.expressnetwork.net
Jan 1 04:01:55 	filterdns: adding entry 46.165.208.224 to table ExpressVPN2 on host germany-cluster4.expressnetwork.net
Jan 1 04:01:55 	filterdns: adding entry 46.165.251.70 to table ExpressVPN2 on host germany-cluster4.expressnetwork.net
Jan 1 04:01:55 	filterdns: adding entry 37.58.52.31 to table ExpressVPN2 on host germany-cluster3.expressnetwork.net
Jan 1 04:01:55 	filterdns: adding entry 46.165.208.224 to table ExpressVPN2 on host germany-cluster3.expressnetwork.net
Jan 1 04:01:55 	filterdns: adding entry 46.165.251.82 to table ExpressVPN2 on host germany-cluster3.expressnetwork.net
Jan 1 04:01:55 	filterdns: adding entry 46.165.251.82 to table ExpressVPN2 on host germany-cluster4.expressnetwork.net
Jan 1 04:01:55 	filterdns: adding entry 37.58.52.31 to table ExpressVPN2 on host germany-cluster4.expressnetwork.net
Jan 1 04:02:04 	dnsmasq[29174]: started, version 2.72 cachesize 10000
Jan 1 04:02:04 	dnsmasq[29174]: compile time options: IPv6 GNU-getopt no-DBus i18n IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth DNSSEC loop-detect
Jan 1 04:02:04 	dnsmasq[29174]: reading /etc/resolv.conf
Jan 1 04:02:04 	dnsmasq[29174]: ignoring nameserver 127.0.0.1 - local interface
Jan 1 04:02:04 	dnsmasq[29174]: using nameserver 213.42.20.20#53
Jan 1 04:02:04 	dnsmasq[29174]: using nameserver 195.229.241.222#53
Jan 1 04:02:04 	dnsmasq[29174]: using nameserver 8.8.8.8#53
Jan 1 04:02:04 	dnsmasq[29174]: using nameserver 8.8.4.4#53
Jan 1 04:02:04 	dnsmasq[29174]: read /etc/hosts - 3 addresses
Jan 1 04:02:05 	filterdns: adding entry 46.165.251.70 to table ExpressVPN2 on host germany-cluster2.expressnetwork.net
Jan 1 04:02:05 	filterdns: adding entry 46.165.251.82 to table ExpressVPN2 on host germany-cluster2.expressnetwork.net
Jan 1 04:02:05 	filterdns: adding entry 46.165.208.224 to table ExpressVPN2 on host germany-cluster2.expressnetwork.net
Jan 1 04:02:05 	filterdns: adding entry 37.58.52.31 to table ExpressVPN2 on host germany-cluster2.expressnetwork.net
Dec 31 09:52:54 	dnsmasq[29174]: reading /etc/resolv.conf
Dec 31 09:52:54 	dnsmasq[29174]: ignoring nameserver 127.0.0.1 - local interface
Dec 31 09:52:54 	dnsmasq[29174]: using nameserver 213.42.20.20#53
Dec 31 09:52:54 	dnsmasq[29174]: using nameserver 195.229.241.222#53
Dec 31 09:52:54 	dnsmasq[29174]: using nameserver 8.8.8.8#53
Dec 31 09:52:54 	dnsmasq[29174]: using nameserver 8.8.4.4#53
Dec 31 09:53:21 	dnsmasq[29174]: reading /etc/resolv.conf
Dec 31 09:53:21 	dnsmasq[29174]: ignoring nameserver 127.0.0.1 - local interface
Dec 31 09:53:21 	dnsmasq[29174]: using nameserver 213.42.20.20#53
Dec 31 09:53:21 	dnsmasq[29174]: using nameserver 195.229.241.222#53
Dec 31 09:53:21 	dnsmasq[29174]: using nameserver 8.8.8.8#53
Dec 31 09:53:21 	dnsmasq[29174]: using nameserver 8.8.4.4#53
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster4.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster4.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster4.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster2.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster4.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster4.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster2.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster2.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster2.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster2.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster2.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster2.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster2.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster2.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster4.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster2.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster4.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster2.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster2.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster4.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster4.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster4.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster2.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster4.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster2.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster4.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster4.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster4.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster4.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster2.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster2.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster2.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster2.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster2.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster2.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster3.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster2.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster2.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster2.expressnetwork.net will retry later again.
Dec 31 09:57:38 	filterdns: failed to resolve host germany-cluster.expressnetwork.net will retry later again.
Dec 31 09:57:39 	filterdns: failed to resolve host germany-cluster2.expressnetwork.net will retry later again.
Dec 31 09:57:39 	filterdns: failed to resolve host germany-cluster.expressnetwork.net will retry later again.
          1 Reply Last reply Reply Quote 0
          • X
            xbipin
            last edited by

            also found this entry in my config file, no idea if its correct or no, in the web gui i have just left it empty for defaults

            <aliasesresolveinterval></aliasesresolveinterval>
            1 Reply Last reply Reply Quote 0
            • C
              cmb
              last edited by

              The log goes from Dec 31 09:52:54 to Jan 1 04:02:05 as if the system's time jumped ~18 hours all at once (though it doesn't show the year, so it could be skipping years too). Does that system not have a functional CMOS battery so it's losing date and time when it loses power? Maybe that's the power loss difference.

              1 Reply Last reply Reply Quote 0
              • X
                xbipin
                last edited by

                actually its alix without a battery backup so when it reboots, it connects to the internet and then syncs the time using ntp so that jump happens everytime

                the jump is from jan 1st to dec 31st as when it reboots it starts with jan 1st and after it syncs the time it shows the proper time

                year doesnt show in any of the system log tabs

                1 Reply Last reply Reply Quote 0
                • C
                  cmb
                  last edited by

                  Oh so it's a major jump forward in time then. That's likely why, it sees all that time go by and maybe creates as many events as it would if the clock ran normally for the same period of time.

                  It's not something that can be replicated by setting a running system's date and time years into the past, restarting relevant services, then bringing its date back up to now. I don't have a system handy where I can replicate that scenario of it not having the proper time at boot then changing significantly.

                  It should keep its date and time cross-reboots if it doesn't lose power, which should narrow down the exact cause. Can you confirm that jump in time doesn't happen on a normal reboot?

                  1 Reply Last reply Reply Quote 0
                  • X
                    xbipin
                    last edited by

                    i just tried a normal reboot and it seems time is kept intact with a reboot but with power loss it resets so i guess thats the main issue, u could try and add code such that once internet is connected to sync the time using ntp first and then follow the rest of the boot or probably kill the event loop for a period of time till its synced or something on those lines as the older alix didnt have a cmos battery nor any provision to add one by hand

                    1 Reply Last reply Reply Quote 0
                    • C
                      cmb
                      last edited by

                      I take back the part about not being able to replicate, I wasn't waiting long enough apparently. A few minutes after that post, the system where I changed the time years back then forward did the same thing.
                      https://redmine.pfsense.org/issues/4166

                      That's a rare circumstance, and I'm not sure it's a regression from earlier versions though I haven't tried anything pre-2.2. Are you sure it's something new after you upgraded? Same config was in place pre-upgrade?

                      Given the rarity, and the fact it recovers on its own then continues to work fine, it's not likely that gets addressed in 2.2. Set target to 2.2.1.

                      1 Reply Last reply Reply Quote 0
                      • X
                        xbipin
                        last edited by

                        well its the same from past many pfsense major releases, but power failure are a rare thing in my location so i was living with it and few other newer alix boxes i installed globally later on came with the cmos battery so they didnt suffer this untill a few of my full installs had a failed battery and the location they were in had frequent power failures so it ended up like a nuisance so i thought of bringing this up because i wasnt sure if it was the battery or some other rare bug with state tables because i was seeing this issue more often in the full installs so tried the same on my alix and i was convinced to get this fixed once and for all.

                        now that we know its the battery i hope it gets fixed soon

                        bytheway it takes ages on the alix to recover, full installs still recover quicker. config was same from the last 3 major releases and all have this issue, it happens only after like 5-9mins when booting from power failure and rest of the components work fine without any issues when time jumps

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post