| === yuki-onna_ is now known as yuki-onna | ||
| === yuki-onna_ is now known as yuki-onna | ||
| === hpeter_ is now known as hpeter | ||
| === hpeter_ is now known as hpeter | ||
| === dahlSTROM|sleep is now known as dahlSTROM | ||
| === hpeter_ is now known as hpeter | ||
| sabhain | going from 10.04 LTS to 12.04 LTS on a backend. Better to re-install and restore db backup, or just upgrade? | 16:36 |
|---|---|---|
| dmfrey | tgm4883, hey, since I moved to 0.27, my mythfilldatabase doesn't seem to be running based on the schedule setup by mythtv-setup, which is set to run at the schedulesdirect recommended timeslot | 17:06 |
| dmfrey | is there a service or cron that i need to re-enable after the update? | 17:07 |
| === dahlSTROM is now known as dahlSTROM|sleep | ||
| === dahlSTROM|sleep is now known as dahlSTROM | ||
| tgm4883 | dmfrey, no, that is all handled by mythbackend. It should spawn a mythfilldatabase when it's suppose to. I'd check the logs and see if there are any errors | 18:59 |
| tgm4883 | sabhain, I usually just reinstall | 18:59 |
| dmfrey | they aren't showing errors, just that they didn't run | 18:59 |
| dmfrey | maybe i am looking in the wrong log | 18:59 |
| tgm4883 | dmfrey, I'd think mythbackend.log | 19:01 |
| tgm4883 | but possibly mythfilldatabase | 19:01 |
| tgm4883 | .log | 19:01 |
| superm1 | i think in general it will go quicker if you just backup/restore DB | 20:47 |
| superm1 | sabhain: ^ | 20:47 |
| sabhain | tgm4883: thanks, just starting it now. I've been planning to swap out the / drive for a new SSD so it's a pretty low risk approach I think. I can essentially go right back if anything gets totally screwed up. | 20:54 |
| sabhain | superm1: thanks for the input. | 20:54 |
| === dahlSTROM is now known as dahlSTROM|sleep | ||
| superm1 | sabhain: cool even better :) | 23:41 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!