Hi everyone,
I used the latest stable image of OpenMediaVault (microSD Boot) which at the current time of posting is stretch-openmediavault-rock64-0.6.44-239-armhf.img.xz as recommended by the release notes. I wrote the image to a Samsung Evo 32gb microSD card using latest version of Etcher and put it on my recently bought Rock64 4G. It boots up properly and I can access the web GUI. The problem is that the system date and time are not correct. I've spent several hours trying to get it to set the date and time correctly through NTP but no luck.
When booting for the first time and accessing by SSH, when I ran any of the following commands, It gives me an incorrect date and time (May 27th 2017, time is not even close to real current time).
or
Both of those commands give me the same incorrect date.
Has anyone experienced the same issue? My Rock64 is brand new and I haven't found any solution yet to this issue. I've also tried using other Debian images from ayufan's repo (with GUI environments) and there is an access error every time I try to set up the date and time through the GUI.
I'll appreciate any help
What have you done to setup NTP ?
Did you tried to stop NTP service and tried the "ntpdate <ntp-server-name>" manually ?
(06-19-2018, 03:03 PM)martinayotte Wrote: What have you done to setup NTP ?
Did you tried to stop NTP service and tried the "ntpdate <ntp-server-name>" manually ?
I've done that and I've also tried updating the servers through the "ntp.conf" file. Before making any change to NTP I always stop the service, make the change, then start it. No luck
(06-19-2018, 03:13 PM)erickpeniche Wrote: (06-19-2018, 03:03 PM)martinayotte Wrote: What have you done to setup NTP ?
Did you tried to stop NTP service and tried the "ntpdate <ntp-server-name>" manually ?
I've done that and I've also tried updating the servers through the "ntp.conf" file. Before making any change to NTP I always stop the service, make the change, then start it. No luck
Have a read through this. Things have slightly changed. This should help sort your problem out https://www.digitalocean.com/community/t...untu-16-04
Please let us know how you get on
(06-20-2018, 01:25 AM)mikedhoore Wrote: Maybe not the correct time zone ??
https://wiki.debian.org/TimeZoneChanges
Not relevant considering OP have very high shift in date, not time alone (May 27th, what TZ could it be ?  )
Does internet connection work ?
With what you have provided, it's clear you have working LAN connection, but no info on internet one.
Be careful too, there is too ntp packages on debian, ntp and ntpdate, unless I'm wrong, the first is for synchronizing your own network with one or more ntp server(s), the second is for actual sync with internet server (in conf something like pool.ntp.....debian.org as I recall)
To avoid too big shift, it's better to start ntpdate on reboot + eventually every day with cron if you keep your SBC up all the time.
Follow this post exactly as it is written. I experienced a similar problem to you after a sudo apt-get update/upgrade in Debian. As I explained things have changed in Debian and it is necessary to remove ntp and replace it with ntpd. Systemd will look after everything from there
https://feeding.cloud.geek.nz/posts/time...d-systemd/
06-25-2018, 06:52 PM
(This post was last modified: 06-25-2018, 07:21 PM by erickpeniche.)
(06-19-2018, 08:01 PM)Rocklobster Wrote: (06-19-2018, 03:13 PM)erickpeniche Wrote: (06-19-2018, 03:03 PM)martinayotte Wrote: What have you done to setup NTP ?
Did you tried to stop NTP service and tried the "ntpdate <ntp-server-name>" manually ?
I've done that and I've also tried updating the servers through the "ntp.conf" file. Before making any change to NTP I always stop the service, make the change, then start it. No luck
Have a read through this. Things have slightly changed. This should help sort your problem out https://www.digitalocean.com/community/t...untu-16-04
Please let us know how you get on
I have tried most of the instructions there when I spent a couple hours in the beginning with this issue. I gave up for a wee and now I will continue trying to look for a solution. I'll post some initial steps of my process so you get an idea
(06-20-2018, 01:48 AM)MichaelRock Wrote: (06-20-2018, 01:25 AM)mikedhoore Wrote: Maybe not the correct time zone ??
https://wiki.debian.org/TimeZoneChanges
Not relevant considering OP have very high shift in date, not time alone (May 27th, what TZ could it be ? )
Does internet connection work ?
With what you have provided, it's clear you have working LAN connection, but no info on internet one.
Be careful too, there is too ntp packages on debian, ntp and ntpdate, unless I'm wrong, the first is for synchronizing your own network with one or more ntp server(s), the second is for actual sync with internet server (in conf something like pool.ntp.....debian.org as I recall)
To avoid too big shift, it's better to start ntpdate on reboot + eventually every day with cron if you keep your SBC up all the time.
I'm almost sure I've tried ntpdate. These are the steps I follow each time I decide to try again from scratch, some steps might answer your questions:
- Format microSD card
- Write latest stable image to microSD card using etcher and verify image
- Insert microSD to Rock64, plug ethernet cable and lastly official power supply
- Wait a couple of minutes for it to boot
- Access web gui with default username and password (notice incorrect datetime once logged in)
- Disable session timeout, change admin password, enable root ssh. Apply all changes
- SSH using root, ping google.com, curl www.google.com (network test success)
- apt-get update, apt-get upgrade
- Reboot, login again through web gui, datetime still incorrect
(06-20-2018, 04:01 AM)Rocklobster Wrote: Follow this post exactly as it is written. I experienced a similar problem to you after a sudo apt-get update/upgrade in Debian. As I explained things have changed in Debian and it is necessary to remove ntp and replace it with ntpd. Systemd will look after everything from there
https://feeding.cloud.geek.nz/posts/time...d-systemd/
Let me try this now and will let you know the results. Thanks!
(06-20-2018, 04:01 AM)Rocklobster Wrote: Follow this post exactly as it is written. I experienced a similar problem to you after a sudo apt-get update/upgrade in Debian. As I explained things have changed in Debian and it is necessary to remove ntp and replace it with ntpd. Systemd will look after everything from there
https://feeding.cloud.geek.nz/posts/time...d-systemd/
It works! But the package ntp is a dependency for other packages:
Code: The following packages will be REMOVED:
ntp openmediavault openmediavault-flashmemory openmediavault-netatalk openmediavault-omvextrasorg
If I continue with the instructions on link, I'm able to fix the datetime issue, but since the above packages were removed, Im no longer able to open OMV web gui.
I'm starting to think that my Rock64 board is defective. I even downloaded OMV release 0.5.15 which is said to be one of the most stables (runs OMV 3 instead of 4), and have the same datetime problem...
(06-26-2018, 08:12 PM)erickpeniche Wrote: I'm starting to think that my Rock64 board is defective. I even downloaded OMV release 0.5.15 which is said to be one of the most stables (runs OMV 3 instead of 4), and have the same datetime problem...
Your board is fine. Try armbian Xenial by downloading from this link https://www.armbian.com/rock64/ and follow the instruction I posted previously for correcting your time issue.
Report back ASAP on your results.
|
