[05:39] <cpaelzer> good morning ubuntu server
[06:56] <technoob> Guys
[06:56] <lordievader> Good morning
[06:57] <technoob> If say i had numerous failed login attempt caused by none other than me does ubuntu ban my pcs ip?
[06:57] <technoob> I tried to ssh using my mobile and it works
[06:57] <technoob> But if i ssh using my pc it times out
[06:57] <technoob> Help pls
[06:59] <lordievader> Do you have fail2ban running or something?
[06:59] <technoob> Dunno
[06:59] <technoob> How do i check
[07:00] <lotuspsychje> technoob: you are the owner of your system, you cant recall?
[07:00] <technoob> Im new. I just install new server a few days ago
[07:00] <technoob> I havent been installing much
[07:00] <lordievader> If you didn't install it it ain't there.
[07:01] <lordievader> Per default there is no mechanism which blocks a client after X login attempts.
[07:01] <technoob> Ok ill shutdown and reconnect
[07:01] <technoob> Hope for the best
[07:04] <technoob> Ok it wotked
[07:18] <CarlFK> anyone know why disco is smaller?
[07:18] <CarlFK> http://cdimage.ubuntu.com/ubuntu/releases/18.04/release/ubuntu-18.04.2-server-amd64.iso 883M
[07:18] <CarlFK> http://cdimage.ubuntu.com/ubuntu-server/daily/pending/disco-server-amd64.iso  752M
=== bhuddah_ is now known as bhuddah
[09:36] <rbasak> cpaelzer: no git ubuntu repo for python-libnacl? Do we need to add that?
[09:37] <cpaelzer> rbasak: we can add that, we know that sooner or later it will be in main anyway
[09:37] <cpaelzer> at least in X/T
[09:38] <cpaelzer> rbasak: I have added it to the whitelist already, just not done the (re)imports of all those
[09:38] <cpaelzer> rbasak: a8340557e shows the interesting list of packages - you wanted to run thos eon the bastion you said
[09:38] <rbasak> cpaelzer: ah. Shall I manually run the imports?
[09:39] <rbasak> OK
[09:39] <cpaelzer> but all but +python-libnacl are already imported as they are in main in latter Ubuntu releases
[09:39] <cpaelzer> so it comes down to just the import of that
[09:40] <rbasak> Just running that one now then. Thanks!
[09:40] <cpaelzer> or accepting thins in proposed which will trigger a publishing event which since it is in the whitelist get it imported :-)
[09:40] <rbasak> :)
[09:40] <rbasak> I haven't published a new snap with latest whitelist entries included though
[09:40] <cpaelzer> I see
[09:41] <rbasak> It can be specified manually on CLI invocation FWIW
[09:41] <rbasak> I've just never done that for fear of it getting confusing and out of sync etc
[09:41] <rbasak> We could figure out a better way but probably not worth it
[09:41] <rbasak> Ah
[09:41] <rbasak> Import fails - DPMT.
[09:42] <cpaelzer> ah right there was a blocker with those
[09:44] <rbasak> Worked around for now
[09:47] <rbasak> cpaelzer: there's an outstanding pymacaroons SRU in xenial-proposed and I see the backport is against the version in xenial-updates. Is this relevant, or if not, do we need to explain?
[09:51] <cpaelzer> rbasak: last two updates in https://bugs.launchpad.net/ubuntu/+source/httmock/+bug/1735160
[09:51] <ubottu> Launchpad bug 1735160 in py-macaroon-bakery (Ubuntu Artful) "[SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic" [Undecided,In progress]
[09:51] <cpaelzer> this will soon be cleared from proposed
[09:52] <rbasak> cpaelzer: ah, sorry. I didn't read far enough down the bug. Thanks!
[10:34] <rbasak> cpaelzer: any action needed on bug 1811554? It came up on my weekend triage. It's not in the backlog or anything, but I'm the third triager to touch it now.
[10:34] <ubottu> bug 1811554 in bind9 (Ubuntu) "bind9 slow response after netplan apply" [Undecided,Incomplete] https://launchpad.net/bugs/1811554
[10:58] <rbasak> cpaelzer: noticed you're subscribed to bug 1814124. Was my triaging accurate?
[10:58] <ubottu> bug 1814124 in openssh (Ubuntu) "sshd does not start after update on non-Ubuntu kernels where fchownat() is broken" [Undecided,Invalid] https://launchpad.net/bugs/1814124
[10:58] <pagios>  question, if i have an nfs mount on my server, and i am writing directly to this network location, am i using the disk io of my server? or directly writing to the network?
[11:17] <rbasak> pagios: yes to both
[11:19] <cpaelzer> rbasak: yes to ..124
[11:19] <cpaelzer> rbasak: it is unfortunate that they are hit by it, but vor these BZ hosting we can't really do anything about the host kernel
[11:19] <cpaelzer> and that seems to be the root cause there :-/
[11:20] <cpaelzer> rbasak: for ...554 I didn't see anything we can action, that is why I added a netplan task to get it to the eyes of cyphermox
[11:21] <cpaelzer> as I hope he knows all the steps that happen at "apply" to maybe identify what is going on
[11:42] <rbasak> So cpaelzer so backlog for 554?
[11:46] <rbasak> cpaelzer: I'm not sure how to re-triage bug 1817027 - he's come back with more information, but not steps to reproduce.
[11:46] <ubottu> bug 1817027 in samba (Ubuntu) "samba crashes when uploading files" [Undecided,New] https://launchpad.net/bugs/1817027
[11:47] <rbasak> So IMHO it's still a support request but I don't know how to tell him that and stop answering politely.
[11:47] <rbasak> cpaelzer: and thank you for reviewing 124. I'll consider that one done then.
[11:51] <frickler> jamespage: freyes: pinging once more regarding this bug in case you missed it yesterday https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1783203
[11:51] <ubottu> Launchpad bug 1783203 in rabbitmq-server (Ubuntu) "Upgrade to RabbitMQ 3.6.10 causes beam lockup in clustered deployment" [Undecided,Confirmed]
[12:01] <frickler> coreycb: any specific reason why you did 17.0.7-2 for nova in queens instead of bumping to latest upstream at 17.0.9? I'm still waiting for the fix for https://launchpad.net/bugs/1801702 to get in
[12:01] <ubottu> Launchpad bug 1801702 in OpenStack Compute (nova) ocata "Spawn may fail when cache=none on block device with logical block size > 512" [Medium,In progress]
[12:21] <coreycb> frickler: 17.0.9 must not have been available the last time we did point releases
[12:21] <coreycb> frickler: we're due so i'll get point releases out soon
[12:22] <frickler> coreycb: o.k., great, thx
=== logan_ is now known as Guest11647
=== not_phunyguy is now known as phunyguy
=== Guest11647 is now known as logan-
[12:36] <ahasenack> rbasak: hi, should I remove the "removal-candidate" tag when I complete the sru verification? https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/1576187/comments/24
[12:36] <ubottu> Launchpad bug 1576187 in backuppc (Ubuntu Xenial) "backuppc/smb: BackupPC failes to backup SMB shares after smbclient update" [Undecided,Fix committed]
[12:43] <Odd_Bloke> rbasak: What does DPMT mean in the context of that git-ubuntu failure?
[14:06] <rbasak> Odd_Bloke: I mean it's an instance of bug 1764814
[14:06] <ubottu> bug 1764814 in usd-importer "awscli import fails: package_creator.display_name results in HTTP error 410: Gone" [Undecided,New] https://launchpad.net/bugs/1764814
[14:07] <rbasak> The catch is that I want to properly specify what string *should* be used, given that we can't rely on the real name
[14:07] <rbasak> And a workaround for now will cause a second "hash-abi-break" (though we are still experimental)
[14:08] <rbasak> ahasenack: removal-candidate> sure. I don't see why anyone would object to that. AIUI the bug would still be checked manually before actual removal but removing the tag would make it clearer.
[14:10] <kstenerud> Are special build commands necessary to build php 7.2.11 in cosmic? I've tried dpkg-buildpackage, but it fails partway through due to a permission error
[14:10] <Odd_Bloke> rbasak: Thanks for the info. :)
[14:11] <kstenerud> I basically did git ubuntu clone php7.2, copied it to a builder, and dpkg-buildpackage
[14:38] <cpaelzer> kstenerud: importer/import/7.2.15-0ubuntu0.18.10.1 built for me - let me try the 7.2.11 as well
[14:39] <cpaelzer> kstenerud: works just fine on 7.2.11-3build2 as well
[14:39] <cpaelzer> as it comes out of git ubutnu clone
[14:39] <cpaelzer> I run git ubuntu export-orig to get the tarball
[14:39] <cpaelzer> and then dpkg-buildpkg works
[14:40] <kstenerud> hmm can't figure out what I'm doing wrong...
[14:40] <cpaelzer> kstenerud: are you breaking on dpkg-buildpackage or later on once you build the .dsc/.changes that got generated?
[14:40] <kstenerud> Literally all I do is git ubuntu clone, put orig in the parent dir, run dpkg-buildpackage
[14:40] <cpaelzer> kstenerud: if you want join the standup call
[14:40] <cpaelzer> kstenerud: you can share your console and we can check step by step if you want
[14:41] <kstenerud> sure sec
[16:24] <kstenerud> cpaelzer: After sbuild fails, can I restart the build using dpkg-buildpackage, or is it a different command?
=== lotuspsychje__ is now known as lotuspsychje
[19:01] <nacc_> kstenerud: what's the exact error?
[20:06] <johnfg> hi guys
[20:06] <johnfg> yesterday, I was going to install ubuntu-server-18.04.  I wanted to use an existing vg and lv's.
[20:06] <johnfg> However, the installer didn't recognize or show them.
[20:07] <johnfg> from ubuntuforums, they suggest to boot from the livecd to try without installing; install lvm2, then start the installation.
[20:07] <johnfg> Is there any other way to get the installer to recognize existing vgs and lvs?
[20:07] <lordcirth_> johnfg, I thought lvm2 was already on the installer? But if it isn't, yeah, you'd need to install it.
[20:08] <lordcirth_> But probably you just need to scan as mentioned in #ubuntu
[20:09] <johnfg> All I know, is that unlike other distros, which see the volume groups and logical volumes, going right to install from the livecd, they aren't present.
[20:09] <tomreyn> johnfg: you need to use the alternative installer
[20:09] <tomreyn> the default installer doesn't allow you to work with existing structures.
[20:09] <johnfg> tomreyn: I'll have to boot it to choose it.  Can't try while in here.  This is my dual-booting machine (actually 3, fwiw).
[20:11] <tomreyn> johnfg: you can also do a chroot / debootstrap installation from the live / desktop installer
[20:13] <tomreyn> ubuntu-server-18.04 actually sounds like you were using the ("debian-installer" based) alternative/classic installer. the current default one contains "live" in the ISO file name.
[20:13] <tomreyn> oh gone
[20:28] <johnfg> Back after a try...lvm2 is installed on the installer; lvscan --all recognized the volumes.
[20:29] <compdoc> \o/
[20:29] <johnfg> However, I couldn't install, as this is *not* the live iso, but just the server, so there wasn't any alternative installer.  and the volumes weren't shown and available.
[20:30] <johnfg> I just downloaded, and will burn the live server iso.  Think that's the problem?
[20:30] <tomreyn> johnfg: can you tell s which iso you're working with?
[20:31] <tomreyn> like, so far? getting the live server iso won't improve detection of existing storage structures.
[20:31] <johnfg> Ubuntu-Server 18.04.2 LTS amd64 is what I have now.
[20:31] <tomreyn> that's not an iso name.
[20:31] <tomreyn> i mean a file name
[20:32] <johnfg> ubuntu-18.04.2-live-server-amd64.iso is what I was going to burn.
[20:32] <johnfg> tomreyn: Ok, I'll get you the other.
[20:32] <tomreyn> so live-server is not what you want for this use case
[20:33] <tomreyn> alternative server may work, not sure whether it detects existing lvms fine, you may need to help it a little there.
[20:34] <tomreyn> or you go with the live/desktop installer and a manual installation via debootstrap.
[20:34] <johnfg> tomreyn: what alternative server are you talking about?
[20:35] <tomreyn> the installer that is also known as debian-installer, and that used to be the default server installer until and including ubuntu 16.04 LTS
[20:37] <johnfg> Do you think that this will work: ubuntu-18.04.2-server-amd64.iso?  That's from the alternatives (which I didn't notice before), if needing, e.g., lvm, on the server web page.
[20:39] <johnfg> tomreyn: What do you think of that last image I wrote?
[20:39] <Odd_Bloke> johnfg: That's the one Tom was directing you towards, so I think it's worth a try.
[20:40] <johnfg> Odd_Bloke: I agree.  Will burn and proceed and report back.  Thanks all!
[20:42] <tomreyn> right. you may need to lvmscan from tty2 to convince the installer' partitioner to use the existing ones. not sure. try normally first.
[20:43] <johnfg> yeah, if it sees them then no problem.
[22:29] <cpaelzer> kstenerud: you just issue the sbuild again
[22:30] <cpaelzer> kstenerud: no need to re-build the .dsc/.changes
[23:58] <runelind_q> is Landscape On Prem 19.01 not available via dist-upgrade yet?