No I am not suggesting you add more ntp sticks to the fire.
.. another stick in the fire. why did you install this too? Kind of a rhetorical question as I know you are trying to ensure WireGuard has access.. But truly there are too many ntp packages confusing the issue.
Have you rebooted your router since removing the GUI version Time Sync?
I see the device name clearly, and it should work without the avalanche of errors unless their is a conflict the packages.
I'd suggest making a backup of your conifg and then using this opportunity to upgrade to the latest stable release. Don't keep settings when you do this. Then install only the required pacakges (such as Wireguard and anything else you directly need)... your ntp stuff should work out of the box as long as wireguard doesn't try to start first. Then you just need to make a script to start WG after NTP success... fairly straight forward and shouldn't require installing other pacakges.
No but rebooting now
Ok but i really building my own build,.never had a problem, only here with wg.
If it is only that, it would be great to have script about wg so..
after rebbot, time sync is back in setting system, should I enable it? Cause it seems to have a bug with that one and ntpdate?
If you really want to, sure... but what is the benefit or need here? If you want to create your own custom image, you can do that with the stable release builds (really easy using the online image builder)... working with snapshots has value for some users, but can also be a headache in some situations.
I don't personally have a script for this, but I think it'd be good to get to the baseline of everythign working normally again... a fresh install does tend to fix a lot of underlying problems.
but I have the stable release, I use 2203 instead of master
It's time (no pun intended) to put on the training wheels and load suggestion #1.
From there build out on a known good image. That is beyond my skill set atm.
Sorry for the above link reply showed me a blank response. @psherman
No, you don't have stable. You have a snapshot.
If you had stable, it would be 22.03.0 or 22.03.1, etc. It would not say "SNAPSHOT". The current stable version is 22.03.3
OpenWrt 22.03-SNAPSHOT
we can see snapshot cause it is a custom, but we can see 2203
Right.... you're using a snapshot. You should use stable. Download and install 22.03.3.
No, you see SNAPSHOT because it is a snapshot.
Creating a custom build does not mean it is on snapshot... for example, if I create a custom image with 22.03.3 + Wireguard, it will still report as 22.03.3.
I note you have installed the ISC ntp suite. So have you disabled the busybox sysntpd default implementation?
Thanks @RuralRoots
yep but not sure if it is working.
and btw, I did not enable time synch in system setting in LuCi but if I still see the open wrt server in system, does it mean it is active? Or my ntpdate scripts will be in first?
root@OpenWrt:~# cat /etc/config/system
config system
option hostname 'OpenWrt'
option ttylogin '0'
option log_size '64'
option urandom_seed '0'
option log_proto 'udp'
option conloglevel '8'
option cronloglevel '5'
option zonename 'America/New York'
option timezone 'EST5EDT,M3.2.0,M11.1.0'
config timeserver 'ntp'
list server '0.openwrt.pool.ntp.org'
list server '1.openwrt.pool.ntp.org'
list server '2.openwrt.pool.ntp.org'
list server '3.openwrt.pool.ntp.org'
now I only have the ntpdate
now working
root@OpenWrt:~# ntpd -d -n -q -N -I eth0.2 -p 149.56.37.32 -p 162.159.200.1
ntpd: sending query to 162.159.200.1
ntpd: sending query to 149.56.37.32
ntpd: reply from 162.159.200.1: offset:+0.011417 delay:0.018315 status:0x24 strat:3 refid:0x7a08460a rootdelay:0.026108 reach:0x01
ntpd: reply from 149.56.37.32: offset:+0.022640 delay:0.022291 status:0x24 strat:2 refid:0xfe0aa8c0 rootdelay:0.074678 reach:0x01
ntpd: sending query to 162.159.200.1
ntpd: reply from 162.159.200.1: offset:+0.010950 delay:0.017323 status:0x24 strat:3 refid:0x7a08460a rootdelay:0.026139 reach:0x03
See, you've got it working and ndpdate should show up higher in the sys log.
If the above statement is true, then you can rest for the day and see if upon a sudden power lose or manual pull of the plug, and repower will keep WireGuard happy.
thanks, last thing,
that ip server to sync time that I chose in ntpdate, I have to add it in system setting, right? But it is not enable yet cause I thought it was in conflict with ntpdate
Server: 127.0.0.1
Address: 127.0.0.1:53
Non-authoritative answer:
32.37.56.149.in-addr.arpa name = ip32.ip-149-56-37.net
You configured the ntpd rc.local not the ntpdate. Don't confuse them. 
so Do I have to add the ip somewhere else?
I think I've read that I has to add it to ntp time server but not sure