Search results

I keep getting hundreds of these lines in my syslog - also net_ratelimit: 4655 callbacks suppressed when this happens I seem to get getting network disruption as well which connections hanging etc. how can I diagnose where the issue is? here is my network config auto lo iface lo inet...

This is a non-root filesystem but I cannot umount it once the system is up and running. (even using init 1 I could still not unmount it, lsof didn't appear to tell me what was using it) so I have tried to force a fsck on boot, but using tune2fs -c 1 /dev/sdXY on the relevant partition does not...

For anyone else wanting to do this the easiest way I found is to do a fresh install of proxmox on the new disks and then reboot back to the original os and doing zfs send/receive from the old rpool to the new rpool (easier than restoring 30+ backups) you have to rename the new rpool whilst doing...

thanks - managed to hold off doing this until now. I pretty much know how to do the zpool send recv and how to create a new rpool but can you expand on how I should create the partitions and set it bootable. looking at the current disk its a gpt table Units: sectors of 1 * 512 = 512 bytes...

NB I have temporarily replaced the failed one with another consumer ssd I had spare but want to replace both with the 480gb enterprise ssds.

Hi, I have 2 ssds in a zfs mirror 500gb for my rpool. One disk failed recently (consumer cosair - only lasted about 5 months) I bought two enterprise ssds to replace the failed one. These are only 480gb (didn't check when ordering so my fault!) Ideally I do not want to have to reinstall as its...

hmm guess its probably caused by this [549694.775318] BUG: kernel NULL pointer dereference, address: 0000000000000014 [549694.775471] #PF: supervisor read access in kernel mode [549694.776082] #PF: error_code(0x0000) - not-present page [549694.776832] PGD 0 P4D 0 [549694.777561] Oops: 0000 [#1]...

trying to start it again fails with this Mar 15 15:45:47 pve systemd[1]: pvestatd.service: Processes still around after final SIGKILL. Entering failed mode. Mar 15 15:45:47 pve systemd[1]: pvestatd.service: Failed with result 'timeout'. Mar 15 15:45:47 pve systemd[1]: Failed to start PVE Status...

My instance of proxmox seems to be working fine (all vms'v conatiners are running fine. However when going to the the web interface It just shows question marks against everything. Its happened twice in the last week so not sure if it related to a recent update? rebooting fixed it last time...

Hi, did either of you manage to do this?

@tobox added to github - builds in vs 2017 not tested in other versions so far https://github.com/toby11/windows-promox-spice-viewer

@tobox yes sure I'll get it on github, will let you know once its on there

yes using it here with 6.1-5 :)

is this still an issue? I have a container with a mount point thats doing very heavy disk io and the disk IO graph shows nothing? Does it just affect mountpoints?

Ok thanks I will have a read up on it. Now I know what the issue is though I may be able to work around it and remove the port forwarding as it seems less complicated from a firewall point of view. thanks again for your help.

yes your right from running the same init script on my test machine this line /sbin/iptables -t nat -A POSTROUTING -j MASQUERADE breaks everything! Is there a preferred way to do port forwarding in this kind of scenario? (I assume its not something that can be done in the proxmox ui?)...

-A PREROUTING -p tcp -m tcp --dport 3306 -j DNAT --to-destination 192.168.128.95:3306 -A PREROUTING -p tcp -m tcp --dport 5001 -j DNAT --to-destination 192.168.128.69:5001 -A PREROUTING -p tcp -m tcp --dport 5002 -j DNAT --to-destination 192.168.128.69:5002 -A POSTROUTING -j MASQUERADE -A...

yes thats what I thought. here you go # Generated by iptables-save v1.8.2 on Tue Nov 5 17:08:00 2019 *nat :PREROUTING ACCEPT [112831:46427489] :INPUT ACCEPT [987:87755] :OUTPUT ACCEPT [10901:5706860] :POSTROUTING ACCEPT [0:0] -A PREROUTING -p tcp -m tcp --dport 3306 -j DNAT --to-destination...

Interestingly I have another test proxmox system on the same exact version which should be setup in the same way but that one does not have this issue.

I tested the conntrack -F but it didn't do anything I still had to reboot to fix it. I have also tried leaving the dc/node level firewall turned on and then rebooting to see if that worked but the same situation. Just done some more testing and when the firewall is turned on : Inbound...