Jump to content

Falsche Zeit in log-Datei


Go to solution Solved by wsxws,

Recommended Posts

Posted (edited)

Hallo zusamen,

auf meinem Server habe ich die richtige Uhrzeit. emby läuft bei mir im Docker (4.8.6.0) und die dort angezogte Zeit stimmt auch.

Wenn ich auf Protokolle gehe stimmt dort die Zeit auch noch (sihe time1.jpg)

Wenn ich da aber eine log-Datei runterlade stimmt die Zeit in dieser Datei nicht, da sind 2 Stunden Differenz drin (siehe time2.jpg)

Ist das ein Fehler oder muss ich das irgendwo noch was einstellen ?

VG

PS: habe gerade ein update auf 4.8.7.0 gemacht und Logfile rolliert ist aber noch das gleiche

time1.jpg

time2.jpg

Edited by wsxws
Posted

Timezone in yaml ist set

 

# emby
# Media-Server
#version: "2.3"
services:
  emby:
    image: emby/embyserver
    container_name: embyserver
#    runtime: nvidia # Expose NVIDIA GPUs
#    network_mode: host # Enable DLNA and Wake-on-Lan
    environment:
      - UID=0 # The UID to run emby as (default: 2)
      - GID=0 # The GID to run emby as (default 2)
      - GIDLIST=0 # A comma-separated list of additional GIDs to run emby as (default: 2)
      - TZ:"Europe/Berlin"
    volumes:
      - ./config:/config
      - ./backup:/backup
      - /mnt/video:/data/movies
#      - /mnt/video2:/data/movies2
#      - /mnt/backup:/data/movies3
#      - /mnt/incoming:/data/movies4
    ports:
      - 8096:8096
      - 12345:12345 https
    devices:
      - /dev/dri:/dev/dri # VAAPI/NVDEC/NVENC render nodes
    restart: unless-stopped

Problem still the same (2 hours difference)

Posted

Hi, what about on the host machine?

Posted (edited)
Nas:~# timedatectl | grep "Time zone"
                Time zone: Europe/Berlin (CEST, +0200)

thats the putput of the host.

the log-files show 2 hours less which would match to CEST (i dont know of this fact might be of interesset)

 

Edited by wsxws
  • Solution
Posted (edited)

okay, found it:

i chnged the systax in compose-yaml from

- TZ:"Europe/Berlin" (syntax as in Luke's link above) to - TZ=Europe/Berlin (as i found it in another yaml running on my server)

i wonder why docker does not throgh an error if there is something nonunderstandable but anyway, now it works

Edited by wsxws
  • Thanks 1
Posted

Thanks for following up.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...