[00:31] <keithzg> darsparx_: I've actually noticed that on a few 16.04 systems recently; I blame systemd, since at least in my case it was only TTY1 (and systemd handles the TTYs these days, I believe).
[00:31] <keithzg> darsparx_: So ctrl+alt+F2 or such might well get you a non-black screen!
[00:32] <keithzg> (I might be misremembering, perhaps it drops you down on TTY7 but only 1-6 are created by default? Hmm, yeah that sounds closer to correct.)
[00:33] <darsparx_> keithzg: I'll try that....was going to just switch to doing it on digitalocean but I'd really like to have a personal homeserver that can host this >_>
[00:34] <darsparx_> keithzg: nothing.....
[00:35] <darsparx_> keithzg: is there a certain point where that should be held? because I still can't get it to work
[00:36] <keithzg> darsparx_:  Naw, just holding down ctrl and alt, and then pressing any of the F keys, should switch you to the corresponding TTY.
[00:37] <darsparx_> well I'm still getting a black screen when booting up server.....it wasn't doing this before now, I get the system bios loading screen then nothing
[00:38] <keithzg> darsparx_: Can you get to the boot menu from your BIOS/UEFI?
[00:39] <keithzg> I literally had a computer whose motherboard firmware mysteriously reset the other day and forgot what boot device to use :( which seems quite unlikely, but not impossible.
[00:39] <darsparx_> nope....tried hitting right shift like I saw somewhere and that does nothing
[00:39] <keithzg> darsparx_: Your best bet might be to repeatedly hit Delete as you're booting the computer up, which on nearly every motherboard will get you to the "BIOS" (really UEFI these days) interface.
[00:41] <keithzg> Beyond that, every piece of firmware seems to be its own special snowflake. I've seen boot menus be F8, F9, F12, ctrl-b . . . often easier to just get into the firmware interface and manually choose a boot device from there.
[00:43] <darsparx_> keithzg: no dice....I've even gone in and selected it and it's still not coming up. Would be nice if I could just straight reinstall it
[00:43] <sarnold> iirc the install media also has an easy 'recovery' mode with a few useful tools; that might be a decent environment to try troubleshooting with
[00:44] <keithzg> Yeah, I've leaned on that recovery mode more times than I can count!
[00:45] <darsparx_> yeah no I tried that too....and now I'm in to my ubu server on digital ocean so I'm going to see if I can get that working for quassel
[00:48] <darsparx_> yeah looks like I'm actually in and able to install quassel this way. If I could just wipe the thing and reinstall I would since I've not got much to lose but since digital ocean is working I'll just use it instead.....
[00:51] <darsparx_> crap well now it won't let me add a user to it :-\
[00:53] <darsparx> keithzg: thanks anyways got it working
[00:54] <keithzg> darsparx: All well that ends well, at least; take care :)
=== darsparx is now known as kaosine
[00:55] <kaosine> and I'm trying to use a old nick when this one works wow *sigh*
=== JanC is now known as Guest31516
=== JanC_ is now known as JanC
=== CodeMouse92 is now known as CodeMouse92__
[06:57] <cpaelzer> rharper: thanks for diving into that logging issue of jamespage
[06:58] <cpaelzer> jamespage: rharper: and in the details you'll find that with tcp instead of pty it would have behaved correctly already
[06:58] <cpaelzer> that is only an issue of the pty code it seems
[07:00] <cpaelzer> Extending the bug to cover for qemu in Zesty
[07:15] <tobasco> jamespage: is there any difference between uca mitaka and mitaka in ubuntu repo or do they package the same and can be ran together?
[07:25] <cpaelzer> rharper: jamespage: I pushed a ppa for the logging fix and linked the commits in the bgu so you can easily pick that up for UCA Tests
[07:25] <cpaelzer> jamespage: I outlined my schedule in the bug, please let me know if you want/need me to release that to zesty earlier
[07:50] <lordievader> Good morning
[07:51] <cpaelzer> rbasak: do you happen to know when the base-passwd allocated mysql user on uid 640001 would be used?
[10:44] <rbasak> cpaelzer: hmm. No idea. I didn't know there was a specific allocation!
[10:45] <cpaelzer> rbasak: interesting
[10:45] <cpaelzer> rbasak: I found another example in ceph and could debug with that
[10:46] <cpaelzer> rbasak: pull-lp-source base-passwd
[10:46] <cpaelzer> rbasak: check README and you'll find mysql
[11:24] <jamespage> tobasco, the mitaka UCA is actually for trusty, whereas xenial shipped with mitaka in-archive (so no UCA required for mitaka on 16.04)
[11:24] <jamespage> rharper, cpaelzer: ack thanks for the investigations!
[12:05] <tobasco> jamespage: thanks, I'm just wondering if they will play nice together if we have mitaka machines running on 14.04 and now gonna spin up new machines and would like 16.04 instead, any info?
=== ashleyd is now known as ashd
=== clvx is now known as Guest92024
[14:20] <tobasco> jamespage: any info on 13:03 < tobasco> jamespage: thanks, I'm just wondering if they will play nice together if we have mitaka machines running on 14.04 and now gonna spin up new machines and would like 16.04 instead, any info?
[14:20] <tobasco> jamespage: iirc last time I tested that we had some weird issues
[14:21] <jamespage> tobasco, that should be OK - the libvirt/qemu/openvswitch versions are all matched between trusty/mitaka and xenial/mitaka
[14:21] <jamespage> and of course openstack is as well :-)
[14:22] <tobasco> jamespage: cool, thanks :]
[14:22] <jamespage> tobasco, infact I'm running this exact mix in our qa cloud at the moment - five older trusty/mitaka compute hosts and two newer xenial/mitaka compute hosts
[15:06] <jamespage> zul, coreycb: https://bugs.launchpad.net/cloud-archive/+bug/1667334
[15:06] <ubottu> Launchpad bug 1667334 in aodh (Ubuntu) "aodh-dbsync: newton->ocata upgrade fails" [High,Triaged]
=== Poster|z is now known as Poster
=== gaughen_ is now known as gaughen
[15:49] <bekks> hi
[15:50] <bekks> for apache2, is there a way to autogenerate an index.html with links to all vhosts, like /phpmyadmin, /owncloud, and such?
[15:51] <rbasak> I don't know if some mechanism already exists, but you could write one against augeas.
[15:53] <nacc> bekks: --^
[15:55] <bekks> hmm. Ok. :)
[15:59] <nacc> bekks: http://httpd.apache.org/docs/current/mod/mod_autoindex.html maybe?
[16:02] <nacc> bekks: hrm, that may just autoindex each vhost, i'm not sure if there's a way to do that outside the context of the vhosts (e.g., you want apache to index the vhosts themselves, i think)
[16:27] <cpaelzer> jamespage: will you test the ppa (or mor likely the commits I linked) on bug 1667033 and let us know if that helps?
[16:27] <ubottu> bug 1667033 in qemu (Ubuntu) "nova instance console log empty" [High,Triaged] https://launchpad.net/bugs/1667033
[16:27] <cpaelzer> jamespage: or do you wait for that to show up in zesty first?
[16:27] <bekks> Yeah, mod_autoindex is working for each vhost, but not for a list of vhosts.
[16:27] <cpaelzer> jamespage: just want to understand your need in terms of timing
[16:28] <compdoc> zesty fist would be a great name
[16:28] <cpaelzer> did I have a typo?
[16:29] <compdoc> no, just my reading skillz
[16:29] <cpaelzer> hehe
[16:29] <cpaelzer> If you consider anything a great name do a "image search" on those names first - that sometimes is revealing to me that my impression of a good name doesn't match the Inet
[16:30] <cpaelzer> Lets stick to classic like Iron fists
[16:30] <cpaelzer> compdoc: enough fisting for now :-P
[16:30] <compdoc> k  :(
[17:27] <jamespage> cpaelzer, will look shortly
[17:35] <jamespage> cpaelzer, doing a quick backport to xenial and will test on my running deployment
[17:35] <jamespage> cpaelzer, I'll let you know in an hour or so
[17:38] <cpaelzer> jamespage: I'll likely be EOD then, but I can pick up tomorrow - if you want you can as well drop the info to the bug if it helps
[18:47] <jancoow> Hi. Can I configure a NFS server the same as a Samba server? Create shares, allow only some people etc.
[18:50] <nacc> jancoow: https://help.ubuntu.com/community/SettingUpNFSHowTo but I believe you need to add steps for authentication (using either LDAP or NIS)
[18:50] <sarnold> jancoow: if you've got identical userids/groupids among all machines, you just use standard unix discretionary access controls
[18:50] <nacc> jancoow: or what sarnold said, depending :)
[18:50] <sarnold> jancoow: ldap or nis or nis+ or similar is usually the easieast way to get all identical ids
[18:51] <sarnold> jancoow: or what nacc just said :) hehe
[18:52] <genii> jancoow: Supplement to the link nacc provided: https://help.ubuntu.com/lts/serverguide/network-file-system.html
[18:55] <jancoow> Well; Want to keep it as simple as possible. So share name, share directory and users who are allowed to acces it. But I believe that's not exactly possible with nfs, is it ?
[18:57] <genii> If you have the nfs packages installed, man exports gives you options on what sort of things you can put in the /etc/exports file
[18:57] <sarnold> jancoow: and nfsv4 has very flexible acls
[18:57] <genii> You can do at least rudimentary access control or user mapping there
[19:00] <jancoow> okay so
[19:00] <jancoow> if I want to share /mnt/hdd1
[19:01] <jancoow> for user X
[19:01] <jancoow> how would my export file looks like?
[19:02] <jancoow> user X could be on any host, so * for host would be okay
[19:18] <jamespage> cpaelzer, that all looks good to me
[19:32] <coreycb> jamespage, beisner: can you promote python-pyeclib 1.2.1-1~cloud0 and liberasurecode 1.2.0-1~cloud0 to newton-proposed for bug 1667375
[19:32] <ubottu> bug 1667375 in Ubuntu Cloud Archive newton "newton: backport pyeclib and liberasurecode1 for swift" [High,In progress] https://launchpad.net/bugs/1667375
[19:33] <coreycb> jamespage, beisner: also can you promote qemu from kilo-proposed and liberty-proposed to -updates, and then qemu from liberty-staging to liberty-proposed?
[19:34] <jamespage> coreycb, got it
[19:34] <coreycb> jamespage, thanks
[19:45] <jamespage> coreycb, done
=== lamont` is now known as lamont
=== Guest92024 is now known as clvx
[20:55] <geigerCounter> Hello