[00:03] <teward> anyone know how to enable the php hash plugin/functionality?
[00:06] <mdev> install uh
[00:06] <mdev> apt-get install php5-mcrypt
[00:06] <mdev> but I believe it already has some builtin to core
[00:06] <mdev> like md5, sha256 etc...
[02:07] <keithzg> Hmm, where does do-release-upgrade (or is it just apt?) get its expected download speed from? I'm doing a 12.04 -> 14.04 upgrade right now, and it told me "You have to download a total of 992 M. This download will take about 1 minute with your connection." I mean, I WISH our connection was that fast ;)
[02:10] <lifeless> keithzg: you are on 1Gbps ethernet, right ? :)
[02:10] <lifeless> keithzg: erm 10Gbps
[02:11] <lifeless> keithzg: alternatively, it might be going by how long it took to update the package indices, I'm not sure - have never bothered looking
[02:12] <mdev> has there been another shellshock patch?
[02:12] <mdev> google engineers said the things still super vulnerable to where it was before
[02:12] <mdev> in a different way
[02:14] <sarnold> mdev: the hardening patch that we released on saturday should mitigate the scope of the remaining flaws down from "crisis" to "bug that needs to be fixed"
[02:15] <mdev> alrighty thanks
[02:15] <mdev> i'd say it'd be nice to avoid this sort of thing in the future but apparently bash is worked on literally 1 guy so...
[02:15] <mdev> yeah
[02:16] <sarnold> and he's done heroic work this last week
[02:16] <mdev> thought an ubuntu dev fixed it for ubuntu?
[02:19] <sarnold> yes, mdeslaur provided us with updated packages; he used Chet's patches :)
[02:19] <mdev> ahh nice
[02:19] <mdeslaur> sarnold: for the record, I used redhat's patch, as did debian
[02:20] <mdeslaur> Chet's patch came out a few hours later, and used a different suffix
[02:21] <sarnold> mdeslaur: aha :)
[02:21] <mdeslaur> and now apparently apple has used a different prefix/suffix combo also
[02:21] <mdev> well inital ubunut patch wasn't completely, was that from redhat?
[02:21] <sarnold> >() or something.. go figure.
[02:27] <iDealz> anyone know how I can lookup what version of ubuntu I'm running from initramfs prompt?
[02:28] <iDealz> I know it is 12.04 but dont remember if there was anything beyond that
[02:28] <mdev> lsb_release -a
[02:28] <mdev> may have to apt-get install lsb_release
[02:28] <iDealz> doesnt work from initramfs prompt
[02:29] <iDealz> I have a broken array so loads into funky prompt
[02:29] <iDealz> trying to get a boot usb going so I can boot into root
[02:29] <mdev> cat /etc/*-release
[02:29] <iDealz> but want to make sure I get the right version
[02:29] <mdev> cat /proc/version
[02:30] <mdev> uname -a
[02:31] <iDealz> hmm
[02:31] <iDealz> cat /proc/version and uname -a both worked
[02:31] <iDealz> but unexpected results
[02:32] <iDealz> Linux (none) 3.2.0-43-generic #68-Ubuntu SMP
[02:32] <iDealz> is what it returned
[02:32] <iDealz> and a date
[02:33] <mdev> uname -r
[02:34] <iDealz> same result less date
[02:34] <iDealz> 3.2.0-43generic
[02:34] <iDealz> must be because of the failed array and not being able to boot into root
[02:34] <mdev> lsb_release really the best way, when I first started porting code to nix I was rather annoyed it was so hard to cross distro version info reliabily like you can on windows, but apparently that's not really cared about in nix community
[02:35] <mdev> *get rather
[02:35] <mdev> you maybe able to get version info based off your repo but I don't know how
[03:18] <iDealz> anyone have any experience with rebuilding broken arrays?
[03:47] <iDealz> anyone have any experience with rebuilding broken arrays?
[06:28] <lordievader> Good morning.
[06:59] <|\n> hey guys, noob situation here... was trying to set it with a value much lower than 65535 and got "sysctl: setting key "net.core.somaxconn": Invalid argument" what should i read to get understanding on why i see this error at all?
[07:34] <soren> |\n: EINVAL for that sysctl should only be caused by the value being outside the valid range.
[07:34] <soren> |\n: ..which is 0-65535.
[07:34] <|\n> soren, i can not agree with that due to what i see, many thanks for pointing that out
[07:35] <soren> |\n: How are you setting the value?
[07:35] <|\n> soren, i've edited sysctl.conf directly and -p
[07:36] <|\n> that is not all, i also got the same for net.ipv4.tcp_max_tw_buckets, net.ipv4.tcp_tw_reuse and most of things i tried to set out of experimental purposes
[07:36] <soren> |\n: pastebin your sysctl.conf.
[07:37] <|\n> k
[07:38] <|\n> soren, http://pastebin.ovrnet.ru/paste/gH1BsuJ-#J2z2Ic2i
[07:40] <soren> |\n: If you stop putting comments after the values, you'll be fine.
[07:40] <soren> |\n: Those aren't comments. They'll get written to the sysctl, too, so you're not even passing in integeres.
[07:40] <soren> integers.
[07:40] <|\n> soren, oh, hah, good if so! many thanks!
[07:40] <soren> np
[07:41] <|\n> soren, i don't do such things often enough to stop myself from commenting things like that before i put em
[07:41] <|\n> thank you, man
[07:42] <soren> Sure.
[07:54] <jamespage> rbasak, there is a bug for that writable /usr/lib thing in mysql already I think
[07:54] <jamespage> let me check
[07:54] <jamespage> morning soren
[07:54] <soren> jamespage: 'morning!
[09:27] <gnuoy> jamespage, I've updated https://code.launchpad.net/~gnuoy/nova/bug1314677/+merge/236321 as per your comments however the patch has been -2 upstream due to stable/icehouse freeze for 2014.1.3
[09:27] <jamespage> gnuoy, bah - nm - we can carry it as a patch for .3
[11:34] <sveinse> Hi. I'm running 14.04 server in a VMWare Datacenter (don't know exact which, but I'm using vSphere to access it). I have problems with this build server where it becomes mindbuggingly slow. It is doing dpkg-builds and may take ages to complete. We have a similar server running 12.04 on the same datacenter, with the same setup which runs fine. When the 12.04 takes 1.5 hrs to build all...
[11:34] <sveinse> ...software, the 14.04 server may take 8-10 hours.
[11:35] <sveinse> I can't figure out why this happens. From the data center side, the two servers are identical. Looking from the 14.04 guest side, the kernel log sais nothing, but you see it running at 100% on all cores and is generally very slow
[11:36] <sveinse> I'm running the latest kernel 3.13.0-36-generic 64-bit. The core of the problem is: How can I figure out if this is a datacenter issue or a kernel/guest issue?
[11:37] <sveinse> I'm lost and IT cant help me any more as I can't provide any description to what is wrong
[11:43] <jamespage> zul, ok - what do we have rc's for - keystone?
[11:43] <zul> jamespage: ?
[11:44] <zul> jamespage:  afaik nothing has changed packaging wise for keystone or glance
[11:44] <jamespage> zul, yes - I mean't which upstream rc's
[11:44] <zul> jamespage:  glance and keystone so far
[11:47] <jamespage> zul, http://pad.ubuntu.com/juno-rc1
[11:47] <jamespage> for tracking
[11:48] <zul> jamespage: coolio...ill keep my eye on things and update it if i see any more
[11:52] <rtfmoz> Hello, I was wondering why "w" was returning an ip address like 1.128.31.14. Ubuntu 12.04.05 kernel 3.8.0-44-generic. Is there a bugtrack I can check?
[11:54] <maxb> rtfmoz: Nothing you've said so far indicates a bug
[11:54] <rtfmoz> ok what should I check...
[11:55] <maxb> Nothing, as nothing appears to be wrong?
[11:55] <jamespage> zul, rage watch files
[11:56] <rtfmoz> oh? my ip address is 101.168.42.151
[12:00] <rtfmoz> system seems to think I am coming from that address... 21:59:12.243307 IP 172.31.0.23.22 > 1.128.31.140.62793: Flags [P.], seq 1178096:1178304, but i dont think I am. will be back
[12:00] <rtfmoz> to check something
[12:02] <maxb> 172.31.0.23 is a RFC1918 private address
[12:02] <maxb> Clearly NAT is involved
[12:05] <rtfmoz> yes but thats happens inbound to that address. my source is internet address and should not be modified.. investigating.
[12:11] <jamespage> zul, coreycb: hmm - either of you doing MIR for python-glance-store ?
[12:11] <coreycb> jamespage, I can, the sync just went through yesterday
[12:11] <jamespage> coreycb, please - its needed for glance rc1
[12:11] <jamespage> coreycb, I'll upload with it added to the deps
[12:11] <coreycb> jamespage, ok
[12:12] <rtfmoz> ok it seems 1.128.31.14 is a valid IP address after all. go figure.
[12:13] <henkjan> inetnum:        1.128.0.0 - 1.159.255.255
[12:13] <henkjan> netname:        TELSTRAINTERNET49-AU
[12:13] <jamespage> coreycb, ok - just dealing with an issue in the unit test execution in glance
[12:13] <rtfmoz> yep that the carrier I am using. just thought it was a bogus address. thanks
[12:24] <jamespage> coreycb, zul: glance needs a minor bump on retrying as well - syncing that now
[12:30] <sveinse> I am now testing server performance with sysbench, and I am seeing that my 14.04 server is on cpu performance is a factor 5(!) worse performance than on a twin 12.04 server installation.
[12:31] <sveinse> I don't understand this. Kernel issue? Kernel on vmware host issue? Only on 14.04?
[12:35] <jamespage> sveinse, are you benchmarking ontop of vmware?
[12:37] <coreycb> jamespage, https://bugs.launchpad.net/ubuntu/+bug/1375770
[12:37] <sveinse> jamespage: Yes. Because this is the (corporate) environment we have to run our build servers.
[12:38] <sveinse> jamespage: the 12.04 server performs adequate, but the 14.04 server performs very poorly for unknown reason. Takes factor 3-5 longer time to compile same software as on 12.04 server
[12:39] <jamespage> sveinse, are they on the same underlying hypervisor?
[12:39] <sveinse> jamespage: They are on the same host, with the same back-end storage solution
[12:39] <patdk-wk> well, didn't the scheduler change?
[12:39] <patdk-wk> for the disk?
[12:40] <patdk-wk> did you tune any of them? or both just default installs?
[12:40] <sveinse> both servers are running out-of-box solution for storage, that is with lvm2 default. No encryption
[12:40] <patdk-wk> lvm2 default? that was never a default when I installed my servers
[12:41] <patdk-wk> you need to check for differences
[12:41] <patdk-wk> are both vm's built using the same scsi controller? same queue scheduler? same readahead? .....
[12:42] <sveinse> patdk-wk, yes, that is what IT is telling me.
[12:42] <patdk-wk> heh? it? what is an it?
[12:43] <sveinse> The biggest difference I can see is the kernel, but I guess you guys would have known if there were issues with the 3.13.0 kernel...
[12:43] <sveinse> IT = IT department. The BOFH that controls the mandatory datacenter in our company
[12:44] <sveinse> And they are giving up claiming that this is the 14.04 guest's fault, not the host system. So here I am
[12:45] <qman__> Well, you could install the trusty kernel on 12.04 and see if it causes the problem
[12:46] <sveinse> qman__: What about the oposite? Taking the 12.04 kernel to the 14.04 server?
[12:46] <patdk-wk> how exactly are you using sysbench?
[12:46] <patdk-wk> sveinse, that would never work
[12:47] <sveinse> patdk-wk: Rudimentary really. sysbench --test=cpu --cpu-max-prime=20000 run
[12:47] <qman__> The current kernel is backported to 12.04 and supported, the reverse is not
[12:47] <patdk-wk> what? that is a cpu test, not disk
[12:47] <patdk-wk> why would you think disk is the issue
[12:47] <qman__> That's the only reason I suggested it
[12:47] <sveinse> Takes 30.2s on 12.04, while it uses 168.5s on 14.04
[12:48] <patdk-wk> but that doesn't even involve the kernel
[12:48] <sveinse> I never said disk perf, did I? I said system performance. My apps compile awfully slow
[12:49] <patdk-wk> ah
[12:49] <sveinse> Disk performance is not that skewed, just a factor of 30-40%, instead of 500% percent difference on CPU
[12:49] <patdk-wk> for me
[12:50] <patdk-wk> 23.3525s on 14.04
[12:50] <patdk-wk> 23.7733s on 12.04
[12:50] <patdk-wk> so it is defently the 14.04 kernels issue
[12:50] <patdk-wk> not that cpu tests even use the kernel
[12:52] <sveinse> patdk-wk, on my VirtualBox 14.04 instance: 25.2s
[12:53] <jamespage> sveinse, the 14.04 kernel does have more in-tree support for the esx hypervisor - its possible something there is causing issues; are you running open-vm-tools?
[12:54] <patdk-wk> most likely, using a cpu's that lack ept support
[12:55] <sveinse> jamespage: I was reccommended to install the commercial vmware tools from the hypervisor instead of using the open-vm-tools. Could this help perhaps?
[12:56] <jamespage> sveinse, well its something to try
[12:56] <patdk-wk> jamespage, it's still just cpu benchmark
[12:56] <patdk-wk> tools aren't going make a difference
[12:56] <patdk-wk> except to help network/disk/memory
[12:56] <jamespage> hmm true
[12:57] <patdk-wk> I would look for lack of ept support on the cpu, the host overloaded, or cpu overtemp
[12:57] <sveinse> jamespage: I notice in vsphere that my 14.04 vm is setup with "hardware virtualization" disabled, and "performance counters" disabled. They are so for the 12.04, but could this be related as well?
[12:57] <patdk-wk> what cpu is in this server?
[12:57] <sveinse> patdk-wm: I would too, except 12.04 and 14.04 run on the same host server
[12:58] <patdk-wk> does the server only have a single cpu?
[12:58] <RoyK> sveinse: I am such a BOFH ;)
[12:58] <patdk-wk> could be improperly installed heatsink on one
[12:58] <patdk-wk> and intel is suprising resilent about mixmatched cpu's :)
[12:59] <RoyK> sveinse: this is vmware, right? is vmware tools installed on the guest? I'd recommend using the vmware tools from vmware, not the open source variant
[12:59] <sveinse> patsk-wk: I don't know the specs for it (as I don't have the rights to access this info in vsphere). I think its a 12-core AMD blade server (but I'm guessing)
[13:00] <sveinse> RoyK: Yes, that was the recommendation from the datacenter admins as well
[13:00] <patdk-wk> cat /proc/cpuinfo, should get you *close*
[13:00] <RoyK> patdk-wk: on the guest? ;)
[13:00] <patdk-wk> yes
[13:00] <patdk-wk> it normally shows the *correct* cpu model name
[13:00] <RoyK> it should show the cpu model, yes
[13:00] <patdk-wk> but not the correct flags :)
[13:00] <patdk-wk> but only the one the system was booted on, incase of vmotions it will be wrong
[13:01] <sveinse> patdk-wk: AMD Opteron 6238
[13:01] <jamespage> coreycb, http://pad.ubuntu.com/juno-rc1
[13:01] <jamespage> for rc1 tracking - I'm dealing with keystone and glance - next is all yours ;-)
[13:02] <sveinse> RoyK, you have any experience with running 14.04 on vmware data center? (unfortunately I don't which and which version)
[13:03] <patdk-wk> sveinse, all of my tests where from ubuntu 12.04/14.04 running on esxi 5.5
[13:03] <RoyK> sveinse: I have a few VMs running 14.04, yes
[13:03] <sveinse> patdk-wk: Thanks
[13:05] <coreycb> jamespage, ah thanks!  it looks like only Keystone and Glance have been released thus far?
[13:06] <sveinse> What I'm seeing in vsphere management is that my 14.04 server is almost always maxing out the CPU figure (and gives CPU usage alarms). The other's are only a few 100's MHz, but 14.04 is consistently maxing out to 10320 Mhz (it is setup with 2 cores 2 sockets)
[13:08] <jamespage> sveinse, "hardware virtualization" disabled sounds bad to me
[13:10] <coreycb> jamespage, zul: could one of you merge this?  https://code.launchpad.net/~cjohnston/horizon/icehouse-1308651/+merge/235978
[13:10] <sveinse> jamespage: I'll try to change that. I also see that CPU/MMU virtualization is set to automatic. What is it for you guys?
[13:11] <coreycb> jamespage, zul: and this please, https://code.launchpad.net/~corey.bryant/horizon/b3-css-fix/+merge/236161
[13:17] <patdk-wk> sveinse, you want automatic
[13:17] <patdk-wk> but where is hardware virtualization even an option?
[13:19] <sveinse> In vsphere (the web page). My VMs are running VM version 10 (ESXi 5.5 and later) and as such only available on the web interface, not the dedicated client
[13:19] <sveinse> Under CPU options
[13:20] <patdk-wk> ah, I only use the web interface if required
[13:20] <sveinse> vmware has changed the policy, so some new features are only available in the web interface
[13:20] <patdk-wk> that has always been the policy
[13:21] <sveinse> Setting HW virtualization enabled didn't help. 12.04: 30.3s, rebooted 14.04: 182.1s
[13:23] <sveinse> This is just so weird
[13:24] <sveinse> Hmm. Hang on. My 14.04 is set to 32-bit linux in the host, while running 64-bit linux. Could this be the cause?
[13:25] <patdk-wk> it will cause issues, yes
[13:25] <patdk-wk> cause using 32bit on a 64bit system is slower than crap
[13:25] <patdk-wk> so it will use software virtualization for 32bit guests
[13:25] <patdk-wk> instead of hardware
[13:27] <tafa2> really?
[13:27]  * tafa2 did not know that
[13:28] <tafa2> from #ubuntu [14:27:00]  BluesKaj:	 kodiak1, kvm and qemu, virtualbox
[13:28] <sveinse> patdk-wk: That's it! Just rebooted. And it took 10s to come online with ssh. Results: 28.8s :D
[13:28] <kodiak1> Hey folks, Redhat sysadmin here - wondering if Ubuntu has a supported oVirt-based virtualization product (like Redhat has with RHEV)
[13:28] <sveinse> I am really happy guys! Let me test this for a day or two, but I am very optimistic
[13:29] <kodiak1> tafa2:  Those aren't really a reasonable competitor to VMWare.  If those are 'it', I'm guessing Canonical aren't really trying to compete with Redhat or VMWare in the virtualization market...
[13:30] <tafa2> kodiak1 im just the messenger someone posted that after u left
[13:30] <kodiak1> tafa2, thanks haha
[13:30] <tafa2> :)
[13:30] <jrwren> what is ovirt? isn't that just the windows driver for kvm?
[13:30] <tafa2> i thought that was virtio
[13:31] <jrwren> ah, yes, virtio. I was confused.
[13:31] <jrwren> https://en.wikipedia.org/wiki/Red_Hat_Enterprise_Virtualization is just KVM with extra stuff.
[13:32] <jrwren> oh... this ovirt: https://en.wikipedia.org/wiki/OVirt  huh, never heard of it.
[13:33] <jrwren> kodiak1: I think you are correct in saying that Canonical has nothing which directly matches up to those products.
[13:34] <tafa2> looks cool
[13:34] <kodiak1> "RHEV is just KVM with extra stuff" is kind of an understatement.
[13:35] <kodiak1> That's kind of like saying that Openstack is just KVM with extra stuff
[13:35] <jrwren> kodiak1: i'm crazy enough, I probably would say that :)
[13:35] <kodiak1> I know that Canonical is heavily invested in Openstack but I'm still kind of surprised that they don't have the resources to roll a supported oVirt product.
[13:35] <RoyK> jrwren: heh - kvm is just the hypervisor - there's a *lot* more
[13:35] <jrwren> kodiak1: I know enough about openstack to know how foolish that would be. Is RHEV as much of a beast as OS?
[13:36] <kodiak1> If you've ever used vSphere & ESX in a clustered config you're seeing basically the gamut of what oVirt does
[13:36] <jrwren> kodiak1: what would such a product do? Allow management of virtual machines?
[13:36] <jrwren> kodiak1: transparent migration too?
[13:36] <kodiak1> All of it
[13:36] <jrwren> kodiak1: that is impressive. good job redhat!
[13:37] <kodiak1> People like to say that Openstack is for managing herds and RHEV / oVirt is for managing pets
[13:38] <kodiak1> If you have specific long-running VMs that make up important long-term services they usually go on RHEV or VMWare, whereas appdev, testing, and more transient VMs go in Openstack
[13:38] <kodiak1> -generally-
[13:38] <jrwren> That is one approach. Another approach is everything in openstack.
[13:38] <kodiak1> People are starting to use Openstack where they would traditionally use VMWare but that's kind of overkill
[13:39] <jrwren> I think some folks have a goal of making openstack so easy that it is not overkill.
[13:40] <kodiak1> oVirt is much more mature as well, I think a lot of mid-size shops are waiting on dust to settle on openstack because as-is it takes a lot more care and maintenance
[13:41] <jrwren> i don't know that it takes a lot more care and maint. In fact, that was not my experience. It required very little maint.  It does havea  very steep learning curve.
[13:42] <kodiak1> There's the learning curve
[13:42] <kodiak1> There's the upgrades
[13:42] <jrwren> kodiak1: at this point we are really talking business and markets, right? RHT wants to sell in that market right now and apparently canonical does not.
[13:43] <kodiak1> Trust me as someone who's dealt with both recently oVirt is much simpler for people who don't have dedicated ostack people - and it'll run for way longer than havana, icehouse, etc are supported
[13:43] <jrwren> kodiak1: is there a free open source ovirt thing that one can play with? Can I install fedora and try out the tools you are talking about?
[13:44] <kodiak1> Yep oVirt is 100% free upstream project of the RHEV product
[13:44] <kodiak1> I'm not too bummed that Canonical isn't in on oVirt in a paid-support kind of way, just a little surprised.  I'm a Redhat guy coping with a buddy working on Canonical stuff so it's not a big deal to me
[13:45] <kodiak1> http://resources.ovirt.org/pub/ovirt-3.4/
[13:45] <jrwren> kodiak1: :)  Why be "a redhat guy" why not be a linux guy ?
[13:46] <kodiak1> When there are a million other things to stay current on it's easier to focus on what the employer is interested in using.
[13:47] <kodiak1> I do check in on Canonical every few years.  I was a Debian user from 2002 on and used Ubuntu from 4.10-9.10
[13:47] <jrwren> kodiak1: always good to stay aware of what is out there.
[13:47] <kodiak1> Allegedly oVirt is supported on Debian
[13:48] <jrwren> kodiak1: i saw that on ovirt.org. Probably not much to make it work on ubuntu.
[13:48] <jamespage> coreycb, zul: keystone done
[13:48] <zul> jamespage:  sweet
[13:55] <gnuoy> coreycb, do you have anytime for https://code.launchpad.net/~gnuoy/nova/bug1314677/+merge/236321 ?
[13:55] <coreycb> gnuoy, sure I'll take a look
[13:55] <gnuoy> thanks
[14:04] <TuxBrother> If I have a UnixListenSocket at /var/chroot/dev/log, how do I redirect the input to it to /var/log/blah.log?
[14:04] <TuxBrother> Within rsyslog, the only possibility is to create a socket, not where the input is directed
[14:12] <frickler> bug #1322568 also affects cloud-archive:icehouse, should this be added to the bug report and if yes, how? or will the updated libvirt packages be backported anyway?
[14:19] <zul> coreycb: ceilometer is out
[14:20] <coreycb> zul, thanks
[14:38] <tafa2> I personally dislike vmware - a lot
[14:44] <RoyK> tafa2: why?
[14:44] <tafa2> RoyK so clunky
[14:45] <jamespage> coreycb, both of those horizon merges merged; I switch the changelog entries to UNRELEASED - please do that for any changes that won't be uploaded immediately
[14:45] <tafa2> much prefer for example onapp
[14:45] <RoyK> tafa2: clunky?
[14:45] <coreycb> jamespage, ok, and thanks!
[14:45] <coreycb> jamespage, can we merge liam's update to nova?  https://code.launchpad.net/~gnuoy/nova/bug1314677/+merge/236321
[14:45] <jamespage> coreycb, already done!
[14:46] <jamespage> just call me Mr Merge
[14:46] <RoyK> tafa2: rather different things, though
[14:46] <coreycb> jamespage, whoa, Mr Lighting Fast Merge!
[14:46] <tafa2> RoyK yes - and I meant it from a hosting perspective
[14:47] <tafa2> :)
[14:47] <RoyK> for that, I'd probably used openstack
[14:49] <gnuoy> jamespage, coreycb, thanks
[14:49] <coreycb> gnuoy, yw - nice job
[14:49] <jamespage> gnuoy, the UNRELEASED comment above is a good one for you as well btw
[14:50] <jamespage> coreycb, gnuoy: using UNRELEASED means that additions to the changelog get appended to the UNRELEASED entry
[14:50] <gnuoy> jamespage, yep, I did update the changelog after your comment
[14:50] <jamespage> coreycb, gnuoy: leave releasing to the uploader... normally zul or I but might be others
[14:51] <coreycb> jamespage, k thanks for the tip
[15:55] <smoser> rbasak, or jamespage or anyone..
[15:55] <rbasak> o/
[15:55] <smoser> owonder if we have a sane source of information that shows package upgrades between T->U
[15:55] <smoser> in a consolidated view (ie, not "go crawl utopic-changes")
[15:55] <rbasak> What do you mean?
[15:55] <rbasak> A list of packages that are newer?
[15:56] <smoser> yeah. and i guess new packages too.
[15:56] <rbasak> For the entire archive?
[15:56] <smoser> and dropped.
[15:56] <smoser> well, i care about main more than universe
[15:56] <smoser> and universe more than multiverse
[15:56] <rbasak> I'm not aware of one, but some shell-fu with grep-dctrl and comm or meld might be enough
[15:56] <smoser> but i assume if such a thing exists it probably has data for all.
[15:56] <rbasak> Maybe distrowatch?
[16:01] <jamespage> zul, coreycb: oslo.vmware 0.6.0 also in the release team review queue for glance rc1
[16:01] <jamespage> I'll get there even if it kills me
[16:01] <zul> jamespage:  okies
[16:02] <coreycb> jamespage, thanks
[16:03] <RoyK> oslo.vmware? why 'oslo'? it's where I live :P
[16:03] <jamespage> open stack library something or other
[16:05] <rbasak> smoser: how about something like http://paste.ubuntu.com/8466864/ ?
[16:05] <rbasak> (could do with some tuning though)
[16:07] <smoser> yeah. not unreasonable as a start.
[16:07] <smoser> this was for someone asking "what else is new in ubuntu server"
[16:07] <smoser> and me wanting a way to somewhat easily answer that.
[16:08] <rbasak> I guess maybe we want to filter that to packages subscribe to in LP by ~ubuntu-server or something.
[16:08] <rbasak> There might be stuff in universe that'd slip through that net though
[16:16] <jamespage> zul, are you intending doing anything with ironic? its currently bit-rotted all release stuck in proposed
[16:17] <zul> jamespage:  not really, i thought someone else was taking care of that
[16:17] <jamespage> zul, who?
[16:17] <zul> jamespage:  adam_g
[16:18] <jamespage> oh
[16:53] <[1]Az> I want to ignore the error I get when I try and run an uninstalled program, but its not on STDERR
[16:53] <[1]Az> is there a way around this?
[16:54] <RoyK> [1]Az: 2>/dev/null
[16:55] <[1]Az> ah
[16:55] <[1]Az> i had a space in there like an idiot
[16:55] <[1]Az> too pro
[16:55] <RoyK> [1]Az: > somewhere or 1> somewhere sends stdout to somewhere, 2> somewhere sends stderr to somewhere
[16:55] <[1]Az> yeah i know :)
[16:55] <RoyK> 2>&1 sends stderr to stdout
[16:55] <[1]Az> but I'd done 2 > /dev/null
[16:55] <RoyK> ah
[16:55] <RoyK> :)
[16:56] <[1]Az> and assumed it was a kernel error
[16:56] <[1]Az> which you cant send to /dev/null?
[16:56] <RoyK> it very rarely is ;)
[16:56] <[1]Az> dd does it i think
[16:56] <[1]Az> oh no it wasnt dd
[16:56] <[1]Az> it was something weird
[16:56] <[1]Az> cant remember now
[16:57] <[1]Az> one of time or sync has unpipable messages
[17:26] <roaksoax> you are reading more than me about it
[17:26] <roaksoax> lol
[17:27] <smb> hallyn, So if you not beating me to it, I would do that forward of the libvirt/apparmor discussion tomorrow
[17:29] <hallyn> smb: sure.  reply go guido now though to tell him you'll do so
[17:30] <smb> ack
[17:36] <hallyn> smb: zul: you'r enot working on any utopic libvirt push right now are you?
[17:36] <zul> hallyn: hell no
[17:36] <smb> nope
[17:37] <hallyn> ok, pushing a quick fix for bug 1375910
[17:50] <TuxBrother> I want logrotate to store the rotated files in a subdirectory
[17:55] <wedgie> Hello. running 12.04 and am noticing this HWE business. Just trying to make sure i'm understanding the ramifications of updating to 12.04.5 HWE: Does this mean that i will be moving from a 3.5 kernel to a 3.13 kernel?
[18:05] <patdk-wk> if you are on anything other than 3.2, yes, you will get 3.13
[18:05] <sarnold> wedgie: correct, this is the package you'd be using https://launchpad.net/ubuntu/+source/linux-lts-trusty
[18:05] <patdk-wk> anything inbetween is *unsupported*
[18:07] <wedgie> ok, thanks
[19:19] <iDealz> anyone have any experience with rebuilding broken RAID arrays?  I had a drive fail completely in an mdadm array 5 and now when I boot my server it boots into initramfs prompt.
[19:20] <iDealz> when I choose the option to load a degraded array it seems to ignore my response and proceed to initramfs prompt anyway
[19:28] <nyktovus> running ubuntu server 12.04. looking for someone to help walk me thru adding a swap file on a system
[19:28] <nyktovus> swapon -s
[19:28] <nyktovus> Filename                                Type            Size    Used    Priority
[19:29] <nyktovus>  Device Boot      Start         End      Blocks   Id  System
[19:29] <nyktovus> /dev/sda1   *          63    36812799    18406368+  83  Linux
[19:29] <nyktovus> /dev/sda2        41082880    80021503    19469312    5  Extended
[19:29] <nyktovus> /dev/sda3        36812800    41082879     2135040   82  Linux swap / Solaris
[19:29] <nyktovus> /dev/sda5        41084928    80019455    19467264   83  Linux
[19:29] <nyktovus> so theres no swap on currently.. yet i have a partition available for it.
[19:30] <nyktovus> all the walkthroughs i've seen dont seem to cover this scenario
[19:30] <lordievader> nyktovus: Could you pastebin your /etc/fstab?
[19:30] <lordievader> !paste| nyktovus
[19:33] <nyktovus> http://paste.ubuntu.com/8468072/
[19:33] <nyktovus> thanx for the  link
[19:38] <lordievader> nyktovus: Your swap partition is not defined in fstab that is why it is not used.
[19:38] <nyktovus> agreed.
[19:39] <nyktovus> so how should i best define this?
[19:40] <hallyn> utlemming: heads-up, https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1373981 sounds like a bug in cloud images (awaiting more info)
[19:40] <lordievader> nyktovus: Add an entry like "/dev/mapper/padme-swap_1 none            swap    sw              0       0"
[19:40] <lordievader> nyktovus: Of course edit to your configuration.
[19:41] <nyktovus> how bout add "
[19:41] <nyktovus> /dev/sda3       swap            swap    defaults        0       0
[19:41] <nyktovus> "
[19:41] <nyktovus> sorry.. there shouldnt have been line breaks in that
[19:41] <lordievader> nyktovus: /dev/sda3       swap            sw    defaults        0       0
[19:42] <lordievader> nyktovus: /dev/sda3 none       swap            sw    defaults        0       0
[19:42] <lordievader> Disregard the previous one ;) none needs to be added.
[19:42] <nyktovus> which one?
[19:44] <nyktovus> ok.. so i added your line.. reboot? or do i need to tell it to swap on or something?
[19:46] <lordievader> nyktovus: Try 'mount -a' or 'swapon', I forgot...
[19:47] <nyktovus> swapon -s is now showing my listing
[19:48] <nyktovus> i dont need the UUID of the partition in fstab?
[19:48] <lordievader> It's preferable but not mandatory.
[19:48] <nyktovus> why preferred?
[19:48] <blaaa> hwat is preferable? the UUID of the partition or the UUID of the filesystem?
[19:48] <lordievader> nyktovus: sdXY namings can change, UUID's should not.
[19:49] <nyktovus> gotcha.
[19:50] <nyktovus> apparantly i've been running this server for years with no swap... been flawless tho
[19:52] <blaaa> nyktovus: should be like that
[19:52] <blaaa> nyktovus: if not get more ram
[19:54] <iDealz> anyone have any experience with rebuilding broken RAID arrays?  I had a drive fail completely in an mdadm array 5 and now when I boot my server it boots into initramfs prompt.
[19:54] <iDealz> anyone have any experience with rebuilding broken RAID arrays?  I had a drive fail completely in an mdadm array 5 and now when I boot my server it boots into initramfs prompt.
[19:54] <iDealz> oops, sorry for the double post
[19:55] <slops17> hey all i have a wierd question. I am running ubuntu server 14.04 and during boot up the resolution is fine once it gets to the login prompt the resolution is just a small box on the screen. any one ever experienced this before
[19:55] <nyktovus> so i shouldnt use a swap?
[19:55] <sarnold> nyktovus: swap is nice but if you have too much swap traffic too often it's a sign you need more memory. :)
[19:56] <blaaa> nyktovus: swap can be useful sometimes, to keep stuff in memory when it's _not_ used
[19:56] <nyktovus> oh i dont have that issue at all.. i'm at 20% usage as we speak..
[19:56] <slops17> its on a dell 1907 monitor
[19:58] <iDealz> slops17: this might be of some help http://askubuntu.com/questions/299975/proper-way-to-change-terminal-resolution-in-ubuntu-server-13-04
[19:58] <slops17> iDealz, i tried that already and didnt work
[20:02] <iDealz> anyone have any experience with rebuilding broken RAID arrays?  I had a drive fail completely in an mdadm array 5 and now when I boot my server it boots into initramfs prompt. I believe I need to boot from a CD to get into root, but dont know where to go from there
[20:15] <slops17> iDealz, i found this and seams to have worked
[20:16] <slops17> http://www.thomas-krenn.com/en/wiki/Fixing_Graphics_Output_Driver_Problems_of_LES_with_newer_Linux_Kernels
[20:20] <patdk-wk> slops17, good thing we don't do graphics in this channel :)
[20:21] <slops17> patdk-wk, i had problem number 3 on that link only the upper left portion of the screen was in use and it was a paint to do anything on the box but it is now fixed
[20:54] <Logos01> Howdy folks. I just updated my LXC binary, and now my apparmor service is dying on me with the below error. Can someone help me understand what "TOK_MODE" means so I can maybe take a stab at remediating it?
[20:54] <Logos01> "AppArmor parser error for /etc/apparmor.d/lxc-containers in /etc/apparmor.d/abstractions/lxc/container-base at line 42: syntax error, unexpected TOK_OPENPAREN, expecting TOK_MODE"
[20:58] <tyhicks> Logos01: Hi - what Ubuntu release are you running?
[20:59] <tyhicks> Logos01: also, can you copy and paste line 42 of /etc/apparmor.d/abstractions/lxc/container-base?
[20:59] <Logos01> 14.04
[21:00] <Logos01> err, 14.04.1 (just updated) -- Whole line is "  unix (receive),"
[21:00] <blaaa> Logos01: I have run into issues with apparmor scriptsa few months ago, don't know if they have been fixed, have stopped trying
[21:00] <blaaa> Logos01: your issue looks different though
[21:01] <Logos01> Mine is specific to LXC.
[21:01] <Logos01> I have the lxc-daily ppa enabled (necessary because I'm using ZFS as backing store)
[21:01] <tyhicks> Logos01: what is the output from `apt-cache policy lxc apparmor | grep Installed`?
[21:02] <Logos01> Installed: 1.1.0~alpha1+master~20140930-0358-0ubuntu1~trusty ; Installed: 2.8.95~2430-0ubuntu5
[21:03] <Logos01> If I only knew what "TOK_MODE" meant I could maybe puzzle out what's going on.
[21:03] <tyhicks> Logos01: the problem stems from having a brand new version of lxc and an slightly old version of apparmor
[21:03] <patdk-wk> heh? it makes perfect sense
[21:03] <tyhicks> Logos01: ignore the TOK_MODE error message - it is just trying to tell you that the apparmor_parser program can't compile your policy
[21:03] <Logos01> I get that TOK_OPENPAREN means it's seeing the open parenthesis in "unix (receive)", when it's expecting some other character.
[21:04] <patdk-wk> unexpected token open parentheses, expecting token mode
[21:04] <Logos01> tyhicks: Okay, then how do I resolve this?
[21:04] <Logos01> (And how do I rule out a typo making it into the daily PPA?)
[21:05] <tyhicks> Logos01: you can do one of two things: 1) comment out, with '#' characters, the lines that start with "unix" or 2) install the apparmor package from Utopic
[21:05] <tyhicks> Logos01: I'd go with option #1
[21:05] <Logos01> It seems to me that neither of these are optimal.
[21:05] <Logos01> What *does* "TOK_MODE" mean anyhow?
[21:05] <patdk-wk> mode :)
[21:05] <Logos01> patdk-wk: heh.
[21:05] <patdk-wk> read, write, create, ....
[21:06] <tyhicks> Logos01: the apparmor_parser program in 14.04 doesn't know about "unix" rules
[21:06] <tyhicks> Logos01: we just recently landed support for unix rules in Utopic
[21:07] <tyhicks> Logos01: unfortunately, those are the only two possible workarounds available at the moment
[21:07] <Logos01> Hrm...
[21:08] <patdk-wk> rm / being one?
[21:08] <Logos01> Okay, so going into backup of the etc dir I see the old file did not in fact have the unix lines.
[21:08] <Logos01> So I'm not losing anything by commenting them out I suppose.
[21:09] <tyhicks> Logos01: just a sec
[21:09] <patdk-wk> you will be
[21:09] <patdk-wk> you need something to give you that permission
[21:09] <patdk-wk> so what is missing in the new file? that the old one had
[21:09] <tyhicks> Logos01: looks like the lxc guys have a workaround for this in the lxc packaging
[21:09] <tyhicks> Logos01: I'm not sure why it isn't working for you
[21:09] <tyhicks> Logos01: what does `grep DISTRIB_RELEASE /etc/lsb-release | cut -d= -f2` output on your machine?
[21:10] <Logos01> 14.04
[21:11] <tyhicks> maybe they use different packaging for their daily ppa
[21:11]  * tyhicks goes to look for it
[21:12] <Logos01> I've had good history with the daily ppa, kinda surprised by this.
[21:13] <Logos01> But ... it's rare that *nothing* goes wrong.
[21:13] <Logos01> ( And at least this isn't bash related ... <_< )
[21:13] <patdk-wk> oh ya, I haven't had time to check my bash hit counter today yet
[21:15] <Logos01> patdk-wk: Just be thankful you don't have to deal with explaining to infosec people that "no, it's not possible to patch the system-provided bash shell on an OS version that went End of Life 12 years ago."
[21:17] <patdk-wk> why?
[21:17] <patdk-wk> I was in charge of patching our systems from 10years ago
[21:17] <Logos01> Re-read that.
[21:18] <patdk-wk> patching bash 3.2
[21:18] <Logos01> 2.05
[21:18] <patdk-wk> ah, I didn't have to go that far back
[21:18] <tyhicks> Logos01: upgrade to lxc 1.1.0~alpha1+master~20140930-1924-0ubuntu1~trusty and everything should work without any manual changes
[21:18] <Logos01> tyhicks: I did just perform upgrade about half an hour ago
[21:18] <Logos01> But there's an LXC package available. Interesting.
[21:18] <tyhicks> Logos01: do another
[21:19] <tyhicks> Logos01: it'll fix it
[21:19] <tyhicks> Logos01: they added in the change that removes the unix rules if you're running 14.04 or older in the latest version
[21:20] <Logos01> tyhicks: It did not fix it.
[21:22] <tyhicks> Logos01: same error?
[21:22] <Logos01> Yes
[21:22] <Logos01> It left my modified file in place.
[21:22] <Logos01> When I uncommented the unix lines it errored again
[21:23] <tyhicks> Logos01: I thought I stopped you before you edited it
[21:23] <Logos01> Nope.
[21:26] <tyhicks> Logos01: well, you now know the fix
[21:27] <tyhicks> Logos01: sorry that you upgraded in the small window where the install script was missing the logic to comment out the unix rule
[21:27] <Logos01> tyhicks: I'm not sure I do know the fix.
[21:27] <Logos01> I tried uninstalling and reinstalling lxc altogether, both with and without the container-base file present, and it's not doing any good.
[21:30] <Logos01> Well this is interesting. I decompressed the latest lxc *.deb from /var/cache/apt/archive and compared it's container-base to what I had on-hand. http://paste.ubuntu.com/8468711/
[21:30] <tyhicks> Logos01: I think `sudo apt-get -o Dpkg::Options::="--force-confask" install --reinstall lxc` should do the trick
[21:31] <Logos01> I then *copied* the deb's container-base file in place and restarted apparmor and it did not balk at the syntax.
[21:32] <tyhicks> good to hear
[21:33] <Logos01> Odd behavior is odd, to say the least.
[21:39] <Logos01> tyhicks: Thanks for your help. Much appreciated.
[21:40] <tyhicks> no problem!
[21:49] <iDealz>     hhhhhju[p5+]\7
[21:49] <iDealz> 1
[22:25] <adam_g> zul, jamespage https://code.launchpad.net/~gandelman-a/ubuntu/utopic/ironic/juno/+merge/236635 <- refreshed the ironic packaging for juno. RC1 isn't released yet but it shouldnt require anythign new. python-ironicclient could use an upload, and eventlet could use those patches for bug 1321787
[22:29] <mgw> I've got an install that's failing on setting up grub
[22:29] <mgw> I dropped into a shell
[22:29] <Logos01> mgw: What device are you using?
[22:29] <mgw> and there's no device.map
[22:29] <mgw> I've tried hd0 (default) and hd1
[22:29] <mgw> once I drop into a shell I can run grub-mkdevicemap
[22:29] <mgw> and then grub-install works
[22:30] <Logos01> device.map shouldn't be necessary.
[22:30] <mgw> Might it be mapped to a different name?
[22:30] <mgw> how can I print what devices grub knows about
[22:30] <Logos01> Something seems odd that this is necessary at all.
[22:31] <Logos01> What would be a brief description of your hardware setup? Anything unusual? VM? Physical? Installing to LVM?
[22:33] <mgw> The unusual thing is that hda is a 3TB XFS volume and hdb has / on the first partition
[22:33] <mgw> It's physical
[22:34] <mgw> I can't set the 3TB as bootable
[22:34] <mgw> hdb0 is marked as bootable
[22:34] <Logos01> What version of Ubuntu are you trying to use?
[22:35] <mgw> 14.04
[22:37] <Logos01> mgw: If I understand correctly, your goal is to boot off of an XFS volume?
[22:37] <mgw> no
[22:37] <mgw> Logos01: it's to boot off the ext4
[22:37] <mgw> on the second drive
[22:37] <mgw> first partition of second drive is an ext4 partition
[22:38] <Logos01> Physical partition?
[22:38] <mgw> I got grub to install once, by dropping into a shell when it failed
[22:38] <mgw> and running mkdevicemap
[22:38] <mgw> and install hd1
[22:38] <mgw> Yes, the first partition is physical
[22:38] <mgw> there are some logical volumes there too
[22:39] <mgw> after the first
[22:40] <Logos01> logical partitions, not LVM2 logical volumes
[22:40] <Logos01> ?
[22:40] <mgw> right
[22:40] <mgw> sorry
[22:41] <Logos01> mgw: Just for confirmation, are you able to remove the XFS drive from the system?
[22:41] <mgw> partitions
[22:41] <mgw> no LVM involved
[22:41] <mgw> physicall remove it?
[22:41] <Logos01> (Re-attempt installation w/o XFS present is the goal, to isolate behavior)
[22:41] <mgw> I cannot physically remove it
[22:41] <mgw> this is PXE booting
[22:41] <mgw> remotely
[22:41] <mgw> I'm on kvm
[22:41] <mgw> I can reformat it as ext4 though
[22:42] <mgw> but I cannot make the 3TB bootable even as ext4
[22:42] <mgw> in the paritioning manager
[22:42] <Logos01> "the partitioning manager" being ... ?
[22:42] <mgw> in the installer
[22:46] <mgw> Logos01: should I try again having formatted the 3TB as ext4?
[22:47] <mgw> And leaving "d-i grub-installer/bootdev string (hd1)" in the preseed?
[22:51] <mgw> Logos01: would the devices always be hd0, hd1, etc?
[22:51] <Logos01> mgw: Just a sec. I'll admit that I'm far better w/ kickstarts than w/ preseeds.
[22:52] <mgw> or maybe they're sda1 ro something?
[22:52] <mgw> before i run mkdevicemap
[22:52] <mgw> to reiterate, before running mkdevicemap, grub-install complains that hd1 (or hd0 for that matter) does not exist
[22:53] <mgw> after I run mkdevicemap hd0 and hd1 are properly mapped
[22:53] <mgw> and grub-install works
[22:56] <mgw> Logos01: I think i got it
[22:56] <mgw> I can run "grub-install /dev/sdb" from busybox
[22:56] <mgw> and it works
[22:56] <Logos01> https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1012629
[22:57] <mgw> It's not ignoring it
[22:57] <mgw> in my case
[22:57] <Logos01> Right, but read that ticket history.
[22:57] <mgw> It complains the device in the preseed does not exist
[22:57] <Logos01> What you describe is very similar.
[22:58] <mgw> reading
[22:58] <mgw> hmm, I think the installer i'm booting into is newer than the release
[22:58] <mgw> but perhaps not
[22:59] <mgw> I"m going to try setting bootdev to /dev/sdb though and run through an install
[22:59] <mgw> if that doesn't work, I'll ensure I have the latest install image
[23:00] <mgw> Logos01: thanks for the help!
[23:00] <Logos01> mgw: You tried 'd-i grub-installer/bootdev string /dev/sdb' ?
[23:00] <mgw> no, i'm about to
[23:01] <mgw> I was using hd1
[23:01] <mgw> previously
[23:01] <mgw> (hd1)
[23:01] <Logos01> I'd suspect that by using the string you'd be able to avoid the need for the mkdevicemap.
[23:04] <mgw> yeah, that's what my tests in busybox indicate
[23:04] <mgw> since grub-install /dev/sdb worked
[23:04] <mgw> and grub-install (hd1) did not
[23:05]  * Logos01 crosses crossable phalanges
[23:05] <Logos01> (that's fingers/toes)
[23:19] <mgw> will know in a few minutes