It is your container having incorrect date. Not OMV. Perhaps it is just not using correct timezone. Depending on what image you use, there could be a env var or you could try to bind mount /etc/localtime:/etc/localtime:ro. That was necessary on some of my containers too.
It is your container having incorrect date. Not OMV. Perhaps it is just not using correct timezone. Depending on what image you use, there could be a env var or you could try to bind mount /etc/localtime:/etc/localtime:ro. That was necessary on some of my containers too.
That's about the easiest way to keep your containers time properly.. I add that all my containers irregardless if there's an enviornment variable that controls timezone or not.
Then as long as my host time is right, my container times are right... As he put however, just make sure you flag it :ro as that makes it read only.. so you don't have to worry about accidentally allowing a container to change your host time.
It is your container having incorrect date. Not OMV. Perhaps it is just not using correct timezone. Depending on what image you use, there could be a env var or you could try to bind mount /etc/localtime:/etc/localtime:ro. That was necessary on some of my containers too.
Ehm, no; the time zone is correct in Owncloud and in OMV; if you take a look to the screenshots, you can see that some folders have the correct date and some not; in OMV, in the log's section, some have the correct date and some not.
Is not a timezone's problem.
Oh I see. That is weird indeed 
i noticed the same problem in my installation
Hi, I am having this issue too, since I'm using OMV. I haven't found any solution so far. It's a big problem for time based applications like generating TOTP codes.
You should check the NTP sync and sources status. It is surely not OMV or chrony, but your hardware or the configured NTP server.
# chronyc tracking
# chronyc sourcesYou should check the NTP sync and sources status. It is surely not OMV or chrony, but your hardware or the configured NTP server.
Code# chronyc tracking # chronyc sources
Thanks a lot for your answer. Here are the results of these commands:
root@server:~# chronyc tracking
Reference ID : 058789BC (ananas.bitschine.fr)
Stratum : 4
Ref time (UTC) : Sun Aug 13 22:06:37 2023
System time : 0.000022187 seconds fast of NTP time
Last offset : +0.000043361 seconds
RMS offset : 0.000106279 seconds
Frequency : 5.902 ppm fast
Residual freq : +0.010 ppm
Skew : 0.392 ppm
Root delay : 0.012955161 seconds
Root dispersion : 0.001964857 seconds
Update interval : 130.1 seconds
Leap status : Normal
root@server:~# chronyc sources
MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
^* ananas.bitschine.fr 3 8 377 222 +116us[ +159us] +/- 9066usI'm not sure what to conclude from this
Thanks a lot for your answer. Here are the results of these commands:
CodeAlles anzeigenroot@server:~# chronyc tracking Reference ID : 058789BC (ananas.bitschine.fr) Stratum : 4 Ref time (UTC) : Sun Aug 13 22:06:37 2023 System time : 0.000022187 seconds fast of NTP time Last offset : +0.000043361 seconds RMS offset : 0.000106279 seconds Frequency : 5.902 ppm fast Residual freq : +0.010 ppm Skew : 0.392 ppm Root delay : 0.012955161 seconds Root dispersion : 0.001964857 seconds Update interval : 130.1 seconds Leap status : Normal root@server:~# chronyc sources MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ananas.bitschine.fr 3 8 377 222 +116us[ +159us] +/- 9066usI'm not sure what to conclude from this
Looks all good IMO, except stratum 4 which means that there are 4 instances (I am not exactly sure here where stratum count starts) between your system and the original time server. The lesser the stratum the better.
Then you say it could be my hardware ? How ?
The configured ntp server is pool.ntp.org, I didn't edit anything. Would there be something to edit here ?
Update :
So I've fixed my problem. For an unknown reason, pool.ntp.org isn't working correctly at all for me. I changed to another server, I searched for the closest I could find. If you're in France, you can pick from this list : https://services.renater.fr/ntp/serveurs_francais . time.windows.com also works well. That's strange because pool.ntp.org is supposed to include all those french servers. So I've you're having the same issue, try some other servers.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
