Unable to sync the system clock of jeston orin to internet time

Hi,

I have already looked related threads to the subject, although the error still persists. When I enter timedatectl the ntp is active but the clock is not synchronized to the internet time. Any help would be appreciated.

Hi, I’m facing issues regarding synchronizing the date and time of my jetson orin according to the internet time. PFA the screenshots below.

Hi,
We don’t see the issue on AGX Orin developer kit. Would be great if you can try developer kit with latest Jetpack 6.1.

My jetpack version is 5.1, is there any way I can sync the time on this version? Or I’ll have to reflash the orin and upgrade the jetpack?

Hi, I did update the development kit to jetpack 6.1 , the issue still persists.

Hi,
Please check if you can replicate it on developer kit. If yes, please share the steps and we can set up and try.

Your timedatectl shows System clock synchronized: No

make sure timesyncd is running

systemctl status systemd-timesyncd.service

run these 3 commands to confirm configuration.

timedatectl set-ntp true

Set the system clock to the correct time. update to your current time.

timedatectl set-time “2024-11-06 18:02:12”

Takes a boolean argument. If “0”, the system is configured to maintain the RTC in universal time. according to man that is preferred.

timedatectl set-local-rtc 0 --adjust-system-clock

Yes, I had previously tried all these commands , although the problem still persists even after upgrading the jetpack. Here are the screenshots. Are there anymore settings that I need to configure?

1 Like

More you could try:

  1. If you have chrony installed, uninstall it.

  2. timedatectl set-ntp true

  3. perhaps edit /etc/systemd/timesyncd.conf.d/nv-fallback-ntp.conf and change these lines to this.
    [Time]
    FallbackNTP=0.pool.ntp.org 1.pool.ntp.org 0.fr.pool.ntp.org

reboot
4. if “systemctl status systemd-timesyncd” still shows timed out awaiting 0.fr(ance).pool.ntp.org open up these ports ?

sudo ufw allow 123/udp
sudo ufw allow out 123/udp
sudo ufw allow out 53

Tried everything you suggested, chrony wasnt installed, edited the config file, opened up the ports, it still shows timed out. Honestly a little lost as to how should I go further.

It may be that your internet service provider blocks ntp port 123/udp ?
If your ultimate goal is to keep computer time correct you could do this.
If this works then you could: apt remove systemd-timesyncd
Create file: sudo nano /usr/local/bin/set-date.sh

Add this to the file:
#!/bin/bash
date -s “$(curl http://s3.amazonaws.com -v 2>&1 | \
grep “Date: " | awk '{ print $3 " " $5 " " $4 " " $7 " " $6 " GMT”}')”

Run this: sudo chmod +x /usr/local/bin/set-date.sh


Create systemd service file to run the script:
sudo nano /etc/systemd/system/set-date.service

Add the following to it:

[Unit]
Description=Set system date from AWS server
After=network-online.target
Wants=network-online.target

[Service]
Type=oneshot
ExecStart=/usr/local/bin/set-date.sh

[Install]
WantedBy=multi-user.target


Then run:

sudo systemctl daemon-reload
sudo systemctl enable set-date.service

Test the service by starting it manually:
sudo systemctl start set-date.service

Check to ensure it ran successfully:
sudo systemctl status set-date.service

I was able to sync the system clock,Thank you! any suggestions as to how should I synchronize my RTC to the local timezone?

a decent online man page

and in particular this section suggests keeping rtc 0

set-local-rtc [BOOL]

Takes a boolean argument. If “0”, the system is configured to maintain the RTC in universal time. If “1”, it will maintain the RTC in local time instead. Note that maintaining the RTC in the local timezone is not fully supported and will create various problems with time zone changes and daylight saving adjustments. If at all possible, keep the RTC in UTC mode. Note that invoking this will also synchronize the RTC from the system clock, unless --adjust-system-clock is passed (see above). This command will change the 3rd line of /etc/adjtime, as documented in hwclock(8).

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.