[09:05] <admin1> hi all.. is there a command to see what voltage the cpu is getting/using ? 
[11:52] <effendy[m]> admin1: there's the lm-sensors package that you can install on Ubuntu. Then run "sensors".
[12:21] <admin1> thanks.. i used dmidecode --type processor | grep -i volt 
[12:23] <effendy[m]> ah, I was wondering if dmidecode already had it
[12:23] <effendy[m]> I don't know why I thought about the temperature actually
[12:24] <effendy[m]> running sensors displays the temperature only anyway.
[12:25] <admin1> i have one server thats drawing 1.8 volts .. trying to reduce it somehow using linux . 
[12:25] <admin1> 1.8 volts on the cpu 
[12:25] <admin1> temp 90* :) 1* below thermals kick in  i think 
[12:25] <admin1> sorry 89* .. 
[13:11] <Assid> heya.. i have a situation.. ive disabled password authentication and challengeresponse .. but it still asks for passworrd
[13:14] <sdeziel> Assid: stupid question but did you restart sshd after making those changes?
[13:14] <Assid> yes
[13:14] <sdeziel> Assid: can you pastebin the output of `ssh -vv ...`
[13:15] <sdeziel> Assid: also the output of `sshd -T`, please
[13:16] <Assid> debug1: Authentications that can continue: publickey,password   ....
[13:17] <Assid> https://pastebin.com/JHSjjzpK
[13:18] <Assid> for some reason passwordauth is saying yes here
[13:32] <Assid> so why isnt it parsing the info from sshd_config
[13:34] <Assid> found it.. finally
[13:37] <sdeziel> glad you found it
[14:04] <JanC> was it PAM?
[14:05] <Assid> it was in the cloud-init file . strage enough .. i dont use cloud init
[14:05] <JanC> oh
[14:05] <Assid> in /etc/ssh/sshd_config.d/50-cloud-init.conf
[14:06] <Assid> so whoever packaged this .. didnt clean up
[14:07] <JanC> how did you install it?
[14:08] <Assid> used the sevrer install iso.. and during setup i enabled ssh
[14:27] <JanC> it appears the server ISO uses cloud-init
[14:28] <JanC> (but my test-install crashed before it could finish, so I can't see if it leaves any unasked-for files behind)
[14:29] <JanC> can we please get the old installer back?
[14:31] <JanC> apparently the installer needs > 4GiB disk space? that's insane
[14:32] <patdk-lap> I just always use jeos
[14:35] <ravage> my current way of installing Ubuntu 22.04 is a bash script in grml via debootstrap. the new installer really feels like a rushed beta release :)
[14:36] <ravage> the useless official documentation adds to that
[14:40] <ogra> ravage, beta ?? ... https://git.launchpad.net/subiquity/commit/?id=d812ff23b8e5d53b66bde481d653755d3e4b9e03 ... 
[14:40] -ubottu:#ubuntu-server- Commit d812ff2 in subiquity "Initial commit"
[14:40] <ravage> just read the full message
[14:41] <ogra> well, it was initially created i 2015 (as you can see above) and had its first release in 2016 
[14:41] <ravage> still feels unfinished to me
[14:41] <ogra> (with being the default installer since 201😎
[14:41] <ravage> and thats all i said
[14:41] <ogra> *2018
[14:42] <ogra> you had already 4 LTSes to make sure the bugs make it feel like beta to you could have been fixed 
[14:42] <ravage> feelings are complicated
[14:42] <ogra> heh
[14:45] <JanC> crashing half way an install without a proper error message doesn't feel particularly "finished" to me...
[14:46] <ravage> but you had time to report that 4 LTSes ago JanC. Now you have to live with it. It was decladed perfect already :)
[14:47] <ravage> (no hard feelings)
[20:56] <Arlion> Performing a do-release-upgrade from bionic to focal yields me an interesting issue. grub-pc fails to complete due to mandating that I select which drive grub needs to be installed on on the account of the previous drive is gone or w/e. The answer is /dev/sda always for me. Where can I make this modification so /dev/sda will automatically get grub installed to and do-release-upgrade will be allowed to finish with a return code of 0
[21:13] <patdk-lap> it will always remember
[21:13] <patdk-lap> unless you remove a drive and mess it up
[21:13] <patdk-lap> dpkg-reconfigure grub-pc
[21:40] <Arlion> That's what the issue is right? The last remember drive is no longer present. I need to point it to the new one so this issue doesn't occur doing the upgrade process.
[21:43] <Arlion> debconf-show grub-pc
[21:43] <Arlion> * grub-pc/install_devices: /dev/disk/by-id/scsi-36782bcb006b90800232a448e1e5b07ff
[21:44] <Arlion> cool, that is the option that needs to change