Return to Question

Completed question

Source Link

edited Jun 3, 2016 at 14:29

My raspberry Pi 2 has a wrong date and it is not a timezone problem since UTC time right now is (6:53 PM Thursday, June 2, 2016) and running:

pi@raspberrypi2:~ $ date -u
mié jun  1 14:13:45 UTC 2016

Also, see this:

pi@raspberrypi2:~ $ ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 ntp.copaco.com. .INIT.          16 u    - 1024    0    0.000    0.000   0.000
 190.15.128.72   .INIT.          16 u    - 1024    0    0.000    0.000   0.000
 c.ntp.br        .INIT.          16 u    - 1024    0    0.000    0.000   0.000
 234.229.33.186. .INIT.          16 u    - 1024    0    0.000    0.000   0.000

What i get from tha output is that, apparently, since the offset is 0 then raspbian thinks its time is perfect and it doesn't change it to the right value.

Any clues here? Thanks!

EDIT1: I do have interent connection, I can ping servers and get responses, also DNS is properly configured, I can sucessfully use nslookup

My raspberry Pi 2 has a wrong date and it is not a timezone problem since UTC time right now is (6:53 PM Thursday, June 2, 2016) and running:

pi@raspberrypi2:~ $ date -u
mié jun  1 14:13:45 UTC 2016

Also, see this:

pi@raspberrypi2:~ $ ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 ntp.copaco.com. .INIT.          16 u    - 1024    0    0.000    0.000   0.000
 190.15.128.72   .INIT.          16 u    - 1024    0    0.000    0.000   0.000
 c.ntp.br        .INIT.          16 u    - 1024    0    0.000    0.000   0.000
 234.229.33.186. .INIT.          16 u    - 1024    0    0.000    0.000   0.000

What i get from tha output is that, apparently, since the offset is 0 then raspbian thinks its time is perfect and it doesn't change it to the right value.

Any clues here? Thanks!

My raspberry Pi 2 has a wrong date and it is not a timezone problem since UTC time right now is (6:53 PM Thursday, June 2, 2016) and running:

pi@raspberrypi2:~ $ date -u
mié jun  1 14:13:45 UTC 2016

Also, see this:

pi@raspberrypi2:~ $ ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 ntp.copaco.com. .INIT.          16 u    - 1024    0    0.000    0.000   0.000
 190.15.128.72   .INIT.          16 u    - 1024    0    0.000    0.000   0.000
 c.ntp.br        .INIT.          16 u    - 1024    0    0.000    0.000   0.000
 234.229.33.186. .INIT.          16 u    - 1024    0    0.000    0.000   0.000

What i get from tha output is that, apparently, since the offset is 0 then raspbian thinks its time is perfect and it doesn't change it to the right value.

Any clues here? Thanks!

EDIT1: I do have interent connection, I can ping servers and get responses, also DNS is properly configured, I can sucessfully use nslookup

Source Link

asked Jun 2, 2016 at 18:58

seed_87

Raspberry pi time wrong

My raspberry Pi 2 has a wrong date and it is not a timezone problem since UTC time right now is (6:53 PM Thursday, June 2, 2016) and running:

pi@raspberrypi2:~ $ date -u
mié jun  1 14:13:45 UTC 2016

Also, see this:

pi@raspberrypi2:~ $ ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 ntp.copaco.com. .INIT.          16 u    - 1024    0    0.000    0.000   0.000
 190.15.128.72   .INIT.          16 u    - 1024    0    0.000    0.000   0.000
 c.ntp.br        .INIT.          16 u    - 1024    0    0.000    0.000   0.000
 234.229.33.186. .INIT.          16 u    - 1024    0    0.000    0.000   0.000

What i get from tha output is that, apparently, since the offset is 0 then raspbian thinks its time is perfect and it doesn't change it to the right value.

Any clues here? Thanks!

pi-2 ntp