NodeBB

Je viens de demander la suppression … à suivre. [image: 1780836881023-4e28bb1c-97e9-4c8d-b7d1-577215138732-image.png]

https://lemmy.cyber-neurones.org/topic/5/mon-serveur-proxmox-balkany?_=1771866012056 Bizarre j’ai un truc plus ancien maintenant : NVIDIA-SMI 535.288.01 Driver Version: 535.288.01 CUDA Version: 12.2 Avant : NVIDIA-SMI 575.51.03 Driver Version: 575.51.03 CUDA Version: 12.9

Je viens de finir le gros ménage … # wc -l /etc/pve/firewall/*.fw 12 /etc/pve/firewall/104.fw 9 /etc/pve/firewall/116.fw 42 /etc/pve/firewall/124.fw 20 /etc/pve/firewall/126.fw 9 /etc/pve/firewall/127.fw 13 /etc/pve/firewall/129.fw 5850 /etc/pve/firewall/cluster.fw

Rollback

Mise à jours de Ollama : # curl -fsSL https://ollama.com/install.sh | sh >>> Cleaning up old version at /usr/local/lib/ollama >>> Installing ollama to /usr/local >>> Downloading ollama-linux-amd64.tar.zst ######################################################################## 100.0% >>> Adding ollama user to render group... >>> Adding ollama user to video group... >>> Adding current user to ollama group... >>> Creating ollama systemd service... >>> Enabling and starting ollama service... >>> NVIDIA GPU installed. Visiblement même problème : ... juin 19 10:51:37 ollama[2964]: time=2026-06-19T10:51:37.153Z level=INFO source=model_list_cache.go:111 msg="model list cache hydration complete" models=16 failures=0 elapsed=654.370427ms juin 19 10:51:42 ollama[2964]: time=2026-06-19T10:51:42.591Z level=WARN source=cuda_compat.go:38 msg="NVIDIA driver too old" device="Quadro M5000" compute=5.2 driver=535 required_driver="570 or newer" juin 19 10:51:42 ollama[2964]: time=2026-06-19T10:51:42.591Z level=WARN source=cuda_compat.go:38 msg="NVIDIA driver too old" device="Quadro M4000" compute=5.2 driver=535 required_driver="570 or newer" juin 19 10:51:43 ollama[2964]: time=2026-06-19T10:51:43.181Z level=INFO source=types.go:32 msg="inference compute" id=1 filter_id=1 library=Vulkan compute=0.0 name=Vulkan1 description="Quadro M4000" libd> juin 19 10:51:43 ollama[2964]: time=2026-06-19T10:51:43.181Z level=INFO source=types.go:32 msg="inference compute" id=0 filter_id=0 library=Vulkan compute=0.0 name=Vulkan0 description="Quadro M5000" libd> ...

J’ai supprimé les commandes hostpci : # grep "hostpci" /etc/pve/qemu-server/*.conf /etc/pve/qemu-server/100.conf:#hostpci0: 0000:01:00.0,rombar=0 /etc/pve/qemu-server/100.conf:#hostpci1: 0000:01:00.1,rombar=0 Et maintenant j’ai plus de suppression du drivers : # networkctl | grep "enp" systemd-networkd is not running, output might be incomplete. 2 enp1s0f0 ether - unmanaged 3 enp0s31f6 ether - unmanaged 4 enp1s0f1 ether - unmanaged # dmesg | grep "igb" [ 1.695998] igb: Intel(R) Gigabit Ethernet Network Driver [ 1.695999] igb: Copyright (c) 2007-2014 Intel Corporation. [ 1.696010] igb 0000:01:00.0: enabling device (0000 -> 0002) [ 1.878837] igb 0000:01:00.0: added PHC on eth0 [ 1.878861] igb 0000:01:00.0: Intel(R) Gigabit Ethernet Network Connection [ 1.878862] igb 0000:01:00.0: eth0: (PCIe:2.5Gb/s:Width x4) 90:e2:ba:08:85:50 [ 1.879161] igb 0000:01:00.0: eth0: PBA No: G18758-003 [ 1.879162] igb 0000:01:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s) [ 1.879174] igb 0000:01:00.1: enabling device (0000 -> 0002) [ 2.061778] igb 0000:01:00.1: added PHC on eth2 [ 2.061797] igb 0000:01:00.1: Intel(R) Gigabit Ethernet Network Connection [ 2.061798] igb 0000:01:00.1: eth2: (PCIe:2.5Gb/s:Width x4) 90:e2:ba:08:85:51 [ 2.062101] igb 0000:01:00.1: eth2: PBA No: G18758-003 [ 2.062102] igb 0000:01:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s) [ 2.292065] igb 0000:01:00.1 enp1s0f1: renamed from eth2 [ 2.292529] igb 0000:01:00.0 enp1s0f0: renamed from eth0 [ 7.030374] igb 0000:01:00.0 enp1s0f0: entered allmulticast mode [ 7.030413] igb 0000:01:00.0 enp1s0f0: entered promiscuous mode [ 9.314164] igb 0000:01:00.0 enp1s0f0: igb: enp1s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [ 121.086711] igb 0000:01:00.0 enp1s0f0: igb: enp1s0f0 NIC Link is Down [ 155.491157] igb 0000:01:00.0 enp1s0f0: igb: enp1s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX

J’ai bien le dernier : # composer self-update Upgrading to version 2.9.5 (stable channel). Use composer self-update --rollback to return to version 2.8.9

J’ai ajouté des IP : # grep "/.well-known/acme-challenge/" /var/log/apache2/acces*log | sed 's/:/ /g' | awk '{print $2}' | sort | uniq -c 3 13.53.57.129 1 13.59.218.195 1 13.62.228.137 1 16.146.60.234 1 23.178.112.103 1 23.178.112.104 1 23.178.112.107 1 23.178.112.213 1 3.16.22.70 1 52.13.93.231

C’est bon ! # df -h Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur udev 12G 0 12G 0% /dev tmpfs 2,3G 560K 2,3G 1% /run /dev/sda1 108G 25G 79G 24% / tmpfs 12G 0 12G 0% /dev/shm tmpfs 5,0M 0 5,0M 0% /run/lock tmpfs 2,3G 0 2,3G 0% /run/user/1000

Je ne comprends pas … j’ouvre un bugs : https://github.com/rtuszik/photon-docker/issues/210

Check /etc/pve/lxc/*.conf : lxc.apparmor.profile: unconfined lxc.cgroup.devices.allow: a lxc.cap.drop:

J’ai du mal à voir : # /usr/sbin/parted -l Model: ATA QEMU HARDDISK (scsi) Disk /dev/sda: 64,4GB Sector size (logical/physical): 512B/512B Partition Table: loop Disk Flags: Number Start End Size File system Flags 1 0,00B 64,4GB 64,4GB ext4 Model: ATA QEMU HARDDISK (scsi) Disk /dev/sdb: 85,9GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 1 1049kB 63,4GB 63,4GB primary ext4 boot 2 63,4GB 64,4GB 1022MB extended 5 63,4GB 64,4GB 1022MB logical linux-swap(v1) swap

Sur un seul jours, j’ai 11617 blocage IP… # cat /var/log/pve-firewall.log | sed 's/2025:/2025 /g' | awk '{print $3 " " $4}' | grep "GROUP" | sort -n | uniq -c 11617 GROUP-attack-IN 01/Dec/2025 2 GROUP-attackmail-IN 01/Dec/2025 4417 GROUP-ccbot-IN 01/Dec/2025 10 GROUP-honeypot-IN 01/Dec/2025 30 GROUP-huawei-IN 01/Dec/2025 7 GROUP-russian-IN 01/Dec/2025

Je viens de modifier la configuration : ErrorLog ${APACHE_LOG_DIR}/error.munin.log # CustomLog ${APACHE_LOG_DIR}/access.munin.log combined LogFormat "%a %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" common2 CustomLog ${APACHE_LOG_DIR}/access.munin.log common2 J’ai mis ‘%a’ à la place de ‘%h’

L’IP a bloqué en priorité : 2.57.121.148 .

Ma version : # cat /etc/os-release NAME="Oracle Linux Server" VERSION="8.10" ID="ol" ID_LIKE="fedora" VARIANT="Server" VARIANT_ID="server" VERSION_ID="8.10" PLATFORM_ID="platform:el8" PRETTY_NAME="Oracle Linux Server 8.10" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:oracle:linux:8:10:server" HOME_URL="https://linux.oracle.com/" BUG_REPORT_URL="https://github.com/oracle/oracle-linux" ORACLE_BUGZILLA_PRODUCT="Oracle Linux 8" ORACLE_BUGZILLA_PRODUCT_VERSION=8.10 ORACLE_SUPPORT_PRODUCT="Oracle Linux" ORACLE_SUPPORT_PRODUCT_VERSION=8.10

Miracle cela fonctionne : # node app.js Starting wizard... ✓ Path to WordPress export file? /root/import/cyberneurones.WordPress.2025-09-22-3.xml ✓ Put each post into its own folder? Yes ✓ Add date prefix to posts? Yes ✓ Organize posts into date folders? Year and month folders ✓ Save images? All Images Parsing...

38.211.193.130 => Argentina

J’ai bloqué le range de FBW Networks SAS : 185.177.72.0/24

Pour Ubuntu : # apt-get install libsystemd-dev