[08:09] Hi 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] Am on 16.04LTS [08:18] Hi 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. [10:03] May I add; I've also installed ivtv-utils incl. v4l - no success! Problem persist and this is the third re-install, please help. [16:35] Any idea where to find a fix for the "Enable MySQL Performance Tweaks"-issue? I am having serious trouble after I enabled it... [17:07] any 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 install [17:08] qwebirc94831: A fix for it is in progress [17:08] You could manually do it though if you want [17:11] I already fixed the mythtv-tweaks.cnf file : table_cache = 128 -> table_open_cache = 128 [17:11] But what next? [17:12] My frontends or mythweb will not connect to backend... [17:12] qwebirc28266: well that's a different issue then [17:13] oh, how so? [17:13] well performance tweaks don't prevent clients from connecting [17:14] The only bug with the performance tweaks was preventing mysql from starting [17:17] have to check my logs, all this happened after enabling the tweaks [17:22] qwebirc28266: 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 file [17:22] (mysql -h -u 1) one instance is local [17:32] 2) 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:* LISTEN [17:35] 3) yes i can connect [17:35] so all seems to be workin in this sense [17:36] any ideas? [17:46] qwebirc28266: run mythfrontend from the command line and see what config.xml file it's using [17:47] There will be one in the home directory at ~/.mythtv.config.xml that should link back to /etc/mythtv/config.xml [17:52] sorry what am i looking for in the text? [17:53] qwebirc28266: well you should see a few checks for xonfig.xml [17:53] config.xml* [17:54] should I past the output of the terminal? [17:56] qwebirc28266: sure [17:56] pastebin it [17:58] http://paste.ubuntu.com/23059181/ [17:58] hmm, interesting [17:59] ? [17:59] qwebirc28266: do your /etc/mythtv/config.xml and ~/.mythtv/config.xml files match? [17:59] lets see. [17:59] actually wait, that's your issue [17:59] or at least, here is one issue [18:00] do 'sudo dpkg-reconfigure mythtv-database' [18:00] it should ask you if you are going to have other clients connect, say yes [18:00] remote clients* [18:01] thats all it did ask [18:01] perfect [18:01] now restart mysql [18:01] 'sudo service mysql restart [18:01] ' [18:01] then do 'netstat -tulpn' again [18:01] ok, done [18:02] What i'm seeing is mysql listening on 127.0.0.1 but your frontend is trying to use the private IP [18:02] so is mysql still only listening on 127.0.0.1 [18:02] This is what is shouldn't look like "127.0.0.1:6543" [18:02] It should look like "0.0.0.0:6543" [18:03] Or possibly something similiar due to ipv6 [18:03] still is tcp 0 0 127.0.0.1:6543 0.0.0.0:* LISTEN [18:03] hmm [18:04] and tcp 0 0 127.0.0.1:6544 0.0.0.0:* LISTEN [18:05] qwebirc28266: are you able to do (from your remote machine) 'mysql -h 192.168.1.100 -u mythtv -p mythconverg' [18:06] mysql> [18:09] yes i am [18:09] hmm [18:09] qwebirc28266: and 192.168.1.100 is your master backend? [18:09] yes [18:10] from the master backend fe clien when i try to watch tv it says all my dvb-t cards are busy [18:11] qwebirc28266: wait, I thought you said your frontends can't connect to your backend? [18:11] 10:12 AM My frontends or mythweb will not connect to backend... [18:12] You can't get to "Watch TV" if the frontend isn't connecting to the backend [18:13] the separate fe wont connect [18:14] qwebirc28266: ok, and when you say won't connect. What do you see? [18:14] and actually just noticed that the one on the backend dos partially work [18:15] sorry for the misinfo! [18:16] mythweb 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] on the separate fe it open the menues but shows no content [18:17] Ok, are we troubleshooting the frontend that won't connect or mythweb first [18:17] the master fe shws menus and old recordings [18:17] you decide [18:18] since you are kindly helping! [18:18] lets do the other frontend [18:18] the separate one? [18:18] yea [18:18] ok [18:20] I'm connected via vnc [18:21] to the fe. [18:22] when i open myth it opens the menus, but says could not connect to mbe [18:26] output from terminal: http://paste.ubuntu.com/23059229/ [18:28] Did you run that mysql command from that box that can't connect? [18:28] yes i did [18:29] qwebirc28266: look at /home/aapo/.mythtv/config.xml, are those credentials correct? [18:31] host ip, username and passwd are all correct [18:32] qwebirc28266: on your master backend, can you run 'netstat -tulpn | nc termbin.com 9999' [18:32] just did a double check and mysq opens from that box just like before [18:32] and give me the link [18:34] http://termbin.com/y5rl [18:35] man I do not understand how your mysql command is working with that config [18:37] I do not understand how everyting went wrong after "tweaks" and it took some time to show [18:38] I would understand if it was compleatly broken...but some of it works [18:39] should I just do a reinstall for the fifth time...I really dont want to [18:39] qwebirc28266: ok do this. One sec [18:39] ok [18:41] 'ls /etc/mysql/conf.d/ /etc/mysql/mysql.conf.d/ | nc termbin.com 9999' [18:42] http://termbin.com/p1tx [18:42] qwebirc28266: can you pastebin both mythtv.cnf files? [18:43] qwebirc28266: or is one just a symlink to the other [18:43] if so, you can just pastebin one [18:45] http://paste.ubuntu.com/23059266/ [18:46] qwebirc28266: is one of those files a symlink to the other? [18:46] the latter one is a symlink [18:46] qwebirc28266: ok good [18:47] qwebirc28266: ok, in that file lets try this, change "bind-address=::" to "bind-address=0.0.0.0" [18:47] then restart mysql [18:49] done [18:50] frontend is the same after restart [19:09] are you out of ideas? [19:22] Is it easy to only reinstall mythtv? I would not like to reinstall the whole distro [19:24] I've done a lot of work on other servers and setup on this computer. [19:26] qwebirc28266: sorry I'm at work so i'm only half paying attention. Can I see the 'netstat -tulpn again'? [19:27] http://paste.ubuntu.com/23059353/ [19:28] qwebirc28266: that legit makes no sense. That is from the master backend where you made that bind-address change and restarted mysql? [19:29] yep [19:29] ok, how about you restart the computer then check it again [19:30] sure, I will join in a few mins [19:33] fe and be_d [19:34] front end and master fe are the same, also mythweb... [19:34] http://paste.ubuntu.com/23059363/ [19:34] above is the latest netstat -tulpn from the master backend [19:43] tgm4883: so no development [19:44] I have to go to sleep soon since its work tomorrow. Any ideas? [19:45] a reinstall of mythtv is not an issue, I will only lose about and hour of work [19:45] whereas a fresh install of mythbuntu 16.04 will take about 6 hours [19:51] qwebirc49029: in mythtv-setup, on the first page of the general section, what do you have for the ip addresses? [19:52] 1 min [19:52] ipv4: 192.168.1.100 [19:53] ipv6 ::1 [19:53] ip on the bottom: 192.168.1.100 [19:54] qwebirc49029: remote frontend still can't connect? [19:54] qwebirc49029: what's the output of 'sudo ufw status' [19:57] fe is still unable to connect. The output from the masterbackend: Status: inactive [20:00] qwebirc49029: this is 16.04? [20:00] yep [20:02] qwebirc49029: ok, try this from the remove machine [20:03] sorry, where do i find this? [20:03] qwebirc49029: from the remove machine "mysql -h 192.168.1.100 -u mythtv -Pmythtv mythtvconverg" [20:04] sorry [20:04] qwebirc49029: from the remove machine "mysql -h 192.168.1.100 -u mythtv -pmythtv mythtvconverg" [20:07] ok im in mysq [20:08] I entered the 'from the remove machine' [20:08] qwebirc49029: you entered the command just as I had put it? [20:09] The first or second command upper or lower case? [20:09] qwebirc49029: can you pastebin the command you ran and the output? [20:10] mysql> from the remove machine -> [20:10] qwebirc49029: no, I, stop [20:10] ok [20:11] qwebirc49029: on your remote frontend, are you logged into the remote frontend now? [20:11] now i am [20:11] sorry! [20:13] from: can't read /var/mail/the [20:13] qwebirc49029: ok, open a terminal on that remote machine and run the command "mysql -h 192.168.1.100 -u mythtv -pmythtv mythtvconverg" [20:14] ok im in mysq on the frontend [20:15] qwebirc49029: using that command I gave? ( "mysql -h 192.168.1.100 -u mythtv -pmythtv mythtvconverg" ) ? [20:16] qwebirc49029: can you pastebin everything in the terminal ? [20:16] I entered "mysql -h 192.168.1.100 -u mythtv -pmythtv mythtvconverg" and then my password [20:16] sorry [20:16] i ment "mysql -h 192.168.1.100 -u mythtv -p mythconverg" [20:16] and then my password [20:18] here is the terminal from the remote fe: http://paste.ubuntu.com/23059439/ [20:19] qwebirc49029: and this is the box that the frontend can't connect? [20:19] yes [20:20] qwebirc49029: 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 correct [20:20] credentials, 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] qwebirc49029: you could also try asking in #mythtv-users where there might be more users that can help [20:22] Is there an easy way to just reinstall myhtbackend from scrach without reinstalling the whole distro? [20:22] thanks for your effort! [20:22] qwebirc49029: 'sudo apt-get install --reinstall mythtv-backend' [20:24] this goes also for the mythbuntu control center setusp? [20:25] ok. i meant how do i start without any settings and db's? [20:28] qwebirc49029: you'd need to drop the mysql database then reinstall mythtv-database [21:00] tgm4883: when i shut down the frontend my backend connection from mythweb and master fe started to work. [21:01] qwebirc49029: how did you shut it down? [21:01] just from the menu shut down, did not put to sleep [21:02] qwebirc49029: did you move your backend to another host or rename your boxes? [21:02] I just did a reinstall of the backend box and upgraded the separate fe to 0,28 myth [21:03] qwebirc49029: so they've always been the same hostnames? [21:03] yep...so I guess this is the problem [21:03] qwebirc49029: well that shouldn't be. Does it break again if you startup your other frontend? [21:04] no for the last 30 mins. the fe is really lagging [21:05] qwebirc49029: the remote frontend is? [21:05] yes the remote fe [21:05] qwebirc49029: what's the output of 'dpkg -l | grep myth' [21:05] for the remote fe [21:05] ? [21:05] yea [21:06] I'll reboot it now [21:07] http://pastebin.ubuntu.com/23059541/ [21:09] ok, looks good. It's still lagging? [21:10] mythfe on the remote opens up good but will not go to recordings. [21:10] qwebirc49029: you'd need to paste the logs from that box. [21:12] frontend and backend logs? [21:12] or what [21:17] here is the remote frontend log: http://pastebin.ubuntu.com/23059566/ [21:21] qeyou've got some malformed packet errors regarding the database [21:21] I'd ask in #mythtv-users