=== Muzer_ is now known as Muzer === Shadow__1 is now known as Shadow__X [19:08] I've got a question about myth updates if anyone is available [19:08] what type of questions [19:09] on some of the mythtv servers I maintain for people when I update to the new mythtv fixes it resets my mysql network setting back to disabled [19:10] I have to enable it after every mythtv update [19:10] qwebirc56669, how are you enabling it? [19:10] in the mythbuntu setup program [19:11] ok [19:11] mostly because I don't know what it's doing to mysql [19:12] qwebirc56669, I've heard it's caused by some corruption in the dpkg database. I've personally not looked into it [19:12] qwebirc56669, It would be mythtv-database that is causing it to get reset [19:13] specifically, this code http://pastebin.ubuntu.com/5647267/ [19:13] qwebirc56669, I'm guessing your question is how to make that stop getting reset? [19:13] yes :) [19:13] or at least what does clicking enabled do [19:14] qwebirc56669, basically, it runs this [19:14] sed -i -e 's/^#bind/bind/' /etc/mysql/conf.d/mythtv.cnf [19:15] technically, thats from the postinst of mythtv-commong [19:15] that pastebin was from mythbuntu-setup? [19:15] so what it probably does is, checks that file exists, runs that command, then restarts mysql [19:15] qwebirc56669, no, it was from mythtv-database [19:15] https://github.com/MythTV/packaging/blob/master/deb/debian/mythtv-database.postinst [19:15] oh [19:16] so maybe it's a permission problem on mythtv.cnf maybe? [19:16] qwebirc56669, does it work after you do it? [19:16] shouldn't be a permission issue, it's run as root [19:16] (the command that is) [19:17] basically every time I update myth I have to go into mythbuntu-setup and click enable under mysql...then it works [19:17] yea, not a permission isus [19:18] qwebirc56669, can you file a bug on that [19:18] sure....don't think I've done that before...what should I include? [19:18] qwebirc56669, for this issue, just explain what is happening and the version you are on [19:18] !bugs [19:19] my mythtv.cnf only has bind-address=0.0.0.0 and max_connections=100 in it [19:19] report it here https://bugs.launchpad.net/mythbuntu [19:19] qwebirc56669, yep [19:19] when it gets reset, bind-address=127.0.0.1 [19:19] ah...now I understand [19:19] when it works externally, bind-address=0.0.0.0 [19:20] qwebirc56669, so also, include a copy of mythtv.cnf when it's working, and also when it doesn't work [19:20] ok [19:21] qwebirc56669, oh, also, the output of 'ifconfig' [19:21] ok [19:21] qwebirc56669, sorry, looking though this I keep seeing more info [19:23] qwebirc56669, post the link to the bug report here when you've submitted it and I'll take a quick look [19:23] np...gotta figure out my launchpad login any ways [19:34] webchat kicked me out...here's the link to the bug report [19:34] https://bugs.launchpad.net/mythbuntu/+bug/1159992 [19:54] qwebirc56042, after the update, are you sure it's bind-address=127.0.0.1 and not #bind-address=0.0.0.0 ? [19:55] no I'm not....I didn't know what was being changed....I just copied what you said for completeness [19:55] ah [19:55] yea we'll need to see what it actually is then [19:56] I can see if I've got another server with the problem and try an update [19:56] that would explain why I can't see where that value was coming from :) [19:56] ok [19:56] that would be great [20:01] tgm4883, you were right...it's #bind-address=0.0.0.0 [20:02] cool [20:02] now to just figure out why it's doing that