[11:05] <solinux> hi
[11:16] <madwizard> hi
[12:47] <YamakasY> was there some bug in the mysql client ?
[12:56] <rbasak> Can you be more specific? Most software have bugs that are found and fixed all the time.
[13:11] <frickler> could someone take a look at https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1384062 and maybe confirm my findings? this would affect not only Ceph, but possibly other services accessing unmounted partitions directly, e.g. databases
[13:23] <rbasak> jamespage: ^
[13:55] <jamespage> rbasak, erg
[13:56] <rbasak> jamespage: does the charm use os-prober or something? I didn't really understand the problem. But it looks like frickler could help with triaging that.
[13:57] <jamespage> rbasak, no - but other things do - I think upgrade-grub does
[13:57] <rbasak> Ah
[14:25] <jamespage> hallyn, the libiscsi MIR completed - are you ok to add that to qemu for next upload?
[14:31] <frickler> jamespage: rbasak: yes, update-grub is the main problem, and it being called implicitly when updating kernel-packages.
[17:01] <coreycb> ddellav, looks like the only things still blocking for python clients atm are python-openstacksdk and python-oslo.config
[17:02] <ddellav> coreycb gotcha. There's some blockers for the oslo's i added to the spreadsheet as well
[17:02] <coreycb> ddellav, ok
[17:20] <coreycb> jamespage, beisner: neutron 7.0.3 and ceilometer 5.0.2 for liberty tested successfully in trusty-liberty-proposed
[17:22] <jamespage> coreycb, okies - please markup the bug verfication-done...
[17:22] <coreycb> jamespage, all done
[17:22] <beisner> coreycb, ack.  thank you.  lmk if you need me to do anything on that.
[17:22] <jamespage> coreycb, of course :-)
[17:42] <coreycb> ddellav, for oslo.messaging we'll need a merge.  take a look at the current ubuntu version (pull-lp-source python-pyngus) to see what our current delta is.
[17:42] <coreycb> pull-lp-source python-oslo.messaging
[17:44] <coreycb> so for that one, we'll need to update the debian repo to the new release and merge with ubuntu
[18:19] <coreycb> ddellav, oslo.i18n and oslo.context uploaded
[18:31] <hallyn> smb: trivially reproduced with a new xenial vm,
[18:31] <hallyn> http://paste.ubuntu.com/15189468/
[18:31] <hallyn> oh, heh,
[18:31] <hallyn> ignore
[18:32] <hallyn> forgot my cloudinit scripts don't work bc of that (&$E^(*$&A*&A$* rc.S postinst prompt
[18:32] <smb> hallyn, not re-logged in to gain libvirtd group
[18:32] <smb> ah
[18:33] <hallyn> yeah i normally don't have to
[18:35] <hallyn> smb: sigh, no it was probably something about upgrading my laptop that made it happen.  dunno.  guess we'll stick to reproducing on p8 :)
[18:36] <smb> hallyn, its a bit odd since I got it installed here without issues (but I should test upgrades)
[18:41] <NwS> Heya guys, a noobish question. Can someone please explain to me how the HDDs split in this server? :/ I know there is a 500GB SSD and a 2TB HDD but that sda/sda2 part lost me.. Another guy said that sdb1 might be a clone of sda1 if I can verify that somehow.. Thanks! http://paste.ubuntu.com/15189379/
[18:50] <sarnold> NwS: sd* means "scsi disk", so scsi disk a, scsi disk b, etc
[18:51] <sarnold> NwS: disks are often partitioned; the partitions get the 1, 2, 5, 6, etc..
[18:51] <sarnold> NwS: so sda1 and sda2 are different partitions on one drive; sdb1 and sdb2 are diffferent partitions on the "second" drive, etc
[18:52] <sarnold> there's no guarantee that drives will come up in the same order -- sda sdb sdc etc -- so there's the whole pile of /dev/disks/by-id/ and related symlinks
[18:52] <NwS> sarnold, ty for the info mate, shouldn't the sda1+sda2 = sda size? or am I missing something?
[18:53] <sarnold> NwS: loads of variables there :) there may be unallocated space on the drive, the formatted filesystems will lose some space, and drive manufacturers use powers of 1000 to advertise their drives but most software uses powers of 1024 when reporting sizes
[18:54] <NwS> sarnold, ah I see. That is a 512GB Samsung 850 PRO if that matters :P
[18:55] <NwS> I didn't setup the server (obviously) but I am trying to figure out how it was "split" and how I can start using the unused space
[18:55] <sarnold> NwS: it does feel like there may be ~80 gigs "missing" somewhere; I've never used lsblk before, so I'm not positive on how to read the results though
[18:56] <wxl> can someone tell me what the heck MaaS is? i'm not sure i quite get it.
[18:56] <lotuspsychje> !maas | wxl
[18:56] <bekks> NwS: Please pastebin "sudo fdisk -l"
[18:57] <NwS> bekks, ok got some warnings here let me paste it
[18:57] <wxl> lotuspsychje: incidentially, i did read the website about it. i'm still not quite wrapping my head around what it is and how it's different from other solutions.
[18:57] <sarnold> wxl: it lets you treat physical machines a bit like a cloud
[18:58] <wxl> sarnold: so you could have a local network of machines and dynamically provision their resources to sort of act as one machine?
[18:58] <NwS> bekks, http://paste.ubuntu.com/15189769/ ty
[18:58] <sarnold> wxl: you were doing great right up until "act as one machine" :) hehe
[18:59] <wxl> ooookie dokie
[18:59] <wxl> sarnold: i'll keep scratching my head about it :)
[18:59] <sarnold> wxl: you could have most of the machines off most of the time, but when someone needs to submit a huge parallel compute job, turn on all the machines with GPUs, install an OS + application and start them running
[19:00] <wxl> sarnold: ok that kind of makes sense. thanks :)
[19:00] <sarnold> wxl: or you could use maas to automatically install openstack, so that you can then use the usual openstack or euca command line tools to launch VMs -- and when new machines are added to the openstack cluster, you can easily tell them if they are going to be storage machines or compute machines or whatever
[19:01] <sarnold> if your needs shrink (say, holidays are oven) then you could use maas to autmatically turn off uneeded machines again
[19:01] <wxl> oic!
[19:03] <sarnold> wxl: I think most folks use it primarily to get openstack installed; that's a pretty flexible environment, and can easily hand out VMs from 1 vcpu, 1 gig of ram, 1 gig of disk, all the way up to whatever the biggest machines can provide...
[19:03] <wxl> sarnold: how is this different from using juju to get openstack installed?
[19:03] <sarnold> wxl: if you were doing scientific computation tasks or something similar that really -needed- to run on bare metalwithout virtualization getting in the way, maas could work
[19:04] <sarnold> wxl: heh, that's the thing, juju just treats maas like another cloud instance -- requesting machines with characteristics to deploy software to :)
[19:04] <wxl> oh!
[19:04] <wxl> NOW i think it makes sense. thanks sarnold!
[19:04] <sarnold> \o/ :)
[19:09] <bekks> NwS: Since you are using gpt, can you please pastebin gdisk -l
[19:09] <bekks> or parted -l ?
[19:13] <NwS> bekks, got an error with gdisk -l but parted -l worked: http://paste.ubuntu.com/15189925/
[19:15] <bekks> NwS: Looks good. You're on a HP server, right? Whats the exact issue at that point?
[19:15] <sarnold> I -think- you could just use parted to create a new partition on /dev/sda or resize the lvm partition of /dev/sda
[19:16] <sarnold> please make sure your backups have been working before starting :)
[19:16] <bekks> No need for new partitions, all space is either in use by partitions or LVM PV.
[19:17] <sarnold> bekks: oh? it feels lik ehtere's roughly 65 gigs missing from the ssd
[19:17] <sarnold> bekks: it reports 512gb but the end of partition 2 is at 435
[19:17] <NwS> bekks, Yeah I am on an HP server. I'm trying to figure out if I am currently using the whole available space (because I think I am missing ~200GB on SSD and can't find any space of the HDD)
[19:18] <bekks> sarnold: thats what we have to investigate now. :)
[19:18] <NwS> And in the end move the logs to the HDD since they are eating up all my boot space..
[19:18] <NwS> The webalizer logs **
[19:19] <bekks> NwS: Logs arent in the boot space, so they dont eat it up ;)
[19:19] <NwS> Logs are on the sda1
[19:19] <bekks> NwS: So lets solve that issue first, since thats the real issue.
[19:20] <NwS> Which is 97% full atm (yesterday the server was down for like 5h because of it being full :/)
[19:20] <bekks> NwS: so pastebin "du -sh /" please, so we can narrow down the space issue.
[19:22] <NwS> bekks, got an error: http://paste.ubuntu.com/15190014/
[19:22] <NwS> ty for the all help btw bekks and sarnold
[19:23] <bekks> NwS: It was my mistake, please use "sudo du -sh /*"
[19:24] <NwS> I'm logged in as su
[19:24] <NwS> got same msg
[19:25] <bekks> But different output.
[19:28] <NwS> Yeah, tried it a few times it gives the exact same msg but with different numbers
[19:28] <bekks> It gives you a total different output, showing all first-level directories in /
[19:28] <bekks> So pastebin "sudo du -sh /*" please.
[19:29] <sarnold> the errors in /proc can be ignored
[19:29] <sarnold> those are processes that existed when du read the /proc directory but were dead by the time it tried to read those files
[19:30] <NwS> Ah sorry I've missed the * /facepalm
[19:30] <sarnold> you'll see that kind of error often, it's a good idea to get familiar with it :)
[19:30] <sarnold> hehe
[19:31] <NwS> Here it is http://paste.ubuntu.com/15190101/
[19:32] <bekks> NwS: And can you pastebin "cat /etc/issue" too, pleasE?
[19:32] <NwS> http://paste.ubuntu.com/15190140/
[19:38] <spm_draget> java 8 ist not really available for trusty, or? Is there some backport?
[19:41] <sarnold> spm_draget: there is nothing supported. there is this, however, which may suffice for your needs https://launchpad.net/~openjdk-r/+archive/ubuntu/ppa
[19:41] <bekks> sarnold: http://www.ubuntuupdates.org/ppa/webupd8_java
[19:41] <spm_draget> Thanks, I will take a look!
[19:42] <sarnold> bekks: whose project is that?
[19:43] <bekks> sarnold: you mean the webupd8team ppa?
[19:43] <sarnold> bekks: yeah
[19:43] <bekks> https://launchpad.net/~webupd8team/+archive/ubuntu/java -- dont know :)
[19:44] <sarnold> looks like alin andrei and stephen brandt
[19:44] <sarnold> dunno them, dunno if I want them to have root on my computers :)
[19:45] <bekks> sarnold: :D
[19:45] <bekks> sarnold: thats a good question for every ppa.
[19:45] <sarnold> bekks: yes, yes it is :)
[19:46] <YamakasY> was there a bug in the mysql client ?
[19:46] <YamakasY> bad connections and such ?
[19:52] <ddellav> coreycb python-oslo.serialization is ready for review
[19:52] <ddellav> everything else is depwait on oslo.config
[19:58] <NwS> bekks, did you see the last paste? just wondering, no hurry or anything
[19:59] <bekks> NwS: And your wbealizer logs are stored where exactly?
[20:00] <NwS> under /var
[20:00] <bekks> Where exactly?
[20:01] <NwS> var/log/virtualmin/
[20:01] <bekks> Ah :)
[20:01] <bekks> So can you pastebin "ls -lha /var/log/virtualmin/" or will that reveal sensitive data?
[20:02] <NwS> It will reveal a ton of websites :)
[20:03] <sarnold> iirc you had 770-ish megs used in /boot -- which might be tight if you've only got one gig for /boot or something; and /var looked like 20-odd gigs of stuff
[20:03] <sarnold> you could clean /boot by keeping just two kernels in there: the currently running kernel and perhaps the newest or second-newest, depending upon which kernel you're running now..
[20:03] <NwS> out of those 20gbs 16 are the webalizer logs :/
[20:03] <sarnold> and apt-get autoclean, apt-get clean, etc may give you a couple of quick gigs
[20:04] <NwS> I did run clean yesterday in order to make some room but that only gave me back like 600MBs
[20:05] <sarnold> bummer
[20:05] <NwS> That's why I am looking for the 2TB drive, and then find a way to move the logs over there :P
[20:11] <bekks> NwS: The 2TB drive is perfectly there, as can be seen in your pastebins.
[20:11] <coreycb> ddellav, python-oslo.serialization uploaded, thanks
[20:12] <ddellav> :)
[20:13] <NwS> bekks, is it possible to find out which folder/s is actually that HDD? :/
[20:13] <bekks> NwS: Look at "mount".
[20:13] <bekks> As your pastebins show, it isnt mounted.
[20:14] <NwS> Oh, so I can mount some GBs for example?
[20:14] <NwS> And one last Q and I'm off looking it up. When I mount it will I need to restart the server?
[20:15] <bekks> Most likely, you just want to create a PV (if it doesnt exist already) on that disk, add the disk to a volume group, add a volume, create a filesystem on that volume, and a folder for your webalizer logs.
[20:15] <bekks> NwS: Mounting does not need a restart of the server.
[20:15] <NwS> tyvm for all the info and help bekks :)
[20:15] <sarnold> no, but if you add a new mount then you'll want to modify /etc/fstab and rebooting afterwards is a good way to make sure you got the change correct :)
[20:16] <bekks> mount -a is a better way to test fstab functionality.
[20:16] <NwS> ty for the info too sarnold :)
[20:16] <NwS> Will do some digging now
[20:34] <patdk-wk> oh, sarnold, I have a question :)
[20:34] <patdk-wk> what is the state of libteam for ubuntu?
[20:35] <patdk-wk> I noticed it was added, more cause it exists in debian
[20:35] <patdk-wk> but was wondering if there would be any config/script for using it, vs the 1 or 2 blog pages I can find, and are not terribly reliable setup processes
[20:37] <sarnold> patdk-wk: hmm, when I reviewed it I found a pile of oddities that I didn't like.. I wonder if anyone got around to addressing them?
[20:37] <patdk-wk> no idea, was looking for any new info, since 16.04 is coming around
[20:37] <patdk-wk> but wasn't able to locate anything new last night
[20:38] <patdk-wk> but went and backported the newest version to trusty to see if it helped my test machine at all
[20:38] <patdk-wk> most of the time, my machine works fine
[20:38] <patdk-wk> but sometimes it will boot without any network working :(
[20:39] <patdk-wk> but just figured out what that was, have to reproduce it again, and dig into it
[20:39] <patdk-wk> I think it's the *standard* issue, udev timing
[20:39] <sarnold> since it's in universe any 'main' packages can't hard-depend upon it.. anything that might have used it may be patched to disable it, or load it only on demand rather than by default, etc..
[20:40] <patdk-wk> na, I wouldn't say make it a default
[20:40] <patdk-wk> was more wondering if there might be any plans to update network up scripts to handle it
[20:40] <patdk-wk> like the bonding driver
[20:40] <patdk-wk> not, make use of it by default :)
[20:41] <patdk-wk> though, i think my biggest issue is, I need to make an init script to run and control teamd, vs launching it via a pre/post-up command
[20:42] <sarnold> ooof. yeah that sounds like a lot of work..
[20:43] <patdk-wk> oh well, was annoying me last night :)
[20:43] <patdk-wk> cause I patched that server, and it didn't come back
[20:43] <patdk-wk> if I thought about it more, I would have got on the console, and dianosed it properly
[20:43] <patdk-wk> instead of just kicking it again
[20:44] <sarnold> ugh.. sometimes the quick way is also the slow and annoying way :)
[20:44] <patdk-wk> depends on what your solving for :)
[20:45] <patdk-wk> customer impact, or future problems
[20:46] <sarnold> true
[21:02] <coreycb> ddellav, python-oslo.config uploaded
[21:18] <Mikel> Hi! I'm experiencing a weird issue where after installing Ubuntu 14.04.4 Server the default network route is missing from the route table. I've configured some interface bonding and VLAns statically in /etc/network/interfaces. Do you know how can I debug this problem or what could be happening?
[21:18] <Mikel> I looked dmesg and syslog but I don't find the problem/I don't have enough knowledge to detect it
[21:18] <Mikel> I verified that I defined only one 'gateway' sentence between all the interfaces as I should do
[21:18] <Mikel> Sometimes a manual route that I have defined in another of the interface also is missing
[21:18] <Mikel> this happens when I reboot the machine, the routes are there intermittently, sometimes yes sometimes no
[23:20] <ddellav> coreycb python-oslo.log, python-oslo.middleware, and python-oslo.cache are ready for review & push