[mythtv-users] Mythweb issues after latest upgrade
Steve Wilson
mythtv_arizona at yahoo.com
Mon Mar 24 15:39:06 UTC 2008
--- "Michael T. Dean" <mtdean at thirdcontact.com> wrote:
> On 03/22/2008 01:01 PM, Steve Wilson wrote:
> > --- "Michael T. Dean" wrote:
> >> Did you ever figure out what's different between
> the
> >> shows that work and
> >> those that don't?
> > Yeah, I had a feeling it's a crappy work around. I
> > used phpmyadmin to look at the tables to see if
> > there's anything glaringly different between the
> two
> > recordings that would cause the code to handle
> each
> > recording differently and there isn't. However,
> I'm
> > surely no php expert. I ran backend with v all and
> > then went to mythweb the recording then details
> and
> > the bad ones give an error and comparing the good
> and
> > bad it's a SQL query that falls over.
> >
>
> Big thanks for taking the time.
>
> > bad:
> > 2008-03-22 00:13:56.884 read <- 15 49
> > QUERY_RECORDING TIMESLOT 2111 2008-03-21T21:02:00
> > 2008-03-22 00:13:56.885 MSqlQuery: SELECT
> > recorded.chanid,starttime,endtime,title,
> > subtitle,description,channel.channum,
> > channel.callsign,channel.name,channel.commmethod,
> > channel.outputfilters,seriesid,programid,filesize,
> >
> lastmodified,stars,previouslyshown,originalairdate,
> > hostname,recordid,transcoder,playgroup,
> >
>
recorded.recpriority,progstart,progend,basename,recgroup,
> > storagegroup FROM recorded LEFT JOIN channel ON
> > recorded.chanid = channel.chanid WHERE
> recorded.chanid
> > = '2111' AND starttime = '2008-03-21T21:02:00' ;
> > 2008-03-22 00:13:56.885 write -> 15 5 ERROR
>
> Was there a message after that one? That's actually
> not a failed SQL
> query, but a socket error that occurred immediately
> after a SQL query,
> but with the above info, I'm missing some
> information I need to
> (possibly) figure out why it occurred.
>
> Any chance you could send me a whole (-v
> important,general,network and,
> if you don't mind, another -v all) backend log from
> one of these runs
> that includes the "bad". You can send them directly
> to my e-mail
> address (but please include "MythTV" (any case) in
> the subject so I
> don't lose it--i.e. you could just reply to this
> message but send to me :).
>
> Thanks,
> Mike
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
>
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
I think I may've figured out the problem but I don't
know how to fix it.
I looked at the code and figured out the meaning of
the numbers in the mythweb URL. The last numbers
signify the start time.
Good recording:
URL start time : 1202079600
Actual start time: 4 PM
Start time converted to GMT (+7) = 23
The URL start time converted: 23:00:00
Bad recording
URL start time: 1206126133
Actual start time: 1:02:13 PM
Start time converted to GMT (+7) = 20:02:13
The URL start time converted: 19:02:13
As you can see, the start time is off by one hour so
mythweb doesn't think there's a valid recording.
I also have KDE on my system so when I check the
timezone setting it says it's set to Arizona but under
the comments it says MST and when I do a #date it says
MST. I suspect myth sees the MST and assumes daylight
savings even though Arizona doesn't go on daylight
savings.
____________________________________________________________________________________
Looking for last minute shopping deals?
Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping
More information about the mythtv-users
mailing list