[07:39] <lordievader> Good morning
[13:50] <jamespage> cpaelzer: libvirt+qemu is now into stein-proposed for the UCA
[13:52] <cpaelzer> thank you ++ jamespage
[13:52] <cpaelzer> you get +1 on my "need to spend a beer list"
[14:11] <jamespage> cpaelzer: I'll exchange that beer for help with
[14:11] <jamespage> "configure: error: Could not find DPDK library in default search path, Use --with-dpdk to specify the DPDK library installed in non-standard location"
[14:11] <jamespage> when backporting openvswitch to bionic (complete with meson and dpdk from disco as well)
[14:11] <jamespage> :)
[14:25] <ahasenack> cpaelzer: do I need to do something special to get the *-dbgsym packages from the bileto ppa?
[14:25] <ahasenack> cpaelzer: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3631/+packages I see, for example, samba-dbgsym in there
[14:25] <ahasenack> but apt-cache policy doesn't, it's still trying to fetch the dbgsym packages from the archive (ddebs.ubuntu.com)
[14:28] <ahasenack> rbasak: do you know? ^
[14:34] <ahasenack> anyone?
[14:35] <rbasak> ahasenack: pastebin the policy output please?
[14:35] <rbasak> Oh, hang on.
[14:35] <rbasak> The ddebs go through some special process to get built I think?
[14:36] <rbasak> Do PPAs even build them?
[14:36] <rbasak> Oh yes, they are there.
[14:36] <ahasenack> rbasak: https://pastebin.ubuntu.com/p/2cp8xgTgqK/
[14:38] <rbasak> ahasenack: looks like you'll need to add the debug bit to your sources.list.
[14:38] <ahasenack> and if I download the deb, and install it with dpkg -i, apt-cache policy shows it as installed of course, but from /var/lib/dpkg/status
[14:38] <rbasak> Try http://ppa.launchpad.net/ci-train-ppa-service/3631/ubuntu bionic/main/debug
[14:38] <ahasenack> rbasak: how? The ddeb entries I have look like normal sources.list lines
[14:38] <ahasenack> # cat /etc/apt/sources.list.d/ddebs.list
[14:38] <ahasenack> deb http://ddebs.ubuntu.com bionic main restricted universe multiverse
[14:38] <ahasenack> ...
[14:38] <rbasak> Uh
[14:39] <rbasak> deb http://ppa.launchpad.net/ci-train-ppa-service/3631/ubuntu bionic main/debug
[14:39] <rbasak> Maybe
[14:39] <ahasenack> that worked
[14:39] <ahasenack> witchcraft
[14:40] <ahasenack> thanks!
[14:41] <rbasak> You're welcome! If it helps, what I did was: found the ddebs being built in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3631/+packages; browsed at the URL given by the PPA sources.list; found http://ppa.launchpad.net/ci-train-ppa-service/3631/ubuntu/dists/bionic/main/debug/binary-amd64/Packages.gz; and reverse engineered the correct sources.list line from that.
[14:41] <ahasenack> as I said, witchcraft
[14:41] <ahasenack> :)
[14:41] <rbasak> Oh, and manually looked in the Packages.gz to confirm it contained the ddebs
[14:41] <rbasak> :-)
[14:52] <cpaelzer> ahasenack: sorry to be late , but a while ago I think I added this https://wiki.ubuntu.com/DebuggingProgramCrash#Installing_dbgsym_packages_from_a_PPA
[14:53] <cpaelzer> is that the way you ended up using?
[14:53] <ahasenack> yes
[14:53] <ahasenack> "have no fear", heh
[14:53] <cpaelzer> jamespage: I usually built it in a sbuild env to debug it when I had that error
[14:53] <cpaelzer> that was what was leading me to the OVS upstream patch to suppotr pkg-config based libs
[14:54] <cpaelzer> it very likely is related to the same
[14:54] <cpaelzer> jamespage: do you have the configure.log available?
[14:54] <jamespage> cpaelzer: no that's from the backporter
[14:56] <cpaelzer> what could it be - I bundled the new pkg-config macros
[14:56] <cpaelzer> hmm
[14:56] <cpaelzer> jamespage: I think without a configure.log we are lost :-/
[15:01] <paride> ahasenack, I can confirm LP #1783129 is solved in the 18.04.2 RC. I was a bit surprised by finding the bionic-backports repo enabled by default, but its Release file has a 'NotAutomatic: yes' line, so I'm sure everything is as it should be.
[15:02] <jamespage> cpaelzer: I'll need to repro then doing something else right now
[16:35] <teward> stgraber: do you know any oddities with AppArmor on a host system running LXD not being able ot reload or restart itself to refresh apparmor rulesets?
[16:36] <teward> i ask because i ran into this yesterday when adjusting my apparmor overrides for bind9 so it could use a location ondisk without getting killed, and then apparmor couldn't restart/reload/refresh itself because of something related to the LXD snap
[16:36] <teward> not sure what exactly but
[16:38] <sdeziel> teward: to apply changes made to a profile, you not need to restart Apparmor. Instead: apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.named && service bind9 restart
[16:39] <teward> sdeziel: there needs to be an easier 'reload' mechanism :P
[16:39] <teward> sdeziel: thanks though
[16:40] <teward> sdeziel: still intersting to note that AppArmor can't start if LXD is running though, in the case of, say, an AppArmor crash
[16:40] <teward> it can't start itself up in that case of LXD containers running snapped.
[18:27] <ahasenack> rbasak: do you know what this is about in mysql-server-8.0?
[18:27] <ahasenack> 2019-02-05T18:23:37.165647Z 0 [ERROR] [MY-011300] [Server] Plugin mysqlx reported: 'Setup of socket: '/var/run/mysqld/mysqlx.sock' failed, can't create lock file /var/run/mysqld/mysqlx.sock.lock'
[18:27] <ahasenack> mysql itself seems to be running fine, I can connect to it
[18:27] <ahasenack> mysqlx is something new
[18:39] <rbasak> ahasenack: I'm not seen that. I'd need Skuggen's (not here) help with that.
[18:40] <rbasak> You can ask him in #ubuntu-devel, but see my message there just now.
[18:40] <ahasenack> rbasak: I think we will need new apparmor rules
[18:41] <ahasenack> rbasak: https://pastebin.ubuntu.com/p/cWq7ymJKBR/
[18:41] <ahasenack> rbasak: last one is about that mysqlx socket
[18:41] <ahasenack> rbasak: and there is openssl, since it links with it now
[18:42] <ahasenack> the /sys ones I thought was resolved already?
[18:43] <ahasenack> waat (deleting mysql8 from proposed)
[18:43] <ahasenack> well, at least the patches I added to net-snmp were not mysql-8 exclusive, I took the extra work so that it should still build with 5.6.x
[18:43] <ahasenack> er, 5.7.x
[18:48] <rbasak> That makes sense.
[18:48] <rbasak> Please tell Skuggen though!
[18:50] <ahasenack> rbasak: I can file a bug, objections?
[18:51] <rbasak> No objections, but might be worth checking the bug won't be impacted by the delete.
[18:52] <rbasak> Apart from that, bugs against 8.0 would be helpful for tracking, thanks.
[21:54] <how2hack> hi, i'm trying to join a ubuntu client to a ubuntu server domain controller, but i run into the following error: https://paste.ubuntu.com/p/vyppT2SCQf/
[21:54] <how2hack> a quick look in the journal shows these two errors: https://paste.ubuntu.com/p/XDMVx2BMyY/
[21:55] <how2hack> can anyone tell me how to fix this?
[22:00] <lordcirth__> how2hack, check that your time on the two systems is accurate (<1s)
[22:00] <lordcirth__> 'date'
[22:03] <how2hack> oh, it's not
[22:03] <how2hack> it's off, by exactly 1hour
[22:03] <sarnold> lordcirth__: nice :)
[22:05] <how2hack> https://paste.ubuntu.com/p/DS7b6czYTc/
[22:05] <how2hack> i changed the hour so it's the same in both but still i get that error in the journal
[22:43] <zzlatev_> Hi guys