Author |
Message |
Liv2Cod
|
Posted: Mon Mar 19, 2007 1:45 am |
|
Joined: Fri May 21, 2004 11:55 pm
Posts: 1206
Location:
Silicon Valley, CA
|
I fixed the DST issue with the excellent how-to on the subject, and all went very well. For the last week I've had perfect recordings. Until today.
When I look at my schedule, every show has been shifted later by one hour. Every day I have checked so far is shifted. This is a new problem that occurred today after my shows were recorded.
I have run the "mythfilldatabase --update-all" again without fixing anything. I checked my timezone and it is set properly to PDT and the clock is correct. What the h*ll is going on, and is it just me??
_________________ Do you code to live, or live to code? Search LinHES forum through Google
|
|
Top |
|
 |
adoute
|
Posted: Mon Mar 19, 2007 6:07 am |
|
Joined: Tue Mar 29, 2005 6:15 pm
Posts: 79
Location:
Plymouth, MI
|
I had a similar problem, but it wasn't as global as yours sounds. I had several channels that would have programs listed in the correct time slot, but would also have the same program listed again right after it (example: 10:00 News on channel 2 at 10:00, then again at 11:00). Scheduled recordings ran fine - even with the discrepancy in the program guide, strangely enough. I ran 'mythfilldatabase --refresh-all' and restarted the backend - neither fixed the issue. I finally rebooted the system last night, and everything seems to be back to normal now. I'm not sure, but I suspect Mysql may have been part of the problem - in hindsight, I wish I would have thought of restarting Mysql prior to rebooting.
Anyway, in my case, a reboot fixed the issue - but you might want to try restarting the backend & Mysql before bothering with a full reboot.
Hope this helps -
Allan
_________________ Running Knoppmyth R5F27 since 09/12/07
Hardware Specs
|
|
Top |
|
 |
Liv2Cod
|
Posted: Mon Mar 19, 2007 12:27 pm |
|
Joined: Fri May 21, 2004 11:55 pm
Posts: 1206
Location:
Silicon Valley, CA
|
Wow, that's what I love about this place!
You nailed it, Allan. I stopped mythbackend, did a restart on mysql, and restarted mythbackend. Now the schedule looks perfect.
My KM box is so reliable I almost never restart it. It didn't occur to me to try this obvious fix. (Rebooting is always the first thing we do on Windoze computers, isn't it?)
_________________ Do you code to live, or live to code? Search LinHES forum through Google
|
|
Top |
|
 |
adoute
|
Posted: Mon Mar 19, 2007 12:50 pm |
|
Joined: Tue Mar 29, 2005 6:15 pm
Posts: 79
Location:
Plymouth, MI
|
I know what you mean about KM reliability vs Windows reliability. I am the admin on several Windows servers at work, all of which require periodic rebooting just keep things running 'normally'.
My KM systems, on the other hand, get rebooted VERY rarely. I really wish I would have thought about restarting Mysql BEFORE I typed 'reboot' instead of immediately after. There goes my 'uptime' numbers. Oh well.
Glad I could be of some help.
Allan
_________________ Running Knoppmyth R5F27 since 09/12/07
Hardware Specs
|
|
Top |
|
 |