| enyc | Hrrm... I suspect this is essentially a bug in MythBuntu -- I have a network config where I (knowingly) want to get MythBackend and Mysql listening on 'all interfaces' -- access possible across subnets, not just link-local-addresses ... and know what I'm doing with firewalling etc.... anyway... | 12:49 |
|---|---|---|
| enyc | ... If you install mythbuntu 14.04.1 and select the options for mythbackend used by other machines... -- it seems to setup mysql to listen on 0.0.0.0 | 12:50 |
| enyc | which makes mysql ipv4-only even though the rest of mythtv is correctly listening on the configured IPv4+IPv6 global addresses. | 12:50 |
| enyc | I (think) this needs fixing so that when mysql is set for 'all interfaces' on purpase it actually is set to listen on 0.0.0.0 and ::0, giving 'feature parity' IPv4+IPv6 at least in that regard | 12:51 |
| enyc | This was 'breaking' the auto-discover-mythbackend-from-local-subnet which wanted to talk to the IPv6 address and failed for the database part of course ;p | 12:51 |
| tgm4883 | enyc: that is true I guess, can you file a bug on launchpad for it? | 15:07 |
| tgm4883 | enyc: and for changing the mythtv db password, that can be done with a dpkg-reconfigure | 15:08 |
| enyc | tgm4883: hrrm... seemingly this is in the default mysql default config file.. and rerunning dpkg-reconfigure only comments/uncomments the bind-address= line automatically ... | 15:10 |
| tgm4883 | enyc: what are you running dpkg-reconfigure on? | 15:10 |
| enyc | tgm4883: I wonder what that then does for 'upgraders' -- will it reliably ''installing new version of config file'' or will it get confused by the extra # being / not-being present before updatign the config | 15:10 |
| tgm4883 | enyc: our steps for resetting the password are | 15:10 |
| tgm4883 | !mysql | 15:10 |
| Zinn | If you are having problems connecting to your mysql database, perform the following to reconfigure it: [1] sudo dpkg-reconfigure mysql-server-5.5 (pay attention to the root password you set, you will need it later) [2] sudo dpkg-reconfigure mythtv-database [3] sudo dpkg-reconfigure mythtv-common | 15:10 |
| enyc | tgm4883: ubuntu trusty mythbuntu 14.04.1 amd64, with the mythtv fixes 0.27 series ppa | 15:11 |
| tgm4883 | enyc: as for the bind address, we don't do that in the main mysql config file, there is a mythtv mysql config file we use | 15:11 |
| tgm4883 | IIRC, /etc/mysql/conf.d/mythtv.cnf | 15:11 |
| enyc | tgm4883: I think there must be some misunderstanding -- I wasn't tryingto change mysql password at this point | 15:11 |
| tgm4883 | enyc: right, I was commenting on what you said a few days ago | 15:11 |
| enyc | tgm4883: i know there is, wiht an error in it (0.0.0.0) | 15:11 |
| enyc | tgm4883: aah ok | 15:11 |
| tgm4883 | enyc: the bind address though is set in that other file | 15:12 |
| tgm4883 | it's specific to us, I think we just write it new every time | 15:12 |
| enyc | tgm4883: but see above about .. if we 'fix' the bind-address in mythtv.cnf to be ::0 ... | 15:12 |
| enyc | tgm4883: and somebody with the package _already_ upgrades it to a version that supplies new config | 15:12 |
| tgm4883 | what is the mysql way of binding to any address? | 15:12 |
| enyc | tgm4883: err "::" -- is the way of doing it | 15:13 |
| enyc | http://dev.mysql.com/doc/refman/5.5/en/ipv6-server-config.html | 15:13 |
| tgm4883 | enyc: wouldn't that not listen on ipv4 though? | 15:13 |
| enyc | wheezy, precise, trusty, all have MySQL 5.5 so should be no problem | 15:13 |
| enyc | tgm4883: no, the socket accepts IPv4 and IPv6 connections | 15:13 |
| tgm4883 | hmm, ok | 15:13 |
| tgm4883 | superm1: ^^ that is a packaging change right? | 15:14 |
| tgm4883 | or is it in MCC | 15:14 |
| enyc | tgm4883: however, the IPv4-connections appear to be from ::ffff:ip.v4.adr.ess | 15:14 |
| enyc | tgm4883: which would affect those who have setup per-host mysql permissions (only) | 15:14 |
| enyc | tgm4883: but then those people would probably know what they are doing with address binding too ;p | 15:14 |
| enyc | tgm4883: with *some* daemons there is a way to configure them to listen on ::0 "IPv6-ONLY" (switch off v4 compatibility) and then ALSO listen on 0.0.0.0 [IPv4-only] in which case the above doesn't happen | 15:15 |
| enyc | tgm4883: but using the IPv6-socket-API's automatic IPv4-compatibility for this inbound-only-server really really isn't a problem imho, and is as suggeshed by mysql docs themselves | 15:16 |
| tgm4883 | if we just comment out bind-address completely, what does it do? | 15:16 |
| enyc | tgm4883: it takes the bind-address from the my.cnf which says 127.0.0.1 | 15:16 |
| enyc | tgm4883: NOTE -- the current "dpkg-reconfigure mythtv-database" does EXACTLY that -- it comments/uncomments the bind-address= line in mysql/mythtv.cnf | 15:17 |
| enyc | tgm4883: However, I will TRY commenting it out in BOTH mythtv.cnf AND my.cnf | 15:17 |
| enyc | tgm4883: ok, in that case, trusty MySQL binary 'internal default' defaults to 0.0.0.0 IPv4-ONLY mode | 15:20 |
| tgm4883 | ok, so it sounds like the sensible thing to do is bind to :: | 15:21 |
| enyc | tgm4883: indeed | 15:21 |
| enyc | tgm4883: I would say for some 'niche' users -- who have for some weird reason changed /proc/sys/net/ipv6/bindv6only=1 will stop them connecting to MySQL over IPv4 | 15:24 |
| enyc | tgm4883: equally niche users who have setup Per-IPv4-address permissions at the MySQL level, *may* find they need to change references to user@ipv4-address to user@::ffff:ipv4-address in their permissions | 15:25 |
| enyc | tgm4883: these are equally niche/technical ability problems just as much is the problem of 'ipv6 doesnt sodding well work' =) ... etc... | 15:25 |
| enyc | tgm4883: if needbe i create a bug... Please remind me of the exact approach for bugs in this context.. I will have some more to write r.e. couple simple changes to make our source functional on debian-Wheezy etc. | 15:28 |
| enyc | tgm4883: I don't want to accidentally post bug against mythtv ubuntu version rather than mythbuntu PPA etc | 15:59 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!