Sysadmin Mega Thread

SgtAwesomesauce · May 8, 2020, 12:25am

the list is sorted by postgres.

But yes.

Either way:

cat Result.csv  | cut -d \, -f 1  | sort | uniq -d

Gave the same reults.

yay unix!

We don’t have super complex databases, so no.

But that would probably be me.

Just thicccccc row counts.

thro · May 8, 2020, 2:05am

select * always!

its much easier than typing out all those field names and who knows, you might need something later in the line of SQL you’re writing

oO.o · May 8, 2020, 7:01pm

If any of you smart sysadmins have insight here, I’d appreciate it…

Entropy question Hardware

Noticed that openscap has more profiles for RHEL8 now, which is nice. Looking at the NIST one, it definitely addresses some things that the DISA one overlooks. For instance, I don’t think DISA has any entropy hardening which seems like an oversight. Speaking of entropy, quick question: the NIST profile says to configure strong entropy for ssh): SSH_USE_STRONG_RNG=32 But caveats with by saying: Warning: This setting can cause problems on computers without the hardware random generator, because insufficient entropy causes the connection to be blocked until enough entropy is available. A quick search on this yielded this helpful RHEL article which mentions that Intel has included a hardware random generator starting with Ivy Bridge. I assume AMD offers something comparable. But what does this mean for earlier processors? I have some old servers running Westmere chips. What’s the entropy source there, or was it just left up to software to work out based on inputs, jitter and that sort of thing? Will configuring ssh this way on those systems lead to the system hanging? Is havgead relevant here? You can buy usb entropy generators. These appear to be marketed to raspberry pis and similar which makes sense. Is it work getting something like this for a server from 2011?

cotton · May 11, 2020, 3:41pm

Trolling for protips -

Does anyone have suggestions or documentation for creating a SLES15 template in VMWare?

cotton

thro · May 12, 2020, 12:47am

So, one thing I tried for the first time today that works (as it should, but neat).

Mixing Powershell and Unix CLI tools (on my Mac, but linux too)

e.g.,

PS /Users/jrose> get-vm  | select name,notes | ft | grep -i radius
per-w2k12-17                        Windows 2012R2 virtual machine for NPS (Radius)
per-w2k12-7                         Windows 2012R2 virtual machine for NPS (Radius)
PS /Users/jrose>

nice, if you get a table you want and then just want to filter it for example

Obviously grep works on the TEXT output of powershell and not on the object pipeline, but that’s fine sometimes

freqlabs · May 12, 2020, 10:16am

Accidentally got a barebones server on ebay that’s incompatible with the E5v2 CPUs I already had to put in it, so now I’m getting E5v3 CPUs too.
Sadly also incompatible with the 80GB of DDR3 reg ECC I ordered to go with the 16GB I already have, so now I’m getting 128GB DDR4 reg ECC and that really hurts.
Anyone need some DDR3 server memory T_T

Dynamic_Gravity · May 12, 2020, 3:04pm

GitLab 13.0 is going to ship May 22^nd and is going to be an exciting release. One of the main features I am excited about is the security scanning like how GitHub does it.

Kickoff Review

Breaking Changes

oO.o · May 12, 2020, 6:09pm

I’ve had luck buying directly from Unix Surplus. If they’re not too busy, they’ll spec something custom for you and they readily have compatibility info on their units.

freqlabs · May 12, 2020, 6:17pm

Well it was my fault for assuming compatibility with v3 implied compat with v2. I did check unixsurplus but didn’t see what I was looking for anyway. Not that I ended up getting what I was looking for. But I’m ending up with something better so I can’t complain too much.

oO.o · May 12, 2020, 6:21pm

Sure, if the extra expense was nbd, then party on I guess.

SgtAwesomesauce · May 12, 2020, 10:49pm

So.

New thing I’m working on:

@freqlabs I’ve got a small problem that you might be able to help with, hopefully?

I’m writing out a status line, and writing over it by using \r and just printing the line before. The problem is that when I do that, if the previous line is longer than the next, I get dangling characters. Now, you can just throw a bunch of spaces on the end to clean it up, but that’s a bit hacky. Is there a way to clear the entire line that can be invoked similarly to \r? I’m using python if it helps.

freqlabs · May 13, 2020, 1:02am

A bunch of spaces (counting would be less hacky).
Or start getting complicated with curses but that’s a pain.

Or ansi sequences… “\033[2K” clears the line (not sure if that’s the correct encoding for Python).
Yep that’s right

>>> print("hello\r\033[2Kfoo")
foo

DrunkByDefault · May 13, 2020, 1:24am

sup party people, how does one

monitor their gpu

utilization in linux?.. cli will do just fine

plz just need quick resp

carnogaunt · May 13, 2020, 1:47am

It’s going to depend on the GPU. For Nvidia with the proprietary driver, use nvidia-smi. It can give output in formats which can be parsed by other tools.

SgtAwesomesauce · May 13, 2020, 1:57am

woot!

Thanks dude! I knew you were the guy to ask.

DrunkByDefault · May 13, 2020, 2:02am

that sucks

how can you game on linux if you cant monitor your damn gpu

oO.o · May 13, 2020, 3:55am

Hey drunk, you should make a thread for this. It’s not really sysadmin stuff (I mean, it kinda is but gaming isn’t).

That said, there are a lot of smart people in here who might be able and willing to help you so feel free to drop a link to the thread here.

mutation666 · May 13, 2020, 8:58am

zlynx · May 13, 2020, 3:40pm

You just do it?

I game on my Ryzen 3900X and Vega 56 in Linux and I don’t bother to monitor anything. I think I have the Steam overlay showing FPS in a corner. It’s usually 60.

The Vega does have a little RGB light strip that shows usage and it’s sometimes interesting to watch. It’s generally 1 dot on the desktop or 7 dots under load, so not all that useful.

The Linux “sensors” command shows me the fan speeds and temperatures of most everything.

Like, here’s “sensors” output for the Talos II I am typing this on right now:

Summary

amdgpu-pci-300100
Adapter: PCI adapter
vddgfx: 950.00 mV
fan1: 1176 RPM (min = 700 RPM, max = 4500 RPM)
edge: +55.0°C (crit = +99.0°C, hyst = -273.1°C)
power1: 21.23 W (cap = 95.00 W)

ibmpowernv-isa-0000
Adapter: ISA adapter
Chip 0 Vdd Remote Sense: 663.00 mV (lowest = +0.65 V, highest = +0.97 V)
Chip 0 Vdn Remote Sense: 689.00 mV (lowest = +0.69 V, highest = +0.69 V)
Chip 8 Vdd Remote Sense: 723.00 mV (lowest = +0.70 V, highest = +0.94 V)
Chip 8 Vdn Remote Sense: 661.00 mV (lowest = +0.66 V, highest = +0.66 V)
Chip 0 Vdd: 665.00 mV (lowest = +0.66 V, highest = +0.97 V)
Chip 0 Vdn: 690.00 mV (lowest = +0.69 V, highest = +0.69 V)
Chip 8 Vdd: 725.00 mV (lowest = +0.71 V, highest = +0.95 V)
Chip 8 Vdn: 662.00 mV (lowest = +0.66 V, highest = +0.66 V)
Chip 0 Core 0: +48.0°C (lowest = +27.0°C, highest = +71.0°C)
Chip 0 Core 4: +48.0°C (lowest = +5.0°C, highest = +75.0°C)
Chip 0 Core 8: +48.0°C (lowest = +27.0°C, highest = +75.0°C)
Chip 0 Core 12: +48.0°C (lowest = +27.0°C, highest = +76.0°C)
Chip 0 Core 16: +48.0°C (lowest = +27.0°C, highest = +72.0°C)
Chip 0 Core 20: +48.0°C (lowest = +8.0°C, highest = +73.0°C)
Chip 0 Core 24: +48.0°C (lowest = +26.0°C, highest = +75.0°C)
Chip 0 Core 28: +48.0°C (lowest = +7.0°C, highest = +111.0°C)
Chip 8 Core 32: +36.0°C (lowest = +26.0°C, highest = +69.0°C)
Chip 8 Core 36: +36.0°C (lowest = +7.0°C, highest = +70.0°C)
Chip 8 Core 40: +36.0°C (lowest = +26.0°C, highest = +69.0°C)
Chip 8 Core 44: +36.0°C (lowest = +7.0°C, highest = +70.0°C)
Chip 8 Core 48: +36.0°C (lowest = +7.0°C, highest = +67.0°C)
Chip 8 Core 52: +36.0°C (lowest = +9.0°C, highest = +68.0°C)
Chip 8 Core 56: +37.0°C (lowest = +26.0°C, highest = +69.0°C)
Chip 8 Core 60: +36.0°C (lowest = +7.0°C, highest = +68.0°C)
Chip 0 DIMM 0 : +40.0°C (lowest = +31.0°C, highest = +51.0°C)
Chip 0 DIMM 1 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 0 DIMM 2 : +38.0°C (lowest = +31.0°C, highest = +51.0°C)
Chip 0 DIMM 3 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 0 DIMM 4 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 0 DIMM 5 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 0 DIMM 6 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 0 DIMM 7 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 0 DIMM 8 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 0 DIMM 9 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 0 DIMM 10 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 0 DIMM 11 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 0 DIMM 12 : +41.0°C (lowest = +33.0°C, highest = +54.0°C)
Chip 0 DIMM 13 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 0 DIMM 14 : +41.0°C (lowest = +33.0°C, highest = +54.0°C)
Chip 0 DIMM 15 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 8 DIMM 0 : +29.0°C (lowest = +27.0°C, highest = +41.0°C)
Chip 8 DIMM 1 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 8 DIMM 2 : +29.0°C (lowest = +27.0°C, highest = +38.0°C)
Chip 8 DIMM 3 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 8 DIMM 4 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 8 DIMM 5 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 8 DIMM 6 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 8 DIMM 7 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 8 DIMM 8 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 8 DIMM 9 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 8 DIMM 10 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 8 DIMM 11 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 8 DIMM 12 : +30.0°C (lowest = +28.0°C, highest = +40.0°C)
Chip 8 DIMM 13 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 8 DIMM 14 : +31.0°C (lowest = +29.0°C, highest = +41.0°C)
Chip 8 DIMM 15 : +0.0°C (lowest = +0.0°C, highest = +0.0°C)
Chip 0 Nest: +48.0°C (lowest = +27.0°C, highest = +64.0°C)
Chip 8 Nest: +37.0°C (lowest = +26.0°C, highest = +60.0°C)
Chip 0 VRM VDD: +46.0°C (lowest = +33.0°C, highest = +67.0°C)
Chip 8 VRM VDD: +33.0°C (lowest = +30.0°C, highest = +60.0°C)
Chip 0 : 32.00 W (lowest = 27.00 W, highest = 134.00 W)
Chip 0 Vdd: 4.00 W (lowest = 0.00 W, highest = 105.00 W)
Chip 0 Vdn: 9.00 W (lowest = 7.00 W, highest = 11.00 W)
Chip 8 : 30.00 W (lowest = 28.00 W, highest = 120.00 W)
Chip 8 Vdd: 4.00 W (lowest = 2.00 W, highest = 92.00 W)
Chip 8 Vdn: 7.00 W (lowest = 6.00 W, highest = 10.00 W)
Chip 0 : 14.41 MJ
Chip 0 Vdd: 1.73 MJ
Chip 0 Vdn: 3.86 MJ
Chip 8 : 14.14 MJ
Chip 8 Vdd: 2.06 MJ
Chip 8 Vdn: 3.25 MJ
Chip 0 Vdd: 6.00 A (lowest = +0.13 A, highest = +111.38 A)
Chip 0 Vdn: 13.25 A (lowest = +11.13 A, highest = +16.50 A)
Chip 8 Vdd: 6.75 A (lowest = +2.13 A, highest = +100.25 A)
Chip 8 Vdn: 11.63 A (lowest = +10.38 A, highest = +15.75 A)

nvme-pci-310100
Adapter: PCI adapter
Composite: +30.9°C (low = -273.1°C, high = +76.8°C)
(crit = +78.8°C)
Sensor 1: +30.9°C (low = -273.1°C, high = +65261.8°C)
Sensor 2: +34.9°C (low = -273.1°C, high = +65261.8°C)

nx2l · May 13, 2020, 4:24pm

it just works

for me