Search results

  1. E

    [SOLVED] Upid worker problem (again)

    On one of our nodes that is 497 days up we have the dreaded UPID worker issue. We've edited the Tools.pm as suggested in: https://forum.proxmox.com/threads/cant-perform-backup.15341/ And restart pvedeamon and apache2 It worked before on other servers but this time the problem remains...
  2. E

    [SOLVED] Backup fails cronjob exits status 9

    On a server thats running and backingup fine for over a year suddenly the backup fails since two days with: Jan 17 13:22:01 node12 /USR/SBIN/CRON[887055]: (root) CMD (vzdump 217 --quiet 1 --mode snapshot --mailto support@xxx.xx --node node12 --compress lzo --storage usbdisk-node12) Jan 17...
  3. E

    Backup suddenly stopped working

    On a node that has been running without problems suddenly the backup stopped working. It backups to a connected USBdisk. The disk is fine, I unmounted and mounted it. It shows fine in df I removed the disk from 'storage' in the mainnode and added it again. No errors. But nothing happens. No...
  4. E

    Connection error: proxy 500 error detected

    ########URGENT HELP NEEDED!########### My VPS on my single node is down. I can't start it because of the error I get in the interface: Error: connection error 500: proxy loop detected I cant start it from the prompt because I get: Container config file does not exist I did find a configfile...
  5. E

    Restore 2.x container to 1.x

    Our backupserver that stores the nightly backups is a 1.x server. We try to restore a container that was backed up on a 2.x server. We cannot set ip's and memory through the interface. I tried changing it by hand editing /etc/vz/conf/xxxx.conf and that works although the interface gives wrong...
  6. E

    Proxmox 2 cluster problem

    Disclaimer: I know I will get the standard answer 'Please update to the latest version' but PLEASE don't. We have a 1.9 cluster and a 2.1 cluster. Keeping nodes up cutting edge to date with live containers on it is just to dangerous for us. On the 2.1 cluster the second node (called node10) is...
  7. E

    Change IP on container

    I just installed a 2.1 node to test. I restored a container from our 1.8 cluster, so far so good. When I try to change the current IP of the container I can only remove or add an IP under network. I see the 'edit' button but it is grayed out.
  8. E

    Kernel questions 2.6.18-6-pve

    We have a production cluster running with Proxmox 1.8 using kernel 2.6.18-6-pve I noew need to add a new machine to this cluster. After install the default kernel is installed (.32) this was always the case so I looked up how we used to change the kernel to have the Openvz support we need. It...
  9. E

    pty not found

    After a reboot of one of our Centos containers we suddenly could not login anymore: Unable to open pty: No such file or directory I found many threads in google mentioning the same problem with a quick fix. I tried and edited /etc/rc.sysinit en commented the line: /sbin/start_udev After that I...
  10. E

    Suddenly no conf file for container?

    I log into a node and want to vzctl enter "containernumber" and suddenly it says: Container config file does not exist Tonight I was in the datacenter because of some weird problems we're experiencing and then I could just enter the container without problems. I looked in /etc/vz/conf and...
  11. E

    No vzdumps on all nodes this morning

    I just woke up and feel like i'm still dreaming. Of our six nodes only one has runned its backups tonight. I've never seen this before. I've even no idea where to start looking?
  12. E

    Speed up Rsync?

    Every night we backup our 6 nodes to usbdisks that are attached to each node. Then during the day all these backups are copied to a 7th node with Rsync for storage. A few weeks ago we changed from pve-kernel-2.6.24-7-pve: 2.6.24-8 to pve-kernel-2.6.18-6-pve: 2.6.18-15. The good news is that...
  13. E

    node down after upgrade

    Tonight I upgraded all our nodes from pm 1.3 to 1.8 an kernel 2.24 to 2.18 One of the nodes that contain all our backups won't boot anymore. BEcause of the large disksize it has two lun's. No matter wich I select in the bios it won;t boot. I just get a black screen with a cursor blinking. I...
  14. E

    Vzdump backups wrong node?

    Recently I upgraded two of our nodes to 1.8 with kernel 1.18. I made a tenporarly new cluster of these two nodes. Entered the backups (snapshot) information for both nodes trough the master. Backups work, I see the naming convention is changed (btw. the hostname of the node in the name of the...
  15. E

    No HD space data?

    I upgraded two nodes from 1.3 to 1.8 (kernel .18). No I noticed the frontend does not show the space for the data partition. Is that normal?
  16. E

    Totally lost on versions

    We decided to upgrade our nodes from proxmox 1.3 to 1.8. So I took a look at the wiki: http://pve.proxmox.com/wiki/Downloads It suggested installing the 2.6.32 kernel branch. So I did. After having some problems we started doubting the versions, 6.18 says latest stable, but 6.32 is the default...
  17. E

    partition lager then 2TB

    I'm doing a reinstall of a server that had 8 1TB disks with 8 2TB disks. I'm installing version 1.3 for the time being, next week we will shift to 1.8. After the 7 hour initialisation of the raid-10 partion of 8TB I tried to install proxmox. Unfortunaly it gave: unable to create data volume at...
  18. E

    upgrade 1.3 -> 1.8 goes wrong

    I'm upgrading (luckily a test server) from PM 1.3 to 1.8 with kernel 2.6.32 I followed the steps on the dowload page. The server uses a 3ware raidcard 2x sata. All was running fine without problems before the reboot. I can't make a screenshot so I post a foto of the error: I searched the...
  19. E

    Node down exploit?

    One of my nodes went just down. I saw this message: What does this mean?
  20. E

    No cdrom found

    I tried to install PVE on a new server. It boots from cdrom and when it should install it tells me cdrom not found. I moved the cdrom to the secundairy position, it makes no difference. Are there any boot options or other tricks I can do to solve this?

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!