5. Strange state table bug since 2.1.5 to 2.2 RC nanobsd alix

Strange state table bug since 2.1.5 to 2.2 RC nanobsd alix

  • X

    i have noticed this strange bug since the last two major pfsense releases on the nanobsd alix. What happens is when its booted up and working and then if there is a sudden power loss and after a while the power returns and it auto starts, that time it boots up fine but soon after that the state table entries just keep rising till they go more than 90% and completely slow down the system, upon checking the state table entries i found just normal loopback ip entries, probably the system is stuck in some loop causing such entries and then to resolve them is to select reboot from the web gui or the serial console and then its all back to normal.

    any idea whats causing this?

    0
  • X

    the other issues is the state table entries dont expire also untill its rebooted normally, happens on nanobsd only

    0
  • C

    what exactly do those states look like?

    0
  • X

    well i tried to recreate the situation, didnt happen for now so give me some time and ill test it a few more time and get u the results

    0
  • X

    i spoke too soon, it happens after like 5mins or so, entries r related to DNS from loopback to loopback IP, it floods the state table with those entries and making everything slow






    0
  • C

    Something is causing a significant number of DNS lookups. You using Unbound or dnsmasq?

    0
  • X

    on 2.1.5 it used to happen with dnsmasq and now with RC 2.2 im using unbound and its still happening

    0
  • C

    Not likely to matter which, mostly wanted to know for purposes of suggestions from there. Add in the advanced box:

    log-queries: yes

    so it logs all your queries and see what it is that's being resolved. That should help determine where all those DNS queries are coming from and what they are.

    0
  • X

    where is the log created and stored?

    0
  • C

    Resolver log.

    0
  • X

    the problem is as soon as i enter that in custom box and hit save and apply, resolver stops working and ig et this error

    
php-fpm[83585]: /services_unbound.php: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '/var/unbound/unbound.conf:89: error: syntax error read /var/unbound/unbound.conf failed: 1 errors in configuration file [1419919488] unbound[34655:0] fatal error: Could not read config file: /var/unbound/unbound.conf'
    0
  • C

    Ah, yeah that ends up in the wrong section for that purpose. If you're not reliant on anything in unbound only, easiest thing to try at this instant is switching back to DNS Forwarder, and adding advanced option:

    log-queries

    That will definitely work. Same log.

    0
  • X
     

    php-fpm[27874]: /services_unbound.php: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '/var/unbound/unbound.conf:89: error: unknown keyword 'log-queries' read /var/unbound/unbound.conf failed: 1 errors in configuration file [1419921946] unbound[32026:0] fatal error: Could not read config file: /var/unbound/unbound.conf'
    0
  • C

    That reply was entirely unclear. I meant not unbound, switch back to DNS Forwarder and do that. Original post edited to correct.

    0
  • X

    oh ok, trying it

    0
  • X

    tried it and the log shows this, the address its trying to resolve in endless loop is relating to an alias i have with domain names relating to a openvpn tunnel with expressvpn

    Dec 30 11:41:39 	kernel: [zone: pf states] PF states limit reached

    Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster2.expressnetwork.net is 37.58.52.31
Dec 30 11:41:22 	dnsmasq[31602]: overflow: 4 log entries lost
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster.expressnetwork.net is 46.165.208.224
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster.expressnetwork.net is 46.165.251.82
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster.expressnetwork.net is 46.165.251.70
Dec 30 11:41:22 	dnsmasq[31602]: overflow: 7 log entries lost
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster4.expressnetwork.net is 46.165.251.82
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster4.expressnetwork.net is 37.58.52.31
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster4.expressnetwork.net is 46.165.251.70
Dec 30 11:41:22 	dnsmasq[31602]: overflow: 4 log entries lost
Dec 30 11:41:22 	dnsmasq[31602]: query[A] germany-cluster3.expressnetwork.net from 127.0.0.1
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster3.expressnetwork.net is 46.165.208.224
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster3.expressnetwork.net is 46.165.251.82
Dec 30 11:41:22 	dnsmasq[31602]: overflow: 3 log entries lost
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster2.expressnetwork.net is 37.58.52.31
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster2.expressnetwork.net is 46.165.208.224
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster2.expressnetwork.net is 46.165.251.82
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster2.expressnetwork.net is 46.165.251.70
Dec 30 11:41:22 	dnsmasq[31602]: overflow: 8 log entries lost
Dec 30 11:41:22 	dnsmasq[31602]: query[AAAA] germany-cluster3.expressnetwork.net from 127.0.0.1
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster3.expressnetwork.net is NODATA-IPv6
Dec 30 11:41:22 	dnsmasq[31602]: overflow: 3 log entries lost
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster4.expressnetwork.net is 46.165.208.224
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster4.expressnetwork.net is 46.165.251.82
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster4.expressnetwork.net is 37.58.52.31
Dec 30 11:41:22 	dnsmasq[31602]: overflow: 2 log entries lost
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster.expressnetwork.net is NODATA-IPv6
Dec 30 11:41:22 	dnsmasq[31602]: overflow: 1 log entries lost
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster3.expressnetwork.net is 37.58.52.31
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster3.expressnetwork.net is 46.165.208.224
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster3.expressnetwork.net is 46.165.251.82
Dec 30 11:41:22 	dnsmasq[31602]: overflow: 20 log entries lost
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster4.expressnetwork.net is 46.165.251.70
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster4.expressnetwork.net is 46.165.208.224
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster4.expressnetwork.net is 46.165.251.82
Dec 30 11:41:22 	dnsmasq[31602]: overflow: 16 log entries lost
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster4.expressnetwork.net is NODATA-IPv6
Dec 30 11:41:22 	dnsmasq[31602]: query[A] germany-cluster.expressnetwork.net from 127.0.0.1
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster.expressnetwork.net is 46.165.208.224
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster.expressnetwork.net is 46.165.251.82
Dec 30 11:41:22 	dnsmasq[31602]: overflow: 3 log entries lost
Dec 30 11:41:22 	dnsmasq[31602]: query[AAAA] germany-cluster3.expressnetwork.net from 127.0.0.1
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster3.expressnetwork.net is NODATA-IPv6
Dec 30 11:41:22 	dnsmasq[31602]: overflow: 12 log entries lost
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster3.expressnetwork.net is 46.165.251.82
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster3.expressnetwork.net is 46.165.251.70
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster3.expressnetwork.net is 37.58.52.31
Dec 30 11:41:22 	dnsmasq[31602]: overflow: 9 log entries lost
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster.expressnetwork.net is 37.58.52.31
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster.expressnetwork.net is 46.165.208.224
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster.expressnetwork.net is 46.165.251.82
Dec 30 11:41:22 	dnsmasq[31602]: overflow: 6 log entries lost
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster2.expressnetwork.net is NODATA-IPv6
Dec 30 11:41:22 	dnsmasq[31602]: query[A] germany-cluster4.expressnetwork.net from 127.0.0.1
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster4.expressnetwork.net is 46.165.251.82
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster4.expressnetwork.net is 37.58.52.31
Dec 30 11:41:22 	dnsmasq[31602]: overflow: 12 log entries lost
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster2.expressnetwork.net is 37.58.52.31
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster2.expressnetwork.net is 46.165.208.224
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster2.expressnetwork.net is 46.165.251.82
Dec 30 11:41:22 	dnsmasq[31602]: overflow: 4 log entries lost
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster.expressnetwork.net is 46.165.251.70
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster.expressnetwork.net is 37.58.52.31
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster.expressnetwork.net is 46.165.208.224
Dec 30 11:41:22 	dnsmasq[31602]: overflow: 4 log entries lost
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster3.expressnetwork.net is NODATA-IPv6
Dec 30 11:41:22 	dnsmasq[31602]: query[AAAA] germany-cluster2.expressnetwork.net from 127.0.0.1
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster2.expressnetwork.net is NODATA-IPv6
Dec 30 11:41:22 	dnsmasq[31602]: overflow: 2 log entries lost
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster4.expressnetwork.net is 46.165.251.82
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster4.expressnetwork.net is 37.58.52.31
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster4.expressnetwork.net is 46.165.251.70
Dec 30 11:41:22 	dnsmasq[31602]: overflow: 5 log entries lost
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster3.expressnetwork.net is 37.58.52.31
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster3.expressnetwork.net is 46.165.208.224
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster3.expressnetwork.net is 46.165.251.82
Dec 30 11:41:22 	dnsmasq[31602]: overflow: 7 log entries lost
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster4.expressnetwork.net is NODATA-IPv6
Dec 30 11:41:22 	dnsmasq[31602]: query[A] germany-cluster.expressnetwork.net from 127.0.0.1
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster.expressnetwork.net is 46.165.251.82
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster.expressnetwork.net is 46.165.251.70
Dec 30 11:41:22 	dnsmasq[31602]: overflow: 7 log entries lost
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster2.expressnetwork.net is NODATA-IPv6
Dec 30 11:41:22 	dnsmasq[31602]: query[A] germany-cluster4.expressnetwork.net from 127.0.0.1
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster4.expressnetwork.net is 46.165.251.70
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster4.expressnetwork.net is 46.165.208.224
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster4.expressnetwork.net is 46.165.251.82
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster4.expressnetwork.net is 37.58.52.31
Dec 30 11:41:22 	dnsmasq[31602]: overflow: 3 log entries lost
Dec 30 11:41:22 	dnsmasq[31602]: query[A] germany-cluster3.expressnetwork.net from 127.0.0.1
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster3.expressnetwork.net is 46.165.251.70
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster3.expressnetwork.net is 37.58.52.31
Dec 30 11:41:22 	dnsmasq[31602]: overflow: 8 log entries lost
Dec 30 11:41:22 	dnsmasq[31602]: cached germany-cluster4.expressnetwork.net is NODATA-IPv6

    now no idea why does it go in a loop, probably some bug relating to aliases

    0
  • X

    the strange thing is this happens when there is power failure or power cord is pulled and reconnected but doesnt happen when its gracefully shutdown or rebooted

    0
  • C

    What are the contents of the alias in question?

    0
  • X

    below


    0
  • C

    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?

    0
  • X

    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


    0
  • X

    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.
    0
  • X

    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>
    0
  • C

    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.

    0
  • X

    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

    0
  • C

    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?

    0
  • X

    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

    0
  • C

    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.

    0
  • X

    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

    0
Log in to reply
 

Products

Services

Support

News

Resources

Company

Our Mission

We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

Subscribe to our Newsletter

Product information, software announcements, and special offers. See our newsletter archive for past announcements.

© Copyright 2002 - 2019 Rubicon Communications, LLC | Privacy Policy