/srv/irclogs.ubuntu.com/2016/08/15/#ubuntu-mythtv.txt

qwebirc72150Hi All, I have the following problem: "ivtv0: Encoder mailbox not found" resulting in; "ivtv0: Failed to initialize on device" everything online I find isn't the solution and the material found is now dated. How do I fix this problem? This problem renders my installation useless, please help.08:09
qwebirc72150Am on 16.04LTS08:09
abongileHi All, I have the following problem: "ivtv0: Encoder mailbox not found" resulting in; "ivtv0: Failed to initialize on device" everything online I find isn't the solution and the material found is now dated. How do I fix this problem? This problem renders my installation useless, please help. Am on Mythbuntu 16.04LTS fresh install.08:18
abongileMay I add; I've also installed ivtv-utils incl. v4l - no success! Problem persist and this is the third re-install, please help.10:03
qwebirc29687Any idea where to find a fix for the "Enable MySQL Performance Tweaks"-issue? I am having serious trouble after I enabled it...16:35
qwebirc94831any fix on the enable MySQL performance tweaks? Saw a lot of trouble setting up my new Mythbuntu 16.04 and don't want to  do a fresh install17:07
tgm4883qwebirc94831:  A fix for it is in progress17:08
tgm4883You could manually do it though if you want17:08
qwebirc28266I already fixed the mythtv-tweaks.cnf file : table_cache = 128 -> table_open_cache = 12817:11
qwebirc28266But what next?17:11
qwebirc28266My frontends or mythweb will not connect to backend...17:12
tgm4883qwebirc28266: well that's a different issue then17:12
qwebirc28266oh, how so?17:13
tgm4883well performance tweaks don't prevent clients from connecting17:13
tgm4883The only bug with the performance tweaks was preventing mysql from starting17:14
qwebirc28266have to check my logs, all this happened after enabling the tweaks17:17
tgm4883qwebirc28266: well there's only really a few things to check here. 1) Are the clients remote to the backend or local.  2) Is MySQL running and listening on the appropriate address (netstat -tulpn). If remote, should be on the private IP address 3) Can you connect from the client machine from the command line with the credentials from your config.xml file17:22
tgm4883(mysql -h <host> -u <user -p mythconverg)17:22
qwebirc282661) one instance is local17:26
qwebirc282662) tcp        0      0 127.0.0.1:6543          0.0.0.0:*               LISTEN      -                tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      -                tcp        0      0 127.0.0.1:6544          0.0.0.0:*               LISTEN17:32
qwebirc282663) yes i can connect17:35
qwebirc28266so all seems to be workin in this sense17:35
qwebirc28266any ideas?17:36
tgm4883qwebirc28266: run mythfrontend from the command line and see what config.xml file it's using17:46
tgm4883There will be one in the home directory at ~/.mythtv.config.xml that should link back to /etc/mythtv/config.xml17:47
qwebirc28266sorry what am i looking for in the text?17:52
tgm4883qwebirc28266: well you should see a few checks for xonfig.xml17:53
tgm4883config.xml*17:53
qwebirc28266should I past the output of the terminal?17:54
tgm4883qwebirc28266: sure17:56
tgm4883pastebin it17:56
qwebirc28266http://paste.ubuntu.com/23059181/17:58
tgm4883hmm, interesting17:58
qwebirc28266?17:59
tgm4883qwebirc28266: do your /etc/mythtv/config.xml and ~/.mythtv/config.xml files match?17:59
qwebirc28266lets see.17:59
tgm4883actually wait, that's your issue17:59
tgm4883or at least, here is one issue17:59
tgm4883do 'sudo dpkg-reconfigure mythtv-database'18:00
tgm4883it should ask you if you are going to have other clients connect, say yes18:00
tgm4883remote clients*18:00
qwebirc28266thats all it did ask18:01
tgm4883perfect18:01
tgm4883now restart mysql18:01
tgm4883'sudo service mysql restart18:01
tgm4883'18:01
tgm4883then do 'netstat -tulpn' again18:01
qwebirc28266ok, done18:01
tgm4883What i'm seeing is mysql listening on 127.0.0.1 but your frontend is trying to use the private IP18:02
tgm4883so is mysql still only listening on 127.0.0.118:02
tgm4883This is what is shouldn't look like "127.0.0.1:6543"18:02
tgm4883It should look like "0.0.0.0:6543"18:02
tgm4883Or possibly something similiar due to ipv618:03
qwebirc28266still is tcp        0      0 127.0.0.1:6543          0.0.0.0:*               LISTEN18:03
tgm4883hmm18:03
qwebirc28266and tcp        0      0 127.0.0.1:6544          0.0.0.0:*               LISTEN18:04
tgm4883qwebirc28266: are you able to do (from your remote machine) 'mysql -h 192.168.1.100 -u mythtv -p mythconverg'18:05
qwebirc28266mysql>18:06
qwebirc28266yes i am18:09
tgm4883hmm18:09
tgm4883qwebirc28266: and 192.168.1.100 is your master backend?18:09
qwebirc28266yes18:09
qwebirc28266from the master backend fe clien when i try to watch tv it says all my dvb-t cards are busy18:10
tgm4883qwebirc28266: wait, I thought you said your frontends can't connect to your backend?18:11
tgm488310:12 AM <qwebirc28266> My frontends or mythweb will not connect to backend...18:11
tgm4883You can't get to "Watch TV" if the frontend isn't connecting to the backend18:12
qwebirc28266the separate fe wont connect18:13
tgm4883qwebirc28266: ok, and when you say won't connect. What do you see?18:14
qwebirc28266and actually just noticed that the one on the backend dos partially work18:14
qwebirc28266sorry for the misinfo!18:15
qwebirc28266mythweb gives the heades but shows no content exept:  Error  Unable to connect to the master backend at 192.168.1.100:6543. Is it running?18:16
qwebirc28266on the separate fe it open the menues but shows no content18:16
tgm4883Ok, are we troubleshooting the frontend that won't connect or mythweb first18:17
qwebirc28266the master fe shws menus and old recordings18:17
qwebirc28266you decide18:17
qwebirc28266since you are kindly helping!18:18
tgm4883lets do the other frontend18:18
qwebirc28266the separate one?18:18
tgm4883yea18:18
qwebirc28266ok18:18
qwebirc28266I'm connected via vnc18:20
qwebirc28266to the fe.18:21
qwebirc28266when i open myth it opens the menus, but says could not connect to mbe18:22
qwebirc28266output from terminal: http://paste.ubuntu.com/23059229/18:26
tgm4883Did you run that mysql command from that box that can't connect?18:28
qwebirc28266yes i did18:28
tgm4883qwebirc28266: look at /home/aapo/.mythtv/config.xml, are those credentials correct?18:29
qwebirc28266host ip, username and passwd are all correct18:31
tgm4883qwebirc28266: on your master backend, can you run 'netstat -tulpn | nc termbin.com 9999'18:32
qwebirc28266just did a double check and mysq opens from that box just like before18:32
tgm4883and give me the link18:32
qwebirc28266http://termbin.com/y5rl18:34
tgm4883man I do not understand how your mysql command is working with that config18:35
qwebirc28266I do not understand how everyting went wrong after "tweaks" and it took some time to show18:37
qwebirc28266I would understand if it was compleatly broken...but some of it works18:38
qwebirc28266should I just do a reinstall for the fifth time...I really dont want to18:39
tgm4883qwebirc28266: ok do this. One sec18:39
qwebirc28266ok18:39
tgm4883'ls /etc/mysql/conf.d/ /etc/mysql/mysql.conf.d/ | nc termbin.com 9999'18:41
qwebirc28266http://termbin.com/p1tx18:42
tgm4883qwebirc28266: can you pastebin both mythtv.cnf files?18:42
tgm4883qwebirc28266: or is one just a symlink to the other18:43
tgm4883if so, you can just pastebin one18:43
qwebirc28266http://paste.ubuntu.com/23059266/18:45
tgm4883qwebirc28266: is one of those files a symlink to the other?18:46
qwebirc28266the latter one is a symlink18:46
tgm4883qwebirc28266: ok good18:46
tgm4883qwebirc28266: ok, in that file lets try this, change "bind-address=::" to "bind-address=0.0.0.0"18:47
tgm4883then restart mysql18:47
qwebirc28266done18:49
qwebirc28266frontend is the same after restart18:50
qwebirc28266are you out of ideas?19:09
qwebirc28266Is it easy to only reinstall mythtv? I would not like to reinstall the whole distro19:22
qwebirc28266I've done a lot of work on other servers and setup on this computer.19:24
tgm4883qwebirc28266: sorry I'm at work so i'm only half paying attention. Can I see the 'netstat -tulpn again'?19:26
qwebirc28266http://paste.ubuntu.com/23059353/19:27
tgm4883qwebirc28266: that legit makes no sense. That is from the master backend where you made that bind-address change and restarted mysql?19:28
qwebirc28266yep19:29
tgm4883ok, how about you restart the computer then check it again19:29
qwebirc28266sure, I will join in a few mins19:30
qwebirc49029fe and be_d19:33
qwebirc49029front end and master fe are the same, also mythweb...19:34
qwebirc49029http://paste.ubuntu.com/23059363/19:34
qwebirc49029above is the latest netstat -tulpn from the master backend19:34
qwebirc49029tgm4883: so no development19:43
qwebirc49029I have to go to sleep soon since its work tomorrow. Any ideas?19:44
qwebirc49029a reinstall of mythtv is not an issue, I will only lose about and hour of work19:45
qwebirc49029whereas a fresh install of mythbuntu 16.04 will take about 6 hours19:45
tgm4883qwebirc49029: in mythtv-setup, on the first page of the general section, what do you have for the ip addresses?19:51
qwebirc490291 min19:52
qwebirc49029ipv4: 192.168.1.10019:52
qwebirc49029ipv6 ::119:53
qwebirc49029ip on the bottom: 192.168.1.10019:53
tgm4883qwebirc49029: remote frontend still can't connect?19:54
tgm4883qwebirc49029: what's the output of 'sudo ufw status'19:54
qwebirc49029fe is still unable to connect. The output from the masterbackend: Status: inactive19:57
tgm4883qwebirc49029: this is 16.04?20:00
qwebirc49029yep20:00
tgm4883qwebirc49029: ok, try this from the remove machine20:02
qwebirc49029sorry, where do i find this?20:03
tgm4883qwebirc49029: from the remove machine "mysql -h 192.168.1.100 -u mythtv -Pmythtv mythtvconverg"20:03
tgm4883sorry20:04
tgm4883qwebirc49029: from the remove machine "mysql -h 192.168.1.100 -u mythtv -pmythtv mythtvconverg"20:04
qwebirc49029ok im in mysq20:07
qwebirc49029I entered the 'from the remove machine'20:08
tgm4883qwebirc49029: you entered the command just as I had put it?20:08
tgm4883The first or second command upper or lower case?20:09
tgm4883qwebirc49029: can you pastebin the command you ran and the output?20:09
qwebirc49029mysql> from the remove machine     ->20:10
tgm4883qwebirc49029: no, I, stop20:10
qwebirc49029ok20:10
tgm4883qwebirc49029: on your remote frontend, are you logged into the remote frontend now?20:11
qwebirc49029now i am20:11
qwebirc49029sorry!20:11
qwebirc49029from: can't read /var/mail/the20:13
tgm4883qwebirc49029: ok, open a terminal on that remote machine and run the command  "mysql -h 192.168.1.100 -u mythtv -pmythtv mythtvconverg"20:13
qwebirc49029ok im in mysq on the frontend20:14
tgm4883qwebirc49029: using that command I gave? ( "mysql -h 192.168.1.100 -u mythtv -pmythtv mythtvconverg" ) ?20:15
tgm4883qwebirc49029: can you pastebin everything in the terminal ?20:16
qwebirc49029I entered "mysql -h 192.168.1.100 -u mythtv -pmythtv mythtvconverg" and then my password20:16
qwebirc49029sorry20:16
qwebirc49029i ment "mysql -h 192.168.1.100 -u mythtv -p mythconverg"20:16
qwebirc49029and then my password20:16
qwebirc49029here is the terminal from the remote fe: http://paste.ubuntu.com/23059439/20:18
tgm4883qwebirc49029: and this is the box that the frontend can't connect?20:19
qwebirc49029yes20:19
tgm4883qwebirc49029: I legit don't know. My gut says it's an issue with mysql stating it's only listening on 127.0.0.1, but somehow you said you can connect remotely using your credentials from the config.xml file (which shouldn't be possible if it's only listening on localhost). You've checked on the remote machine that your config.xml file has the correct20:20
tgm4883credentials, so we know it's not a username/password issue. I've heard faint rumblings about ipv6 causing connectivity issues so you could try disabling that completely.20:20
tgm4883qwebirc49029: you could also try asking in #mythtv-users where there might be more users that can help20:20
qwebirc49029Is there an easy way to just reinstall myhtbackend from scrach without reinstalling the whole distro?20:22
qwebirc49029thanks for your effort!20:22
tgm4883qwebirc49029: 'sudo apt-get install --reinstall mythtv-backend'20:22
qwebirc49029this goes also for the mythbuntu control center setusp?20:24
qwebirc49029ok. i meant how do i start without any settings and db's?20:25
tgm4883qwebirc49029: you'd need to drop the mysql database then reinstall mythtv-database20:28
qwebirc49029tgm4883: when i shut down the frontend my backend connection from mythweb and master fe started to work.21:00
tgm4883qwebirc49029: how did you shut it down?21:01
qwebirc49029just from the menu shut down, did not put to sleep21:01
tgm4883qwebirc49029: did you move your backend to another host or rename your boxes?21:02
qwebirc49029I just did a reinstall of the backend box and upgraded the separate fe to 0,28 myth21:02
tgm4883qwebirc49029: so they've always been the same hostnames?21:03
qwebirc49029yep...so I guess this is the problem21:03
tgm4883qwebirc49029: well that shouldn't be. Does it break again if you startup your other frontend?21:03
qwebirc49029no for the last 30 mins. the fe is really lagging21:04
tgm4883qwebirc49029: the remote frontend is?21:05
qwebirc49029yes the remote fe21:05
tgm4883qwebirc49029: what's the output of 'dpkg -l | grep myth'21:05
qwebirc49029for the remote fe21:05
qwebirc49029?21:05
tgm4883yea21:05
qwebirc49029I'll reboot it now21:06
qwebirc49029http://pastebin.ubuntu.com/23059541/21:07
tgm4883ok, looks good. It's still lagging?21:09
qwebirc49029mythfe on the remote opens up good but will not go to recordings.21:10
tgm4883qwebirc49029: you'd need to paste the logs from that box.21:10
qwebirc49029frontend and backend logs?21:12
qwebirc49029or what21:12
qwebirc49029here is the remote frontend log: http://pastebin.ubuntu.com/23059566/21:17
tgm4883qeyou've got some malformed packet errors regarding  the database21:21
tgm4883I'd ask in #mythtv-users21:21

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