Search results

Is there still no fixes on this issue? I'm still seeing it now even with the latest version. # pveversion -v proxmox-ve: 4.4-79 (running kernel: 4.4.35-2-pve) pve-manager: 4.4-12 (running version: 4.4-12/e71b7a74) pve-kernel-4.4.35-2-pve: 4.4.35-79 pve-kernel-4.2.2-1-pve: 4.2.2-16 lvm2...

I have same issue as https://forum.proxmox.com/threads/cant-do-anything-with-container.29964/ I'm running latest version already, how do I kill the pct? pct list shows running, tried lxc-stop -W -k still running for hours, not actually stopping it. Tried shutdown from GUI and error "TASK ERROR...

I too have same issue, I'm running latest version already, how do I kill the pct? pct list shows running, tried lxc-stop -W -k still running for hours, not actually stopping it. Tried shutdown from GUI and error "TASK ERROR: command 'lxc-wait -n XXX -t 5 -s STOPPED' failed: exit code 1" #...

# pveversion pve-manager/4.4-5/c43015a5 (running kernel: 4.4.35-2-pve)

Anyone has any ideas why when using a debian or ubuntu templates from openvz, it gets setup just fine, and IP shows up when you do ifconfig inside CT, but no ping, no access from outside. If we use debian turnkey templates and centos templates from openvz v3.4, it does work fine. Just no other...

Currently, the node has SSD-cached HW RAID setup, so I plan to change it to SSD HW RAID, so if I setup a new server with SSD RAID and new IP, and after I did upgrade to match the proxmox version, can I just then do rsync on / from the current SSD-cached node to the new SSD RAID node? What's...

It's an upgrade from 3.1 to now 3.4, have been searching but the only other solutions suggested that I have not tried is remove/install pve-manager and adding loopback to /etc/network/interfaces. need suggestions from someone if it is safe to do that or not on a cluster.

Yes, thanks for reply, the only thing have not tried is reinstall pve-manager as suggested on other thread, not sure if it'll be safe to do it on a cluster node or not There's also another thread about adding loopback in interfaces, not sure on the correct entry to add.

If the node has cluster, is it safe to just remove and reinstall pve-manager via the command below? apt-get remove pve-manager apt-get install pve-manager been getting login failed to web interface also every 24 hours, try restarted all services with no luck. only fixed was to reboot whole...

# pveversion -v proxmox-ve-2.6.32: 3.4-166 (running kernel: 2.6.32-43-pve) pve-manager: 3.4-13 (running version: 3.4-13/4c745357) pve-kernel-2.6.32-39-pve: 2.6.32-157 pve-kernel-2.6.32-43-pve: 2.6.32-166 lvm2: 2.02.98-pve4 clvm: 2.02.98-pve4 corosync-pve: 1.4.7-1 openais-pve: 1.1.4-3 libqb0...

the node has cluster, someone mentioning to reinstall pve-manager, is it safe to just remove and reinstall pve-manager? apt-get remove pve-manager apt-get install pve-manager

already did apt-get update and apt-get upgrade then reboot yesterday, only worked for few hours then Login Failed again to web interface. No firewall is setup.

out of mutiple proxmox nodes, seems only 1 node with over 1060 openvz/kvm vps keep getting error Login Failed from time to time, when trying to access the proxmox GUI, have tried restarting below services but still no luck, only workaround seems to reboot the whole node. But it happens again...

Thank you but it was actually a ram issue, wish it would give out more info on errors, instead of just blinking cursor. it was ecc ram, not sure why it would suddenly caused blinking cursor.

this node been working for few months and was just rebooting it this morning after some kernel updates, and during the starting up one of the CT, it just stuck, keyboard not responding, ping stopped responding, so had no choice than to power it off and power on again. Now after got the grub...