[05:46] <foo> I'm looking at how many workers to set on an app. It says this: Rule of thumb : (#CPU * 2) + 1 - how do I know how many know of #CPU's I have? What command would show me that? This instance is running in aws
[06:18] <lordievader> Good morning
[06:19] <lordievader> foo: `lscpu` shows the cpu count.
[06:19] <foo> lordievader: thank you
[12:35] <coreycb> jamespage: i'm going to promote qemu to pike-updates for LP: 1779162. only been in proposed for a day but it's tested and causing data corruption on migration for s390 guests.
[14:01] <jamespage> coreycb: +1 sounds like a priority
[15:42] <Ussat> Sooo....getting headache here or hurting the wall hitting it with my head...have a log check issue on Ubuntu 18.04 LTS, sure its a user issue :) but I have no idea what I crewed up, here is a pastbin with errors at bottom: https://pastebin.com/dRLqUR45
[15:42] <Ussat> command run was"  su -s /bin/bash -c "/usr/sbin/logcheck -d" logcheck
[15:43] <Ussat> the -d is for debug output
[16:28] <Ussat> hmm no one ?
[16:32] <Epx998> Where can I get a PPC iso for 16.04.3?
[16:34] <Epx998> nm found it
[16:35] <tomreyn> 16.04.4 is current, though
[16:35] <Epx998> yeah this is a corner case where I need .3
[16:37] <njbair> any known issues with conjure-up on 18.04? I've tried and failed several times to set up a novalxd server on two different machines over the last couple days.
[16:41] <whislock> Epx998: Do you -actually- need .3?
[16:50] <nacc> Epx998: rather curious why you need .3?
[16:51] <whislock> Any time I see that, it's some variant of "software maker X says I need this exact version."
[16:51] <whislock> Which is 99.9% of the time not true.
[16:51] <nacc> right, and .3 is not really a thing, it's *maybe* a HWE level
[16:52] <nacc> inasmuch as .3 was just a time when an iso was spun up (iirc)
[16:52] <whislock> Exactly.
[16:52] <nacc> so perhaps they meant they wanted to test that kernel :)
[16:53]  * Ussat slams head into desk
[16:53] <whislock> That seems painful.
[16:54] <Ussat> yup.....so is this issue
[16:54] <nacc> Ussat: did you see if /usr/sbin/logtail2 on that file works manually?
[16:54] <Ussat> no did not try that
[16:55] <Ussat> bah it is useing logtail2
[16:55] <Ussat> LOGTAIL="/usr/sbin/logtail2"
[16:55] <Epx998> NACC: It's for an IBM P9 server with a specific CPU, current stuff doesnt work on it - dev wants specfically some 16.04.3 PPCEL proposed that has some nvidia drivers in it
[16:56] <Epx998> something to that effect, the plea for help from my workmate isnt very clear
[16:56] <nacc> Epx998: oh ppc64el not ppc
[16:56] <nacc> Epx998: that's confusing "ppc64el proposed"?
[16:57] <Epx998> yeah sorry - im being told the ibm p9 with this 2.1 cpu version is locked into this release and a kernel on it
[16:57] <whislock> Epx998: No, it's locked into that kernel.
[16:57] <Epx998> the info from my workmate doesnt feel complete on what hes looking for
[16:57] <nacc> none of that seems right to me
[16:57] <whislock> Epx998: There's no such thing as a "18.04.3" release.
[16:57] <Ussat> manually, it runs fine
[16:57] <whislock> And I am highly suspect of the notion that the .3 kernel works, and the current one doesn't.
[16:57] <Epx998> I am talking 16.04.3
[16:58] <whislock> Epx998: Same idea applies, replace 18 with 16.
[16:58] <Epx998> ppc64el - thats whjat i told him, there was no prposed for that
[16:58] <whislock> There's no such thing as "16.04.3".
[16:58] <whislock> There is 16.04.
[16:58] <nacc> Epx998: so they need the 4.10 kernel?
[16:59] <nacc> Epx998: which didn't get patched for meltdown/spectre??
[16:59] <Ussat> as an IBM shop P9's are not kernel locked to ANYTHING
[16:59] <nacc> dpb1: --^ would you know?
[17:00] <whislock> Epx998: Okay, so there's a lot of experience here saying that your requirement isn't really needed.
[17:01] <Ussat> I run a fairly large P9 install base as well as X86 linux and no
[17:01] <dpb1> no, would need a bug link.
[17:01] <dpb1> hi nacc
[17:01] <nacc> dpb1: heya :)
[17:01] <nacc> dpb1: figured you would be able to more definitively tell us re: p9 support, etc.
[17:02] <dpb1> p9 is supported for sure, if there is an issue, it should be filed as a bug
[17:02] <nacc> dpb1: ack, thanks
[17:29] <Ussat> We have it on 4 LPARS here
[17:52] <pankaj> I am trying to install virtual box guest additions on my virtual machine. I clicked on device tab and downloaded the package but it does not work. Please help me.
[18:33] <pankaj> I have successfully installed virtual box guest additions now and checked with lsmod but it is still not working.
[18:44] <lopta> Is it difficult to install Ubuntu Server onto an md mirror?
[18:49] <pankaj> lopta: What?
[18:50] <nacc> lopta: md is a software construct
[18:50] <lopta> pankaj: Software RAID-1
[18:50] <nacc> lopta: are you asking if you can setup swraid during install?
[18:50] <lopta> nacc: Yes, probably ;-)
[18:51] <pankaj> lopta: I was following a blog on 'techrepublic.com' with topic 'how to install virtualbox guest additions on ubuntu server'. It was successfull till the end and my ubuntu server told me to just restart and everything will be fine but it did not happen. I cannot enjoy full screen.
[18:51] <pankaj> lopta: I am not asking about software RAID now.
[18:52] <lopta> pankaj: I am though.
[18:52] <nacc> lopta: ok, afaik, yes
[18:53] <nacc> lopta: use the old installer not the new one, iirc
[18:53] <whislock> lopta: Requires the use of the "legacy" installer, I believe.
[18:53] <lopta> Thanks whislock
[18:54] <lopta> (and nacc)
[23:38] <runelind_q> how can I disable the HWE kernel and go back to stock 16.04 kernel?
[23:40] <sarnold> runelind_q: there's no explicit instructions I nkow of .. ttps://wiki.ubuntu.com/Kernel/RollingLTSEnablementStack
[23:41] <sarnold> runelind_q: I think from what I can see on that page I'd try "apt-get install linux-generic linux-generic-hwe-16.04-"
[23:42] <runelind_q> well I had the option in my bootloader for just booting into the 4.4 kernel again, so I'm running that kernel atm.  Should I just uninstall the linux-generic-hwe-16.04?
[23:43] <sarnold> aha, yeah, that sounds good
[23:46] <runelind_q> ok, trying the reboot.