pfsense 2.6.0 sshguard @ web gui bug/crash
-
Hi folks,
So there seems to be a problem with 2.6.0, the web gui stops working when sshguard is triggered it's like my box is being brute forced but it not I have checked the logs, but when sshguard is triggered it causes the web gui to completely stop working until sshgaurd crashes and restarts. I have verified that ssh is not publicly exposed by using a server off-site in another location.
how i reproduced the issue unplugged the wan rebooted which caused it to stop until I
attempted to log in via ssh with wrong details it causes sshguard to be triggered and stops the web gui loading, once sshguard crashes the web gui then starts working until sshguard is triggered again.I have disabled SSH via console but sshguard is still triggered either with or without WAN being connected. Logs show no signs of brute forced attack. Only started happening on 2.6.0, Output of logs below are when I attempt the brute-force myself.
Apr 13 06:45:38 pfSense sshguard[21085]: 192.168.102.9: unblocking after 158 secs Apr 13 06:48:00 pfSense sshguard[21085]: Exiting on signal. Apr 13 06:48:00 pfSense sshguard[81847]: Now monitoring attacks. Apr 13 06:49:00 pfSense sshguard[81847]: Exiting on signal. Apr 13 06:49:00 pfSense sshguard[86231]: Now monitoring attacks. Apr 13 06:50:00 pfSense sshguard[86231]: Exiting on signal. Apr 13 06:50:00 pfSense sshguard[89077]: Now monitoring attacks.Thanks.
Jack.
-
@violetdragon said in pfsense 2.6.0 sshgaurd @ web gui bug/crash:
192.168.102.9
That's a LAN device that was being blocked.
It's probably nothing, but keep in mind that some one coming from "LAN" wants to use 'ssh', or was attempting to use the GUI access.Why your sshguard received a signal ordering it to stop, I can't tell (that's why logs exists ;)).
I know it starts as soon as the syslog service starts. Ans stops when syslog stops. Both shouldn't restart that often.Also, good news, I'm pretty sure 2.6.0 has no issues, otherwise you wouldn't be the only one seeing what you showed above.
@violetdragon said in pfsense 2.6.0 sshgaurd @ web gui bug/crash:
I have disabled SSH via console but sshguard is still triggered either with or without WAN being connected
sshguard also protects the GUI access.
If it detects a failed login, it can add the IP used to the sshguard pf table, thus blocking further access attempts for a certain time.Normally, you should allow only trusted devices - devices you control - on your LAN.
Use another LAN interface for every body else. On this interface, the first rule just blocks all pfSense SSH/GUI access. -
@gertjan Hi, not sure if you read it properly. IP Address is me reproducing the issue. Issue is when WAN is connected sshguard is imetely triggered but there is nothing in the logs. Disconnected WAN rebooted and I can reproduce the problem when SSH to firewall with multiple failed attempts. Soon as you connect WAN it is triggered but nothing in logs which is the issue.
sshguard is crashing as you can see when it comes back online web GUI starts working again.
-
@violetdragon said in pfsense 2.6.0 sshgaurd @ web gui bug/crash:
Apr 13 06:48:00 pfSense sshguard[21085]: Exiting on signal.
Apr 13 06:48:00 pfSense sshguard[81847]: Now monitoring attacks.
Apr 13 06:49:00 pfSense sshguard[81847]: Exiting on signal.
Apr 13 06:49:00 pfSense sshguard[86231]: Now monitoring attacks.
Apr 13 06:50:00 pfSense sshguard[86231]: Exiting on signal.
Apr 13 06:50:00 pfSense sshguard[89077]: Now monitoring attacks.That's not sshguard crashing, it's being restarted at exactly 1min intervals.
That is usually caused by something rotating the logs but it's odd to see it at 1min intervals.
Are you unable to connect to the gui or ssh when WAN is connected?
Steve
-
@stephenw10 Hi, when it happens I cannot connect to the Gui at all it just sits there then times out. SSH on the other hand works perfectly fine. But I have narrowed it down to sshguard as I triggered it by using false login credentials for SSH but when its triggered no device can connect to the Gui at all. It has started after 2 weeks since updating to 2.6.0 from 2.5.2. It is currently behaving itself.
-
If it is sshguard I would expect all connections to the firewall to be blocked. sshguard monitors login attempts, both via ssh and the webgui, and adds source IPs to the sshguard table after several failed attempts. That table is used in a firewall rule to block all traffic.
The fact you are still able to connect via SSH implies that's not happening.Do connections to the webgui eventually show a 504 or 502 error or just never respond?
Is there anything in the system or webgui logs when this is happening?
Steve
-
@violetdragon said in pfsense 2.6.0 sshgaurd @ web gui bug/crash:
not sure if you read it properly. IP Address is me reproducing the issue
I didn't know that you were using "192.168.102.9" and that was you.
@violetdragon said in pfsense 2.6.0 sshgaurd @ web gui bug/crash:
Disconnected WAN
This happens often ?
I can't test the "remove the WAN" cable, or provoke a WAN disconnect right now, as I use pfSense for a company, and like 'cutting the power', it can be disruptive.I can't tell for sure what happens when WAN goes down, if that initiates a syslog restart.
It's not a real solution of course, but can you keep the WAN up and stable ?
( humm, this does make me think about another recent forum post where I advised the same thing - the advise wasn't well taken )@violetdragon said in pfsense 2.6.0 sshgaurd @ web gui bug/crash:
sshguard is crashing
A process that crashes doesn't log "Exiting on signal" and then exits normally. A crashing process just stop interacting with everything. Maybe the FreeBSD kernel will log a message like "removed process X from the list as it is dead" but that's not what's happening here , according info supplied.
sshguard was told to stop. So it confirms with a log line, and it stops.
Your issue is : why and who stops it.
I presume syslogd.
Why does syslogd restarts ?
I presume some event, like a NIC going down and up, or something else.@violetdragon said in pfsense 2.6.0 sshgaurd @ web gui bug/crash:
still triggered
With triggering you mean stopping and starting, right ?
@violetdragon said in pfsense 2.6.0 sshgaurd @ web gui bug/crash:
comes back online web GUI starts working again
Do you have a console (not ssh) access ?
Can you check if the pfsense gui webser is still running ? Keeps on running ?ps ax | grep 'nginx ' -
@gertjan Hi sorry. What I mean by WAN offline is I unplugged the WAN cable and rebooted the firewall without WAN connected, problem seem to went away and how I triggered the problem was logging into SSH with the wrong information that is all I know right now. Once I reconnected the WAN cable the problem then came back with those in the logs related to sshguard however I disabled SSH via console but the problem still remains the web GUI just completely went unresponsive, I will report back with the logs from what you suggest. It is a strange one.
Thanks.
Jack.
-
@stephenw10 503 errors is when I try and connect through Haproxy with my valid SSL cert but I know that is not the problem as It does the same when connecting using its IP instead of FQDN.
-
Ok. Seeing 50X errors trying to access the GUI is usually an indication php isn't responding. SSH continues to function since it doesn't require php.
I think those sshguard logs are a symptom not a cause here. 1m is probably the minimum log rotation time and that's why you're seeing them. It implies that something is absolutely hammering one of the logs when the WAN is connected. It should be pretty obvious which one of you look in /var/log
Also try running
top -aSHvia ssh when the gui is down. What processes are being used?Steve
-
You can see that the CPU is not pegged, it is behaving itself now as it seems. SSHGuard is not reloading as frequent.
-
Mmm, nothing unexpected shown there. If it's now behaving there wouldn't be though.
I would check the log file though. I bet you will find one of the logs has numerous compressed backups from rotations. I could imagine it being the nginx log if the gui was unavailable.
Steve
-
@stephenw10 Where would the location be of those files ? i was using the auth.log to check.
Thanks.
Jack.
-
/var/log/
-
@gertjan that is where I have been looking, I just took a look at /var/log/nginx/error.log but there the only errors there are is from 2020,
2020/07/31 12:48:14 [crit] 4493#100471: *102827 SSL_write() failed (13: Permission denied) while processing HTTP/2 connection, client: 192.168.1.9, server: 0.0.0.0:4430 2020/08/26 15:32:03 [crit] 8968#100454: *25803 SSL_write() failed (13: Permission denied) while processing HTTP/2 connection, client: 192.168.1.9, server: 0.0.0.0:10443 2020/09/08 04:19:59 [error] 4127#100429: *20842 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 192.168.1.9, server: , request: "POST /acme/acme_certificates.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm.socket", host: "violetdragon.ddns.net:10443", referrer: "https://violetdragon.ddns.net:10443/acme/acme_certificates.php" -
For example on this box I'm doing some OpenVPN testing and have logging turned up and a bunch of clients failing to connect:
[22.05-DEVELOPMENT][admin@plusdev-2.stevew.lan]/root: ls -ls /var/log total 2176 480 -rw------- 1 root wheel 458507 Apr 14 14:19 auth.log 40 -rw------- 1 root wheel 38536 Apr 14 10:00 auth.log.0.bz2 40 -rw------- 1 root wheel 38625 Apr 14 04:52 auth.log.1.bz2 40 -rw------- 1 root wheel 40401 Apr 13 23:46 auth.log.2.bz2 40 -rw-r--r-- 1 root wheel 37447 Apr 12 21:52 bsdinstall_log 16 -rw------- 1 root wheel 12416 Apr 14 13:22 dhcpd.log 12 -rw-r--r-- 1 root wheel 9237 Apr 12 22:27 dmesg.boot 100 -rw------- 1 root wheel 99080 Apr 14 12:42 filter.log 16 -rw------- 1 root wheel 15266 Apr 13 13:14 filter.log.0.bz2 16 -rw------- 1 root wheel 13850 Apr 13 03:54 filter.log.1.bz2 4 -rw------- 1 root wheel 1862 Apr 12 22:27 gateways.log 0 -rw------- 1 root wheel 0 Apr 12 22:27 ipsec.log 0 -rw------- 1 root wheel 0 Apr 12 22:27 l2tps.log 0 -rw-r--r-- 1 root wheel 0 Apr 12 22:15 lastlog 4 drwxr-xr-x 2 root wheel 512 Apr 12 22:09 nginx 108 -rw------- 1 root wheel 108014 Apr 14 14:10 nginx.log 4 drwxr-xr-x 2 root wheel 512 Apr 12 22:09 ntp 376 -rw------- 1 root wheel 382407 Apr 14 12:42 ntpd.log 168 -rw------- 1 root wheel 171541 Apr 14 14:19 openvpn.log 24 -rw------- 1 root wheel 21875 Apr 14 14:15 openvpn.log.0.bz2 24 -rw------- 1 root wheel 21089 Apr 14 14:01 openvpn.log.1.bz2 24 -rw------- 1 root wheel 21162 Apr 14 13:48 openvpn.log.2.bz2 24 -rw------- 1 root wheel 20837 Apr 14 13:35 openvpn.log.3.bz2 24 -rw------- 1 root wheel 20897 Apr 14 13:22 openvpn.log.4.bz2 24 -rw------- 1 root wheel 21290 Apr 14 13:09 openvpn.log.5.bz2 24 -rw------- 1 root wheel 21258 Apr 14 12:56 openvpn.log.6.bz2 0 -rw------- 1 root wheel 0 Apr 12 22:27 poes.log 0 -rw------- 1 root wheel 0 Apr 12 22:27 portalauth.log 0 -rw------- 1 root wheel 0 Apr 12 22:27 ppp.log 4 -rw------- 1 root wheel 2932 Apr 14 09:32 resolver.log 44 -rw------- 1 root wheel 41582 Apr 14 14:14 routing.log 480 -rw------- 1 root wheel 429823 Apr 14 14:19 system.log 8 -rw------- 1 root wheel 4663 Apr 13 14:55 userlog 4 -rw-r--r-- 1 root wheel 394 Apr 14 14:18 utx.lastlogin 4 -rw------- 1 root wheel 284 Apr 14 14:18 utx.log 0 -rw------- 1 root wheel 0 Apr 12 22:27 vpn.log 0 -rw------- 1 root wheel 0 Apr 12 22:27 watchdogd.log 0 -rw------- 1 root wheel 0 Apr 12 22:27 wireless.logIt's rotating the logs every 15min which is quite rapid.
You can see the times there coincide exactly with this in the system log:Apr 14 12:56:00 sshguard 8441 Exiting on signal. Apr 14 12:56:00 sshguard 8983 Now monitoring attacks. Apr 14 13:09:00 sshguard 8983 Exiting on signal. Apr 14 13:09:00 sshguard 54656 Now monitoring attacks. Apr 14 13:22:00 sshguard 54656 Exiting on signal. Apr 14 13:22:00 sshguard 84504 Now monitoring attacks. Apr 14 13:35:00 sshguard 84504 Exiting on signal. Apr 14 13:35:00 sshguard 98800 Now monitoring attacks. Apr 14 13:48:00 sshguard 98800 Exiting on signal. Apr 14 13:48:00 sshguard 60475 Now monitoring attacks. Apr 14 14:01:00 sshguard 60475 Exiting on signal. Apr 14 14:01:00 sshguard 517 Now monitoring attacks. Apr 14 14:15:00 sshguard 517 Exiting on signal. Apr 14 14:15:00 sshguard 53773 Now monitoring attacks.I suspect one of you logs files was rotating every minute and that should give you a good idea of what was happening.
Steve
-
@stephenw10 Urmm strange one, it is behaving itself now, but there aren't any errors in the Nginx error.log recent anyway, i guess ill keep an eye on it but when it does start acting up again i will report back i will also look at top to see if it gives me any errors.
Something i did do though was run a Memtest on the Memory but it passed the tests so not a memory issue.
-
@stephenw10 Not sure if could be related to the Gui or not but the NTP section in the Gui shows no peers then when you go to the NTP under Status it show's that is not running, Haproxy statistics also doing the same, so maybe there could be something borked with the Gui what do you think?
-
What does the ntp log show?
But do you have any log files that have rotated far faster than the others? That's what I'm showing you above. What's the output of:
ls -ls /var/log -
@stephenw10 Heres the output of,
[2.6.0-RELEASE][jack@pfSense.violets.lan]/var/log: ls -ls total 1970 89 -rw------- 1 root wheel 476444 Apr 14 16:07 auth.log 33 -rw------- 1 root wheel 28893 Apr 11 09:56 auth.log.0.bz2 29 -rw------- 1 root wheel 28032 Apr 8 19:11 auth.log.1.bz2 33 -rw------- 1 root wheel 28998 Apr 6 04:29 auth.log.2.bz2 33 -rw------- 1 root wheel 29217 Apr 2 19:54 auth.log.3.bz2 29 -rw------- 1 root wheel 28120 Mar 30 12:00 auth.log.4.bz2 29 -rw------- 1 root wheel 27687 Mar 27 05:35 auth.log.5.bz2 29 -rw------- 1 root wheel 27999 Mar 24 07:37 auth.log.6.bz2 13 -rw-r--r-- 1 root wheel 61784 Jul 11 2020 bsdinstall_log 9 -rw------- 1 root wheel 42842 Apr 14 16:06 dhcpd.log 17 -rw------- 1 root wheel 13920 Apr 14 14:47 dhcpd.log.0.bz2 17 -rw------- 1 root wheel 14055 Apr 13 22:44 dhcpd.log.1.bz2 17 -rw------- 1 root wheel 14856 Apr 13 06:49 dhcpd.log.2.bz2 17 -rw------- 1 root wheel 13473 Apr 12 14:44 dhcpd.log.3.bz2 17 -rw------- 1 root wheel 13258 Apr 11 22:33 dhcpd.log.4.bz2 17 -rw------- 1 root wheel 13449 Apr 11 06:16 dhcpd.log.5.bz2 17 -rw------- 1 root wheel 13433 Apr 10 14:03 dhcpd.log.6.bz2 9 -rw-r--r-- 1 root wheel 12159 Apr 13 06:38 dmesg.boot 33 -rw------- 1 root wheel 149181 Apr 14 16:07 filter.log 33 -rw------- 1 root wheel 29512 Apr 14 16:00 filter.log.0.bz2 29 -rw------- 1 root wheel 28214 Apr 14 15:30 filter.log.1.bz2 33 -rw------- 1 root wheel 29153 Apr 14 15:01 filter.log.2.bz2 29 -rw------- 1 root wheel 28029 Apr 14 14:24 filter.log.3.bz2 33 -rw------- 1 root wheel 29776 Apr 14 13:53 filter.log.4.bz2 33 -rw------- 1 root wheel 29545 Apr 14 13:33 filter.log.5.bz2 33 -rw------- 1 root wheel 28726 Apr 14 13:12 filter.log.6.bz2 41 -rw------- 1 root wheel 465069 Apr 13 06:48 gateways.log 5 -rw------- 1 root wheel 6059 Mar 15 01:13 gateways.log.0.bz2 9 -rw------- 1 root wheel 8179 Mar 15 00:19 gateways.log.1.bz2 9 -rw------- 1 root wheel 7461 Mar 4 11:51 gateways.log.2.bz2 13 -rw------- 1 root wheel 10273 Mar 4 08:56 gateways.log.3.bz2 57 -rw------- 1 root wheel 503298 Apr 14 16:07 haproxy.log 13 -rw------- 1 root wheel 10667 Apr 13 12:23 haproxy.log.0.bz2 17 -rw------- 1 root wheel 15846 Apr 13 07:18 haproxy.log.1.bz2 13 -rw------- 1 root wheel 10079 Apr 12 05:10 haproxy.log.2.bz2 13 -rw------- 1 root wheel 10086 Apr 11 23:49 haproxy.log.3.bz2 21 -rw------- 1 root wheel 18933 Apr 11 13:55 haproxy.log.4.bz2 21 -rw------- 1 root wheel 17074 Apr 10 01:19 haproxy.log.5.bz2 13 -rw------- 1 root wheel 10329 Apr 9 01:13 haproxy.log.6.bz2 1 -rw------- 1 root wheel 0 Apr 13 06:37 ipsec.log 1 -rw------- 1 root wheel 0 Apr 13 06:37 l2tps.log 1 -rw-r--r-- 1 root wheel 0 Jul 11 2020 lastlog 1 drwx------ 2 www www 2 Jan 13 2020 lighttpd 1 drwxr-xr-x 2 root wheel 3 Jul 11 2020 nginx 49 -rw------- 1 root wheel 440586 Apr 14 14:37 nginx.log 13 -rw------- 1 root wheel 9734 Apr 13 07:44 nginx.log.0.bz2 13 -rw------- 1 root wheel 10221 Apr 13 07:11 nginx.log.1.bz2 13 -rw------- 1 root wheel 11284 Apr 13 06:48 nginx.log.2.bz2 17 -rw------- 1 root wheel 13970 Apr 13 05:07 nginx.log.3.bz2 13 -rw------- 1 root wheel 11333 Apr 6 20:20 nginx.log.4.bz2 13 -rw------- 1 root wheel 9552 Apr 4 18:50 nginx.log.5.bz2 13 -rw------- 1 root wheel 9869 Apr 4 18:07 nginx.log.6.bz2 1 drwxr-xr-x 2 root wheel 2 Jul 11 2020 ntp 17 -rw------- 1 root wheel 83456 Apr 14 02:16 ntpd.log 29 -rw------- 1 root wheel 26441 Apr 4 17:01 ntpd.log.0.bz2 1 drwxr-xr-x 2 uucp uucp 2 Jun 24 2021 nut 17 -rw------- 1 root wheel 127699 Apr 14 15:27 openvpn.log 21 -rw------- 1 root wheel 19454 Apr 4 03:43 openvpn.log.0.bz2 9 -rw------- 1 root wheel 7459 Feb 28 14:31 openvpn.log.1.bz2 17 -rw------- 1 root wheel 14950 Feb 25 14:10 openvpn.log.2.bz2 21 -rw------- 1 root wheel 19548 Feb 11 17:19 openvpn.log.3.bz2 21 -rw------- 1 root wheel 19758 Jan 20 09:53 openvpn.log.4.bz2 21 -rw------- 1 root wheel 16680 Dec 26 09:34 openvpn.log.5.bz2 21 -rw------- 1 root wheel 17905 Oct 3 2021 openvpn.log.6.bz2 9 drwxr-xr-x 2 root wheel 12 Apr 14 16:06 pfblockerng 1 -rw------- 1 root wheel 0 Apr 13 06:37 poes.log 13 -rw------- 1 root wheel 11227 Apr 13 06:37 portalauth.log 81 -rw------- 1 root wheel 465398 Apr 13 06:48 ppp.log 25 -rw------- 1 root wheel 22405 Mar 4 12:05 ppp.log.0.bz2 25 -rw------- 1 root wheel 21618 Aug 8 2021 ppp.log.1.bz2 1 drwx------ 4 root wheel 4 Jun 23 2021 radacct 1 -rw------- 1 freeradius freeradius 0 Jun 23 2021 radius.log 1 -rw------- 1 freeradius freeradius 0 Jun 23 2021 radutmp 1 -rw------- 1 freeradius freeradius 0 Jun 23 2021 radwtmp 13 -rw------- 1 root wheel 511488 Jul 11 2020 relayd.log 69 -rw------- 1 root wheel 460822 Apr 14 16:06 resolver.log 21 -rw------- 1 root wheel 20372 Apr 13 07:50 resolver.log.0.bz2 25 -rw------- 1 root wheel 20689 Apr 12 04:32 resolver.log.1.bz2 21 -rw------- 1 root wheel 20227 Apr 10 18:05 resolver.log.2.bz2 25 -rw------- 1 root wheel 20850 Apr 9 07:06 resolver.log.3.bz2 25 -rw------- 1 root wheel 20983 Apr 7 22:32 resolver.log.4.bz2 25 -rw------- 1 root wheel 21109 Apr 6 14:06 resolver.log.5.bz2 25 -rw------- 1 root wheel 20578 Apr 5 08:11 resolver.log.6.bz2 1 -rw------- 1 root wheel 0 Apr 13 06:37 routing.log 9 drwxr-xr-x 3 root wheel 5 Feb 17 2021 snort 1 drwx------ 2 root wheel 3 Dec 17 2020 suricata 21 -rw------- 1 root wheel 129542 Apr 14 16:07 system.log 41 -rw------- 1 root wheel 40644 Apr 14 01:49 system.log.0.bz2 33 -rw------- 1 root wheel 30645 Apr 11 20:35 system.log.1.bz2 33 -rw------- 1 root wheel 30312 Apr 9 07:00 system.log.2.bz2 41 -rw------- 1 root wheel 37309 Apr 6 22:58 system.log.3.bz2 41 -rw------- 1 root wheel 39148 Apr 4 16:35 system.log.4.bz2 33 -rw------- 1 root wheel 30902 Apr 2 08:49 system.log.5.bz2 33 -rw------- 1 root wheel 30102 Mar 30 07:01 system.log.6.bz2 13 -rw------- 1 root wheel 48962 Apr 14 14:29 userlog 5 -rw-r--r-- 1 root wheel 591 Apr 14 16:07 utx.lastlogin 5 -rw------- 1 root wheel 11299 Apr 14 16:07 utx.log 1 -rw------- 1 root wheel 0 Apr 13 06:37 vpn.log 1 -rw------- 1 root wheel 0 Apr 13 06:37 wireless.logNTP log
Apr 13 04:55:19 pfSense ntpd[9625]: Command line: /usr/local/sbin/ntpd -g -c /var/etc/ntpd.conf -p /var/run/ntpd.pid Apr 13 04:55:19 pfSense ntpd[9625]: ---------------------------------------------------- Apr 13 04:55:19 pfSense ntpd[9625]: ntp-4 is maintained by Network Time Foundation, Apr 13 04:55:19 pfSense ntpd[9625]: Inc. (NTF), a non-profit 501(c)(3) public-benefit Apr 13 04:55:19 pfSense ntpd[9625]: corporation. Support and training for ntp-4 are Apr 13 04:55:19 pfSense ntpd[9625]: available at https://www.nwtime.org/support Apr 13 04:55:19 pfSense ntpd[9625]: ---------------------------------------------------- Apr 13 04:55:19 pfSense ntpd[9901]: proto: precision = 0.109 usec (-23) Apr 13 04:55:19 pfSense ntpd[9901]: basedate set to 2021-12-31 Apr 13 04:55:19 pfSense ntpd[9901]: gps base set to 2022-01-02 (week 2191) Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 0 lo0 [::1]:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 1 lo0 [fe80::1%6]:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 2 lo0 127.0.0.1:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 3 lagg0 [fe80::225:90ff:fe26:f40%9]:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 4 lagg0 192.168.1.254:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 5 lagg0 10.10.10.1:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 6 lagg0.50 [fe80::225:90ff:fe26:f40%10]:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 7 lagg0.50 192.168.50.254:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 8 lagg0.60 [fe80::225:90ff:fe26:f40%11]:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 9 lagg0.60 192.168.60.254:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 10 lagg0.70 [fe80::225:90ff:fe26:f40%12]:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 11 lagg0.70 192.168.70.254:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 12 lagg0.80 [fe80::225:90ff:fe26:f40%13]:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 13 lagg0.80 192.168.80.254:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 14 lagg0.90 [fe80::225:90ff:fe26:f40%14]:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 15 lagg0.90 192.168.90.254:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 16 lagg0.100 [fe80::225:90ff:fe26:f40%15]:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 17 lagg0.100 192.168.100.254:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 18 lagg0.101 [fe80::225:90ff:fe26:f40%16]:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 19 lagg0.101 192.168.101.254:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 20 lagg0.102 [fe80::225:90ff:fe26:f40%17]:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 21 lagg0.102 192.168.102.254:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 22 lagg0.102 192.168.102.10:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 23 lagg0.102 192.168.102.11:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 24 lagg0.102 192.168.102.12:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 25 lagg0.104 [fe80::225:90ff:fe26:f40%18]:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 26 lagg0.104 192.168.104.254:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 27 lagg0.105 [fe80::225:90ff:fe26:f40%19]:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 28 lagg0.105 192.168.105.254:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 29 lagg0.106 [fe80::225:90ff:fe26:f40%20]:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 30 lagg0.106 192.168.106.254:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 31 lagg0.103 [fe80::225:90ff:fe26:f40%22]:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 32 lagg0.103 192.168.103.254:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 33 ovpns1 [fe80::225:90ff:fe26:f40%24]:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listen normally on 34 ovpns1 192.168.200.1:123 Apr 13 04:55:19 pfSense ntpd[9901]: Listening on routing socket on fd #55 for interface updates Apr 13 04:55:19 pfSense ntpd[9901]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Apr 13 04:55:19 pfSense ntpd[9901]: 0.0.0.0 c01d 0d kern kernel time sync enabled Apr 13 04:55:19 pfSense ntpd[9901]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Apr 13 04:55:19 pfSense ntpd[9901]: 0.0.0.0 c012 02 freq_set kernel 36.409 PPM Apr 13 04:55:19 pfSense ntpd[9901]: 0.0.0.0 c016 06 restart Apr 13 04:55:20 pfSense ntpd[9901]: Soliciting pool server 81.21.65.169 Apr 13 04:55:21 pfSense ntpd[9901]: Soliciting pool server 85.199.214.101 Apr 13 04:55:21 pfSense ntpd[9901]: Soliciting pool server 185.53.93.157 Apr 13 04:55:22 pfSense ntpd[9901]: Soliciting pool server 129.250.35.250 Apr 13 04:55:22 pfSense ntpd[9901]: Soliciting pool server 162.159.200.1 Apr 13 04:55:22 pfSense ntpd[9901]: Soliciting pool server 134.0.16.1 Apr 13 04:55:23 pfSense ntpd[9901]: Soliciting pool server 81.128.218.110 Apr 13 04:55:23 pfSense ntpd[9901]: Soliciting pool server 217.114.59.3 Apr 13 04:55:23 pfSense ntpd[9901]: Soliciting pool server 2606:4700:f1::123 Apr 13 04:55:28 pfSense ntpd[9901]: 0.0.0.0 c615 05 clock_sync Apr 13 05:07:39 pfSense ntpd[9901]: 81.21.65.169 local addr 10.10.10.1 -> <null> Apr 13 05:19:22 pfSense ntpd[9901]: 217.114.59.3 local addr 10.10.10.1 -> <null> Apr 13 05:19:22 pfSense ntpd[9901]: 81.128.218.110 local addr 10.10.10.1 -> <null> Apr 13 05:19:22 pfSense ntpd[9901]: 134.0.16.1 local addr 10.10.10.1 -> <null> Apr 13 05:19:22 pfSense ntpd[9901]: 162.159.200.1 local addr 10.10.10.1 -> <null> Apr 13 05:19:22 pfSense ntpd[9901]: 185.53.93.157 local addr 10.10.10.1 -> <null> Apr 13 05:19:22 pfSense ntpd[9901]: 85.199.214.101 local addr 10.10.10.1 -> <null> Apr 13 05:20:13 pfSense ntpd[9901]: 0.0.0.0 0618 08 no_sys_peer Apr 13 05:20:13 pfSense ntpd[9901]: 217.114.59.3 local addr 10.10.10.1 -> <null> Apr 13 05:20:26 pfSense ntpd[9901]: Soliciting pool server 81.21.65.169 Apr 13 05:30:34 pfSense ntpd[9901]: 81.21.65.169 local addr 10.10.10.1 -> <null> Apr 13 06:38:12 pfSense ntpd[17974]: ntpd 4.2.8p15@1.3728-o Wed Jan 12 15:39:52 UTC 2022 (1): Starting Apr 13 06:38:12 pfSense ntpd[17974]: Command line: /usr/local/sbin/ntpd -g -q -c /dev/null 216.239.35.0 216.239.35.4 216.239.35.8 216.239.35.12 Apr 13 06:38:12 pfSense ntpd[17974]: ---------------------------------------------------- Apr 13 06:38:12 pfSense ntpd[17974]: ntp-4 is maintained by Network Time Foundation, Apr 13 06:38:12 pfSense ntpd[17974]: Inc. (NTF), a non-profit 501(c)(3) public-benefit Apr 13 06:38:12 pfSense ntpd[17974]: corporation. Support and training for ntp-4 are Apr 13 06:38:12 pfSense ntpd[17974]: available at https://www.nwtime.org/support Apr 13 06:38:12 pfSense ntpd[17974]: ---------------------------------------------------- Apr 13 06:38:12 pfSense ntpd[17974]: proto: precision = 0.188 usec (-22) Apr 13 06:38:12 pfSense ntpd[17974]: line 0 column 0 syntax error, unexpected $end Apr 13 06:38:12 pfSense ntpd[17974]: basedate set to 2021-12-31 Apr 13 06:38:12 pfSense ntpd[17974]: gps base set to 2022-01-02 (week 2191) Apr 13 06:38:12 pfSense ntpd[17974]: Listen and drop on 0 v6wildcard [::]:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen and drop on 1 v4wildcard 0.0.0.0:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 2 lo0 [::1]:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 3 lo0 [fe80::1%6]:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 4 lo0 127.0.0.1:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 5 lagg0 [fe80::225:90ff:fe26:f40%9]:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 6 lagg0 192.168.1.254:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 7 lagg0 10.10.10.1:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 8 lagg0.50 [fe80::225:90ff:fe26:f40%10]:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 9 lagg0.50 192.168.50.254:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 10 lagg0.60 [fe80::225:90ff:fe26:f40%11]:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 11 lagg0.60 192.168.60.254:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 12 lagg0.70 [fe80::225:90ff:fe26:f40%12]:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 13 lagg0.70 192.168.70.254:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 14 lagg0.80 [fe80::225:90ff:fe26:f40%13]:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 15 lagg0.80 192.168.80.254:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 16 lagg0.90 [fe80::225:90ff:fe26:f40%14]:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 17 lagg0.90 192.168.90.254:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 18 lagg0.100 [fe80::225:90ff:fe26:f40%15]:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 19 lagg0.100 192.168.100.254:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 20 lagg0.101 [fe80::225:90ff:fe26:f40%16]:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 21 lagg0.101 192.168.101.254:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 22 lagg0.102 [fe80::225:90ff:fe26:f40%17]:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 23 lagg0.102 192.168.102.254:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 24 lagg0.102 192.168.102.10:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 25 lagg0.102 192.168.102.11:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 26 lagg0.102 192.168.102.12:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 27 lagg0.104 [fe80::225:90ff:fe26:f40%18]:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 28 lagg0.104 192.168.104.254:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 29 lagg0.105 [fe80::225:90ff:fe26:f40%19]:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 30 lagg0.105 192.168.105.254:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 31 lagg0.106 [fe80::225:90ff:fe26:f40%20]:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 32 lagg0.106 192.168.106.254:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 33 lagg0.40 [fe80::225:90ff:fe26:f40%21]:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 34 lagg0.103 [fe80::225:90ff:fe26:f40%22]:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 35 lagg0.103 192.168.103.254:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 36 ovpns1 [fe80::225:90ff:fe26:f40%24]:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listen normally on 37 ovpns1 192.168.200.1:123 Apr 13 06:38:12 pfSense ntpd[17974]: Listening on routing socket on fd #58 for interface updates Apr 13 06:38:42 pfSense ntpd[17974]: ntpd exiting on signal 15 (Terminated) Apr 13 06:38:42 pfSense ntpd[21121]: ntpd 4.2.8p15@1.3728-o Wed Jan 12 15:39:52 UTC 2022 (1): Starting Apr 13 06:38:42 pfSense ntpd[21121]: Command line: /usr/local/sbin/ntpd -g -c /var/etc/ntpd.conf -p /var/run/ntpd.pid Apr 13 06:38:42 pfSense ntpd[21121]: ---------------------------------------------------- Apr 13 06:38:42 pfSense ntpd[21121]: ntp-4 is maintained by Network Time Foundation, Apr 13 06:38:42 pfSense ntpd[21121]: Inc. (NTF), a non-profit 501(c)(3) public-benefit Apr 13 06:38:42 pfSense ntpd[21121]: corporation. Support and training for ntp-4 are Apr 13 06:38:42 pfSense ntpd[21121]: available at https://www.nwtime.org/support Apr 13 06:38:42 pfSense ntpd[21121]: ---------------------------------------------------- Apr 13 06:38:42 pfSense ntpd[21260]: proto: precision = 0.113 usec (-23) Apr 13 06:38:42 pfSense ntpd[21260]: basedate set to 2021-12-31 Apr 13 06:38:42 pfSense ntpd[21260]: gps base set to 2022-01-02 (week 2191) Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 0 lo0 [::1]:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 1 lo0 [fe80::1%6]:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 2 lo0 127.0.0.1:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 3 lagg0 [fe80::225:90ff:fe26:f40%9]:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 4 lagg0 192.168.1.254:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 5 lagg0 10.10.10.1:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 6 lagg0.50 [fe80::225:90ff:fe26:f40%10]:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 7 lagg0.50 192.168.50.254:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 8 lagg0.60 [fe80::225:90ff:fe26:f40%11]:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 9 lagg0.60 192.168.60.254:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 10 lagg0.70 [fe80::225:90ff:fe26:f40%12]:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 11 lagg0.70 192.168.70.254:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 12 lagg0.80 [fe80::225:90ff:fe26:f40%13]:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 13 lagg0.80 192.168.80.254:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 14 lagg0.90 [fe80::225:90ff:fe26:f40%14]:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 15 lagg0.90 192.168.90.254:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 16 lagg0.100 [fe80::225:90ff:fe26:f40%15]:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 17 lagg0.100 192.168.100.254:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 18 lagg0.101 [fe80::225:90ff:fe26:f40%16]:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 19 lagg0.101 192.168.101.254:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 20 lagg0.102 [fe80::225:90ff:fe26:f40%17]:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 21 lagg0.102 192.168.102.254:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 22 lagg0.102 192.168.102.10:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 23 lagg0.102 192.168.102.11:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 24 lagg0.102 192.168.102.12:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 25 lagg0.104 [fe80::225:90ff:fe26:f40%18]:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 26 lagg0.104 192.168.104.254:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 27 lagg0.105 [fe80::225:90ff:fe26:f40%19]:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 28 lagg0.105 192.168.105.254:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 29 lagg0.106 [fe80::225:90ff:fe26:f40%20]:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 30 lagg0.106 192.168.106.254:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 31 lagg0.103 [fe80::225:90ff:fe26:f40%22]:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 32 lagg0.103 192.168.103.254:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 33 ovpns1 [fe80::225:90ff:fe26:f40%24]:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listen normally on 34 ovpns1 192.168.200.1:123 Apr 13 06:38:42 pfSense ntpd[21260]: Listening on routing socket on fd #55 for interface updates Apr 13 06:38:42 pfSense ntpd[21260]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Apr 13 06:38:42 pfSense ntpd[21260]: 0.0.0.0 c01d 0d kern kernel time sync enabled Apr 13 06:38:42 pfSense ntpd[21260]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Apr 13 06:38:42 pfSense ntpd[21260]: 0.0.0.0 c012 02 freq_set kernel 36.409 PPM Apr 13 06:38:42 pfSense ntpd[21260]: 0.0.0.0 c016 06 restart Apr 13 06:38:43 pfSense ntpd[21260]: error resolving pool 0.pfsense.pool.ntp.org: Name does not resolve (8) Apr 13 06:38:50 pfSense ntpd[21260]: error resolving pool 0.uk.pool.ntp.org: Name does not resolve (8) Apr 13 06:38:50 pfSense ntpd[21260]: error resolving pool 1.uk.pool.ntp.org: Name does not resolve (8) Apr 13 06:38:50 pfSense ntpd[21260]: error resolving pool 2.uk.pool.ntp.org: Name does not resolve (8) Apr 13 06:39:47 pfSense ntpd[21260]: error resolving pool 0.pfsense.pool.ntp.org: Name does not resolve (8) Apr 13 06:39:49 pfSense ntpd[21260]: error resolving pool 0.uk.pool.ntp.org: Name does not resolve (8) Apr 13 06:39:51 pfSense ntpd[21260]: error resolving pool 1.uk.pool.ntp.org: Name does not resolve (8) Apr 13 06:39:52 pfSense ntpd[21260]: error resolving pool 2.uk.pool.ntp.org: Name does not resolve (8) Apr 13 06:40:52 pfSense ntpd[21260]: error resolving pool 0.pfsense.pool.ntp.org: Name does not resolve (8) Apr 13 06:40:55 pfSense ntpd[21260]: error resolving pool 1.uk.pool.ntp.org: Name does not resolve (8) Apr 13 06:40:56 pfSense ntpd[21260]: error resolving pool 0.uk.pool.ntp.org: Name does not resolve (8) Apr 13 06:40:59 pfSense ntpd[21260]: error resolving pool 2.uk.pool.ntp.org: Name does not resolve (8) Apr 13 06:41:56 pfSense ntpd[21260]: error resolving pool 0.pfsense.pool.ntp.org: Name does not resolve (8) Apr 13 06:42:00 pfSense ntpd[21260]: error resolving pool 1.uk.pool.ntp.org: Name does not resolve (8) Apr 13 06:42:00 pfSense ntpd[21260]: error resolving pool 0.uk.pool.ntp.org: Name does not resolve (8) Apr 13 06:42:06 pfSense ntpd[21260]: error resolving pool 2.uk.pool.ntp.org: Name does not resolve (8) Apr 13 06:43:02 pfSense ntpd[21260]: error resolving pool 0.pfsense.pool.ntp.org: Name does not resolve (8) Apr 13 06:43:05 pfSense ntpd[21260]: error resolving pool 1.uk.pool.ntp.org: Name does not resolve (8) Apr 13 06:43:06 pfSense ntpd[21260]: error resolving pool 0.uk.pool.ntp.org: Name does not resolve (8) Apr 13 06:43:13 pfSense ntpd[21260]: error resolving pool 2.uk.pool.ntp.org: Name does not resolve (8) Apr 13 06:44:08 pfSense ntpd[21260]: error resolving pool 0.pfsense.pool.ntp.org: Name does not resolve (8) Apr 13 06:44:10 pfSense ntpd[21260]: error resolving pool 1.uk.pool.ntp.org: Name does not resolve (8) Apr 13 06:44:10 pfSense ntpd[21260]: error resolving pool 0.uk.pool.ntp.org: Name does not resolve (8) Apr 13 06:44:18 pfSense ntpd[21260]: error resolving pool 2.uk.pool.ntp.org: Name does not resolve (8) Apr 13 06:45:13 pfSense ntpd[21260]: error resolving pool 0.pfsense.pool.ntp.org: Name does not resolve (8) Apr 13 06:45:14 pfSense ntpd[21260]: error resolving pool 0.uk.pool.ntp.org: Name does not resolve (8) Apr 13 06:45:17 pfSense ntpd[21260]: error resolving pool 1.uk.pool.ntp.org: Name does not resolve (8) Apr 13 06:45:23 pfSense ntpd[21260]: error resolving pool 2.uk.pool.ntp.org: Name does not resolve (8) Apr 13 06:46:20 pfSense ntpd[21260]: error resolving pool 0.uk.pool.ntp.org: Name does not resolve (8) Apr 13 06:46:20 pfSense ntpd[21260]: error resolving pool 0.pfsense.pool.ntp.org: Name does not resolve (8) Apr 13 06:46:23 pfSense ntpd[21260]: error resolving pool 1.uk.pool.ntp.org: Name does not resolve (8) Apr 13 06:46:28 pfSense ntpd[21260]: error resolving pool 2.uk.pool.ntp.org: Name does not resolve (8) Apr 13 06:47:25 pfSense ntpd[21260]: error resolving pool 0.uk.pool.ntp.org: Name does not resolve (8) Apr 13 06:47:25 pfSense ntpd[21260]: error resolving pool 0.pfsense.pool.ntp.org: Name does not resolve (8) Apr 13 06:47:30 pfSense ntpd[21260]: error resolving pool 1.uk.pool.ntp.org: Name does not resolve (8) Apr 13 06:47:35 pfSense ntpd[21260]: error resolving pool 2.uk.pool.ntp.org: Name does not resolve (8) Apr 13 06:48:30 pfSense ntpd[21260]: Soliciting pool server 81.187.240.205 Apr 13 06:48:30 pfSense ntpd[21260]: Soliciting pool server 139.162.219.252 Apr 13 06:48:31 pfSense ntpd[21260]: Soliciting pool server 193.47.147.20 Apr 13 06:48:32 pfSense ntpd[21260]: Soliciting pool server 83.151.207.133 Apr 13 06:48:32 pfSense ntpd[21260]: Soliciting pool server 162.159.200.123 Apr 13 06:48:33 pfSense ntpd[21260]: Soliciting pool server 85.199.214.100 Apr 13 06:48:34 pfSense ntpd[21260]: Soliciting pool server 80.82.244.120 Apr 13 06:48:35 pfSense ntpd[21260]: Soliciting pool server 80.93.163.202 Apr 13 06:48:42 pfSense ntpd[21260]: 0.0.0.0 061c 0c clock_step -0.494278 s Apr 13 06:48:42 pfSense ntpd[21260]: 0.0.0.0 0615 05 clock_sync Apr 13 06:48:42 pfSense ntpd[21260]: receive: Unexpected origin timestamp 0xe600e2ba.e27741ad does not match aorg 0000000000.00000000 from server@193.47.147.20 xmt 0xe600e2ba.67a7e2eb Apr 13 06:48:43 pfSense ntpd[21260]: 0.0.0.0 c618 08 no_sys_peer Apr 13 06:58:19 pfSense ntpd[21260]: 80.82.244.120 local addr 10.10.10.1 -> <null> Apr 13 07:13:25 pfSense ntpd[21260]: 81.187.240.205 local addr 10.10.10.1 -> <null> Apr 13 07:14:54 pfSense ntpd[21260]: 80.93.163.202 local addr 10.10.10.1 -> <null> Apr 13 07:31:36 pfSense ntpd[21260]: 139.162.219.252 local addr 10.10.10.1 -> <null> Apr 14 02:04:13 pfSense ntpd[21260]: 162.159.200.123 local addr 10.10.10.1 -> <null> Apr 14 02:04:24 pfSense ntpd[21260]: 193.47.147.20 local addr 10.10.10.1 -> <null> Apr 14 02:04:57 pfSense ntpd[21260]: Soliciting pool server 46.227.207.91 Apr 14 02:04:58 pfSense ntpd[21260]: Soliciting pool server 85.199.214.98 Apr 14 02:04:59 pfSense ntpd[21260]: Soliciting pool server 5.101.146.245 Apr 14 02:05:00 pfSense ntpd[21260]: Soliciting pool server 85.199.214.102 Apr 14 02:05:01 pfSense ntpd[21260]: Soliciting pool server 178.79.155.116 Apr 14 02:05:02 pfSense ntpd[21260]: Soliciting pool server 90.255.244.219 Apr 14 02:15:08 pfSense ntpd[21260]: 90.255.244.219 local addr 10.10.10.1 -> <null> Apr 14 02:15:09 pfSense ntpd[21260]: 5.101.146.245 local addr 10.10.10.1 -> <null> Apr 14 02:15:16 pfSense ntpd[21260]: 178.79.155.116 local addr 10.10.10.1 -> <null> Apr 14 02:16:14 pfSense ntpd[21260]: 46.227.207.91 local addr 10.10.10.1 -> <null>
