Has anyone used v4.6.2 of the RAK7289v2 build? I’m having clock and networking issues:
Thu Jan 23 12:17:17 2025 user.notice firewall: Reloading firewall due to ifup of wan6 (eth0.1)
Thu Jan 23 12:17:54 2025 kern.warn kernel: [ 137.983947] done.
Thu Jan 23 12:17:54 2025 kern.notice kernel: [ 137.987805] jffs2: notice: (2467) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
Thu Jan 23 12:17:55 2025 daemon.info mount_root: performing overlay whiteout
Thu Jan 23 12:17:55 2025 kern.warn kernel: [ 138.362231] overlayfs: upper fs does not support tmpfile.
Thu Jan 23 12:17:55 2025 daemon.info mount_root: synchronizing overlay
Thu Jan 23 12:17:55 2025 daemon.err mount_root: failed to sync jffs2 overlay
Thu Jan 23 12:17:55 2025 daemon.notice procd: /etc/rc.d/S96led: setting up led wifi
Thu Jan 23 12:17:55 2025 daemon.notice procd: /etc/rc.d/S96led: setting up led eth
Thu Jan 23 12:17:56 2025 user.err : jail: failed to load dependencies
Thu Jan 23 12:18:00 2025 daemon.info procd: - init complete -
Thu Jan 23 12:18:00 2025 daemon.info urandom_seed[4094]: Seed saved (/etc/urandom.seed)
Thu Jan 23 12:18:01 2025 user.err : jail: failed to load dependencies
Thu Jan 23 12:18:06 2025 user.err : jail: failed to load dependencies
Thu Jan 23 12:18:11 2025 user.err : jail: failed to load dependencies
Thu Jan 23 12:18:16 2025 user.err : jail: failed to load dependencies
Thu Jan 23 12:18:21 2025 user.err : jail: failed to load dependencies
Thu Jan 23 12:18:21 2025 daemon.info procd: Instance sysntpd::instance1 s in a crash loop 6 crashes, 0 seconds since last crash
Not sure why it is launching sysntpd when ntpd is already running:
Mon Sep 23 12:35:55 2024 daemon.debug ntpd[2038]: new interface(s) found: waking up resolver
Mon Sep 23 12:35:57 2024 daemon.notice ntpd[2038]: ntpd exiting on signal 15 (Terminated)
Mon Sep 23 12:35:57 2024 daemon.info ntpd[2038]: 127.127.28.0 local addr 127.0.0.1 -> <null>
Mon Sep 23 12:35:57 2024 daemon.info ntpd[2038]: 162.159.200.1 local addr 192.168.1.107 -> <null>
Mon Sep 23 12:35:57 2024 daemon.info ntpd[2038]: 193.136.152.71 local addr 192.168.1.107 -> <null>
Mon Sep 23 12:35:57 2024 daemon.info ntpd[2038]: 91.209.16.78 local addr 192.168.1.107 -> <null>
Mon Sep 23 12:35:57 2024 daemon.info ntpd[2038]: 193.136.164.4 local addr 192.168.1.107 -> <null>
Mon Sep 23 12:35:58 2024 daemon.notice ntpd[3143]: ntpd 4.2.8p17@1.4004-o Mon Sep 23 12:34:46 UTC 2024 (1): Starting
Mon Sep 23 12:35:58 2024 daemon.notice ntpd[3143]: Command line: /sbin/ntpd -g -u ntp:ntp -p /var/run/ntpd.pid -n -c /var/etc/ntpd.conf
Mon Sep 23 12:35:58 2024 daemon.notice ntpd[3143]: ----------------------------------------------------
Mon Sep 23 12:35:58 2024 daemon.notice ntpd[3143]: ntp-4 is maintained by Network Time Foundation,
Mon Sep 23 12:35:58 2024 daemon.notice ntpd[3143]: Inc. (NTF), a non-profit 501(c)(3) public-benefit
Mon Sep 23 12:35:58 2024 daemon.notice ntpd[3143]: corporation. Support and training for ntp-4 are
Mon Sep 23 12:35:58 2024 daemon.notice ntpd[3143]: available at https://www.nwtime.org/support
Mon Sep 23 12:35:58 2024 daemon.notice ntpd[3143]: ----------------------------------------------------
Mon Sep 23 12:35:58 2024 daemon.notice ntpd[3143]: DEBUG behavior is enabled - a violation of any
Mon Sep 23 12:35:58 2024 daemon.notice ntpd[3143]: diagnostic assertion will cause ntpd to abort
Mon Sep 23 12:35:58 2024 daemon.info ntpd[3143]: proto: precision = 6.106 usec (-17)
Mon Sep 23 12:35:58 2024 daemon.info ntpd[3143]: basedate set to 2024-09-11
Mon Sep 23 12:35:58 2024 daemon.info ntpd[3143]: gps base set to 2024-09-15 (week 2332)
Mon Sep 23 12:35:58 2024 daemon.info ntpd[3143]: Listen and drop on 0 v6wildcard [::]:123
Mon Sep 23 12:35:58 2024 daemon.info ntpd[3143]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Mon Sep 23 12:35:58 2024 daemon.info ntpd[3143]: Listen normally on 2 lo 127.0.0.1:123
Mon Sep 23 12:35:58 2024 daemon.info ntpd[3143]: Listen normally on 3 eth0.1 192.168.1.107:123
Mon Sep 23 12:35:58 2024 daemon.info ntpd[3143]: Listen normally on 4 phy0-ap0 192.168.0.1:123
Mon Sep 23 12:35:58 2024 daemon.info ntpd[3143]: Listen normally on 5 lo [::1]:123
Mon Sep 23 12:35:58 2024 daemon.info ntpd[3143]: Listen normally on 6 eth0 [fe80::8c69:e8ff:fe2a:a44a%2]:123
Mon Sep 23 12:35:58 2024 daemon.info ntpd[3143]: Listen normally on 7 br-lan [fe80::8c69:e8ff:fe2a:a44a%5]:123
Mon Sep 23 12:35:58 2024 daemon.info ntpd[3143]: Listen normally on 8 eth0.1 [fe80::ae1f:9ff:fe18:a0a2%7]:123
Mon Sep 23 12:35:58 2024 daemon.info ntpd[3143]: Listen normally on 9 phy0-ap0 [fe80::ae1f:9ff:fe18:a0a3%8]:123
Mon Sep 23 12:35:58 2024 daemon.info ntpd[3143]: Listening on routing socket on fd #58 for interface updates
Mon Sep 23 12:35:58 2024 daemon.info ntpd[3143]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Mon Sep 23 12:35:58 2024 daemon.info ntpd[3143]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Thu Jan 23 12:17:02 2025 daemon.info dnsmasq[1]: exiting on receipt of SIGTERM
Thu Jan 23 12:17:02 2025 cron.err crond[2188]: time disparity of 175661 minutes detected
I reverted back to 4.5.2 which was preloaded on the gateways, and don’t see any errors, except that my border gateway time is stuck at 1999:
