EPG wrong time - sheduled records fails
Added by Michael Menen over 6 years ago
Hi all,
hope you can help me.
I've set up a tvheadend on a fresh Ubuntu 18 system.
NTP is set correctly on the Ubuntu
root@mmerver:~# ntptime
ntp_gettime() returns code 0 (OK)
time df0d4e72.7bae7924 Thu, Aug 2 2018 11:33:38.483, (.483131261),
maximum error 207500 us, estimated error 0 us, TAI offset 0
ntp_adjtime() returns code 0 (OK)
modes 0x0 (),
offset -3484.571 us, frequency 8.956 ppm, interval 1 s,
maximum error 207500 us, estimated error 0 us,
status 0x6001 (PLL,NANO,MODE),
time constant 7, precision 0.001 us, tolerance 500 ppm,
root@mmerver:~# date
Thu Aug 2 11:34:13 CEST 2018
tvheadend is configured to use NTP (please see tvheadend-ntp).
Taken a deeper look into EPG I can see that the clock is 9 hours behind.
At the moment my clock is showing 11:39am but EPG is showing 2:39am
If trying to record the news at 8:00pm (which is 11:00am in EPG) it's generating the failure attached (tvheadend-ntp-failure.rtf)
Really cunfused what might cause the problem.
Hope you can help me.
Much appreciate!
Michael
Replies (7)
RE: EPG wrong time - sheduled records fails - Added by Hiro Protagonist over 6 years ago
Where are you getting the EPG from?
What do you have set in Configuration/DVB Inputs/Networks/EIT Time Offset for the network in question?
RE: EPG wrong time - sheduled records fails - Added by Michael Menen over 6 years ago
HI,
I'm getting the EPG from my DVB Grabber (over the air).
I've de-activated the "Update time" and "Enable NTP driver" because NTP is already configured and working on the server and I don't want to let tvheadend adjust the time.
Configuration/DVB Inputs/Networks/EIT Local time is aktivated.
tvheadend should use local time because NTP is running on the OS (and working):
mmenen@mmerver:~$ ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
ntp.ubuntu.com .POOL. 16 p - 64 0 0.000 0.000 0.000
-de2.justaguy.be 216.218.254.202 2 u 160 1024 377 19.194 -0.884 1.032
-ntp21.berlin-pr 131.188.3.220 2 u 40 1024 377 20.339 1.342 4.010
+spock.allandant 192.53.103.108 2 u 314 1024 377 15.668 -0.718 0.575
*ntp2.ig-haase.d 130.133.1.10 2 u 208 1024 377 21.010 -1.756 1.015
+chilipepper.can 17.253.34.253 2 u 1027 1024 377 25.551 0.514 2.104
-alphyn.canonica 132.246.11.231 2 u 7 1024 377 100.980 1.111 0.874
-golem.canonical 192.53.103.108 2 u 351 1024 377 25.147 1.507 2.154
-pugot.canonical 131.188.3.220 2 u 258 1024 377 25.691 1.848 1.783
mmenen@mmerver:~$
But it dosen't matter what setting I choose - EPG Bis always 9 hours behind.
Why on hell 9 hours?
2 hours (UTC) I would accept (living in Germany CEST = UTC +2)
RE: EPG wrong time - sheduled records fails - Added by Joe User over 6 years ago
You did not answer his question - "What do you have set in Configuration/DVB Inputs/Networks/EIT Time Offset for the network in question?"
What does is show for the time at the top of the webif?
The times in the webif are set to the timezone of the BROWSER, NOT the server - so also check your settings of the machine you are browsing from...
RE: EPG wrong time - sheduled records fails - Added by Michael Menen over 6 years ago
Hi,
I didn't answered the question because I couldn't find the setting you are mention.
Please the screenshot attached.
RE: EPG wrong time - sheduled records fails - Added by Joe User over 6 years ago
Try removing the check for "EIT localtime"
RE: EPG wrong time - sheduled records fails - Added by Michael Menen over 6 years ago
Unfortunately removing the check for "EIT localtime" didn't solve the problem.
Already tested yesterday.
Today i will trying to use local xmltv-files to see if the problme might be related to OTA.
RE: EPG wrong time - sheduled records fails - Added by Joe User over 6 years ago
The change is not reflected immediately - did you stop tvheadend and remove the epgdb file then restart and wait for new epg updates?
Also,
Joe User wrote:
The times in the webif are set to the timezone of the BROWSER, NOT the server - so also check your settings of the machine you are browsing from...