/srv/irclogs.ubuntu.com/2013/11/12/#ubuntu-mythtv.txt

=== SteveH0_ is now known as SteveH0
SteveH0I 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!01:54
Hydr0p0nXdd02:18
SteveH0_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
Hydr0p0nXdd02:19
=== SteveH0_ is now known as SteveH0
SteveH0Thanks 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:21
Hydr0p0nXjust worried about recordings ?02:22
SteveH0some about the shows, but also my canned searches.02:23
Hydr0p0nXthen, database backup + your media directory02:26
Hydr0p0nXi use dd or ddrescue in those cases though02:29
Hydr0p0nXand I just dealt with it a few months back02:29
SteveH0Not sure about db backup?  Is this a MySQL thing?  (Sorry, my SIL called to wish me happy veterans day)02:32
Hydr0p0nXyep02:42
Hydr0p0nXhttp://www.mythtv.org/wiki/Backup_your_database02:44
SteveH0OK, I see the recordings at /var/lib/mythtv.  I'll look at your link.02:44
Hydr0p0nXonce you have those backed up02:46
Hydr0p0nXtry a dd or ddrescue02:46
Hydr0p0nXyou might be able to get everything mirrored02:46
Hydr0p0nXdd is just, dd if=/dev/src of=/dev/dest02:48
Hydr0p0nXddrescue is covered pretty well here: http://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html02:48
SteveH0Hydr0p0nX: Thanks!  I have made several back ups, and have stored at least one off the dying drive.03:58
qwebirc17277I'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?14:08
skd5anersuperm1: ping, you around?15:14
superm1Yep15:14
skd5anerhey, had a quick question about the current upstart script you guys use...15:15
skd5anerI 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:16
skd5anerhowever, 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 upstart15:17
skd5anersuperm1: ^ :)15:18
superm1skd5aner: which version of ubuntu?15:19
skd5aner12.1015:19
superm1ok so not the super newest version of upstart at least15:19
superm1and i'm assuming you're using master version of packaging and master mythtv too?15:20
skd5anernope, but I am considering upgrading to 13.10 probably sometime soon15:20
skd5aner0.27-fixes15:20
skd5anerfor both15:20
superm1Oh ok15:20
skd5anersorry - I thought I mentioned...15:21
skd5anerI compile mythtv from source :)15:21
skd5anerI don't actually use mythbuntu, but I do like to mirror some of things you guys do (like upstart) :)15:21
superm1right i knew you compiled from source, just wasn't sure what you were compiling these days15:21
skd5anergotcha :)15:21
superm1so have you already tried to make sure those pre-start parts work?15:21
skd5anerI'm wondering if that's actually the problem...15:22
skd5anerjust a quick sec15:22
superm1i mean it should only hang for 15 seconds or so if the pre-start part fails15:22
superm1but mythbackend also wouldn't start15:22
skd5anerhere's what the script looks like15:24
skd5aneryea, I've waited for several mins just to make sure I wans't impatient, heh15:24
skd5anerhttp://pastebin.com/Wk3gC7g015:25
skd5aneractually15:25
skd5anerI commented out that pre-start section just to test15:26
skd5anerand it still doesnt' work15:26
superm1oh ok15:26
superm1and already tried to comment out the ulimit change?15:26
skd5anerwell, hang on... :P15:26
skd5anerI hadn't tried to work on this in about a month15:26
skd5anerso I forgot where i left off...15:26
skd5anerlol15:26
superm1and 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 syslog715:27
superm1if 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 there15:28
skd5anerok, ok...15:29
skd5anerI remember sorta where I left off - sorry for mumbling through my self-made confusion here...15:29
skd5anerthe 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:29
skd5anermy mbe is in the process of rebooting and has still not come backonline, I think it's checking disks...15:30
skd5anersuperm1: yea, that log was very vauge...15:30
skd5aneralso, I don't use syslog, that was one of the differences I made in the script, I output to a file15:30
superm1ah15:30
skd5anerI made only a very few slight tweaks... 1) path to mythbackend was slightly different, and 2) syslog to logfile/path15:31
superm1well 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
skd5anerbeyond that, it's almost identical15:31
skd5anerk, 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
skd5anerthanks for the leads, I'll keep you posted15:32
superm1sure15:32
skd5aneralso, 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:33
superm1awesome :)15:34
superm1if your timing lines up with our 14.04 ISOs starting to stabilize it would be great to have a live tester on them15:34
superm1right now they're a bit of a mess since the installer switched to python3 and not everything is ported yet for the mythbuntu apps15:34
skd5anersuperm1: cool - I'll let you know, it may be at least until Christmas before I'd even consider spending money on hardware15:40
skd5anerfunds are tied up for other reasons this time of year :)15:40
skd5anersuperm1: ok, ran to the basement and my mbe had a kernel panic during reboot (odd)... just came back up...15:42
skd5anersuperm1: so, during boot, the upstart script appears to work.  Mythbackend is running....15:42
superm1cool on the new HW, that's closer to when i'll have more contiguous free time to be fixing 14.04 stuff anyhow15:42
skd5anerhowever, when I do a service mythtv-backend stop, nothing happens15:43
superm1can you pastebin the script as it is?  are you maybe missing some fork or --daemon or exec lines?15:43
superm1we did make some changes there specifically in the past months15:43
skd5anerhttp://pastebin.com/HCpZs40C15:44
superm1yep you're missing the exec command at the start of your mythbackend call15:45
skd5aneromg15:45
skd5anerUGH!15:45
superm1haha, it's always the small things!15:45
skd5anersuperm1: good eye, but I definitely feel like I have egg on my face now15:47
skd5anerI swear it had to have been something like that at first and thought I went through it with a fine tooth comb line by line15:47
skd5anermade the change, trying now15:48
skd5anerhmmmm15:49
skd5anernot sure that "fixed it"15:49
superm1you'll need to reboot most likely15:49
superm1we made that change because upstart was getting in this weird state where it couldn't properly track processes15:49
skd5anerah15:49
skd5anerk, rebooting15:50
skd5anersuperm1: works after a reboot!16:15
skd5anerthanks superm1, really... that was starting to get under my sking, thanks for the second set of eyes :S16:15
superm1woot. sure glad to help16:15
skd5aners/sking/skin16:15
skd5anersuperm1: out of curiosity... if mythbackend were to segfault, would the upstart script attempt to relaunch?16:19
superm1Yep16:19
skd5anerok, that's great news!16:20
superm1that's what that respawn thing should do for you16:20
skd5anerRight now, mythbackend segfaults for me every morning... I've got a couple bug reports in16:20
superm1if it respawns more than twice within 3600 seconds though it won't do it again16:20
skd5anergotcha16:21
skd5anerthat makes sense given the context of the script16:21
skd5anerI thought that's what those lines did, but I know very little about upstart :)16:21
superm1yeah it's one of the big benefits imo on how it does process tracking and can do that16:23
superm1we do the same thing with mythfrontend with a wrapper around it16:23
superm1for 14.04 we might actually make mythfrontend an upstart tracked job though too since it can track user jobs in 14.0416:23
skd5anersuperm1: 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 gracefully17:13
skd5anersuperm1: so, I saw how you guys did it with the loop and now it's rediculously quick to recover17:14
skd5anerthat's been a very welcome addition17:14
Jay2k1how cool is that17:15
Jay2k1i 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 then17:16
=== dahlSTROM|sleep is now known as dahlSTROM
qwebirc66608Hello room19:12
=== dahlSTROM is now known as dahlSTROM|sleep
=== dahlSTROM|sleep is now known as dahlSTROM
TandyUKhey guys having issues with one of my frontends20:53
TandyUKseveral 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 channel20:54
TandyUKif i access mythweb however, all listings are present and correct20:54
TandyUKi have 2 frontends and one backend, both frontends have the problem20:55
TandyUKany idea what is wrong?20:56

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!