NodeBB

Nouveau test :

# du -sh /var/cache/uptrack/*
4.0K    /var/cache/uptrack/backoff
4.0K    /var/cache/uptrack/backoff-counter
2.5G    /var/cache/uptrack/Linux
4.0K    /var/cache/uptrack/status

# uptrack-uname -r
5.4.17-2136.349.3.1.el8uek.x86_64


#  uptrack-show
Installed updates:
None


# du -sh /var/cache/uptrack/Linux/x86_64/*
426M    /var/cache/uptrack/Linux/x86_64/5.4.17-2102.201.3.el8uek.x86_64
287M    /var/cache/uptrack/Linux/x86_64/5.4.17-2136.316.7.el8uek.x86_64
287M    /var/cache/uptrack/Linux/x86_64/5.4.17-2136.324.5.3.el8uek.x86_64
456M    /var/cache/uptrack/Linux/x86_64/5.4.17-2136.331.7.el8uek.x86_64
270M    /var/cache/uptrack/Linux/x86_64/5.4.17-2136.336.5.1.el8uek.x86_64
604M    /var/cache/uptrack/Linux/x86_64/5.4.17-2136.337.5.1.el8uek.x86_64
170M    /var/cache/uptrack/Linux/x86_64/5.4.17-2136.349.3.1.el8uek.x86_64

#  yum remove uptrack
Dependencies resolved.
...
# yum install uptrack
Last metadata expiration check: 1:38:15 ago on Tue 12 May 2026 01:20:27 PM CEST.
Dependencies resolved.
...
# du -sh /var/cache/uptrack/
0       /var/cache/uptrack/

Xeon Gold 6254 vs E5-2450 v2 | Technical City

Comparing E5-2450 v2 with Gold 6254: technical specs, games and benchmarks.

(technical.city)

“Xeon Gold 6254 outperforms Xeon E5-2450 v2 by a whopping 257% based on our aggregate benchmark results.”

Sur CPU BOGOMIPS : 159998.72 à 374460.48 j’ai 134.04 % et pas 257%.

pveperf(1)

(pve.proxmox.com)

• CPU BOGOMIPS :
  - bogomips sum of all CPUs
• REGEX/SECOND :
  - regular expressions per second (perl performance test), should be above 300000

Nouveau serveur :

# inxi -C
CPU:
  Info: 24-core (8-mt/16-st) model: 13th Gen Intel Core i9-13900 bits: 64 type: MST AMCP cache:
    L2: 32 MiB
  Speed (MHz): avg: 4700 min/max: 800/5300:5600:4200 cores: 1: 4700 2: 4700 3: 4700 4: 4700
    5: 4700 6: 4700 7: 4700 8: 4700 9: 4700 10: 4700 11: 4700 12: 4700 13: 4700 14: 4700 15: 4700
    16: 4700 17: 4700 18: 4700 19: 4700 20: 4700 21: 4700 22: 4700 23: 4700 24: 4700 25: 4700
    26: 4700 27: 4700 28: 4700 29: 4700 30: 4700 31: 4700 32: 4700
# pveperf
CPU BOGOMIPS:      127795.20
REGEX/SECOND:      7280708
HD SIZE:           93.93 GB (/dev/mapper/pve-root)
BUFFERED READS:    1948.32 MB/sec
AVERAGE SEEK TIME: 0.03 ms
FSYNCS/SECOND:     201.72
DNS EXT:           40.82 ms
DNS INT:           31.14 ms (pve)

Tableau :

Nouveau serveur :

# inxi -C
CPU:       Info: 2x 18-Core model: Intel Xeon Gold 6240 bits: 64 type: MT MCP SMP L2 cache: 49.5 MiB
           Speed: 2600 MHz min/max: N/A Core speeds (MHz): 1: 2600 2: 2600 3: 2600 4: 2600 5: 2600 6: 2600 7: 2600 8: 2600
           9: 2600 10: 2600 11: 2600 12: 2600 13: 1000 14: 2600 15: 2600 16: 2600 17: 2600 18: 2600 19: 2600 20: 2600 21: 2600
           22: 2600 23: 2600 24: 2600 25: 2600 26: 2600 27: 2600 28: 2600 29: 2600 30: 2600 31: 2600 32: 2600 33: 2600
           34: 2600 35: 2600 36: 2600 37: 2600 38: 2600 39: 2600 40: 2600 41: 2600 42: 2600 43: 2600 44: 2600 45: 2600
           46: 2600 47: 2600 48: 2600 49: 2600 50: 2600 51: 2600 52: 2600 53: 2600 54: 2600 55: 2600 56: 2600 57: 2600
           58: 2600 59: 2600 60: 2600 61: 2600 62: 2600 63: 2600 64: 2600 65: 2600 66: 2600 67: 2600 68: 2600 69: 2600
           70: 2600 71: 2600 72: 2600
# pveperf
CPU BOGOMIPS:      374460.48
REGEX/SECOND:      3748282
HD SIZE:           93.93 GB (/dev/mapper/pve-root)
BUFFERED READS:    127.64 MB/sec
AVERAGE SEEK TIME: 7.99 ms
FSYNCS/SECOND:     8385.41
DNS EXT:           52.64 ms
DNS INT:           24.96 ms 

@divingeek a dit dans PROXMOX : Pveperf :

inxi

apt-get install inxi

Check /etc/pve/lxc/*.conf :

lxc.apparmor.profile: unconfined
lxc.cgroup.devices.allow: a
lxc.cap.drop:

Sur un autre serveur en Ubuntu 22 :

$ cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.5 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.5 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy
$ stat -fc %T /sys/fs/cgroup/
cgroup2fs
$ cat /etc/default/grub | grep "^GRUB"
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX=""
$ docker --version
Docker version 29.3.1, build c2be9cc
$ mount|grep cgroup
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)

Voir https://oneuptime.com/blog/post/2026-02-08-how-to-understand-docker-container-cgroups-in-depth/view

ls /sys/fs/cgroup/cgroup.controllers 2>/dev/null && echo "cgroups v2" || echo "cgroups v1"
stat -fc %T /sys/fs/cgroup/

A faire :

cat /sys/fs/cgroup/devices/devices.list

Voir aussi le paramètre :

lxc.cgroup.devices.allow = a

Le problème :

docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error setting cgroup config for procHooks process: failed to write "a *:* rwm": write /sys/fs/cgroup/devices/docker/9062e5fe97eaccd163ea072644a4593a1dc707e090298a08d959ae5dc8f510b3/devices.allow: operation not permitted: unknown.

Version :

#  lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.5 LTS
Release:        22.04
Codename:       jammy

# docker --version
Docker version 24.0.2, build cb74dfc

# docker info | grep Cgroup
 Cgroup Driver: cgroupfs
 Cgroup Version: 1

# grep cgroup /proc/filesystems
nodev   cgroup
nodev   cgroup2

# stat -fc %T /sys/fs/cgroup/
tmpfs

# dpkg -l | grep docker
ii  docker-buildx-plugin              0.10.5-1~ubuntu.18.04~bionic                     amd64        Docker Buildx cli plugin.
ii  docker-ce                         5:24.0.2-1~ubuntu.18.04~bionic                   amd64        Docker: the open-source application container engine
ii  docker-ce-cli                     5:24.0.2-1~ubuntu.18.04~bionic                   amd64        Docker CLI: the open-source application container engine
ii  docker-ce-rootless-extras         5:24.0.2-1~ubuntu.18.04~bionic                   amd64        Rootless support for Docker.
ii  docker-compose-plugin             2.18.1-1~ubuntu.18.04~bionic                     amd64        Docker Compose (V2) plugin for the Docker CLI.

Pour le menu recovery il faut appuyer une fois sur ESC ou ALT.
noapic + nomodeset => Blocage.
noapic => Blocage. ( Boot long car DISABLE IRQ 11 ).

C’est pas gagné.

GitHub - borestad/blocklist-abuseipdb: Aggregated AbuseIPDB blocklists with worst IPv4 & IPv6 offenders (~99% confidence)

Aggregated AbuseIPDB blocklists with worst IPv4 & IPv6 offenders (~99% confidence) - borestad/blocklist-abuseipdb

GitHub (github.com)

❯ abuseipdb-s100-1d (53363 ips)
❯ abuseipdb-s100-3d (58143 ips)
❯ abuseipdb-s100-7d (69300 ips)
❯ abuseipdb-s100-14d (86898 ips)
❯ abuseipdb-s100-30d (125070 ips)
❯ abuseipdb-s100-60d (183928 ips)
❯ abuseipdb-s100-90d (247119 ips)
❯ abuseipdb-s100-120d (357106 ips)
❯ abuseipdb-s100-180d (654007 ips)
❯ abuseipdb-s100-365d (1173988 ips)
❯ abuseipdb-s100-all (1830085 ips)

https://raw.githubusercontent.com/borestad/blocklist-abuseipdb/refs/heads/main/abuseipdb-s100-3d.ipv4

58.140 IPs.

Voir : https://xtom.com/blog/what-is-nethogs-and-how-to-monitor-network-traffic/

Bilan : 3 heures …

J’ai donc :

# ls -l *.so*
-rw-r--r--    1 root     rezi         95556 Nov  4 15:15 libncurses.so.6
lrwxrwxrwx    1 root     rezi            27 Nov  4 15:14 libpcap.so.0.8 -> /home/root/libpcap.so.1.9.1
-rw-r--r--    1 root     rezi       1068652 Nov  4 14:59 libpcap.so.1.9.1
-rw-r--r--    1 root     rezi        125064 Nov  4 15:16 libtinfo.so.6

J’ai fait :

 export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/home/root/"
ln -s /home/root/libpcap.so.1.9.1 /home/root/libpcap.so.0.8
# ./nethogs