[00:00] <JanC> pstate is an Intel alternative for cpufreq, but it's possible that it doesn't work well with all CPUs, I don't know...
[00:01] <JanC> in theory it shouldn't affect # of CPUs though
[00:01] <JanC> and the two nomdm* are about RAID
[00:03] <Blueking> I have to ask those guys at server shop then
[00:04] <Blueking> or test box with another OS
[00:04] <sarnold> I suspect they will not be able to help you :)
[00:04] <sarnold> other OS seems like a reasonable enough test, but another *cpu* frmo a different supplier might be more useful still
[00:04] <Blueking> I have 5 year warranty on such hardware...
[00:05] <Blueking> might be faulty cpu microcode too ?
[00:06] <Blueking> got error on it last time I ran apt upgrade
[00:08] <sarnold> well at least that one might be easy to nail down, uninstall the intel-microcode package, rebuild initrd, reboot, re-test, and check the microcode date in dmesg..
[00:08] <Blueking> E: intel-microcode: failed to create or prepend the early initramfs to the initramfs
[00:08] <sarnold> it seems insanely unlikely to me though
[00:09] <sarnold> we'll publish a new microcode in a few days for the spectre v4, maybe your cpu is covered in that list...
[00:09] <Blueking>  -> /usr/sbin/iucode_tool: microcode bundle /lib/firmware/intel-ucode/list: unknown microcode format
[00:10] <Blueking> downloaded from intel: microcode-20180425.tgz
[00:21] <JanC> Blueking: my guess would be that it's actually a BIOS/UEFI firmware bug (possibly in ACPI)
[00:22] <sarnold> hmmmm.. I wonder if the fwts package could help?
[00:24] <JanC> I wonder if there is a kernel parameter to ignore ACPI's core count (or whatever makes this wrong)
[05:12] <cpaelzer> good morning
[05:57] <lordievader> Good morning
[08:54] <xnox> sarnold, I do not have access to Better ARK but people on #clearlinux irc channel do
[08:54] <xnox> sarnold, lack of CPUs may indicate custom microcode that disables/enables them; or that cpus were fused away, meaning there is a crippled SKU out there aka a cheap edition.
[08:55] <xnox> sarnold, many of Intel CPUs are the same, and artificially clocked down / cores disabled. And one can sometimes pay to unlock higher clock speeds & cores.
[09:22] <rbasak> ahasenack: I'd say the reporter has modified his system from defaults so much in bug 1772337 that it's likely to be a configuration problem than a bug in Ubuntu. If he thinks it's a bug he should at least present an explanation as to why. So Incomplete.
[13:15] <samba35> can some one please tell on 18.04 i have process with sha256sum and it keep running for long time and it kepp cpu busy ,how do i find what it is doing and trace it ,and it keep changeing pid even kill within second it start new same process ,is it normal ?
[13:17] <Ool> samba35: try ps with the f option to see hierarchy
[13:17] <samba35> ok ,i will try it when this start
[13:17] <Ool> did you put some security stuff who want to have hash from each file ?
[13:18] <samba35> how do i find which package hold this file  /usr/bin/sha256sum
[13:18] <Ool> apt search sha256sum  ?
[13:19] <ivoks> dpkg -S /usr/bin/sha256sum
[13:19] <ahasenack> hm, mod-wsgi dep8 tests passed locally
[13:19]  * ahasenack clicks the retry button in excuses
[13:19] <samba35> ps auxf should be ok ?
[13:19] <Ool> exactly how I use ps :)
[13:20] <Ool> but someones prefer ps -edf
[13:20] <samba35> thanks Ool and ivoks
[13:21] <samba35> ok will that too :) but thanks for give idea get good idea
[13:24] <Neo4> my shell script functionality, what would be good else to add there?
[13:24] <Neo4> https://paste.ubuntu.com/p/ChMScTw5sp/
[13:24] <Neo4> backup, generation and set up sshkey, set up certificates for virtualdomains
[13:25] <Neo4> I think about create a fullfladgit control panel :)
[13:52] <olivierb-> Hello everyone, basic question but can not find answer easily on my side. Let's assume I have a dhcp server on my network which assigns IP AND hostname. When my machine boots, it gets the IP but hostname command and /etc/hostname file contains ubuntu. Machine is ubuntu xenial 64bit with minimal set of packages. Furthermore my seconday IP address is on another network served by another dhcp server but this one does not provide host
[13:52] <olivierb->  names in DHCP offers. How does all this works and what should I add/change to get my hostname properly set ?
[13:54] <ahasenack> I don't know
[14:02] <rbasak> olivierb-: if you're using ifupdown on Xenial, then it's done via dhclient.conf and dhclient-script
[14:02] <rbasak> I'm not sure what the default is or if you need to change it.
[14:03] <rbasak> olivierb-: it's probably not a good idea to have a server's hostname regularly change though. Unless it's an appliance, I'd lock it in statically on the client side anyway.
[14:03] <olivierb-> rbasak I managed to get it working once using service networking restart, but it was only once
[14:04] <olivierb-> name should not change as long as the lease remains same
[14:18] <ahasenack> there is this fence-agents package in the ubuntu archive, that ships a lot of scripts of the type fence_*
[14:18] <ahasenack> there is one of those scripts that doesn't work out of the box because of missing python dependencies
[14:18] <ahasenack> these missing deps are declared as "Suggests" in the d/control file
[14:19] <ahasenack> that seems wrong to me. If the script doesn't even run, surely those deps should be in Depends?
[14:19] <ahasenack> bug is https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1772096
[14:19] <ahasenack> check comment #2
[14:19] <ahasenack> and #4
[14:19] <ahasenack> it's a sync from debian, though
[14:24] <rbasak> ahasenack: depends on the nature of it. AIUI, if it's not the normal use case of a package, it doesn't hae to be a Depends.
[14:24] <ahasenack> it's just one of many fence agents the package ships
[14:24] <ahasenack> take a look at apt-cache show fence-agents
[14:25] <rbasak> "The Depends field should be used if the depended-on package is required for the depending package to provide a significant amount of functionality."
[14:25] <rbasak> "The Recommends field should list packages that would be found together with this one in all but unusual installations."
[14:26] <rbasak> "[Suggests] is used to declare that one package may be more useful with one or more others. Using this field tells the packaging system and the user that the listed packages are related to this one and can perhaps enhance its usefulness, but that installing this one without them is perfectly reasonable."
[14:26] <rbasak> From https://www.debian.org/doc/debian-policy/#binary-dependencies-depends-recommends-suggests-enhances-pre-depends
[14:27] <ahasenack> it backtraces
[14:28] <rbasak> For a package that is essentially a collection of a bunch of different use cases, it's difficult.
[14:28] <rbasak> People might not want it to depend on every single possible use case dependency package.
[14:28] <ahasenack> they should have their own package each then, if it pulls in more deps than the maintainer is willing to accept
[14:28] <rbasak> But by not doing that the user has to know what extra to pull in
[14:29] <ahasenack> the user will see a python backtrace
[14:29] <rbasak> Yeah that's not good. It's not necessarily wrong to not have a dependency, but it's reasonable to expect a more helpful error message.
[14:29] <rbasak> I would leave it to whatever the Debian maintainer thinks is appropriate
[14:30] <ahasenack> there's a changelog entry even, mentioning the two deps being added as build-depends, and suggests, at the same time
[14:30] <ahasenack>   * Add python-requests and time to Build-Depends, add python-requests and
[14:30] <ahasenack>     python-suds to Suggests (needed by fence_vmware_soap).
[14:30] <rbasak> That sounds reasonable
[14:32] <ahasenack> I fail to see how
[14:32] <ahasenack> the package is shipping a binary, like many others it already has, that does not work because of a missing dependency
[14:32] <ahasenack> it crashes
[14:32] <ahasenack> apport will raise its head
[14:33] <rbasak> It can be fixed by adjusting the apport hook or adjusting the error message when the "dependency" isn't found.
[14:34] <rbasak> It doesn't necessarily have to be declared as a Depends unless it is needed to provide a significant amount of functionality for the package.
[14:35] <rbasak> The decision is left to the maintainers otherwise, and it seems that they selected Suggests deliberately.
[15:21] <Blueking> are there any dos tools that can post intel cpu, number of cores and so ?
[15:27] <compdoc> you mean command line
[15:28] <compdoc> https://www.tecmint.com/check-linux-cpu-information/
[16:06] <RoyK> Blueking: lscpu as before
[16:33] <ahasenack> rbasak: success! "   * Move python3-requests and python3-suds to Depends (Closes: #899381)"
[17:07] <samba35> why  usr/bin/sha256sum /etc/aide/aide.conf.d/31_aide_rngd keep cpu usage very hight
[17:08] <samba35> any idea why sha256sum is used for X11 relates file ?
[17:08] <teward> because the CPU has to calculate the hash sum of a given file
[17:08] <teward> why it's doing that I don't know, but sha256sum is not a 'light' function in terms of resources
[17:08] <teward> (any hashsum function will eat CPU)
[17:08] <teward> (to varying degrees depending on the filesize of the file being hashsummed, and the hashing algo)
[17:09] <samba35> yes but what kind of with X11
[17:09] <teward> I... have no idea what you just tried to ask.
[17:09] <teward> which means either a language barrier, or your question was malformed./
[17:10] <teward> samba35: as I said, I can't answer *why* it's used for the X11 relates file, but I can answer the "keep cpu usage very high" part because of the nature of what sha256sum does
[17:11] <teward> i once sha256summed a 240GB disk image file once.  Took full CPU on the 16 cores of that workstation, for a good bit of time.
[17:12] <teward> (100% usage, on pretty much all cores, until it finished the calculation of the sha256sum)
[17:12] <samba35> ok ,got it it seems im-config
[17:12] <samba35> remove this page and let see what happen
[17:13] <ahasenack> rbasak: little help: is this good? https://pastebin.ubuntu.com/p/ZPCZcYtykt/
[17:17] <samba35> /etc/apache2/mods-available/proxy_http2.load now sha256sum is using this file
[17:17] <samba35> so its not static to one file
[17:17] <samba35> i am not trying encrpth /decrypth any file
[17:18] <teward> it's not encryption/decryption
[17:18] <teward> it's hashsumming.  *something* on your system is trying to get hash sums for various files
[17:18] <ahasenack> samba35: you seem to be using aide. That will hash all files in your system
[17:18] <teward> ^ that
[17:19] <samba35> how to i fix this ?
[17:19] <ahasenack> remove aide
[17:19] <ahasenack> or figure out why you installed it
[17:19] <ahasenack> unless this is not your system :)
[17:20] <samba35> is it relaed to check-security ?
[17:21] <ahasenack> don't know what that is
[17:21] <ahasenack> there is no such file or package in ubuntu bionic
[17:21] <samba35> brb will reboot system ,its keeping cpu very hight and its too hot already
[17:22] <ahasenack> rebooting won't fix it
[17:22] <ahasenack> it's likely a cron job, it will just run again
[17:22] <Blueking> hmm how to open this ? intel-microcode_3.20180425.1~ubuntu0.16.04.1.tar.xz
[17:22] <Blueking> tar won't work ?
[17:23] <ahasenack> tar xJf <file>
[17:23] <ahasenack> J is for xz compression
[17:27] <Blueking> hmm how do I implement microcode ?
[17:27] <Blueking> none help file inside this package ?
[17:28] <ahasenack> I don't know, but there is a package in ubuntu that installs new microcode, you could check how it does it
[17:29] <Blueking> are there search function inside apt ?
[17:29] <ahasenack> apt-cache search for packages
[17:29] <ahasenack> apt-file search for files in packages
[17:32] <sdeziel> Blueking: installing the intel-microcode package should be all you need
[17:33] <Blueking> sdeziel how ?
[17:33] <sdeziel> Blueking: on your next reboot, a fresh microcode will be loaded if one is available
[18:25] <sarnold> xnox: oh thanks for the #clearlinux tip -- I knew intel binned CPUs pretty heavily but I thought they were *really* diligent about making sure every unique combination had a descriptive name..
[18:25] <xnox> HAHAHHAHAHAH
[19:06] <sarnold> xnox: well not poor Blueking is likely to return his cpu because it's not what he thought he bought..
[19:08] <lyn||ian> sarnold, that is what ark.intel.com is for as there are too many to memorize
[19:08] <sarnold> lyn||ian: ARK says Blueking's processor should have FOUR cores but it only has TWO cores.
[19:12] <lyn||ian> wow'
[19:13] <sarnold> yeah, that's what has me so surprised :)
[19:14] <sarnold> I've spent so many hours reading ARK details on processors I've thought about buying..
[19:16] <xnox> sarnold, well.... what does the box say? or the markings on the cpu itself? it might be sub-sku with disabled cores.
[19:16] <sarnold> Blueking: hey :) do you still have the box? :D
[19:42] <Blueking> sarnold it's a few months away from beeing used for 5 year :P
[19:43] <sarnold> Blueking: so.. the box is long since discarded? heh
[19:43] <Blueking> bios says 4 core
[19:45] <Blueking> gotta find out how to remove current microcode and force new one in
[19:48] <sarnold> apt-get install intel-microcode; make sure the initrd is rebuild; then reboot
[19:48] <sdeziel> Blueking: again, this should all be automatically done on reboot
[19:48] <sdeziel> Blueking: journalctl -k | grep -i microcode
[19:48] <sdeziel> but IIRC, this will only load a microcode on CPUs visible by the kernel...
[19:49] <Blueking> last line didn't post anything
[19:52] <Blueking> how to remove current microcode.. apt-get install intel-microcode  says 'intel-microcode defined manual installation'
[19:55] <nacc> Blueking: you mean remove the intel-microcode package? `sudo apt-get remove intel-microcode`
[19:56] <Blueking> ok used apt-get remove intel-microcode  ->  then apt-get install intel-microcode -> reply from process  "/usr/sbin/iucode_tool: microcode bundle /lib/firmware/intel-ucode/list: unknown microcode format" and "E: intel-microcode: failed to create or prepend the early initramfs to the initramfs"
[19:58] <Blueking> maybe this error  make it fail update intel-microcode at next boot ?
[19:58] <sdeziel> Blueking: most probably
[19:58] <nacc> uh, don't think there should be a /lib/firmware/intel-ucode/list file
[19:58] <nacc> and yes, if the package failed to install, then it ... didn't install
[19:59] <sdeziel> Blueking: you asked how to untar the intel-microcode tarball earlier, have you extracted that tarball in that dir?
[19:59] <Blueking> no
[19:59] <sdeziel> OK good
[20:00] <nacc> just did a quick chdist check and yea, there shouldn't be a list file
[20:00] <nacc> (at least, afaict)
[20:02] <sdeziel> I can confirm this /list file isn't here on my machines
[20:02] <Blueking> maybe this was bad thing.. what I did 2 weeks ago ? mv intel-ucode /lib/firmware
[20:02] <Blueking> tar -xvzf microcode-20180425.tgz
[20:04] <Blueking> but only had two core before that
[20:04] <sdeziel> is that the tarball provided by Intel?
[20:04] <Blueking> yes
[20:05] <sdeziel> I'd try to do the following: "apt-get purge intel-microcode" then "rm -rf /lib/firmware/intel-ucode" and finally "apt-get install intel-microcode"
[20:06] <Blueking> ok
[20:07] <Blueking> ok rebooting now
[20:10] <Blueking> still 2 core
[20:33] <sdeziel> Blueking: did you have the "unknown microcode format" error prior to the reboot?
[20:34] <sdeziel> if no, I'd be curious to see the "journalctl -k| grep -i microcode"
[21:08] <Blueking> sdeziel: http://paste.ubuntu.com/p/9JmBr77pvZ/
[21:13] <Blueking> sdeziel: interesting here http://paste.ubuntu.com/p/pSs9NcXDv3/
[21:14] <sdeziel> enabledcores=1 looks suspicious
[21:14] <Blueking> only one enabled core..
[21:14] <sdeziel> you have HyperThreading right?
[21:14] <Blueking> yes
[21:17] <sdeziel> OK so that explains the first paste
[21:19] <Blueking> http://paste.ubuntu.com/p/M7nQ3bjjG5/
[21:21] <Blueking> so where do ubuntu have these control sets ?
[21:22] <Blueking> grub/grub2 ?
[21:24] <Blueking> sdeziel ?
[21:25] <sdeziel> Blueking: cat /proc/cmdline
[21:25] <Blueking> sdeziel: http://paste.ubuntu.com/p/t6v8mqtqX2/
[21:46] <sdeziel> Blueking: so there is no kernel arg that artificially limits the number of cores visible
[21:54] <Blueking> there must be sumthin ?
[21:54] <arooni> anyway to check to make sure log rotation is working across web logs/etc.. ? or is this just on by default (16.04 server)
[21:54] <Blueking> hello Janc
[21:54] <Blueking> hello JanC
[21:55] <Blueking> hello JanC_
[21:56] <Blueking> JanC  you had a peek at mine problem ?
[21:57] <sarnold> Blueking: has this cpu always had two cores? :)
[21:57] <Blueking> that I am not sure about
[21:58] <sdeziel> Blueking: yeah, I'd grep old boot logs for nr_cpu_ids
[21:58] <Blueking> sarnold  seems only one core  are enabled   with HT it's '2' core
[21:58] <Blueking> cd ..
[22:01] <JanC> Blueking: currently my guess would be it's an ACPI problem?
[22:02] <Blueking> http://paste.ubuntu.com/p/THJS4XjWH3/
[22:03] <Blueking> not sure
[22:03] <Blueking> should I goin bios and change ?
[22:04] <Blueking> what are RCU ?
[22:04] <Blueking> RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=2.
[22:05] <sarnold> RCU is a go-fast lockless datastructure design scheme
[22:05] <sarnold> it allows working with stale data in a predictable way
[22:06] <JanC> and it needs to know how many CPUs you actually have, I suppose
[22:07] <sarnold> right
[22:08] <Blueking> hmm I need to uncompress log files ?
[22:08] <Blueking> to search through old log files ?
[22:10] <sdeziel> Blueking: zgrep should be able to look into .gz log files
[22:10] <sdeziel> zgrep -F nr_cpu_ids /var/log/syslog*
[22:11] <sarnold> vim also has some autorules to expand compressed files in place
[22:12] <Blueking> kern log files goes back only 3 days..
[22:14] <sdeziel> Blueking: syslog, not kern.log
[22:14] <Blueking> nothing there
[22:15] <sdeziel> do you ship logs to an aggregator/concentrator by any chance?
[22:17] <sdeziel> Blueking: I'm done for the day but good luck
[22:20] <sarnold> gnight sdeziel ;)
[22:20] <sdeziel> thx
[23:05] <Blueking> still a bug ? -> https://ubuntuforums.org/showthread.php?t=2187699&page=2
[23:08] <tomreyn> Blueking: it's either still a *BIOS* bug (and will then surely remain that as BIOSes traditionally have a long lifetime) or it remains to be an ubuntu bug which, at least according to this forum thread, was not yet reported (and would thus not get fixed unless identified AND reported independently).
[23:09] <Blueking> okey
[23:12] <Blueking> tomreyn: configuration: cores=4 enabledcores=1 threads=8  with command lshw -class cpu
[23:13] <tomreyn> Blueking: so?
[23:13] <Blueking> just wonder  cores=4  enabled cores=1  but  the number of threads=8   are it 8 enabled threads ?  thus it indicates 4 enabled cores..
[23:14] <Blueking> just wonder if ubuntu read bios wrong  where bios say 1 core someplace it means 1 physical cpu ?
[23:15] <Blueking> it's supermicro mobo
[23:15] <nacc> Blueking: i don't think the threads relates to how many threads are enabled
[23:15] <nacc> Blueking: not sure, though, i'd need to read the source to be sure
[23:16] <nacc> Blueking: what does `grep -c '^processor' /proc/cpuinfo` say?
[23:16]  * tomreyn would also *assume* it refers to capabilities, not current configuration
[23:16] <Blueking> inside bios  there intel service thing wich tells status of mobo/cpu   disabled cores = 0
[23:17] <nacc> tomreyn: yeah, i assume givne the 'enabled' vs. no-prefix for cores, they are distinct for threads too (but possibly not emitting)
[23:17] <Blueking> nacc nothing.. wrong typo ?
[23:18] <Blueking> 2
[23:18] <nacc> Blueking: ok, so you have 1 core enabled with HT on
[23:18] <nacc> Blueking: which is completely accurate with `lshw`
[23:18] <Blueking> looks like that yes
[23:18] <nacc> Blueking: and your BIOS setting is currently set to 4 cores?
[23:18] <Blueking> 'all'
[23:19] <Blueking> active cores
[23:19] <nacc> Blueking: did you figure out what actual model (by the box) you have?
[23:19] <Blueking> I can define 1,2,3, all
[23:19] <nacc> Blueking: based upon sarnold & xnox's disucssion above
[23:19] <nacc> Blueking: it seems most likely you have a buggy BIOS or you have a not-full-core chip
[23:20] <sarnold> I *really* have trouble seeing supermicro having a bios this buggy
[23:20] <sarnold> I know bioses suck and all
[23:20] <sarnold> but defective-CPU sold at a discount is my current favourite theory
[23:20] <Blueking> billing from shop:  	Intel Xeon Quad-Core E3-1230Lv3 1.8GHz 8MB, 25W, LGA1150
[23:22] <Blueking> shop didn't have this cpu on shelf.. were some ordering time and had to wait some time
[23:23] <Blueking> nacc: I updated Bios  2 days ago to see if update fixed number of visible cores
[23:24] <Blueking> I am gonna put another hdd on mine box and test with windows OS
[23:30] <nacc> sarnold: yeah, i would agree too
[23:31] <nacc> Blueking: also, fwiw, your mobo page didn't list this cpu as explicitly compatible
[23:31] <sarnold> curious
[23:32] <sarnold> I saw e3 v3-4 xeons on the page and though tit looked good enough
[23:32] <nacc> i saw e3 1200, and it wasn't immediately obvious to me if that included 1230
[23:34] <nacc> this person claims to have seen 8 cpus in linux with a 1230: https://superuser.com/questions/851799/proc-cpuinfo-for-xeon-e3-processor
[23:34] <sarnold> I think that's  adifferent model, no L in that name
[23:35] <nacc> ah right
[23:38] <nacc> Blueking: this seems relevant: https://webcache.googleusercontent.com/search?q=cache:eWwSlZlUNDMJ:https://forum.pfsense.org/index.php%3Ftopic%3D128722.0+&cd=3&hl=en&ct=clnk&gl=us
[23:39] <sarnold> nacc: DUDE
[23:39] <sarnold> that looks like it exactly
[23:40] <nacc> they got an actual response from SM
[23:40] <nacc> i don't know if it's the same mobo, but the symptoms seem oddly similar
[23:44] <sarnold> the only slight prblem of course is the bios upgrade was done to try to fix this issue
[23:44] <sarnold> but still, clearing cmos and spending a few minutes to put it all back together again is quick and easy, easier than installing windows anyway :)
[23:44] <nacc> right