trevoragifford 1 Posted June 27, 2025 Posted June 27, 2025 I've noticed an issue with the titles added to my recorded Jeopardy episodes. Each recording, despite getting the correct Season/Episode number, displays the wrong date for the title. Example: Episode 209 was recorded today, Thursday 6/26 but displays with the title "Fri, Jun 27, 2025" Here is my best guess for why this is happening: In my area, new episodes release at 6:30 PM. It seems like the .nfo files saved for the recordings saves the recording start time in UTC. Since I'm in Mountain time (UTC-6), this results in the start date being rolled over into the next day. It also seems to be saving the air date based on that start time. I'm guessing the <aired> field is what is being used to choose the title, and since it is a date only and not a datetime, the timezone offset isn't applied and so the wrong date is used for the title. trevor@gifford-media:/giffordMedia/data/recorded_tv/Jeopardy! (1984)/Season 41$ cat Jeopardy\!\ S41E209.nfo <?xml version="1.0" encoding="utf-8" standalone="yes"?> <episodedetails> <aired>2025-06-27</aired> <episode>209</episode> <season>41</season> <dateadded>2025-06-27 00:29:06</dateadded> <year>2025</year> <mpaa>TV-G</mpaa> <plot>The Emmy-winning quiz show features a unique answer-and-question format.</plot> <genre>Game Show</genre>
Luke 42077 Posted June 27, 2025 Posted June 27, 2025 HI, have you checked the timezone of the server machine to ensure that it's set correctly?
trevoragifford 1 Posted June 27, 2025 Author Posted June 27, 2025 5 minutes ago, Luke said: HI, have you checked the timezone of the server machine to ensure that it's set correctly? Yes I have.
Luke 42077 Posted June 27, 2025 Posted June 27, 2025 6 minutes ago, trevoragifford said: Yes I have. How did you do that?
trevoragifford 1 Posted June 27, 2025 Author Posted June 27, 2025 trevor@gifford-media:~$ date Fri Jun 27 03:26:26 PM MDT 2025 trevor@gifford-media:~$ docker exec -it embyserver date Fri Jun 27 03:26:33 PM MDT 2025 trevor@gifford-media:~$ This did make me re-examine my timezone mappings for my docker container, however and I found that while /etc/localtime is mapped to the container, /etc/timezone is not mapped. I changed it so hopefully this will be resolved now. I'll verify after tonight's recording. 1
Blue278 22 Posted July 16, 2025 Posted July 16, 2025 On 27/06/2025 at 22:30, trevoragifford said: trevor@gifford-media:~$ date Fri Jun 27 03:26:26 PM MDT 2025 trevor@gifford-media:~$ docker exec -it embyserver date Fri Jun 27 03:26:33 PM MDT 2025 trevor@gifford-media:~$ This did make me re-examine my timezone mappings for my docker container, however and I found that while /etc/localtime is mapped to the container, /etc/timezone is not mapped. I changed it so hopefully this will be resolved now. I'll verify after tonight's recording. would you be so kind to tell me step by step how you solved timezone issue? Thanks
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now