Search results

  1. R

    Backup Problem. Way to gracefully stop backup cron job.

    started an extra thread for my problem :) pls delete this post
  2. R

    Where did the names of the VMs go?

    that would be real great! (better would be additionaly the vm-name in the backup-file-name) :)
  3. R

    Force port 443 instead of 8006

    thx i still don't get it why somebody complains about a standard-port used for the "WEB-ui", but ok, maybe i don't see the big picture :)
  4. R

    Installation of PVE2.0 on IBM Blade Center

    thanks i will use this in future cases of such problems in the meantime i found another solution i had to create a virtual drive in the java remote console for the blade and with that mounted the installation found the virtual drive after loosing the hardware-drive and everything went fine
  5. R

    Force port 443 instead of 8006

    i get this error with firefox: ssl_error_rx_record_too_long single machine, no cluster etc. is there a reason why you use now 8006 and not 443 anymore?
  6. R

    Proxmox Mail inside PVE VM with VETH interface

    k, thanks, than i will stay at kvm, just thought that openvz would be nicer over all :)
  7. R

    Installation of PVE2.0 on IBM Blade Center

    Hi, at the moment i try to install the new pve 2.0 on one blade of a ibm blade center (H Chassis) but the installation isn't working cause of this error. Have you any clue how i could get rid of this? one and a half year ago i reported this error with the change from 1.5 to 1.6 but...
  8. R

    Proxmox Mail inside PVE VM with VETH interface

    hi is there a chance that this will work with pve 2.0? thanks
  9. R

    Proxmox Mail inside PVE VM with VETH interface

    has thus been changed? I would like to switch from kvm to openvz but i need a veth (because the mailgateway must be in a specific dmz e.g. vmbr2) tia
  10. R

    Switch back to old vzdump-version?

    hi vm 201 was just an example, it can happen with everyone on the host i have the size set to 4000 cause that was the maximum that was possible, e.g. 4096 was already too much BUT maybe i found the real issue for this problem. my nexentacore nas with napp-it on top just informed me about an...
  11. R

    PVE1.9 Kernel 2.6.32-6 and Proxmox Mailgateway = Fail

    "nice" to hear (i hope you unterstand how i mean that), how have you distributed the vCPUs? All 4 as Socket, or 1 Socket und 4 Cores, or maybe 2 Sockets und 2 Cores and so on. in the mailgateway i have 2 Sockets with each 1 core. in 2008r2 i had the problem with 1 socket and 2 cores, 2 sockets...
  12. R

    Switch back to old vzdump-version?

    i would love to find the issue, same as with the 2.6.32-6 kernel problem i had/have. but the problem is that next week i'm on vacation and i don't like to go with bellyache ;) the strange thing is that the next try i started went through without any problems Sep 23 09:02:01 INFO: Starting...
  13. R

    Switch back to old vzdump-version?

    Hi, is it possible to switch back to an old vzdump-version? the actual vzdump (1.2-15) which came with 1.9 drives me crazy. when the backup starts i can see the rise of the .dat file, e.g. 12GB in 5 minutes and then happens nothing (12gb is the size of the vm, so it would be finished from the...
  14. R

    PVE1.9 Kernel 2.6.32-6 and Proxmox Mailgateway = Fail

    ok thx, and its definitely possible to get back to 2.6.32-4?
  15. R

    PVE1.9 Kernel 2.6.32-6 and Proxmox Mailgateway = Fail

    the mailgateway host is a Dell R310, the host of the 2008r2sp1 servers is a r715 the bluescreen of the 2k8 server says "A clock interrupt was not received on a secondary processor within the allocated time interval." and yes sure, i can test it in the next days on the R310 with the mailgateways...
  16. R

    PVE1.9 Kernel 2.6.32-6 and Proxmox Mailgateway = Fail

    today i had the chance to test it again with 2.6.32-6 and unfortunately it failed again after a few minutes the mailgateway stops working and won't react to anything on the host it looks like this now i'm back on 2.6.32-4 again, and also on my two other machines cause it seems like 2.6.32-6...
  17. R

    PVE1.9 Kernel 2.6.32-6 and Proxmox Mailgateway = Fail

    short update: the restore on another machine showed no problem, with the difference that the mailgateway was not productive and not in the same DMZ as normal i'm going to try the -6 kernel again on the productive machine but it will need a few days until i have the chance und the time to do this...
  18. R

    PVE1.9 Kernel 2.6.32-6 and Proxmox Mailgateway = Fail

    it's a Dell PowerEdge R310 Xeon X3440, 8GB RAM, 2x250GB SATA 7k2rpm, SAS 6iR - Raid 1 3x VMs running on it pve-manager/1.9/6542 atm Linux 2.6.32-4-pve #1 SMP Mon May 9 12:59:57 CEST 2011 proxmox-mailgateway/2.6/4540 Linux 2.6.27-2-proxmox as it comes out of the box (a 3-domain-license...
  19. R

    PVE1.9 Kernel 2.6.32-6 and Proxmox Mailgateway = Fail

    hi i think i'm the victim of some sort of bug with the new kernel-version 2.6.32-6. if u use the free proxmox mailgateway version in a kvm-host with pve kernel version 2.6.32-6 the host hangs up on start. some times the boot is successful but after a few minutes the mailgateway hangs up with...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!