Latest activity
-
Ddamrod replied to the thread Minor apparmor problem with tor.Is it a fix or is it a workaround for the time being, until the kernel supports ABI 4.0? I understand it's a workaround.
-
Ppiotrpierzchala replied to the thread New Import Wizard Available for Migrating VMware ESXi Based Virtual Machines.Hi, After applying workaround from this (link) proxmox forum post, I was able to start import with "Live Import" while VM being powered OFF on VMware side. However, when I try to power ON that VM on VMware side after few seconds/minutes the...
-
fiona replied to the thread Minor apparmor problem with tor.Adding abi <abi/3.0>, profile system_tor flags=(attach_disconnected) { .... to the beginning of /etc/apparmor.d/system_tor and running systemctl reload-or-restart apparmor.service seems to fix the issue for tor too :) -
OOnslow replied to the thread Zabbix integration into Proxmox facing several error & problems.@julwonn: After 3 minutes of googling I doubt you should use port 10050. This port is for systems running zabbix_agent. AFAICS, Meraki uses HTTP API, not zabbix_agent. Have you read e.g. https://www.zabbix.com/integrations/meraki ?
-
Mmaikverheijen reacted to readyspace's post in the thread [SOLVED] VLAN trunk with LACP in Proxmox (OPNsense virtualization) with
Like.
Hi, sounds like a tagging mismatch between Proxmox and OPNSense. You need to do bonding first — create LACP bond (mode 802.3ad) → bridge it to VLAN-aware vmbr → connect OPNSense VM NIC (no VLAN tag). Then do VLANs (10/20/30/40) inside OPNSense... -
Mmaikverheijen replied to the thread [SOLVED] VLAN trunk with LACP in Proxmox (OPNsense virtualization).Thanks so much in advance! I read your message and it really gave me the nudge I needed. I think I just need to follow your steps and not create a LAGG in OPNsense itself (next to the one in proxmox), pretty sure that’s where I messed up last...
-
Nness1602 replied to the thread Opt-in Linux 6.17 Kernel for Proxmox VE 9 available on test & no-subscription.Tested on 3 machines, bcachefs also works :)
-
readyspace replied to the thread not even nomodeset works?.Hi, looks like your installer is stuck during USB device initialization — the usb 1-5: device descriptor read/64, error -32 messages usually mean the installer can’t properly read from the USB stick or the USB controller is having trouble. Try... -
Aabobakr replied to the thread VM keeps freezing on PVE 9 kernel 6.14.11-2.Hello Advin, Do you still got this problem? if you still have this issue then please provide pvereport for double checking. On the command line run: pvereport > $(hostname)-report.txt The resulting TXT file can then be copied off the server, for...
-
readyspace replied to the thread Zabbix integration into Proxmox facing several error & problems.This isn’t a Proxmox issue — it’s between Zabbix and the Meraki API. The problem usually comes from API authentication, Org ID, or network/DNS reachability from your VM to api.meraki.com. Start by testing API access directly from the VM with...
-
Rroger.r replied to the thread Sicherung auf USB?.Mit diesem Script lasse ich die angeschlossene HDD auswerfen, sofern sie angeschlossen ist. Wie oben schon erwähnt, erfolgt dies unmittelbar nachdem der Sync-Job abgeschlossen ist, sofern dieser noch läuft. #!/bin/bash HDD=("HDD-Jan" "HDD-Feb"...
-
-
fiona replied to the thread Minor apparmor problem with tor.Quoting @fabian from the bugzilla entry:
-
Jjsh replied to the thread Replace orphaned PVE.i want to know how to restore the existed proxmoxVE it was drop out and i did ssh generate that why plz tell me
-
Ssensei_pv reacted to HomeSecExplorer's post in the thread Proxmox server hardening document for compliance with Like.
Hi y’all, I’ve released a Proxmox hardening guide (PVE 8 / PBS 3) that extends the CIS Debian 12 benchmark with Proxmox specific tasks. Repo: https://github.com/HomeSecExplorer/Proxmox-Hardening-Guide A few controls are not yet validated and are...
-
OOnslow replied to the thread Zabbix integration into Proxmox facing several error & problems.Execute from the command line shell of the Zabbix server: telnet ip.address.of.meraki 10050 (replace ip.address... with the IP address of that Meraki device) and post the result.
-
fiona replied to the thread Recurring errors in System Log.Could you share a longer excerpt of the system journal? How often does the message occur? Does /var/log/pveproxy/access.log contain any mention of the other nodes?
-
readyspace reacted to FSNaval's post in the thread CEPH Configuration: CephFS only on a Specific Pool? with Like.
Thank you! Above is my use case, since it resembles the current state i currently work, and believe that migrating from single docker node to a docker swarm cluster (keeping the same compose files properly amended for docker swarm will require...
-
l.leahu-vladucu replied to the thread Slow memory leak in 6.8.12-13-pve.The opt-in kernel 6.17 is now available for Proxmox VE 9.0 in the pve-test and pve-no-subscription repositories, if you would like to test it (official announcement of kernel 6.17 will come soon EDIT: added link to announcement post). Currently... -
JJohannes S reacted to LnxBil's post in the thread S.M.A.R.T tests in Proxmox – best practice? with Like.
Yes, neither does any system I know. You need I/O predicability, so running stuff in the background is a no-go for an enterprise. A scrub is the real world metric you need. SMART is not that good at predicting failures. I don't run SMART tests...
-
After more than a week, and ~100 migrations done by ProxLB, no more issue.
