/srv/irclogs.ubuntu.com/2019/11/01/#ubuntu-devel.txt

=== thegoose is now known as el
=== JanC_ is now known as JanC
=== HeadlessHorseman is now known as Unit193
Unit193While I might dispute the validity of the NMU, someone that is gtk2-rm crazy could sync gparted from experimental.05:51
=== pieq_ is now known as pieq
Gargoyledoko: There's a bug in MySQL 8 which seems to have been the same or re-surfaced as I have found an exact same bug un launchpad for 5.5 from 3 years ago. I've had a poke round launchpad but cannot find where to file an updated report or submit a patch. I would like to do it if someone can point me in the right direction.08:34
GargoyleBug is actually with the logrotate script, so probably just a packaging issue and not an issue with MySQL 8.0 itself. (https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1558471)08:35
ubottuLaunchpad bug 1558471 in mysql-5.5 (Ubuntu) "logrotate config mysql-server fails with error "error: skipping "/var/log/mysql.log"" [Undecided,New]08:35
=== alan_g is now known as alan_g_
GargoyleI've greated a fresh patch from the code here:- https://code.launchpad.net/~usd-import-team/ubuntu/+source/mysql-8.0/+git/mysql-8.0 and I've tried to look upstream, but debian is even more confusing as they have dropped mysql from stable. :/ Now I'm lost!09:41
Gargoyles/greated/created09:41
rbasakGargoyle: o/10:25
rbasakGargoyle: you can send a merge proposal against https://salsa.debian.org/mariadb-team/mysql/tree/mysql-8.0/ubuntu/develif you like10:25
rbasakOr file a bug against https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+filebug10:25
jbichaUnit193: oh I didn't realize that was an NMU. Have you tried the new gparted yet?10:49
GargoyleThanks rbasak. Done (https://salsa.debian.org/mariadb-team/mysql/merge_requests/28) :-)10:52
rbasakGargoyle: thanks! Just looking at this now.11:08
rbasakGargoyle: I can reproduce on 19.10 by running "logrotate -f /etc/logrotate.d/mysql-server" but not "logrotate -f /etc/logrotate.conf" which I find puzzling.11:09
rbasakIt makes sense to take your merge as it's obviously correct, but in terms of importance for backporting to 19.10, how does it affect users in practice?11:10
SkuggenMaybe the base config already does something like this?11:12
rbasakWhat I'm wondering is that since in the default configuration /var/log/mysql.log isn't created (I think?), then in the default configuration logrotate would never warn like this?11:13
rbasakIf so, then we should take the fix for future releases but perhaps there's no need to backport the fix?11:13
Skuggen«su root syslog» is in /etc/logrotate.conf11:14
rbasakAha11:19
rbasakSo this isn't a bug after all?11:19
SkuggenAnd yeah, the package default is /var/log/mysql/error.log11:19
SkuggenI don't really know much about how logrotate works :)11:21
SkuggenHm, wait, I was looking on a 18.04 box11:21
SkuggenIn 19.10 it seems to be «su root adm»11:21
RikMillscyphermox: can unity-autopilot be got rid of? it depends src:autopilot, which depends on parts of src:python-qt4 which are dropped in -proposed package12:26
Gargoylerbasak: It stops the logrotate service from starting.12:33
Gargoylehttps://paste.ubuntu.com/p/SCf58hcgYM/12:33
Gargoyle^ Relevant lines from "journalctl -b 0"12:34
rbasakGargoyle: could you give me full steps to reproduce please, on 19.10 presumably?12:34
GargoyleYup. 1 sec12:35
=== TalkingMuffin is now known as Pici
Gargoylerbasak: Hmm. Nope. Apparently I cannot! With my changes removed I can still run "sudo /usr/sbin/logrotate -d /etc/logrotate.conf" without errors.12:51
Gargoylerbasak: This would make sense because "syslog" is actually a member of "adm". :-/12:52
rbasakGargoyle: OK, so no bug?13:04
rbasak"U2F support in OpenSSH HEAD" https://marc.info/?l=openssh-unix-dev&m=157259802529972&w=213:05
rbasakThis would be nice for Focal, but I suspect there won't be an upstream release in time. I assume cherry-picking is going to be frowned upon?13:06
GargoyleThere's a bug somewhere, rbasak. It seems like it's intermittent though:- https://paste.ubuntu.com/p/PX5Zpy4nCp/13:07
GargoyleI'm going to do a bit more poking. Looks like it might be an issue with the post rotate and "sudo systemctl status logrotate.service" was showing me a red herring.13:07
rbasakOK13:10
cjwatsonrbasak: I wouldn't be comfortable with that because (a) it's a large and complicated set of commits to CP, (b) it'd be easy to make a security-critical mistake, and (c) it wouldn't be unheard of for upstream to catch security-critical errors of their own in this sort of thing before release13:10
cjwatsonI agree there's no particular assurance that there'll be an upstream release in time; the release schedule isn't regular, but somewhere around every 4-6 months is typical (though some have been a lot quicker).13:11
rbasakcjwatson: I thought as much, thanks13:12
cjwatsonInteresting that they went for a new key type, which means all servers have to update too.  I guess that's another thing to add to my Twisted patch queue13:13
cjwatson(i.e. it'll be a while before we can support it in LP)13:13
cjwatsonI've had basically the full patch set necessary to support Ed25519 in LP ready for a while, but the Twisted patch review cycle grinds pretty slowly :(13:15
Gargoylerbasak: It's a race condition.13:18
Gargoylerbasak: Not very easy to visualise, but here's a full boot log:- https://termbin.com/zn3c13:25
Gargoylerbasak: If you search for "Starting Rotate log files", then then scroll down, "Starting MySQL Community Server" although it's still in the same second is a page and a half later. My guess would be that when mysql's logs do actually need rotating, the post rotate script tries to run "sudo /usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf flush-logs" but mysql is not yet up and running.13:28
rbasakAh, I see13:29
rbasakSo we need to add a check before the mysqladmin call to no-op if mysqld isn't running perhaps?13:29
rbasakSkuggen: ^?13:29
rbasakSeems like something that flush-logs should have an option for :)13:30
rafaeldtinocotjaalton: ping. would u mind approving sg3-utils SRU for disco ? it has already being checked/verified/tested in bug 1833618.13:30
ubottubug 1833618 in sg3-utils (Ubuntu Disco) "MAAS can't deploy Ubuntu if ID_SERIAL of any block device is broken (USB pendrive in this case)." [High,In progress] https://launchpad.net/bugs/183361813:31
GargoyleI would still like to try and create reliable steps to reproduce, but logrotate somehow knows my log files don't need rotating - even if I decompress the last rotated one13:31
Skuggenrbasak: Hm, the script runs a mysqladmin ping command just before to verify the server is up13:36
Skuggenhttps://salsa.debian.org/mariadb-team/mysql/blob/mysql-8.0/ubuntu/devel/debian/mysql-server-8.0.mysql-server.logrotate#L1613:36
SkuggenActually, what exactly does that if check? That the mysqladmin command doesn't output anything to stderr?13:37
GargoyleSkuggen: It outputs "mysql is alive". If mysql is alive - and nothing on error.13:40
SkuggenAh, of course, that if is for the failure case. Then the flush-logs command should only be run if the server is up and ready13:42
GargoyleSo if mysql is not alive, we enter that block and test the outcome of "killall -q -s0 -umysql mysqld;"13:42
SkuggenYeah13:43
GargoyleWhich has an exit status of 1 when mysql is not running.13:43
GargoyleWhat is signal 0 ?13:44
tjaaltonrafaeldtinoco: no release on a friday, sorry13:44
rafaeldtinocoah ok. was just following what is written in the sru wiki13:44
rafaeldtinocomaybe we should update it the13:45
SkuggenSo if mysql isn't running it should return success13:45
SkuggenSignal 0 is sort of a dry-run thing, if I understand it correctly13:45
cyphermoxRikMills: I suppose unity-autopilot could be dropped (at a glance, it looks like only unity wants it); but this is really a question for the desktop team13:45
Skuggeni.e. it won't actually kill mysql, but will check if it's there13:45
cyphermoxRikMills: as long as the tests are still runnable somehow as they were, it would probably be fine to stop shipping them as a package13:46
SkuggenSo if mysqld is in the startup phase, process running but not ready yet, it makes sense that the logrotate script will fail, I think13:46
GargoyleSkuggen: Thats what I was just typing! :D13:46
SkuggenSo some test to detect that state is what we need :)13:47
SkuggenWhich is basically what rbasak said :D13:48
GargoyleTurned that postrotate script into a stand alone bash script and ran it with a while true and started mysql. Conformed that it hits the "exit 1" during mysql startup.13:58
GargoyleCrude but effective! XD (https://paste.ubuntu.com/p/dCj5ZsvxXH/)14:06
GargoyleI ran "service mysql start" in another term when that was running ^^14:07
TomyWorkhi. are you aware of a problem connecting to DFS shares on bionic that was introduced between 2:4.7.6+dfsg~ubuntu-0ubuntu2.11 and 2:4.7.6+dfsg~ubuntu-0ubuntu2.13? That version has been out for at least a week now (I installed it on oct 24) and I can't see anything on the bug tracker about it. It worked for me on oct 22 and I noticed it only today (hadn't tried mounting that share between oct 22 and today) and going directly to the (only) share14:10
TomyWorkbehind it works. The person responsible for all the file servers says nothing has changed server-side since oct 22, so I'm quite confident that this was introduced with the update.14:10
TomyWorkSo, if any samba maintainers here are unaware of the issue, I'll write up a bug report about it.14:10
rbasakTomyWork: that's not related tohttps://lists.ubuntu.com/archives/ubuntu-server/2019-October/007967.html is it?14:11
TomyWorktemporally correlated for sure :)14:12
TomyWorki don't recognize any error messages14:12
rbasakPlease do file a bug, and if you're reporting a regression in stable release, tag it regression-update14:13
TomyWorkbtw is there any way I can downgrade to .11 so i can confirm this issue?14:13
TomyWork...as a regression?14:13
rbasakYes14:18
rbasakLaunchpad will have the old binaries14:19
rbasakVia https://launchpad.net/ubuntu/+source/samba/+publishinghistory14:19
rbasakhttps://launchpad.net/ubuntu/+source/samba/2:4.7.6+dfsg~ubuntu-0ubuntu2.11 I think?14:19
TomyWorkfound it, thanks14:19
rbasakThen click on amd64 (I assume)14:19
rbasakYou will need to work out which packages from that source you have installed (and thus need to downgrade)14:20
TomyWorkyeah i'll just go through the list on packages.ubuntu.com for the source package14:20
TomyWorkdpkg -l ctdb libnss-winbind libpam-winbind libparse-pidl-perl libsmbclient libsmbclient-dev libwbclient-dev libwbclient0 python-samba registry-tools samba samba-common samba-common-bin samba-dbg samba-dev samba-dsdb-modules samba-libs samba-testsuite samba-vfs-modules smbclient winbind 2>/dev/null | grep ^ii14:22
TomyWorkthat works :)14:22
TomyWorkok, rebooting to be sure it's live14:28
GargoyleSkuggen: rbasak: I think I can re-write that postrotate script to check for all 3 possible outcomes (mysql not running, bad debian-sys-maint user, running and connecting ok) with a single check and eliminate the need for the second "if killall.... etc" check which is causing the race condition.14:34
rbasakGargoyle: that sounds good! I'm working on something else right now so haven't confirmed any of the detail, but I really do appreicate any fixes you want to give us :)14:36
GargoyleShould I open a new bug?14:36
rbasakGood question14:37
rbasakI don't mind if you do14:37
rbasakIf you just want to send a Salsa merge request that's fine too, though if discussion gets complicated then that would probably best be done in a bug14:37
rbasakAnd then there's the question of whether the fix needs to be backported to stable Ubuntu releases14:38
GargoyleOK. I'll get the patch/MR ready and see how well I can explain it! :-)14:38
rbasakIf the conclusion is that it does, then we'll need a bug to exist to track the status of that14:38
rbasakThanks!14:38
SkuggenGargoyle: If you'd make a pr for that it would be great!14:40
tjaaltonrafaeldtinoco: oh, you mean approve to -proposed and not -updates? yeah, that can be done14:42
rafaeldtinocotjaalton: #) yep. thx !14:42
mdeslaurSkuggen: so it turns out my s390x problem is when mysql is built with openssl after all...I properly enabled openssl in 5.7.27 and I'm hitting the same issue14:42
mdeslaurSkuggen: I'm kind of stuck now14:43
xnoxmdeslaur:  is it because openssl tries to use CPU hw acceleration and it's not available on your LPAR / VM?14:43
xnoxmdeslaur:  cause that's "new" in 1.1.1 partially14:44
mdeslaurxnox: how would I find out?14:44
xnoxinvoke jfh14:45
xnoxthere are command line things to check if all the right CPU functionality is enabled and available, but i don't remember them.14:46
mdeslaurjfh?14:46
TomyWorkrbasak, regression confirmed. Mounting works with .1114:48
TomyWorkactually let me upgrade again first, to see whether it was just a reboot that was needed :D14:49
TomyWork(unlikely since everything else worked)14:49
TomyWorkrbasak, ok forget about the whole story, I'm back on .13 and the issue isn't there anymore. I dont know what it was.14:52
TomyWorkit might be an issue, but it's definitely not a regression14:52
rbasakTomyWork: OK. Thank you for investigating anyway - negative results are also good results, and now you know what to do if you do ever spot a regression :)14:56
TomyWorkyeah, and how to downgrade if one is already reported but not fixed yet :)15:02
Skuggenmdeslaur: It's during the build, right? I could try to diagnose it in a ppa15:02
mdeslaurSkuggen: take the current bionic package, switch to -DWITH_SSL=system, add libssl-dev to build-depends, and it will hang during build as soon as the server is started for the tests15:03
mdeslaurSkuggen: last thing in the log is "Installing system database..."15:04
GargoyleIn the current script, it has: "test -x /usr/bin/mysqladmin || exit 0" followed by a comment "# If this fails, check debian.conf" what does that mean? It it trying to say the installation is broken because there is a rote script for a package that is not installed?15:18
rbasakI'm not sure about the comment15:19
rbasakIf you're asking about the -x test, that's pretty common in Debian15:19
rbasakIt's because a package removal doesn't remove its configuration files15:19
rbasakSo that later reinstallation will maintain the previous configuration15:20
GargoyleAhh. ok.15:20
rbasakSo configuration that is actually code must check for that condition and handle it gracefully15:20
=== grumboo is now known as grumble
popeyvorlon: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/178911818:42
ubottuLaunchpad bug 1789118 in linux (Ubuntu Bionic) "Fails to boot under Xen PV: BUG: unable to handle kernel paging request at edc21fd9" [High,Fix released]18:42
popeyThis bug appears fixed in distro, but (as per comment #20) installer images are broken, so unable to install Ubuntu in xen.18:42
vorlonpopey: http://gb.archive.ubuntu.com/ubuntu/dists/bionic/main/installer-i386/current/images/ doesn't have the fix because it's the release pocket.  They want http://gb.archive.ubuntu.com/ubuntu/dists/bionic-updates/main/installer-i386/current/images/18:47
vorlonwell, I mean, they shouldn't want anything i38618:47
vorlonbut generally18:47
gpiccoliHi rbasak, I'd like to discuss LP #1847924 when you have some minutes18:48
ubottuLaunchpad bug 1847924 in mdadm (Ubuntu Focal) "Introduce broken state parsing to mdadm" [Medium,In progress] https://launchpad.net/bugs/184792418:48
popeyAh. Thank you18:59
GargoyleSkuggen: rbasak: This is what I have been able to do with the best of my knowledge as it stands at the moment. Bug = https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1850980, MR = https://salsa.debian.org/mariadb-team/mysql/merge_requests/2920:14
ubottuLaunchpad bug 1850980 in mysql-8.0 (Ubuntu) "mysql-server causes logrotate.service to fail at boot" [Undecided,New]20:14
GargoyleI decided to create the bug anyway because there's still an un-addressed edge case.20:15

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