J
james.cookie
Guest
Hi,
I am having a problem with a proxmox server and its VM's. The problem is that the VM's stop responding after a few hours (sometimes they will stay up for a couple of days, sometimes only a few hours). I have a cron job running to record the time every minute so that I can see how long each VM stays up for and also external monitoring to let me know when it goes down.
Every time it enters this state and I SSH to it to see what's going on, I notice that the system clock has moved on a few centuries as this is amongst the messages when I log on:
Then it's asking me to change my password as it has (unsurprisingly) expired. A quick "Reset" through the UI and everything is back to normal.
Obviously having to reset this VM's is getting annoying and I want to find a solution.
In order to see if it was a proxmox software problem I set up a test machine with the same OS as the others (Ubuntu Server 10.04) and accessed just via the VNC console. I did not install anything (so just a vanilla server) and added the same cron job to record a timestamp. This machine has never had the problem, which leads me to conclude that it must be something I have installed on the machines. However, I have another proxmox server running a similar set of VM's and never had a problem.
The only things I have installed on the VM's are as follows (and all the dependencies):
VM1
openssh-server
openjdk-6-jre-headless
tomcat6
apache2
libapache2-mod-jk
mailutils
VM2
openssh-server
openjdk-6-jre-headless
tomcat6
postgresql
The proxmox version is:
I'm hoping someone out there has had a similar problem and can point the way to some help!
Regards
James
PS. I have already checked my clock source: cat /sys/devices/system/clocksource/clocksource0/current_clocksource: kvm-clock
I am having a problem with a proxmox server and its VM's. The problem is that the VM's stop responding after a few hours (sometimes they will stay up for a couple of days, sometimes only a few hours). I have a cron job running to record the time every minute so that I can see how long each VM stays up for and also external monitoring to let me know when it goes down.
Every time it enters this state and I SSH to it to see what's going on, I notice that the system clock has moved on a few centuries as this is amongst the messages when I log on:
Code:
System information as of Mon May 30 04:39:20 BST 2596Then it's asking me to change my password as it has (unsurprisingly) expired. A quick "Reset" through the UI and everything is back to normal.
Obviously having to reset this VM's is getting annoying and I want to find a solution.
In order to see if it was a proxmox software problem I set up a test machine with the same OS as the others (Ubuntu Server 10.04) and accessed just via the VNC console. I did not install anything (so just a vanilla server) and added the same cron job to record a timestamp. This machine has never had the problem, which leads me to conclude that it must be something I have installed on the machines. However, I have another proxmox server running a similar set of VM's and never had a problem.
The only things I have installed on the VM's are as follows (and all the dependencies):
VM1
openssh-server
openjdk-6-jre-headless
tomcat6
apache2
libapache2-mod-jk
mailutils
VM2
openssh-server
openjdk-6-jre-headless
tomcat6
postgresql
The proxmox version is:
Code:
# pveversion -v
pve-manager: 1.9-24 (pve-manager/1.9/6542)
running kernel: 2.6.32-6-pve
pve-kernel-2.6.32-6-pve: 2.6.32-43
qemu-server: 1.1-32
pve-firmware: 1.0-13
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.28-1pve5
vzdump: 1.2-15
vzprocps: 2.0.11-2
vzquota: 3.0.11-1dso1I'm hoping someone out there has had a similar problem and can point the way to some help!
Regards
James
PS. I have already checked my clock source: cat /sys/devices/system/clocksource/clocksource0/current_clocksource: kvm-clock
