Search results

I upgraded all my production ProxMox hosts to 3.1, last night I ran a full set of back-ups on a server that would crash without fail every time. The backup completely successfully, which hasn't happened in about 2 months! I will continue to run backups and alert if there are any other issues...

Thanks Tom / Dietmar, I understand you guys haven't been able to reproduce it, but it's impacting a lot of users on varied setups (judging by all the threads related to the issue.) I'll try to detail my particular situation, it may be useful, I am not sure. I have been running a ProxMox 1.9...

Tom, What do you require for a test case? I can reproduce this issue simply by attempting a manual backup from the command line on my server. Automated backups also fail and take down the server. I have detailed the hardware / logs and issues in several other related threads. I have tried...

The new kernel -108 did not help in my case - just an update, I attempted one single command-line backup with vzdump - results below (mirrored from another thread on same subject) This particular server is a Dell R815 - See below for storage specs. PERC H700, SAS - Proxmox 1.9 worked fine, we...

The new kernel -108 did not help in my case, see also the following thread (which I will update as well) http://forum.proxmox.com/threads/9097-vzdump-using-lvm-snapshot-kills-the-box?p=78898#post78898 This particular server is a Dell R815 - See below for storage specs. PERC H700, SAS - Proxmox...

From my point of view ProxMox 3.0.x is a very nice upgrade, it's similar to 2.x but with many improvements. The only problem I have had with it is with vzdump backups crashing / locking up the box. There are others reporting this issue as well, specifically it seems anyone using megaraid / LSI...

Thanks for the advice Dietmar, per your instructions I did upgrade to pve-kernel-2.6.32-23-pve: 2.6.32-108, rebooted the box, and enabled some backups again last night. It seemed to make it through 3-4 OpenVZ containers just fine and then it tried to backup a busy KVM VM, the load skyrocketed...

Hi all, As promised - I upgraded the kernel as recommended (version info below) - the same problem is still rearing it's ugly head. The box locks up tight when backups run and the only way to recover is to power down and reboot. This is a Dell R815 / Dell PERC H700 controller. In my previous...

We are using Dell servers - the servers that are failing are using Dell PERC H700 RAID controllers with write / read caching enabled. We have a cluster of 6 new Dell 620 servers that use the Dell PERC H310 controller - these servers are working fine and backups are happening without any issue...

If it hasn't already been posted here - see the following thread: http://forum.proxmox.com/threads/9097-vzdump-using-lvm-snapshot-kills-the-box?p=77084#post77084 I have made several posts related to a very similar issue with the newest ProxMox 3 / snapshots locking up the entire server. We have...

Update - I tried running backups again last night on ProxMox 3.0.23, only on openVZ containers - which caused the exact same problem. System load skyrocketed and I was forced to reboot the machine to get it running properly again. Dumping the backup logs and dmesg / kernel logs shows extensive...

I switched the scheduler as indicated in the above link, however, I didn't restart the server. I am not aware of how to restart ProxMox entirely without a reboot. Anyway, last night at midnight my backups started running, Proxmox backed up 3 openvz containers without issue and then for whatever...

We also have a similar issue - Dell PowerEdge 815 servers, 64GB RAM, RAID5 array for ProxMox - all VMs and related are stored on iSCSI targets. Our backups were going to an NFS mount set up in ProxMox ProxMox 3.0 - backups set to go after midnight of about 15 OpenVZ containers and 3 KVM VMs...

Dietmar, Thanks also for your response - could you describe what you mean? I am not sure how to build such a rule that would work in this manner. Thank you, Joe Jenkins

Tom, Nope we don't, we have a flat user database in LDAP on our mail server only - the sole purpose of this database is to let our spam defense systems (previously two Barracuda 400s) know what are legitimate user accounts. We don't use it for anything else, so there are no groups to separate...

Thanks Tom, We have over 14000 users in LDAP, so this would be impractical. Thanks for the suggestion - maybe it could be a feature request for a future release. Thanks again, Joe

Hi all, We are evaluating Proxmox Mail Gateway 3.1 - we have specific users and mailing list accounts that we do not want daily quarantine reports going out for. How can I stop reports from going out to specific recipients? Thank you, Joe Jenkins WFRMLS

Yes, this is enabled, I just tried increasing the amount of time the data is kept, but it didn't correct the problem. Like I said above, it was working when I first started routing email through the ProxMox gateway, but then at some point they just "disappeared" Thanks! Joe

I am testing ProxMox Mail Gateway 3.1-5695 as a trial. It's working great but some of the statistics pages aren't reporting anything. These pages were working initially but after running for a couple of days no results are returned, specifically: Mail Domain/Address Statistics - Domain Out /...

Re: LDAP Profile issues - Proxmox Mail Gateway 3.1 - connecting to OpenLDAP - FIXED Just wanted to update this thread- this issue was corrected by upgrading OpenLDAP on the LDAP server to 2.4.11 Thanks! Joe Jenkins WFRMLS