Autor Thema: FHEM process datetime different than server datetime  (Gelesen 357 mal)

Offline okebaja

  • Newbie
  • Beiträge: 2
FHEM process datetime different than server datetime
« am: 28 August 2017, 21:20:56 »
I am running FHEM for more than 6 months now without any problem. Yesterday, after a restart, I noticed lamps not being switched at the correct time. After some searching I found the reason: FHEM's datetime is different than my server's datetime.

Different datetime reading from my server, all taken roughly at the same time:

hwclock: Mon 28 Aug 2017 09:15:09 PM XXX  -0.390519 seconds
date: Mon Aug 28 21:15:06 XXX 2017
fhem log: 2017.08.28 00:15:18

Does anybody have any idea? ..puzzled..
Eltako Funk 14-series EnOcean home automation managed by FHEM @ Puppy Linux 5.7.1 @ Dell OptiPlex FX160

Offline okebaja

  • Newbie
  • Beiträge: 2
Antw:FHEM process datetime different than server datetime
« Antwort #1 am: 29 August 2017, 18:14:34 »
I do not understand why after 6 months FHEM decides to be 3 hours off. And why a server restart won't help. Giving up.
Eltako Funk 14-series EnOcean home automation managed by FHEM @ Puppy Linux 5.7.1 @ Dell OptiPlex FX160

Offline viegener

  • Developer
  • Hero Member
  • ****
  • Beiträge: 3303
    • Meine Seite im fhemwiki
Antw:FHEM process datetime different than server datetime
« Antwort #2 am: 29 August 2017, 23:22:06 »
It is normally not the case that this happens based on FHEM, since FHEM only takes the time from perl. But any support for identifying the reason will need more backrhoudn of your platform, operating system, what was changed, is that really a jump or was that moving slowly?

Are there any shell settings (assuming this is unix) where the timezone is set differently than in the restarted fhem ?

Again without more infoirmation this are just random ideas
Kein Support über PM - Anfragen gerne im Forum - Damit auch andere profitieren und helfen können

 

decade-submarginal