[01:27] <xnox> rbasak, which tomcat server is the default in xenial?
[01:27] <xnox> 7 or 8?
[01:27]  * xnox ponders if the tasksel tasks are out of date in xenial
[01:31] <sarnold> my tools tell me tomcat8 is in main in xenial
[02:03] <nacc> xnox: should be tomcat8 in 16.04
[02:03] <nacc> xnox: tomcat7 is in universe, iirc
[02:03] <nacc> xnox: and i believe we also updated the seeds
[02:04] <xnox> sarnold, nacc: ack, will fix tasksel in xenial.
[02:06] <nacc> xnox: thanks!
[06:41] <Nicho1as> Hi, I need an efficient software load balancer for my vsftpd cluster thingy; could anyone recommend one to me?
[07:04] <karstensrage> how do you read /var/crash files? im not use the GUI at all and everything seems to indicate you have to use the UI?
[08:05] <Hetfield> good morning
[08:05] <Hetfield> i need a fast clarification about autopilot-juju-conjure status in ubuntu nowadays
[08:29] <kdo__> Hi
[08:30] <kdo__> I have tried to install Ubuntu 16.04 Server on PowerEdge R530, the installation is working but it is really slow
[08:32] <kdo__> I made Raid 6 install and the server got 8Go RAM
[08:32] <kdo__> I don't understand because there is no error in console log
[08:34] <kdo__> moreover it seems certified to work https://certification.ubuntu.com/hardware/201411-16164
[08:34] <kdo__> I made a mistake the server got 16 Go Ram
[08:42] <lordievader> kdo__: Is there something hogging the cpu?
[08:43] <kdo__> lordievader : no
[10:51] <lordievader> kdo__: Could you run 'vmstat 1' for a while and give the last few lines?
[13:39] <mnms_> Anyone experienced error:  Diskfilter writes are not supported ?
[13:39] <mnms_> Hi
[13:40] <ikonia> mnms_: as I recall it's something to do with raid devices when the machine boots and it can't access the file system in a certain way
[13:41] <ikonia> I think it's software raid only when /boot can't be accessed as a raw device
[13:41] <mnms_> ikonia: what is the best solution for this ?
[13:41] <ikonia> mnms_: I think you'd have to understand what triggers it properly, I'm working from memory
[13:41] <ikonia> mnms_: what's your disk config/layout
[13:42] <ikonia> mnms_: the other thing is, is it causing you a problem ?
[13:42] <mnms_> cause my system doesnt boot up without pressing key
[13:42] <ikonia> ahh, so it won't actually boot without interaction
[13:42] <mnms_> thats right
[13:42] <ikonia> mnms_: tell me about your disk config, specfically around /boot and /
[13:42] <ikonia> lets see if we can figure it out
[13:42] <mnms_> ikonia: I have software raid
[13:42] <mnms_> mirror
[13:42] <ikonia> as in mdadm software raid ?
[13:43] <mnms_> ikonia: everything is under root. I dont have separate boot partition
[13:44] <lordievader> I had that issue once, this fixed it for me: https://askubuntu.com/questions/468466/diskfilter-writes-are-not-supported-what-triggers-this-error
[13:44] <lordievader> Has a good explanation of how it happens too.
[13:44] <ikonia> ooh, lets see
[13:44] <mnms_> lordievader: you applied a patch ?
[13:45] <ikonia> ahhhh I see,
[13:45] <lordievader> mnms_: Back when I ran Ubuntu, yes.
[13:45] <ikonia> I don't think you should have to patch this on a modern ubuntu
[13:45] <mnms_> It is 14.04
[13:46] <lordievader> From the same page "Still not fixed in 16.04. This breakneck pace of bug fixing is hard to keep up with."
[13:46] <mnms_> lordievader, ikonia: So what do you propose? apt-get uprgade, patch ?
[13:46] <mnms_> I dont want to go with quick boot = 0
[13:46] <lordievader> mnms_: I applied his patch, back then.
[13:46] <mnms_> lordievader: and everything was fine after that ?
[13:47] <mnms_> no problems ?
[13:48] <lordievader> Not that I can remember.
[13:49] <mnms_> I understand I could also add disk which is not in RAID and installer grub there?
[13:53] <ikonia> is /boot under LVM
[13:53] <ikonia> or / under lvm
[14:18] <cpaelzer> rbasak: are you stil laround for a mysql dependency to Debian question?
[14:19] <mnms_> ikonia: yes
[14:19] <ikonia> mnms_: easy fix, mirror a 500mb partition as /boot, then put the rest in lvm on a second mirrored partition
[14:19] <ikonia> problem solved
[14:20] <rbasak> cpaelzer: o/
[14:20] <rbasak> Today is my last day.
[14:20] <rbasak> Before January, that is. I am coming back :-)
[14:22] <cpaelzer> yeah, thanks for not being another one :-)
[14:22] <cpaelzer> I was breaking our strongwan changes up to be ready for Debian
[14:22] <cpaelzer> and I'm pretty far - or so I thought
[14:22] <cpaelzer> but now comes mysql
[14:22] <cpaelzer> which gives me a build error on debian-sid
[14:22] <cpaelzer> rbasak: I know that you were in the midst of all these mysql/mariadb things
[14:22] <cpaelzer> rbasak: so I hope for an advice
[14:23] <cpaelzer> current Ubuntu strongwan pulls libmysqlclient-dev and works building the mysql plugin
[14:23] <cpaelzer> the same fails in Debian-sid
[14:23] <rbasak> Can you show me a build log?
[14:23] <cpaelzer> I kind of blindly try exchaning for libmariadbclient-dev now, but any betetr advice is useful
[14:24] <rbasak> For compatiblity with both, you should now use default-libmysqlclient-dev if possible, but that shouldn't matter.
[14:25] <cpaelzer> rbasak: ok, pasting buildlog now ...
[14:26] <cpaelzer> rbasak: http://paste.ubuntu.com/23659110/
[14:26] <cpaelzer> rbasak: I was too eager putting it in an autopkgtest right away, so I had to fetch the buildlog before pastebining it
[14:26] <rbasak> Ah
[14:28] <rbasak> I can't find the bug right now, but it is fixed in VCS
[14:28] <rbasak> Sorry we don't have an upload to sid right now. We haven't found a DD to do it.
[14:28] <mnms_> ikonia, lordievader: thanks for help
[14:28] <rbasak> If building in sid, you can build against default-libmysqlclient-dev and that'll build against MariaDB and should fix the issue.
[14:28] <ikonia> mnms_: no problem
[14:28] <rbasak> (and you'll want to do that anyway for Debian)
[14:29] <cpaelzer> rbasak: ok trying with  default-libmysqlclient-dev already
[14:29] <cpaelzer> rbasak: as I read you 5 minutes before as "that is the way it should be done"
[14:29] <cpaelzer> rbasak: thanks, I'll let you know if that fixed my issues
[14:38] <mnms_> ikonia: do you always create separate boot partition ?
[14:38] <mnms_> or just /
[14:38] <ikonia> mnms_: I do personally yes
[14:39] <mnms_> ikonia: / /boot swap is enough for most cases I quess ?
[14:39] <cpaelzer> rbasak: at least in sbuild it is happy now, spinnign up autopkgtest again
[14:39] <ikonia> mnms_: you can slice it up however you're most happy, there is no right and wrong
[14:39] <mnms_> ikonia: ok, great
[14:40] <cpaelzer> but well I reuse built binaries so I won't double check compilation - only the dep8s int here
[14:40] <cpaelzer> rbasak: thanks for the hint
[14:44] <lordievader> mnms_: No problem
[16:01] <jgrimm> smoser, powersj, rbasak, caribou: irc mtg
[16:16] <jgrimm> smoser, caribou: what needs to happen yet for the cloud-init SRU mentioned in meeting?
[16:16] <dudeji> Hi guys, I have two ubuntu servers under load balancer bt one of them is giving too much CPU-load due to IO operations , what can be probable issue ?
[16:16] <caribou> jgrimm: the SRU team needs to push it to xenial-proposed
[16:16] <smoser> sru team member just needs to let into -proposed for xenial and for yakkety
[16:17] <caribou> yeah, & for yakkety
[16:17] <jgrimm> rbasak, ^^ this was the one you'd already pre-reviewed i thought?
[16:17] <smoser> yakkety is much larger sru
[16:17] <smoser> http://launchpadlibrarian.net/299016220/cloud-init_0.7.8-68-gca3ae67-0ubuntu1~16.10.1_source.changes
[16:17] <jgrimm> well, not the yakkety part
[16:18] <jgrimm> that is, our discussion last week was that xenial should go immediately after proposed cleared (Monday)
[16:18] <smoser> http://launchpadlibrarian.net/298091288/cloud-init_0.7.8-49-g9e904bb-0ubuntu1~16.04.3_source.changes
[16:18] <dudeji> this is the error i am getting : CPU iowait time (xxx:system.cpu.util[,iowait]): 29.07 %
[16:19] <smoser> possibly i guess rbasak might ask for a re-upload with only the new changes in that list
[16:19] <smoser> (ie, only 16.04.3... id' uploaded as a replacement for .2 so it had both the chagnes listed)
[16:20] <rbasak> smoser: I was about to accept cloud-init into Xenial. Are you referring to Yakkety? I hadn't looked at that at all.
[16:22] <smoser> rbasak, there is both needed.
[16:22] <smoser> xenial is small
[16:22] <smoser> yakkety is larger
[16:22] <smoser> xenial's changes file (http://launchpadlibrarian.net/298091288/cloud-init_0.7.8-49-g9e904bb-0ubuntu1~16.04.3_source.changes) has 2 entries
[16:22] <smoser> see ?
[16:22] <smoser> i can re-upload with only the one if you'd like
[16:24] <rbasak> I did review both changes, so I'm happy to accept both. Unless you want to do one at a time?
[16:26] <smoser> rbasak, no. that snot what i meant.
[16:27] <smoser> the Changes file
[16:27] <smoser> has 2 Changes
[16:27] <rbasak> Oh
[16:27] <rbasak> Ah, I see.
[16:27] <smoser> i think if you release it, wont the bugs for 0.7.8-49-g9e904bb-0ubuntu1~16.04.2 get re-marked
[16:27] <rbasak> Yes. That'll probably confuse the tooling.
[16:28] <rbasak> Sorry. I follow now. Please do re-upload with that removed.
[16:28] <smoser> you can NACK that one and i will re-upload. with a new changes
[16:28] <smoser> ok
[16:28] <rbasak> I'll leave the current one there if that's OK. Easier to diff in one go when both are present.
[16:28] <smoser> does that work?
[16:29] <rbasak> Yes
[16:29] <smoser> i'll upload the same thing, just different changes
[16:29] <smoser> ok
[16:30] <smoser> rbasak, uploaded
[16:30] <jgrimm> smoser, rbasak: thank you
[17:05] <caribou> smoser: rbasak: testing uploaded cloud-init atm
[17:06] <smoser> caribou, easiest thing to do is just launch an instance, then install it.
[17:06] <smoser> tnen rm -Rf /var/lib/cloud /var/log/cloud-init*
[17:06] <smoser> reboot
[17:06] <caribou> smoser: not sure I still have my instance on their cloud
[17:07] <smoser> oh. i thought htat is what you meant by uploaded
[17:09] <caribou> smoser:  no the uploaded to xenial-proposed
[17:10] <caribou> smoser: my local test is correct though; it fails later but does find the datasource
[17:11] <caribou> smoser: I'll ask them for one
[17:14] <smoser> caribou, i can give you one
[17:14] <caribou> smoser: then go ahead & I'll test it
[17:15] <smoser> one thing that sucks on their clloud... to my knowledge i now have some funds available on only their zrh region.
[17:15] <smoser> ie, funds are region specific
[17:30] <jgrimm> rbasak, are you also handling the yakkety-proposed cloud-init SRU?
[17:30] <smoser> caribou, well, i'm trying
[17:40] <rbasak> jgrimm: no, that hasn't been on my list
[17:41] <jgrimm> rbasak, no worries, that's what i assumed but noticed that it was v-d now too
[17:44] <caribou> smoser: fine, I'm lightning up the christmas tree in the meantime :-)
[17:46] <smoser> caribou, ubuntu@31.171.245.29
[17:46] <smoser> i think you should be able to get in
[17:46] <caribou> smoser: ok tryign
[17:46] <caribou> trying
[17:47] <caribou> smoser: ok, I'm in
[17:54] <caribou> smoser: works fine on Xenial \o/
[17:57] <smoser> caribou, you all done ?
[17:57] <caribou> smoser: for Xenial, yes
[17:57] <smoser> k. i'll kill that then
[17:57] <caribou> smoser: upgraded, remove /var/lib/cloud & rebooted
[21:02] <rbasak> nacc: o/
[21:02] <rbasak> nacc: FYI, I made some progress on the unapproved queue work
[21:02] <rbasak> nacc: not close to ready yet: https://code.launchpad.net/~racb/usd-importer/+git/usd-importer/+ref/unapproved
[21:03] <rbasak> nacc: I had to refactor some other bits though so you might be interested
[21:03] <rbasak> eg. https://git.launchpad.net/~racb/usd-importer/diff/usd/git_repository.py?h=unapproved&id=9ad33082e532707403d1b91ac91f975825707cd2
[21:03] <rbasak> and https://git.launchpad.net/~racb/usd-importer/diff/usd/importer.py?h=unapproved&id=ac4197077503c34c9b5662c521b46a9cbdba2555
[21:04] <rbasak> https://git.launchpad.net/~racb/usd-importer/diff/usd/git_repository.py?h=unapproved&id=ac4197077503c34c9b5662c521b46a9cbdba2555
[21:04] <rbasak> https://git.launchpad.net/~racb/usd-importer/diff/usd/git_repository.py?h=unapproved&id=d23e267aebe8c1bbed2b8df1f38c6a7651303413
[21:04] <rbasak> That sort of thing
[21:39] <bildz> Can someone help me with an issue with Postfix.  I have tried editing the /etc/aliases file (and running newaliases) and have also created a .forward file for the user account used to send messages, but it all appears to be rejected locally.  Please take a look at the following output and let me know what I am doing wrong.  http://pastebin.com/5s6FnA3b   thanks!
[21:59] <sarnold> bildz: does postfix/local do 'local' deliveries, to unix mbox or maildirs? do those user accounts need to exist in /etc/passwd and so on?
[22:14] <nacc> rbasak: nice, will take a look!
[22:35] <bildz> sarnold: its a default postfix install of 16.04
[22:35] <bildz> i just added a relay host