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

I am trying to connect my raspberry pi to the ntp server to get the correct time. but somehow I am unable to do that. Can someone please help me out.

I followed the steps from here..
https://victorhurdugaci.com/raspberr...-date-and-time

But every time I restarts it, it takes the time that it had when it was power on. What could be the possible problem?

Thanks.

Post the output from the date command.

Verify that ntp is actually running
ps ax | grep ntp

Post the output of the command
sudo ntpq -p

Also, since the Rpi does not have a persistent clock, "ntpd" has to be run with the option -g (or options -gq) the first time after each cold boot. The instructions you link to seem to be missing that in the description and point to some remedial action in step number 10. So I'd check to make sure the init script is passing those options to "ntpd" and add them if they are missing.

Been a while since I played with Pi however depending on the distro, if you are attached to an Internet enabled network at boot, this takes care of itself. Last I used one it was a non-attended system to monitor a storage space. The Pi was supposed to be on or capable of booting into the desired application unattended and it required proper date and time since there were date and time stamps on the logs pertaining to the monitoring. We used Raspberian (sp), their default and as I recall there was no need to force NTP to start or restart, instead we just needed to verify that the network had been up and NTP had resolved the date and time so that the application was capable of creating sensible logs.

sudo ntpq -p gives this output
localhost: timed out, nothing received
***Request timed out

PS I am connected to the internet.

Ntp is not running

sudo /etc/init.d/ntp start

Originally Posted by michaelk Ntp is not running sudo /etc/init.d/ntp start

If it is not getting launched with the -g option, it will exit. From the manual page: "Normally, ntpd exits with a message to the system log if the offset exceeds the panic threshold, which is 1000 s by default."

Possibly and it depends on what distribution is running on the Pi but typically the init script includes the -g option.

Tried sudo /etc/init.d/ntp start.
Still ntpq -p gives the same output.

what is in /etc/ntp.conf?
probably illegal/unreachable time server was configured.

Sorry for being a little late. This is how the ntp.conf looks like:

# /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help

driftfile /var/lib/ntp/ntp.drift


# Enable this if you want statistics to be logged.
#statsdir /var/log/ntpstats/

statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable


# You do need to talk to an NTP server or two (or three).
#server ntp.your-provider.example

# pool.ntp.org maps to about 1000 low-stratum NTP servers. Your server will
# pick a different set every time it starts up. Please consider joining the
# pool: <http://www.pool.ntp.org/join.html>
server 0.asia.pool.ntp.org iburst
server 1.asia.pool.ntp.org iburst
server 2.asia.pool.ntp.org iburst
server 3.asia.pool.ntp.org iburst


# Access control configuration; see /usr/share/doc/ntp-doc/html/accopt.html for
# details. The web page <http://support.ntp.org/bin/view/Support/AccessRestrictions>
# might also be helpful.
#
# Note that "restrict" applies to both servers and clients, so a configuration
# that might be intended to block requests from certain clients could also end
# up blocking replies from your own upstream servers.

# By default, exchange time with everybody, but don't allow configuration.
restrict -4 default kod notrap nomodify nopeer noquery
restrict -6 default kod notrap nomodify nopeer noquery

# Local users may interrogate the ntp server more closely.
#restrict 127.0.0.1
#restrict ::1

# Clients from this (example!) subnet have unlimited access, but only if
# cryptographically authenticated.
#restrict 192.168.123.0 mask 255.255.255.0 notrust


# If you want to provide time to your local subnet, change the next line.
# (Again, the address is an example only.)
#broadcast 192.168.123.255

# If you want to listen to time broadcasts on your local subnet, de-comment the
# next lines. Please do this only if you trust everybody on the network!
#disable auth
#broadcastclient

pan64 is correct.

#restrict 127.0.0.1 #restrict ::1

You disabled access. Uncomment the lines and restart ntp. The correct syntax is below.

restrict 127.0.0.1
restrict ::1

Did that @michaelk
But still it is taking the same time that it had when last active.

Do I need to change something here:
# You do need to talk to an NTP server or two (or three).
#server ntp.your-provider.example

Your using the Asia pool which should be sufficient.

Now post the output of the ntpq -p command.