=== SteveH0_ is now known as SteveH0 [01:54] I have a dying hard drive (hardware errors) and after I reinitialize a replacement, I'd like to know what the easiest method would be to move the old configuration and data (shows) onto the new drive. Any assistance would be most appreciated! [02:18] dd [02:19] I have a dying hard drive (hardware errors) and after I reinitialize a replacement, I'd like to know what the easiest method would be to move the old configuration and data (shows) onto the new drive. Any assistance would be most appreciated! [02:19] dd === SteveH0_ is now known as SteveH0 [02:21] Thanks for the comment about dd, but as I said, the drive is dying. I'm really looking for which directories or files I need to try to move. [02:22] just worried about recordings ? [02:23] some about the shows, but also my canned searches. [02:26] then, database backup + your media directory [02:29] i use dd or ddrescue in those cases though [02:29] and I just dealt with it a few months back [02:32] Not sure about db backup? Is this a MySQL thing? (Sorry, my SIL called to wish me happy veterans day) [02:42] yep [02:44] http://www.mythtv.org/wiki/Backup_your_database [02:44] OK, I see the recordings at /var/lib/mythtv. I'll look at your link. [02:46] once you have those backed up [02:46] try a dd or ddrescue [02:46] you might be able to get everything mirrored [02:48] dd is just, dd if=/dev/src of=/dev/dest [02:48] ddrescue is covered pretty well here: http://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html [03:58] Hydr0p0nX: Thanks! I have made several back ups, and have stored at least one off the dying drive. [14:08] I've installed mythtv on top of ubuntu 12.04.1, and for some reason, when mythfronted starts up, my keyboard doesn't work until I click the mouse - any ideas? [15:14] superm1: ping, you around? [15:14] Yep [15:15] hey, had a quick question about the current upstart script you guys use... [15:16] I can't seem to get it to work for me - I run vanilla ubuntu server, and had used an older version of the script you posted to the wiki for probably 3+ years... [15:17] however, I tried to pull in the changes from the latest you have in the packaging folder on git, but now whenever I try to do a "service mythtv-backend start", it basically just hangs and never launches mythbackend - any ideas? I'm not exactly sure how to even troubleshoot upstart [15:18] superm1: ^ :) [15:19] skd5aner: which version of ubuntu? [15:19] 12.10 [15:19] ok so not the super newest version of upstart at least [15:20] and i'm assuming you're using master version of packaging and master mythtv too? [15:20] nope, but I am considering upgrading to 13.10 probably sometime soon [15:20] 0.27-fixes [15:20] for both [15:20] Oh ok [15:21] sorry - I thought I mentioned... [15:21] I compile mythtv from source :) [15:21] I don't actually use mythbuntu, but I do like to mirror some of things you guys do (like upstart) :) [15:21] right i knew you compiled from source, just wasn't sure what you were compiling these days [15:21] gotcha :) [15:21] so have you already tried to make sure those pre-start parts work? [15:22] I'm wondering if that's actually the problem... [15:22] just a quick sec [15:22] i mean it should only hang for 15 seconds or so if the pre-start part fails [15:22] but mythbackend also wouldn't start [15:24] here's what the script looks like [15:24] yea, I've waited for several mins just to make sure I wans't impatient, heh [15:25] http://pastebin.com/Wk3gC7g0 [15:25] actually [15:26] I commented out that pre-start section just to test [15:26] and it still doesnt' work [15:26] oh ok [15:26] and already tried to comment out the ulimit change? [15:26] well, hang on... :P [15:26] I hadn't tried to work on this in about a month [15:26] so I forgot where i left off... [15:26] lol [15:27] and the other change you have is syslog logging, idk does that syntax still work in 0.27? i know we had to make changes for syslog7 [15:28] if neither of those yield anything, next thing you should go investigate is /var/log/upstart and see if there is a myth related log sitting in there [15:29] ok, ok... [15:29] I remember sorta where I left off - sorry for mumbling through my self-made confusion here... [15:29] the version I sent you is from my slave backend... I commented out the pre-startup stuff because I don't have mysql on that machine... [15:30] my mbe is in the process of rebooting and has still not come backonline, I think it's checking disks... [15:30] superm1: yea, that log was very vauge... [15:30] also, I don't use syslog, that was one of the differences I made in the script, I output to a file [15:30] ah [15:31] I made only a very few slight tweaks... 1) path to mythbackend was slightly different, and 2) syslog to logfile/path [15:31] well if /var/log/upstart isn't too useful when the MBE comes up, you can --verbose to your kernel command line to get upstart into a more verbose mode (http://upstart.ubuntu.com/wiki/Debugging) [15:31] beyond that, it's almost identical [15:32] k, let me see where I get... it had stumped me for quite a while and I just gave up and started using the CLI to launch mythbackend in the interim :/ [15:32] thanks for the leads, I'll keep you posted [15:32] sure [15:33] also, thanks for all the hard work on mythbuntu! I'm possibly going to be implementing a new frontend soon and I think I'll just go the straight mythbuntu route this time :) [15:34] awesome :) [15:34] if your timing lines up with our 14.04 ISOs starting to stabilize it would be great to have a live tester on them [15:34] right now they're a bit of a mess since the installer switched to python3 and not everything is ported yet for the mythbuntu apps [15:40] superm1: cool - I'll let you know, it may be at least until Christmas before I'd even consider spending money on hardware [15:40] funds are tied up for other reasons this time of year :) [15:42] superm1: ok, ran to the basement and my mbe had a kernel panic during reboot (odd)... just came back up... [15:42] superm1: so, during boot, the upstart script appears to work. Mythbackend is running.... [15:42] cool on the new HW, that's closer to when i'll have more contiguous free time to be fixing 14.04 stuff anyhow [15:43] however, when I do a service mythtv-backend stop, nothing happens [15:43] can you pastebin the script as it is? are you maybe missing some fork or --daemon or exec lines? [15:43] we did make some changes there specifically in the past months [15:44] http://pastebin.com/HCpZs40C [15:45] yep you're missing the exec command at the start of your mythbackend call [15:45] omg [15:45] UGH! [15:45] haha, it's always the small things! [15:47] superm1: good eye, but I definitely feel like I have egg on my face now [15:47] I swear it had to have been something like that at first and thought I went through it with a fine tooth comb line by line [15:48] made the change, trying now [15:49] hmmmm [15:49] not sure that "fixed it" [15:49] you'll need to reboot most likely [15:49] we made that change because upstart was getting in this weird state where it couldn't properly track processes [15:49] ah [15:50] k, rebooting [16:15] superm1: works after a reboot! [16:15] thanks superm1, really... that was starting to get under my sking, thanks for the second set of eyes :S [16:15] woot. sure glad to help [16:15] s/sking/skin [16:19] superm1: out of curiosity... if mythbackend were to segfault, would the upstart script attempt to relaunch? [16:19] Yep [16:20] ok, that's great news! [16:20] that's what that respawn thing should do for you [16:20] Right now, mythbackend segfaults for me every morning... I've got a couple bug reports in [16:20] if it respawns more than twice within 3600 seconds though it won't do it again [16:21] gotcha [16:21] that makes sense given the context of the script [16:21] I thought that's what those lines did, but I know very little about upstart :) [16:23] yeah it's one of the big benefits imo on how it does process tracking and can do that [16:23] we do the same thing with mythfrontend with a wrapper around it [16:23] for 14.04 we might actually make mythfrontend an upstart tracked job though too since it can track user jobs in 14.04 [17:13] superm1: yea, I "borrowed" your idea for mythfrotnend too... I used to use gdm with an .xsession, and when mythfrontend died, it'd restart the gdm session. However, when I switched to lightdm, it didn't handle the auto-login as gracefully [17:14] superm1: so, I saw how you guys did it with the loop and now it's rediculously quick to recover [17:14] that's been a very welcome addition [17:15] how cool is that [17:16] i mapped a shell script to the power button on my remote which does a killall mythfrontend.real and then starts it again because it freezes every now and then === dahlSTROM|sleep is now known as dahlSTROM [19:12] Hello room === dahlSTROM is now known as dahlSTROM|sleep === dahlSTROM|sleep is now known as dahlSTROM [20:53] hey guys having issues with one of my frontends [20:54] several of my channels show up as unknown(unknown) on the frontend, with no channel data. If i watch it however, i am viewing the correct channel [20:54] if i access mythweb however, all listings are present and correct [20:55] i have 2 frontends and one backend, both frontends have the problem [20:56] any idea what is wrong?