i have 1 customers VPS which use to many hard disk resources, i mean I/O and another VPS did not work fine. How to limit VPS hdd? I would like to mention that ioprio did not work as i want, and i dont see the results :/
I need replies as soon as possible to solve this problem.
i have few questions:
How to grab VE's information like: HDD, RAM (for example: 10/30GB (30%), 512/1024MB (50%) and not to hang servers with statistics :)
I need them because i would like to include it to my customers page :)
i have a big trouble with my hardnode. Today it crashes two times with Kernel Panic, without exact problem. How can i fix it or how can i got logs about kernel panic? :( Because in /var/log/messages /var/log/debug /var/log/kern no info.
echo:~# pveversion -v
my machine crash and fails to boot after reboot. I do not know what the exactly happens but all my servers with this configuration after reboot crashes.
omega:~# pveversion -v
pve-manager: 1.5-7 (pve-manager/1.5/4660)
running kernel: 2.6.18-2-pve
i have a problem with one of my customers, he use all my bandwidth, so i would like to limit his VPS upload/download rate to 10 Mbit/s.
I did that with this http://wiki.openvz.org/Traffic_shaping_with_tc last code, but:
after limit, other my customers feel greater delay ping (actually...
i have upgraden from 1,4 to 1,5 ProxMox, and i have strange problem with uptime. Proxmox shows that VPSes are alive more than 1 Hour, but Hardnode is alive only 15 minutes, only KVM shows true time.
In Administration -> Cluster - TIME OK
In VM Manager -> Virtual Machines - TIME...
i have problem with my VE's. I had installed 18 and i had disabled that kernel because it didint work properly, so i returned to 2.6.24-9-pve..
So the problem is: my VE after reboot command didint boot back, it show mounted. I need to umount and start by myself.
beta:~# pveversion -v...
i have problems with VPS reboot.. When I type "reboot" in VE machine, VPS didint reboot, but turns off SSH and send message: "vps139:~# reboot
Broadcast message from root@vps139 (pts/0) (Mon Jan 4 10:33:23 2010):
The system is going down for reboot NOW!
If i reboot via...
how to install pve 1.4 not 1.5 but only 1.4 because six my nodes are using pve 1.4 with x.x.18 kernel with cpu and cpulimit capabilities and i dont want to upgrade to 1.5 because need reboot and my uptine would be lower..
i checked my dmesg logs, and i have found these lines:
NETDEV WATCHDOG: eth0: transmit timed out
r8169: eth0: link up
How to fix?
This problem persists from 2 to 10 times per day, starting from the day before yesterday..
one or more of my VPS customers are using a lot of international roaming (at the moment - all) and i have problem, for example: apt-get update takes about 10 minutes... How to find a pest? How to track traffic?