Search results

Hey there, found the issue. One of the SystemSSD war failing, so the IO Load was beyond good and evil. Swapping the SSD fixed everything.

Okay, a new update. After making sure no process is running I noticed: apt-update takes 30 Minutes to fetch all! That is way to long ... I'll change some sources maybe :/

Thats the Problem ... nothing is locked! When I remove all sources from the apt list its working fine. It seems to me that my Proxmox is not able to proccess the packages

Heyho, sorry for the late reply! Private life was turbulent :eek: root@proxmox1:~# ps aux | grep "apt\|dpkg" 100000 2209312 0.0 0.0 4476 2176 ? S 10:03 0:00 /bin/bash ./mk_apt 100000 2209313 0.0 0.0 4476 1276 ? S 10:03 0:00 /bin/bash ./mk_apt 100000...

Hey there, nope, nothing more as Repos :(

Hey there, for a couple of days my proxmox Hypervisor isn't able to update apt :confused:. This is my current output: E: Could not get lock /var/lib/apt/lists/lock. It is held by process 3885896 (apt-get) N: Be aware that removing the lock file is not a solution and may break your system. E...

Interesting to see that I'm not the only one facing this issue. It's really crazy. Wny Updates on that?

They are several SSDs, but its true, not datacenter SSDs, that were consumer SSDs from old Lenovo Notebooks. But I'm not quite sure, is was from one day to another on 4 different machines after the update

Hey everyone, I got some weird issues now on multiple servers here. The Problem is that my IO Load is high in 25% - 80% and the write Speed on the SSDs are ~20 MByte/s. I noticed it now that I reinstalled it on a server running pve 6.3 and upgraded to 7.4. Proxmox was always installed on ZFS...

Thanks for the command: I guess I found the reason why everything is breaking: May 02 13:21:18 proxmox2 pvedaemon[2063469]: <root@pam> successful auth for user 'root@pam' May 02 13:21:33 proxmox2 zed[2238072]: eid=30 class=checksum pool='rpool' vdev=nvme-eui.8ce38e100037bcf3-part3...

Hello everyone, sorry for the small amount of details but at the moment I don't have any clue how to debug it. For two Days my Proxmox Nodes lockes completly up when a backup Job is done. The only way to get my systems back running is with: systemctl --force --force reboot How should I...

Hey everyone, I'm having now a weird issue after setting up VLANs on my Hypervisor and pfSense. Following Network config is currently running: auto lo iface lo inet loopback auto enp3s0 iface enp3s0 inet manual iface enp2s0 inet manual iface enp4s0 inet bridge-pvid 100 iface...

There was a typo from myside. My client is connected on enp4s0, not enp5s0. Beside that, after some digging I found a different term. My Goal was it to set a different "native" VLAN. ... Seeing this with some typos was the issue. Now my Windows Client is in the desiered VLAN and receiving the...

So on my proxmox host is a pfsense VM with one bridge vmbr0, in pfsense it is called vtnet0. First step was to add VLANID 7 on vtnet 0 because this is the VID needed to use PPPoE on our VDSL. After that I created two VLANs, the test VLAN 22 and VLAN 100, which should be my internal System. Then...

Sadly no, the client on that is connected doesn’t get an connection into this VLAN :(

Thanks for that, and how do I get this untagged pvid 22 into vmbr0 ? Or is that happening automaticly?

True, but the issue this time was a missing reboot of the proxmox node. Then the vmbr was really VLAN aware.

The config of the pfsense is not posted. DHCP is enabled an all devices, and after the reboot of the host the container got the desired IP Address :)

Sometimes the solution is far more easier then I thought. After making the bridge VLAN Aware I didn't reboot the host. After rebooting that everything works as intented.

Hey everyone, sorry for this basic question but I guess there is something missing in my mind setting up correctly my VLANs. My current goal is to connect a LXC Container via VLAN ID 5 to my pfsense. My current Interface settings on my hypervisor is: auto lo iface lo inet loopback auto...