Search results

I still have the problem. Please help.

Any idea please? Thanks

@Neobin @pschonmann I'd tried the workaround without any success. The issues continue happening. I notice it happening only under heavy network loads. Under low load, it is not happening.

Hello, Still need help as the issue still on going. Thanks. Guillaume

Hello, After a fresh install, Proxmox is loosing his connectivity and showing this on console: If hit the return key it ask me to login so the host is not frozen. The NIC is an Intel one. The issue wasn't happening before in previous versions of Proxmox VE. Thanks, Guillaume

@Chris Good news, backup task who seem hanging or something is not there anymore and the WebUI is now back to normal. To answer the question if the VM was still running, yes that VM never stops and also I wish to add that I had hard time to fetch the status of all the other VMs on the host...

I thought that it was still running as it's still showing in the webUI. And still tried to stop the backup process from the WebUI, some part aren't loading: And it lead to communication failure. But, the WebUI is not down, I can access some other parts. For the backup task this is what...

The task seem still running: │ pve-004-dc │ 3566291 │ 339398990 │ 1673514005 │ vzdump │ UPID:pve-004-dc:00366AD3:143AD14E:63BFCC15:vzdump::root@pam: │ root@pam │ 1673533773 │ unexpected status pvesh delete...

Yes, I've got timeouts. The command seem returning no UPID. I attach the output to this message. Thank-you, Guillaume

Yes it works now, the backup process kick in by itself. Also, I had to stop backup process on another host and now the host's WebGUI seem to hang, how to kill the backup process completely, I did the kill PID command but it seem to be stuck. Thank-you, Guillaume

I updated the duplicated link. Thank-you

I wrote the results to file except the last one, I'd pasted here. journalctl -b ps auxwf strace -yyttT -f -s 512 -p 1145 strace: Process 1145 attached 12:39:35.473433 read(9<pipe:[25032]>, Thank-you, Guillaume

No, I see no errors. Just a thing, when booting the host I had to stop the starts of the VMs which normally starts by themself with a delay of 60 seconds in interval. Is the issue can be caused because I interrupted the starting sequence of the VMs? Guillaume

pve-guests.service seem not running. ● pve-guests.service - PVE guests Loaded: loaded (/lib/systemd/system/pve-guests.service; enabled; vendor preset: enabled) Active: activating (start) since Thu 2023-01-05 15:48:51 EST; 4 days ago Process: 1144...

Good morning, journalctl -b -u pvescheduler.service returns journalctl -b -u pvescheduler.service -- Journal begins at Fri 2022-04-15 12:31:55 EDT, ends at Tue 2023-01-10 04:54:52 EST. -- -- No entries -- and systemctl status pvescheduler.service reports the service as dead. systemctl...

Hello, I notice that my automated backups wasn't going through. After reading, it is related to Pvescheduler who wasn't running. The problem is I can't start the service with: systemctl start pvescheduler.service Using the WebGUI doesn't work either. It loads forever: It can hang for...

Okay, that good, I will give this a try. However, I rarely need to reboot hosts, the only time I do need to do so is when I'm making hardware upgrades. Even power outages aren't affecting the servers because I do have standby generators. Startup order/delays will be very useful in my case...

Hello, If I'd setup a start/shutdown order, is that mean the value for the delay could be 60 everywhere instead of 60, 120, 180? Guillaume

Hello, I just want to confirm if my setup is correctly configured. For the first VM in Startup delay field I'd put nothing, the second one I'd put 60, the third one 120, the fourth one 180 till I reach the last one whom is set to 900. I red the documentation but it is not clear to me. Best...

Still good. The previous NIC was probably bad.