Doh, missed it. Output follows:-
...
Oct 01 16:00:40 pve systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
Oct 01 16:00:41 pve pveproxy[10119]: start failed - unable to create socket - Address already in use
Oct 01 16:00:41 pve...
Output of journalctl -xeu pveproxy.service:-
░░ The job identifier is 5708 and the job result is failed.
Oct 01 16:00:41 pve systemd[1]: pveproxy.service: Consumed 1.261s CPU time, 149.8M memory peak.
░░ Subject: Resources consumed by unit...
There was a typo in the journal command - extra p at the end, did you fix it by chance in your run?
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Hello Stoiko,
A quick update regarding the pci=notph testing.
I started a new test using the same setup:
- kernel 7.0.14-20-pve
- pci=notph enabled
I can confirm that the parameter is active:
BOOT_IMAGE=/boot/vmlinuz-7.0.14-20-pve...
Output of pveversion -v follows. The jounalctl command gave me a No entries response.
proxmox-ve: 9.2.0 (running kernel: 7.0.14-20-pve)
pve-manager: 9.2.21 (running version: 9.2.21/4f6e0ac86f9e8c7f)
proxmox-kernel-helper: 9.2.0...
You can try to run the pveproxy manualy to see the error you are getting:
pveproxy start
or
pveproxy start --debug 1
Looking at the log, as @fabian suggested, should, of course, be the first step.
Blockbridge : Ultra low latency all-NVME shared...
I was hoping to find a solution here. I found the Systems-Management_Application_WMJ1N_LN64_5.4.2.0_A00_02.BIN and installed the dcism and dcism-osc files with no issue. But the service never installed.
systemctl start dcismeng
Failed to start...
Your /etc/resolv.conf is a symlink to systemd-resolved's generated file (as evident by the text at the start), and resolved has no DNS servers, hence "No DNS servers known." Removing the package leaves the symlink behind, pointing at a stale...
Just chiming in and wanting to follow, we also had problems with this. Everything was working great with 7.0.14-19, but not with 7.0.14-20.
Dell Server
Broadcom 57414
Firmware: 23.11.16.22
Ich nutze einen NUC14 135H mit PL1:16W PL2:26W (TAU 56).
Damit ist er gut sparsam und trotzdem leistungsfähig wenn benötigt.
Er kann 2 m.2 (2280/2242), kann 128GB RAM und hat mit den LPE Kernen auch die Möglichkeit VMs sehr stromsparend zu...
Hello all. I ran a kernel upgrade today from within the GUI and it all seemed to go through fine but after rebooting the GUI no longer loads. The server is running and my containers are running but when I run 'systemctl status pveproxy.service' I...
Hi @Nemesiz, it's just a little console tool we wrote for this project. One Python script on top of the Rich library: https://github.com/Textualize/rich.
Strictly read-only: it pulls from /sys/class/net, /proc/stat, /proc/interrupts, the CPPC...
I can basically confirm your findings, we have the following trouble:
7.0.14-20
Network connectivity on an empty host fails after a short time with
================
NETDEV WATCHDOG: CPU x; transmit queue 1 timed out 5700 ms
bnxt_en...
Hi,
I've just updated five Dell hardware- and config-identical Proxmox VE nodes from v8 to 9.2, and while four of them work fine, the fifth one cannot resolve DNS. I cannot therefore apply further updates.
The output of cat /etc/resolv.conf on...
Thanks, I tested pci=notph on the affected pve3 host with 7.0.14-20-pve. Unfortunately, it does not resolve the issue.
The parameter is definitely active:
BOOT_IMAGE=/boot/vmlinuz-7.0.14-20-pve ... pci=notph
PCIe TPH is disabled
However, the...
LVM is not my area of expertise, but here are a few things to try and report back:
1. An open count of 1 on -tpool is normal while the pool is active. It's the internal pool device, held open by the thin LVs and by dmeventd monitoring. lvchange...
Hello Stoiko,
I performed the test with:
pci=notph
and booted again on kernel 7.0.14-20-pve.
The system remained operational longer than before, however the issue eventually reoccurred and the host finally rebooted.
The most interesting...
Ist bei mir nie passiert, aber ich habe auch nur 2x Win10 nach 11 geupgraded. Wenn du beim PVE bereits eine TPM Disk und EFI Disk drin hast, macht er das trotzdem?
see https://forum.proxmox.com/threads/proxmox-ve-9-2-21-bcm57412-bnxt_en-network-failure-after-upgrade-to-kernel-7-0-14-20-pve.186749/ for an issue that might be related.
if possible try booting with `pci=notph` (see the linked thread for other...
Hello,
we are investigating recurring duplicate deliveries on a Proxmox Mail Gateway cluster node. The evidence indicates that a rule-database synchronization triggers SIGUSR1 while a filter worker is reinjecting a message through local Postfix...