Orange Pi Zero: Wrong Date and Time even given Internet Access
up vote
0
down vote
favorite
I am using Orange Pi Zero and running Armbian Stretch OS 5.59 on it.
Problem is, it is giving wrong date and time even in the presence of the Internet. I have tried restarting "ntp" service but to no avail. I have also tried rebooting, but the same annoying result. I have already set the right timezone which is PKT, but it shouldn't matter. So what do I need to do or change?
Thank you.
linux armbian
asked Nov 27 at 9:46
Saad Abdul Majid
4
add a comment |
up vote
0
down vote
favorite
I am using Orange Pi Zero and running Armbian Stretch OS 5.59 on it.
Problem is, it is giving wrong date and time even in the presence of the Internet. I have tried restarting "ntp" service but to no avail. I have also tried rebooting, but the same annoying result. I have already set the right timezone which is PKT, but it shouldn't matter. So what do I need to do or change?
Thank you.
linux armbian
asked Nov 27 at 9:46
Saad Abdul Majid
4
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am using Orange Pi Zero and running Armbian Stretch OS 5.59 on it.
Problem is, it is giving wrong date and time even in the presence of the Internet. I have tried restarting "ntp" service but to no avail. I have also tried rebooting, but the same annoying result. I have already set the right timezone which is PKT, but it shouldn't matter. So what do I need to do or change?
Thank you.
linux armbian
asked Nov 27 at 9:46
Saad Abdul Majid
4
I am using Orange Pi Zero and running Armbian Stretch OS 5.59 on it.
Problem is, it is giving wrong date and time even in the presence of the Internet. I have tried restarting "ntp" service but to no avail. I have also tried rebooting, but the same annoying result. I have already set the right timezone which is PKT, but it shouldn't matter. So what do I need to do or change?
Thank you.
linux armbian
linux armbian
asked Nov 27 at 9:46
Saad Abdul Majid
4
asked Nov 27 at 9:46
Saad Abdul Majid
4
asked Nov 27 at 9:46
Saad Abdul Majid
4
asked Nov 27 at 9:46
Saad Abdul Majid
4
asked Nov 27 at 9:46
Saad Abdul Majid
4
4
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Now that I have resolved the problem, I want to share it with others. I had to make changes in "/etc/resolv.conf". Here nameserver field stated "127.0.0.1", I changed it to google nameserver "8.8.8.8". The problem resolved and I have correct date and time now.
But now that I see again, "/etc/resolv.conf" has been overwritten by OS(I believe) and it again displays "127.0.0.1" as my nameserver. But, still I am getting the right date and time. My take is, I needed to coordinate with Google to update correct date and time. But upon reboot, OS retraces any changes made in "/etc/resolv.conf" but changes stick.
answered Nov 27 at 10:06
Saad Abdul Majid
4
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Now that I have resolved the problem, I want to share it with others. I had to make changes in "/etc/resolv.conf". Here nameserver field stated "127.0.0.1", I changed it to google nameserver "8.8.8.8". The problem resolved and I have correct date and time now.
But now that I see again, "/etc/resolv.conf" has been overwritten by OS(I believe) and it again displays "127.0.0.1" as my nameserver. But, still I am getting the right date and time. My take is, I needed to coordinate with Google to update correct date and time. But upon reboot, OS retraces any changes made in "/etc/resolv.conf" but changes stick.
answered Nov 27 at 10:06
Saad Abdul Majid
4
add a comment |
up vote
0
down vote
Now that I have resolved the problem, I want to share it with others. I had to make changes in "/etc/resolv.conf". Here nameserver field stated "127.0.0.1", I changed it to google nameserver "8.8.8.8". The problem resolved and I have correct date and time now.
But now that I see again, "/etc/resolv.conf" has been overwritten by OS(I believe) and it again displays "127.0.0.1" as my nameserver. But, still I am getting the right date and time. My take is, I needed to coordinate with Google to update correct date and time. But upon reboot, OS retraces any changes made in "/etc/resolv.conf" but changes stick.
answered Nov 27 at 10:06
Saad Abdul Majid
4
add a comment |
up vote
0
down vote
up vote
0
down vote
Now that I have resolved the problem, I want to share it with others. I had to make changes in "/etc/resolv.conf". Here nameserver field stated "127.0.0.1", I changed it to google nameserver "8.8.8.8". The problem resolved and I have correct date and time now.
But now that I see again, "/etc/resolv.conf" has been overwritten by OS(I believe) and it again displays "127.0.0.1" as my nameserver. But, still I am getting the right date and time. My take is, I needed to coordinate with Google to update correct date and time. But upon reboot, OS retraces any changes made in "/etc/resolv.conf" but changes stick.
answered Nov 27 at 10:06
Saad Abdul Majid
4
Now that I have resolved the problem, I want to share it with others. I had to make changes in "/etc/resolv.conf". Here nameserver field stated "127.0.0.1", I changed it to google nameserver "8.8.8.8". The problem resolved and I have correct date and time now.
But now that I see again, "/etc/resolv.conf" has been overwritten by OS(I believe) and it again displays "127.0.0.1" as my nameserver. But, still I am getting the right date and time. My take is, I needed to coordinate with Google to update correct date and time. But upon reboot, OS retraces any changes made in "/etc/resolv.conf" but changes stick.
answered Nov 27 at 10:06
Saad Abdul Majid
4
answered Nov 27 at 10:06
Saad Abdul Majid
4
answered Nov 27 at 10:06
Saad Abdul Majid
4
answered Nov 27 at 10:06
Saad Abdul Majid
4
4
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1378707%2forange-pi-zero-wrong-date-and-time-even-given-internet-access%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
