Beiträge von Rd65

    Sometimes you want to quickly identify configuration differences between two hosts.

    These could be different settings in configuration files, files that are present on one host but missing on the other, or any number of other differences. The following script helps you detect differences in files and directories between two hosts. Of course, the more files it has to process, the longer it will take.


    this will show things like:

    bash verg.sh '/etc/hosts' slave1 root slave2 root

    [INFO] Testing SSH connection to root@slave1...

    [INFO] SSH connection to root@slave1 successful.

    [INFO] Testing SSH connection to root@slave2...

    [INFO] SSH connection to root@slave2 successful.

    [DIFFERENCE] /etc/hosts

    ============== Difference: /etc/hosts ==============

    --- /tmp/tmp.gj8S18rtQp 2025-07-04 12:50:43.569949236 +0200

    +++ /tmp/tmp.0hZBYAtcp4 2025-07-04 12:50:46.013860959 +0200

    @@ -1,10 +1,10 @@

    127.0.0.1 localhost.localdomain localhost

    192.168.178.11 slave1 slave1

    -192.168.178.11 slave1 slave1

    +192.168.178.12 slave2 slave2

    192.168.178.12 slave2 slave2

    192.168.178.13 slave3 slave3

    192.168.178.3 omv omv

    -::1 localhost ip6-localhost ip6-loopback slave1 slave1

    +::1 localhost ip6-localhost ip6-loopback slave2 slave2

    fe00::0 ip6-localnet

    ff00::0 ip6-mcastprefix

    ff02::1 ip6-allnodes

    =======================================================



    Things like /etc/apt/ work too.

    bash verg.sh '/etc/apt/' slave1 root slave2 root

    [INFO] Testing SSH connection to root@slave1...

    [INFO] SSH connection to root@slave1 successful.

    [INFO] Testing SSH connection to root@slave2...

    [INFO] SSH connection to root@slave2 successful.

    [INFO] Directory mode: Searching '/etc/apt/' recursively on slave1...

    [DIFFERENCE] /etc/apt/sources.list

    ============== Difference: /etc/apt/sources.list ==============

    --- /tmp/tmp.pw1we59d5e 2025-07-04 11:59:35.964741770 +0200

    +++ /tmp/tmp.sJpHnF6GIn 2025-07-04 11:59:38.400653861 +0200

    @@ -1,4 +1,3 @@

    -deb http://deb.debian.org/debian-security/ bookworm-security main non-free-firmware

    deb http://debian.charite.de/debian/ bookworm main contrib non-free non-free-firmware

    deb http://debian.charite.de/debian/ bookworm-updates main contrib non-free non-free-firmware

    deb-src http://debian.charite.de/debian/ bookworm main contrib non-free non-free-firmware

    =======================================================

    [EQUAL] /etc/apt/update-post-invoke-success.d/README

    [EQUAL] /etc/apt/pre-invoke.d/README

    [EQUAL] /etc/apt/update-pre-invoke.d/README

    [EQUAL] /etc/apt/trusted.gpg.d/debian-archive-trixie-stable.asc

    [EQUAL] /etc/apt/trusted.gpg.d/debian-archive-bookworm-security-automatic.asc

    grep: /etc/apt/trusted.gpg.d/openmediavault-archive-keyring.gpg: binary file matches

    grep: /etc/apt/trusted.gpg.d/openmediavault-archive-keyring.gpg: binary file matches

    [EQUAL] /etc/apt/trusted.gpg.d/openmediavault-archive-keyring.gpg

    grep: /etc/apt/trusted.gpg.d/openmediavault-keyring.gpg: binary file matches

    grep: /etc/apt/trusted.gpg.d/openmediavault-keyring.gpg: binary file matches

    [EQUAL] /etc/apt/trusted.gpg.d/openmediavault-keyring.gpg

    grep: /etc/apt/trusted.gpg.d/openmediavault.key.chroot.gpg: binary file matches

    grep: /etc/apt/trusted.gpg.d/openmediavault.key.chroot.gpg: binary file matches

    [EQUAL] /etc/apt/trusted.gpg.d/openmediavault.key.chroot.gpg

    [EQUAL] /etc/apt/trusted.gpg.d/debian-archive-trixie-automatic.asc

    [EQUAL] /etc/apt/trusted.gpg.d/openmediavault.key.binary.asc

    [EQUAL] /etc/apt/trusted.gpg.d/debian-archive-bookworm-automatic.asc

    [EQUAL] /etc/apt/trusted.gpg.d/debian-archive-bullseye-automatic.asc

    [EQUAL] /etc/apt/trusted.gpg.d/debian-archive-bullseye-stable.asc

    [EQUAL] /etc/apt/trusted.gpg.d/debian-archive-bookworm-stable.asc

    [EQUAL] /etc/apt/trusted.gpg.d/debian-archive-bullseye-security-automatic.asc

    [EQUAL] /etc/apt/trusted.gpg.d/debian-archive-trixie-security-automatic.asc

    [EQUAL] /etc/apt/post-invoke.d/20fix-start-stop-daemon

    [EQUAL] /etc/apt/post-invoke.d/README

    [EQUAL] /etc/apt/listchanges.conf.d/95openmediavault.conf

    [EQUAL] /etc/apt/listchanges.conf.d/98openmediavault-mail.conf

    [EQUAL] /etc/apt/sources.list~

    [EQUAL] /etc/apt/sources.list.d/openmediavault-kernel-backports.list

    [EQUAL] /etc/apt/sources.list.d/openmediavault.list

    [EQUAL] /etc/apt/sources.list.d/openmediavault-os-security.list

    [EQUAL] /etc/apt/sources.list.d/omvextras.list

    [EQUAL] /etc/apt/sources.list.d/openmediavault-local.list

    [EQUAL] /etc/apt/preferences.d/proxmox.pref

    [EQUAL] /etc/apt/preferences.d/openmediavault-local.pref

    [EQUAL] /etc/apt/preferences.d/omvextras.pref

    [EQUAL] /etc/apt/preferences.d/openmediavault-kernel-backports.pref

    [EQUAL] /etc/apt/listchanges.conf

    [EQUAL] /etc/apt/apt.conf.d/01autoremove

    [EQUAL] /etc/apt/apt.conf.d/00trustcdrom

    [EQUAL] /etc/apt/apt.conf.d/20listchanges

    [EQUAL] /etc/apt/apt.conf.d/20auto-upgrades

    [EQUAL] /etc/apt/apt.conf.d/70debconf

    [EQUAL] /etc/apt/apt.conf.d/00CDMountPoint

    [EQUAL] /etc/apt/apt.conf.d/99openmediavault-apt-hooks

    [EQUAL] /etc/apt/apt.conf.d/98openmediavault-periodic-custom

    [EQUAL] /etc/apt/apt.conf.d/99openmediavault-localrepository

    [EQUAL] /etc/apt/apt.conf.d/95openmediavault-periodic

    [EQUAL] /etc/apt/apt.conf.d/99openmediavault-norecommends

    [EQUAL] /etc/apt/apt.conf.d/95openmediavault-unattended-upgrades

    [EQUAL] /etc/apt/apt.conf.d/99openmediavault-mkaptidx

    [EQUAL] /etc/apt/apt.conf.d/98openmediavault-unattended-upgrade-mail

    [EQUAL] /etc/apt/apt.conf.d/99dpkgnotify

    [EQUAL] /etc/apt/apt.conf.d/00recommends

    [EQUAL] /etc/apt/apt.conf.d/99openmediavault-nosuggests

    [EQUAL] /etc/apt/apt.conf.d/95openmediavault-unattended-upgrade

    [EQUAL] /etc/apt/update-post-invoke.d/README

    Sometimes it is necessary to quickly compare the list of installed packages between two hosts in order to identify any differences. Provided you have access via SSH key, you can use the following script from a third machine (or from one of the hosts itself) to compare two systems with each other.


    an output can show:


    bash compare-pkgs.sh slave1 slave2

    ==> Pakete von slave1 werden geholt...

    Pakete insgesamt auf slave1: 595

    ==> Pakete von slave2 werden geholt...

    Pakete insgesamt auf slave2: 584

    Pakete, die NUR auf slave1 installiert sind:

    inetutils-telnet

    libblas3

    liblinear4

    liblua5.3-0

    libpcap0.8

    libpcre3

    libprotobuf-c1

    libunwind8

    linux-image-6.1.0-28-amd64

    lua-lpeg

    net-tools

    Pakete, die NUR auf slave2 installiert sind:



    this help to decide which packets to install on slave2 or remove on slave1 to be equal.

    I would like to (hopefully with the team's permission) open a thread where friendly people can share helpful scripts that are not directly related to OMV, but that make life easier—for example, scripts that can be used with the script plugin.

    Personally, I find it rather complicated to determine when exactly something was installed in Debian. While there is plenty of information available, evaluating it is complex. Here, therefore, is a Bash script that accomplishes this task.


    It show tings like this:


    Start-Date: 2025-06-30 15:10:41

    Commandline: apt-get --yes --allow-downgrades --allow-change-held-packages --fix-broken --fix-missing --auto-remove --allow-unauthenticated --show-upgraded --option DPkg::Options::=--force-confold dist-upgrade

    Upgrade: openmediavault-scripts:amd64 (7.3.1, 7.3.2)

    End-Date: 2025-06-30 15:11:27



    Start-Date: 2025-06-30 22:58:15

    Commandline: apt-get --yes --allow-downgrades --allow-change-held-packages --fix-broken --fix-missing --auto-remove --allow-unauthenticated --show-upgraded --option DPkg::Options::=--force-confold dist-upgrade

    Upgrade: sudo:amd64 (1.9.13p3-1+deb12u1, 1.9.13p3-1+deb12u2)

    End-Date: 2025-06-30 22:58:49


    or

    Start-Date: 2025-06-27 03:03:14

    Commandline: apt install openmediavault-scripts

    Install: python3-isort:amd64 (5.6.4-1, automatic), python3-wrapt:amd64 (1.14.1-2+b2, automatic), shellcheck:amd64 (0.9.0-1, automatic), pylint:amd64 (2.16.2-2, automatic), python3-mccabe:amd64 (0.7.0-1, automatic), python3-platformdirs:amd64 (2.6.0-1, automatic), python3-tomlkit:amd64 (0.11.7-1, automatic), openmediavault-scripts:amd64 (7.3), python3-lazy-object-proxy:amd64 (1.9.0-1+b1, automatic), python3-mypy-extensions:amd64 (0.4.3-4, automatic), python3-logilab-common:amd64 (1.9.8-1, automatic), python3-astroid:amd64 (2.14.2-1, automatic), python3-toml:amd64 (0.10.2-1, automatic), python3-dill:amd64 (0.3.6-1, automatic)

    Error: Sub-process /usr/bin/dpkg returned an error code (1)

    End-Date: 2025-06-27 03:04:28

    i'm not 100% shure but...
    By normal you actiavte homedirs only in the SMB/CIFS Tab. There is no need to create an extra share for homedirs but
    if you do it on your own at /home, you may destroy the system managed default homedirs in /home/%username%.
    You may need additionaly activate Homedirs in User/Setup to use Win Homedirs.
    this is mostly SAMBA dependend, So take a look @ the Samba Manual and your /etc/samba/smb.conf.

    ok boot from a pendrive linux and post:
    #cat /proc/mdstat
    #blkid
    #mdadm --examine /dev/sd[bc] | grep -E "^/dev|Update|State|Event|Role|Array State"


    you set up raid on hole disks, not on patitions? weired.

    What does "omv under Proxmox" mean? OMV as LXD in a Proxmox environment or OMV baremetal with a Proxmox kernel? "Under" is not a technical term. And why RAID? The RAID array starts even without mdadm.conf if at least the corresponding disks / bootsectors are found. Where did the disk or the RAID array with the uuid go? Why didn't the installation create mdadm.conf if it was supposedly initialized correctly? Did you set up the RAID in omv, or is it part of your Proxmox server? Did you install the md plugin? Did you reboot after installation and check if it was still running? Are there any differences in the configuration since then? Questions, questions, and more

    you can boot via pxe to see lan lights, there is no need to reinstall os'es for hardwarediagnostics. Or use a pendrive Linux and take a look at dmesg.

    It's not uncommon for multiple disks to fail one after the other in a RAID. They were usually purchased at the same time from the same batch and are subjected to the same load in the RAID. So why shouldn't they fail sooner? With six drives, you usually use a spare drive. And you usually have at least one spare disk in stock. RAID 5 doesn't mean it will last forever. It mean, it is easy to maintain without downtime - if you care right.
    And by the way, 54° are much too warm for a Harddisk and constantly maybe a reason for dying drives.

    omv depends on os's and os's depend on drivers and drivers depend on bios and bios depends on hardware.
    if you get no lights at the active lan port then omv it is the wrong (most distant) place to look for Problems.
    look at your bios or in os (driver) logs... i 'm shure, your hardware lan port is gone. maybe a thunderstrike nearby.

    the actual upadate for openmediavault-scripts 7.3 is buggy.

    chmod: cannot access '/var/log/omv-scripts-exec-tracker': No such file or directory

    dpkg: error processing package openmediavault-scripts (--configure):

    installed openmediavault-scripts package post-installation script subprocess returned error exit status 1

    Processing triggers for openmediavault (7.7.9-1) ...

    Updating workbench configuration files ...

    Restarting engine daemon ...

    Processing triggers for man-db (2.11.2-2) ...

    Errors were encountered while processing:

    openmediavault-scripts


    de/reinstalling do not fix this. so i removed it.

    # apt purge openmediavault-scripts

    Reading package lists... Done

    Building dependency tree... Done

    Reading state information... Done

    The following packages were automatically installed and are no longer required:

    pylint python3-astroid python3-dill python3-isort python3-lazy-object-proxy python3-logilab-common python3-mccabe python3-mypy-extensions

    python3-platformdirs python3-toml python3-tomlkit python3-wrapt shellcheck

    Use 'apt autoremove' to remove them.

    The following packages will be REMOVED:

    openmediavault-scripts*

    0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.

    1 not fully installed or removed.

    After this operation, 312 kB disk space will be freed.

    Do you want to continue? [Y/n] y

    (Reading database ... 78913 files and directories currently installed.)

    Removing openmediavault-scripts (7.3) ...

    Processing triggers for openmediavault (7.7.9-1) ...

    Restarting engine daemon ...

    Updating workbench configuration files ...

    (Reading database ... 78831 files and directories currently installed.)

    Purging configuration files for openmediavault-scripts (7.3) ...

    Processing triggers for openmediavault (7.7.9-1) ...

    Updating workbench configuration files ...

    Scanning processes...

    Scanning candidates...

    Scanning processor microcode...

    Scanning linux images...

    Running kernel seems to be up-to-date.

    The processor microcode seems to be up-to-date.

    Restarting services...

    systemctl restart wsdd.service

    Service restarts being deferred:

    /etc/needrestart/restart.d/dbus.service

    systemctl restart systemd-logind.service

    systemctl restart unattended-upgrades.service

    systemctl restart wpa_supplicant.service

    No containers need to be restarted.

    User sessions running outdated binaries:

    root @ session #2: sshd[1975]

    root @ user manager service: systemd[2012]

    No VM guests are running outdated hypervisor (qemu) binaries on this host.

    By searching a bug in nfs i found lots of messages like this:


    Jun 12 16:39:57 omv systemd[1]: Configuration file /etc/systemd/system/k3s.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.


    this mean....

    root@omv:~# ls -la /etc/systemd/system/k3s.service

    -rw-rw-rw- 1 root root 878 Jun 9 15:34 /etc/systemd/system/k3s.service


    Rights set by installing the k8s Plugin are wrong.
    fixing that by


    root@omv:~# chmod 0644 /etc/systemd/system/k3s.service


    will change that to

    -rw-r--r-- 1 root root 878 Jun 9 15:34 /etc/systemd/system/k3s.service

    and systemd stops complaining.

    Oh, I didn’t mean to suggest using RAID with USB drives — I was just comparing a fast single USB drive on a USB 3.2 port to a RAID setup in a NAS.

    Of course, you shouldn’t build a RAID using USB drives...

    And yes, not all RAID levels detect or correct bit rot —

    but honestly, if a RAID setup can’t even detect bit rot, it’s not really worth using anyway.

    RAID and NAS were great solutions back when cloud storage didn’t exist and SATA/NVMe weren’t around.

    Today, many users don’t need that complexity. A fast USB 3.2 NVMe drive (e.g. 2–4 TB) can deliver 4–10 GB/s — faster than any LAN — and is more than enough for typical use cases.

    USB ≠ slow anymore. USB 3.2 outperforms SATA, and modern drives have better error correction.

    So no, “never use USB drives” is outdated advice.

    Why still use RAID then? Not for speed — but for reliability. Bit errors still happen, and RAID helps reduce that risk.

    Do you care if one bit flips in a movie? Probably not.

    Do you care if it flips in a production system or codebase? Definitely.

    Bottom line: RAID doesn’t replace backups. But if your data must be reliable, use it.

    If not — keep it simple.

    In my opinion, this isn’t a small Spanish computer company, but rather someone trying to distribute trojans worldwide.

    His IP address points to an HAProxy server located in Lansing, USA — which also hosts domains like gemoney.com.

    That domain, in turn, appears in blocklists such as EasyList due to trojan-related activity involving the URL pattern "page_bouncy_php?$doc_ument".*

    If there’s a virtual name host setup behind it, he might just be unlucky that the same server hosts other questionable services.

    But if he owns the entire server, then this is clearly a fake front.*some chars modifyed

    on his domain AND gemoney.com this happen actualy.


    https:HTTP-Anforderung gesendet, auf Antwort wird gewartet … Lesefehler (Die TLS-Verbindung wurde nicht sauber beendet.) beim Vorspann (header). Erneuter Versuch.

    http:

    HTTP-Anforderung gesendet, auf Antwort wird gewartet … Keine Daten empfangen.

    Erneuter Versuch.

    maybe someone pull the Plug...

    i see no Problems... do you install openmediavault-md from system/extras?


    my cat /etc/mdadm/mdadm.conf show


    ARRAY /dev/md/0 metadata=1.2 UUID=cae6820a:792fec63:d14f8032:77ad4cf1 name=debian:0

    ARRAY /dev/md/1 metadata=1.2 UUID=f9db66ba:05a7bc16:cd5f7b20:93c53179 name=debian:1

    and cat /proc/mdstat


    Personalities : [raid1] [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid10]

    md1 : active raid5 sda2[0] sdb2[1] sdd2[3] sdc2[2]

    5857216512 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]

    bitmap: 0/15 pages [0KB], 65536KB chunk


    md0 : active raid1 sda1[0] sdb1[1] sdd1[3] sdc1[2]

    974848 blocks super 1.2 [4/4] [UUUU]

    By the way.... if you press Ctrl+Shift+R or anything else to reload on the Guru Meditation banner, you may get only a fresh version of the Guru Meditation url. :)
    you can call it even on running servers like https://omvip/#/503
    one of the best Features on omv!

    Long live Amiga! :P