Mythweb using wrong time/timezone [Solved]
Posted: Wed Jul 06, 2016 6:38 pm
I'm having trouble with getting mythweb to show the correct time/timezone. I'm in EDT but in mythweb (mythtv 0.28 on Ubuntu 16.04), the displayed time is 3hr off. I'm presuming that mythweb thinks the correct timezone is PDT. I read in some old posts that mythweb (pre 0.28) automatically grabs the system timezone but that has not happened over the last few days. I assume that is still the case, but that is not apparently happening in my system. The hardware time (as shown in BIOS) is the correct UTC time and the linux system clock has been set and confirmed ('data +%Z' + 'hwclock -r') to be the correct timezone and shows the current time.
The system is a fresh install of Ubuntu 16.04 with a follow-up installation of mythtv 0.28 + mythweb (upgrading from mythtv 0.27). But I had not noticed until a few days later that mythweb was showing the wrong time by 3 hours. I checked the linux system clock, and sure enough, it showed PDT instead of the proper EDT, so I corrected it. But since then, mythweb has not updated it's knowledge of time. In mythweb, the program guide and "Recorded Programs" stilll shows all everything in with 3 hr offset (seemingly PDT). On the other hand, the various frontends (remote and local to backend) all show the corrent EDT times in both the program guide and recording times. And the backend is starting/ending all recordings at the correct time.
I've now waited 2+ days for mythweb to correct itself, since I corrected the backend system timezone for mythweb. I've restarted the server multiple times, dpkg-reconfigure mythweb several times, and have purged and reinstalled mythweb several times...over the last couple of days....all to no avail.
Can some please help me figure out what is going on with mythweb? I might be willing to live with the problem, but mythweb is also not letting me schedule any recordings (it complains about 'Incorrect datetime value') and I'm wondering if it might have something to do with the timezone.
EDIT (7/24): I injected the "date_default_timezone_get" command into the mythweb.php code and it reports the correct "America/NewYork" timezone.
Thanks
The system is a fresh install of Ubuntu 16.04 with a follow-up installation of mythtv 0.28 + mythweb (upgrading from mythtv 0.27). But I had not noticed until a few days later that mythweb was showing the wrong time by 3 hours. I checked the linux system clock, and sure enough, it showed PDT instead of the proper EDT, so I corrected it. But since then, mythweb has not updated it's knowledge of time. In mythweb, the program guide and "Recorded Programs" stilll shows all everything in with 3 hr offset (seemingly PDT). On the other hand, the various frontends (remote and local to backend) all show the corrent EDT times in both the program guide and recording times. And the backend is starting/ending all recordings at the correct time.
I've now waited 2+ days for mythweb to correct itself, since I corrected the backend system timezone for mythweb. I've restarted the server multiple times, dpkg-reconfigure mythweb several times, and have purged and reinstalled mythweb several times...over the last couple of days....all to no avail.
Can some please help me figure out what is going on with mythweb? I might be willing to live with the problem, but mythweb is also not letting me schedule any recordings (it complains about 'Incorrect datetime value') and I'm wondering if it might have something to do with the timezone.
EDIT (7/24): I injected the "date_default_timezone_get" command into the mythweb.php code and it reports the correct "America/NewYork" timezone.
Thanks