Search results

Hi guys, I am getting this error very 20mins on my system running proxmox 1.9 kernel:EDAC MC0: UE row 0, channel-a= 0 channel-b= 1 labels "-": NON-FATAL recoverable (Branch=0 DRAM-Bank=0 Buffer ID = 0 RDWR=Read RAS=0 CAS=0 NON-FATAL recoverable Err=0x10000800 (Non-Aliased Uncorrectable Patrol...

I guess my question is that: in order to solve my main issue, should I keep the size to the default 1024MB or should I increase it from the initial 2048MB I had to say 4096MB in /etc/vzdump.conf ?

Ok I did it. 1. how can I confirm that my issue is resolved? And what is the actually issue? 2. Also originally I had set "size: 2048" in my /etc/vzdump.conf. But after the initial backup issues (see beginning of this thread) I removed that line and the backup was able to start but stalled the...

I am not sure I fully understand what you are suggesting that I do. Here is the output of lvs: lvs /dev/dm-5: read failed after 0 of 4096 at 0: Input/output error /dev/dm-7: read failed after 0 of 4096 at 0: Input/output error LV VG Attr LSize Origin Snap%...

The server was not very responsive. The reboot command wouldn't go through. I had to hard reboot the server by shutting down the power and reboot this way. I made it skip the fsck but it still took a very long time to boot the 7 containers we have on there. Something is wrong, things are a...

Right now the server would not even reboot it. It is showing: Load: 694.08 CPU: 0% IODelay: 61% And all containers are stalled on their max memory. Any idea what could be the cause of this issue?

Definitely not my lucky day. I started the backup of the openvz containers but a backup that usually takes less than 6 hours has now been running for over 14 hours and slowing the server down. Any idea why I am having these issues?

Nevermind I fixed it by removing the "size: 2048" line from the /etc/vzdump.conf file.

Since we upgraded from proxmox 1.2 to proxmox 1.9, the scheduled backup no longer works. We get the following error, any idea why and why we need to do to fix it? command 'lvcreate --size 2048M --snapshot --name vzsnap-proxmox1-0 /dev/pve/data' failed with exit code 5

Not sure. You might have to run the update on each individual node.

Most likely. But I doubt you'll be able to upgrade the OS from Debian Lenny to Squeeze without doing a fresh install.

Thanks. I completely removed all the block for vmbr0.

Oh I noticed that my issues even after renaming was that I was still using x86_64. Proxmox should be clear saying that for 64bit the architecture has to be named amd64 and not x86_64.

Hi, I have a server running proxmox 1.9 and I am only interested in running OpenVZ. Is it safe to disable the default bridge vmbr0:0 as follows? auto vmbr0:0 iface vmbr0:0 inet static

Any reason why: 1. There is no Centos 6 openvz template available in proxmox 1.9 although they are available on the openvz website? Especially when even after renaming the downloaded template it still fails to upload to the proxmox interface? 2 and most of the proxmox template seem to be only...

Re: FATAL: Could not load /lib/modules/2.6.32-7-pve/modules.dep: No such file or dire Wow.. this did the trick. Thank you for the suggestion… problem solved.

Re: FATAL: Could not load /lib/modules/2.6.32-7-pve/modules.dep: No such file or dire the container is running Centos 5.x After the upgrade and restarting the hardware node, the svn web console which uses java and apache is failing to launch.. So our web access to the svn server is no longer...

Re: FATAL: Could not load /lib/modules/2.6.32-7-pve/modules.dep: No such file or dire On our of my virtual servers we were running the collabnet subversion edge application. After upgrading Proxmox from 1.2 to 1.9 the (java-apache) console stopped working. I am trying to understand if...

Re: FATAL: Could not load /lib/modules/2.6.32-7-pve/modules.dep: No such file or dire Thank for clarifying. Does this have any impact on applications running inside a container?

I would like to report that I see the same issue with Proxmox 1.9 after a close look at the boot screen log, except that the message does not show at the very beginning like on Proxmox 2.0. See attached screenshot.