[SOLVED] How to set time for my raspberry pi?

Output of ntpq -p:

remote refid st t when poll reach delay offset jitter
==============================================================================
129.250.35.250 .INIT. 16 u - 64 0 0.000 0.000 0.000
118.67.200.10 .INIT. 16 u - 64 0 0.000 0.000 0.000
80.241.0.72 .INIT. 16 u - 64 0 0.000 0.000 0.000
103.245.79.18 .INIT. 16 u - 64 0 0.000 0.000 0.000

Output of ntpq -p:

remote refid st t when poll reach delay offset jitter
==============================================================================
129.250.35.250 .INIT. 16 u - 64 0 0.000 0.000 0.000
118.67.200.10 .INIT. 16 u - 64 0 0.000 0.000 0.000
80.241.0.72 .INIT. 16 u - 64 0 0.000 0.000 0.000
103.245.79.18 .INIT. 16 u - 64 0 0.000 0.000 0.000

Since the stratum level (st) is 16 ntp will not use those servers. If you stop and restart ntp you will get a new set of servers. If the results are the same try switching the pool.

st is still the same. The remote addresses are different now.

remote refid st t when poll reach delay offset jitter
============================================================================
77.235.14.49 .INIT. 16 u - 64 0 0.000 0.000 0.000
125.62.193.121 .INIT. 16 u - 64 0 0.000 0.000 0.000
218.186.3.36 .INIT. 16 u - 64 0 0.000 0.000 0.000
133.242.142.232 .INIT. 16 u - 64 0 0.000 0.000 0.000

And what do you by switching the pool? Do i need to change my server?

Yes, you can pick a different pool. It could take a few minutes before the Pi is synced.

http://www.pool.ntp.org/en/

See what happens when you try:
server 0.pool.ntp.org
server 1.pool.ntp.org
server 2.pool.ntp.org
server 3.pool.ntp.org

Still the same. I changed the pool, restarted the ntp. Nothing happened. Time is still the same and st is still 16 while the remote ip addresses are changed.

Wait a few minutes. Looks like ntp is stuck at init.

What should I change the localtime to in sudo cp /usr/share/zoneinfo/US/Pacific /etc/localtime?
Universal, UTC or to my timezone Asia or something else?

I changed the pool to:
server 0.pool.ntp.org
server 1.pool.ntp.org
server 2.pool.ntp.org
server 3.pool.ntp.org

Syncing depends on the network being up. And access to the internet. I tend to not run ntp(d) and opt to sync one time manually at boot.

# ntpdate <server>

In my case time-b.nist.gov is what I use most often, but regionally appropriate. In the absence of a network, I go even more manual.

# date -s "YYYYMMDD"
# date -s "HH:MM:SS"

There's probably better ways. But sometimes at a fresh installation, the old manual ways get you through the day.

Some ntp servers don't let you sync if you're more than a day or two off. And since the RPi starts at epoch 0 (1970), you're literally years off. So the manual date method helps to overcome that hurdle by putting you back into tolerances.

How do I set ntpdate <server>? Just by running this command?

The set time using:
# date -s "YYYYMMDD"
# date -s "HH:MM:SS"
is not permanent. The raspberry pi just carried on from the time it had got to before I'd turned it off.

Unless you added a battery backed real time clock the clock should start at 0000 1 Jan 1970 at power up. It can't just carry on.

The pi does not have the ntpdate command which is obsolete anyway but can be installed. Although it does help with diagnosing problems. You can use ntpd -g -q but you still need to use a valid time server.

Could be a network issue. Do other computers run linux and sync using ntp? Try the following.

sudo apt-get install ntpdate
sudo ntpdate -u pool.ntp.org

Done
Thank you for your help.