| === qwebirc83810 is now known as blackbart | ||
| === blackbart is now known as kdx7214 | ||
| kdx7214 | Does the control centre not install mysql/db structure/users when you do a secondary backend? It's failing to connect and none of it is present | 02:42 |
|---|---|---|
| tgm4883 | kdx7214: you shouldn't have mysql on a secondary backend | 02:49 |
| kdx7214 | then why does it ask for the information and error out in the logs? I'm confused | 02:50 |
| tgm4883 | kdx7214: you should be connecting the the mysql server on your master backend | 02:51 |
| kdx7214 | ok, so then do I leave the local backend config blank in setup on the remote frontend? | 02:52 |
| tgm4883 | kdx7214: you would still have that populated | 02:52 |
| kdx7214 | so it has information but actually does nothing (except show errors in the backend log file that is) | 02:53 |
| tgm4883 | kdx7214: can you post a screenshot and pastebin the log? | 02:53 |
| kdx7214 | yeah, hold on and let me generate it again - just cleared logs to check something | 02:54 |
| kdx7214 | ok, here's a quick screen cap (couldn't figure out the pastbin part on short notice) | 03:01 |
| kdx7214 | http://imgur.com/a/nyK79 | 03:01 |
| kdx7214 | this machine is on 16.04 so have to use journalctl for the logs | 03:01 |
| tgm4883 | kdx7214: might be worth checking /home/mythtv/.mythtv/config.xml and see if the proper DB credentials are in there | 03:03 |
| kdx7214 | they are correct for master backend | 03:04 |
| tgm4883 | hmm, ok | 03:04 |
| === qwebirc44555 is now known as kdx7214 | ||
| kdx7214 | Quick question about secondary frontend and livetv | 21:27 |
| kdx7214 | I have a primary backend without a frontend - it has disk and mysql only | 21:28 |
| kdx7214 | secondary front end mounts disks via cifs (working find) | 21:28 |
| kdx7214 | (*fine) | 21:28 |
| kdx7214 | no db overrides on secondary front end so should use storage groups defined on master | 21:28 |
| kdx7214 | but when I go to watch livetv it tries to use a default file in /mnt/store which I do not have setup anywhere | 21:28 |
| kdx7214 | any thoughts on what I'm doing wrong? | 21:29 |
| kdx7214 | here's a snip of the log http://imgur.com/a/1bJkX | 21:30 |
| tgm4883 | kdx7214: why are you mounting stuff on the frontend? | 21:30 |
| kdx7214 | because the wiki said I have to | 21:30 |
| kdx7214 | since storage is on primary backend | 21:31 |
| tgm4883 | kdx7214: why do you have mythbackend running on your frontend? | 21:31 |
| kdx7214 | because there is a capture card there and the wiki says you must run backend for that | 21:31 |
| tgm4883 | ah ok | 21:32 |
| tgm4883 | And you've defined the card in your secondary backend? | 21:32 |
| kdx7214 | I've run mythtv for years but always on one machine - this is my first attempt to load balance for eventual more front ends | 21:32 |
| kdx7214 | Yup | 21:32 |
| kdx7214 | Card is there and it's showing as active | 21:32 |
| kdx7214 | when I start LiveTV it just delays a few seconds and returns to the front end | 21:33 |
| kdx7214 | only suspicious thing is the wrong path it tries to open for the recording | 21:33 |
| tgm4883 | Ok, so on your secondary backend, you ran mythtv-setup? | 21:34 |
| kdx7214 | yes | 21:34 |
| tgm4883 | and you don't have that path listed in your livetv storage group on either backend? | 21:35 |
| kdx7214 | not the /mnt/store one | 21:35 |
| tgm4883 | odd | 21:35 |
| kdx7214 | I suspect it's a default in the code. I checked the mysql tables and that is not anywhere in the db | 21:35 |
| tgm4883 | possibly | 21:35 |
| kdx7214 | just not sure under what conditions it tries to use it | 21:36 |
| tgm4883 | I would suggest adding a directory on your secondary backend for a livetv storage group | 21:36 |
| kdx7214 | would have to be the mount point as the ssd doesn't have enough space for that long term | 21:36 |
| kdx7214 | was hoping to avoid a secondary override | 21:36 |
| tgm4883 | kdx7214: what do you mean by secondary override? | 21:37 |
| kdx7214 | according to the wiki, if you go into mythtv-setup on the secondary backend and define a storage group, that will override what is on the primary | 21:37 |
| kdx7214 | trying to keep the secondary backend setup as simplistic as possible | 21:37 |
| tgm4883 | kdx7214: that is true. So without that, it will use the values from your primary backend. What do you have for live tv storage group on your primary? | 21:38 |
| kdx7214 | I have 3 setup: | 21:39 |
| kdx7214 | - /storage/disk1/a/livetv | 21:39 |
| kdx7214 | - /storage/disk2/b/livetv | 21:39 |
| kdx7214 | - /storage/disk3/c/livetv | 21:39 |
| kdx7214 | all folders exist, have correct permissions, and are fully accessible | 21:39 |
| tgm4883 | kdx7214: those are mounted on the secondary backend at those same locations? | 21:40 |
| kdx7214 | yes | 21:40 |
| kdx7214 | also made sure uid/gid for user mythtv and group mythtv are same on both machines | 21:40 |
| tgm4883 | hmm | 21:41 |
| tgm4883 | kdx7214: I would test adding one of those directories to the SG at the SBE level | 21:41 |
| kdx7214 | k, I'll give that a shot. Hadn't tried that yet in case I was doing something stupid :D | 21:42 |
| kdx7214 | Oh, btw, you were helping me yesterday and I figured out the problem... | 21:42 |
| kdx7214 | it seems Mythbuntu Control Center (or mythtv-setup) creates numerous config.xml files | 21:42 |
| kdx7214 | and they are not all links - and were different, which is odd on a fresh install on a new machine | 21:43 |
| tgm4883 | yea that's weird | 21:43 |
| tgm4883 | they should all be a symlink to /etc/mythtv/config.xml | 21:43 |
| kdx7214 | had no idea it creates so many of those | 21:43 |
| kdx7214 | I changed them all to be symlinks to that file for simplicity | 21:43 |
| tgm4883 | should be one in each home directory and then in /etc/mythtv | 21:43 |
| tgm4883 | yea that makes it easier | 21:43 |
| kdx7214 | for whatever reason the one in /home/mythtv and /root were not links and were different | 21:44 |
| kdx7214 | ok, the sbe override did fix it. LiveTV now works just fine - just wonder why needed the override | 21:47 |
| kdx7214 | One last question (for now anyway)... | 21:47 |
| kdx7214 | when I run mythtv-setup anywhere on a machine with systemd, it fails to start/stop the backend properly | 21:48 |
| kdx7214 | Is that normal for mythtbuntu on 16.04? | 21:48 |
| tgm4883 | kdx7214: I don't believe so, does it kick out an error? How are you trying to stop it? | 21:48 |
| kdx7214 | It normally does it by itself on non-systemd machines. If I run the setup program it stops the backend, runs setup, and then gives option to start backend/mythfilldatabase at exit | 21:49 |
| kdx7214 | both stop and start fail so I have to do it manually with sudo systemctl start mythtv-backend | 21:50 |
| kdx7214 | (or stop, obviously) | 21:50 |
| kdx7214 | my assumption was it still tried to run /etc/init.d/mythtv-backend but that's there and just runs the systemctl stuff | 21:50 |
| kdx7214 | but not critical - I know it has to be done so can deal with it that way :) | 21:52 |
| kdx7214 | Thanks for the help! | 21:52 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!