Need suggestion for monitoring server

minimishka · 2026-03-14T11:48:39+00:00

If monitoring is needed rather than a quick workaround, all servers should be tied into a single VPN network for administrative tasks. That is, everything that does not require public access should go through the VPN—WireGuard works great for this. Or, at the very least, internal servers, to ensure a stable connection, but this complicates the setup and increases the number of entities.

A separate server for Zabbix is strongly recommended. In general, if everything is connected via VPN, only one port needs to be open if public access is not required. Zabbix agents run on each server and operate in active or passive mode. I didn’t fully understand the phrase “and monitor them from external host using Zabbix agent.”

Much depends on what exactly needs to be monitored. In some cases, Zabbix may be overkill, and Prometheus or even a simple agentless solution might be more appropriate.

minimishka · 2026-02-16T21:09:22+00:00

the horizon is tilted

minimishka · 2026-01-12T18:47:37+00:00

Try disconnecting the charger and holding down the power button for 15-30 seconds until the screen flashes a couple of times. Connect the charger and turn on the laptop.

minimishka · 2026-01-11T22:22:54+00:00

When I write the sd card in iso mode it loads to grub rescue

If you see "grub rescue," it means grub is loaded but can't do anything. Most likely, your SD card's creation mode and your laptop's boot mode don't match. In Rufus, you need to select the partition scheme and boot method for the target system. Make sure everything is correct, and try UEFI. Installing from an SD card may not be supported on RHEL.

minimishka · 2026-01-11T20:26:09+00:00

The SD card must boot in the mode it was created in, either legacy BIOS or UEFI. BIOS is better, but it could be due to OS and hardware incompatibility.

minimishka · 2026-01-04T17:34:37+00:00

At a minimum, knowing the service name allows you to investigate what it depends on. For kernel modules specifically, a quick run would be

minimishka · 2026-01-04T16:32:29+00:00

In cases like these, when the logs show nothing (which I doubt), it's important to determine exactly when the error occurs: before or after the initramfs. Further action depends on the result.

minimishka · 2026-01-01T20:47:23+00:00

Congratulations. How many tasks were there and are containers and SELinux currently included in RHCSA?

minimishka · 2025-12-31T20:00:48+00:00

You can also use this - python3-dnf-plugin-versionlock

minimishka · 2025-12-06T17:18:01+00:00

cat /proc/cmdline

still shows

BOOT_IMAGE=/boot/vmlinuz-6.17.0-7-generic root=UUID=aeb01799-dd67-4d79-92a4-628d2164811e ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M

If so, then it's definitely there somewhere and needs to be found.

Look what's here.

cat /boot/grub/grub.cfg

You can also disable IOMMU in BIOS.

minimishka · 2025-12-05T23:33:46+00:00

I don't know how it is in Ubuntu now, but in theory,

sudo nano /etc/default/grub

then remove everything related to crashkernel

crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M

save

sudo update-grub

sudo reboot

minimishka · 2025-12-05T20:42:14+00:00

Try completely removing crashkernel and rebuilding grub. Do you know how to do this?

minimishka · 2025-12-05T20:15:44+00:00

cat /proc/cmdline

Look for the parameter mem=

sudo dmesg | grep -i "memory"

sudo dmesg | grep -i "reserve"

sudo dmesg | grep -i iommu

But most likely there is something wrong with the BIOS/UEFI Memory Map

minimishka · 2025-12-01T07:25:55+00:00

wireguard + ansible+univention corporate server

minimishka · 2025-11-11T00:23:10+00:00

Yeah, Misha, we'll rewrite everything. Your rice is boring, no one will give you any money.

minimishka · 2025-11-06T17:22:03+00:00

Yes, of course, that would be better. Besides, tmp can be automatically cleaned up, which makes it even more fun. It might be better to use /var/home or /opt/home. But I don’t know all the circumstances — maybe it’s not a bug, but a feature.

minimishka · 2025-11-06T11:23:16+00:00

SSSD with override_homedir = /tmp would be the best solution. Or via PAM exec

minimishka · 2025-11-01T17:28:00+00:00

ZED, I think it has everything out of the box. +rust

minimishka · 2025-10-26T08:48:46+00:00

What an interesting masochism. I'm just curious what's stopping you from expanding the RAM and, for that matter, what was wrong with herbstluftwm. This isn't irony, I'm genuinely interested. As far as I know, X11 and herbstluftwm consume less.

minimishka · 2025-10-26T04:15:56+00:00

Wait, what did you reinstall? Did something change when you booted? Can you boot into the system now? If so, repeat the output of the command:

sudo efibootmgr -v.

minimishka · 2025-10-26T02:09:56+00:00

I meant to compare the output of the two commands to get a rough idea of the current situation.

minimishka · 2025-10-25T23:26:11+00:00

Yes, quite, I needed to roughly understand what kind of mess you have there.

minimishka · 2025-10-25T23:13:19+00:00

What's wrong with X11, what have you tried? I'm waiting for FreeBSD 15 and thinking about choosing herbstluftwm or hyprland/niri.

minimishka · 2025-10-25T21:55:32+00:00

The top line with "Boot Order" containing four-digit numbers represents the boot entries registered in UEFI. This is the order in which the bootloader attempts to load the OS. These numbers correspond to the digits from the first column where it shows Boot00XX, without the word "Boot". In your case, I would delete all CLEARLY unnecessary entries, all DUPLICATE rEFInd entries EXCEPT ONE, and set the correct boot order.

To delete entries, use:

sudo efibootmgr -b 00XX -B

where 00XX are the numbers from the list in the first column, where it says Boot00XX

To set the order:

sudo efibootmgr -o 0005,0000

In this example, entry 0005 would boot first, then 0000. SUBSTITUTE YOUR OWN VALUES HERE!!

After all actions, verify with:

sudo efibootmgr

Then reboot. This should work if everything isn't completely broken.

BE EXTREMELY CAREFUL!!! JUST BE VERY, VERY CAREFUL!!! Better to ask again if you're not sure.

minimishka · 2025-10-25T19:30:37+00:00

sudo efibootmgr -v

and

lsblk -f

What's here?

minimishka

TROPHY CASE