@jaredbusch said in beyond bash shell scripting, what language should I use:

@scottalanmiller said in beyond bash shell scripting, what language should I use:

@jaredbusch said in beyond bash shell scripting, what language should I use:

@stacksofplates said in beyond bash shell scripting, what language should I use:

@jaredbusch said in beyond bash shell scripting, what language should I use:

@scottalanmiller said in beyond bash shell scripting, what language should I use:

Go is great as a language. But like Ruby, not installed generally. And fewer resources. If it was a greenfield new OS, yeah, Go for sure. But for practical reasons, Python I think.

As these are systems that I control, there is no reason Go cannot be installed.

Between your comments and prior ones from @stacksofplates I think I might try Go in order to learn it.

You normally wouldn't install it anyway as it's not a scripting language. You'd just compile your binary and ship that to your systems.

I completely misunderstood that about Go. Okay, I will do a bit of checking and decide what I want to do.

oh sorry, I figured you knew. That's why I never look at it, I don't want to deal with binaries in that way. But nothing wrong with that. Write it on your machine at home, compile, ship binary. Works just fine.

As fixed tasks, this is not a bad solution. So I will keep it in mind.

Right, no big deal in this case.

@stuartjordan I seem to recall this being one of the reasons I got away from KDE a while back. Some quick google work shows that it might be solved by using kio-fuse but YMMV.

minfree Defines the amount of free space left in the LVM volume group pve. With more than 128GB storage available the default is 16GB, else hdsize/8 will be used.

This is space to leave behind for snapshots. They suggest 1/8th the size of your hard drive.

@scottalanmiller said in New to Linux Administration: RHEL-Based or Debian-Based OS:

I agree, both is the obvious choice. But to truly answer the question, I'd focus on Ubuntu (not Debian) and then RHEL. Debian is great, but it is Ubuntu specifically that has the market.

Yes, almost the same is never the same as exactly the same.

@Dashrender

Gotta love Bob-

Just install one of the old supported OSes on another drive, reboot and run the firmware update. It's a self extracting executable.

With HP and Dell, it's their intention to support you by providing an additional layer of management on top of the actual manufacturers product. But you have to be in warranty to be able to leverage that support. If you intend to run equipment longer than the 5 year warranty, don't use Dell or HP or live without any firmware upgrades or support. If you use Dell or HP, replace hardware when it's out of warranty.

HP Gen8 servers are from 2012-2013 so 7-8 years old and not the best candidates for new installations.

2nd attempt worked!

@stacksofplates said in Installing Hugo Static Website Generator on Linux:

@scottalanmiller said in Installing Hugo Static Website Generator on Linux:

@stacksofplates said in Installing Hugo Static Website Generator on Linux:

@scottalanmiller said in Installing Hugo Static Website Generator on Linux:

However, they don't have any standard Linux install documentation on their website and only show using Homebrew, a MacOS package that essentially no one on Linux uses. Very odd.

I just looked. I'm not sure what you're talking about. The page clearly shows snaps, dnf, apt, pacman, eopgk, and pkg_add for OpenBSD.

https://gohugo.io/getting-started/installing

Completely different than what I got from the same link this morning. I went to that page, clicked on Linux, and they only showed Brewlinux, which isn't even the current name of the system.

Way back machine shows it's been there since at least the 13th.

https://web.archive.org/web/20191113183617/https://gohugo.io/getting-started/installing/

Very weird. I wonder if it was a cache somewhere? I definitely poked around this morning and Linuxbrew was the only thing that it had and had it from every link that I tried on their site.

Congrats 🐶

@Pete-S Ok, I went ahead and let the installer partition it using the defaults for LVM. Everything is working!

The installer creates a small primary partition and installs /boot to it. It then creates an extended partition with the remainder of the drive and slices up logicals out of that for the LVM. It puts “/“ in vg1 as “lv root” and puts /swap in vg1 as well as lv swap”.

I was not creating a /boot. Never have. I was just creating a primary for the “/“ and then saving some of it for an extended /swap. I’ve done this forever. It even works in a VM. I have no idea why I couldn’t get it to work on the physical machine.

We use ghost adapters to allow EDID hi res with no head attached, I wonder if there is one that forces 640x480? I'll search around...

@IRJ said in Splunk vs iptables:

iptables -A OUTPUT -o eth0 -p tcp --sport 9997 -m state --state NEW,ESTABLISHED -j ACCEPT

Looks like the solution was
iptables -A INPUT -i lo -j ACCEPT
iptables -A OUTPUT -o lo -j ACCEPT

Or at least that got it working. 🙂

@scottalanmiller said in EFI Pace Won't Start After Vault Configuration Change:

Had to deal with Fiery too.

I think they misspelled that name slightly. Fire that company (I know, you wish they would.)

Something in the shutdown triggers a start of a service or doesn't stop in time. Since something is still running the shutdown never completes.

Looking at the screenshot for instance it says "Stopping monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...".
But there is no acknowledgment [OK] that it has completed.

I'd start looking there.

@marcinozga said in Linux partitioning:

@travisdh1 said in Linux partitioning:

@marcinozga said in Linux partitioning:

@travisdh1 said in Linux partitioning:

@marcinozga said in Linux partitioning:

@travisdh1 said in Linux partitioning:

@marcinozga said in Linux partitioning:

@JaredBusch said in Linux partitioning:

@marcinozga said in Linux partitioning:

Last option on that screen. Why? Because if your root partition fills up, your system won't boot. Having /var on separate partition reduces that risk. Think of a bad app creating gigabytes of log entries, or writing junk to database.

Better solution, don't use bad apps

You never know if an app or kernel update doesn't go nuts. Here's an example of bad kernel module causing writing gigs of logs in minutes: https://unix.stackexchange.com/questions/195360/my-var-log-is-mysteriously-filling-up-gbs-in-minutes-any-cure-before-i-re-ins

Sure it's possible, but how many times do we see this sort of thing in normal use day to day? This is the first one I've heard of in years.

Used to happen more often because bad programming was more common.

Take Ubuntu for example, it will fill up /boot after a few kernel upgrades, so anything is possible.

That's a known badly implemented system. IE bad programming. Don't use it.

Also, it has nothing to do with /var filling up.

It's just an example of partition filling up, doesn't matter which one. It proves the point that it does happen.

In your example, they are causing a new problem because they've implemented your solution to the problem.

No, it would've had the same outcome if /boot wasn't on separate partition, but under root. Eventually it would've filled up entire disk with old kernel versions. The main point is to prevent root partition from filling up, not any other mount point.

That's not really true. That's making a lot of assumptions. In reality...

It would not likely ever fill up. The scales are so different. This is where creating a separate /boot actually CREATES the risk. The very pattern you are trying to follow is the one causing the issue.

It has lots and lots of chances for humans AND monitoring systems to catch and resolve it long before becoming an issue. This should have years, typically, to be flagged rather than filling up in a day or two.

Works on Debian 10.

Wow this must be an old server. pam_tally was replaced with faillock in RHEL 6.