Search results

Its an old version. I tried to delete this thread (moderator?) as it is solved with the method in the mentioned thread. It turned out my college who made the change in Tools.pm made an error. Everything works and I'm feeling a bit silly now :) Spirit and Wolfgang, thank you very much for your...

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...

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...

Dear Hashment, I saw you post in: http://forum.proxmox.com/threads/18812-Submit-patch-on-Tools-pm-and-pvemanagerlib-js I had the exact same problem and I hope I can ask you something. I'm running a PM 2.x cluster and am not a programmer or full fledged sysadmin. I edited the Tools.pm file and...

Hi Manu, I found several threads about this, that one led me on the right track: http://forum.proxmox.com/threads/15341-Can-t-perform-backup I found there was a bugfix: https://goo.gl/uzfWIW The forumthread speaks of also editing /usr/share/pve-manager/ext4/pvemanagerlib.js but in the other...

Hi Manu, Thanks. The problem seems the 497 days uptime bug that is fixed in newer versions. Sure enough the node is up for 498 days :) I found this solution (last post): http://forum.proxmox.com/threads/15341-Can-t-perform-backup Can you confirm this is safe? Thank you again.

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...

Excellent, thank you esud.

Can someone comment if this is a save solution for older Proxmox Lenny? https://gist.github.com/mattwhite/86de50d30134129e44ef

I found this: https://gist.github.com/mattwhite/86de50d30134129e44ef Unfortunatly I can't judge if its any good.

Dear Tom, So do I understand it right that you just choose not to help me anymore once you learned I had not all the latest updates installed? Even though I just paid €200,- and you understood I had serious problems? Thats a pretty 'high and mighty' attitude. I understand you are highly...

Lucky for me (buying €200,- support and sending a ticket with 'emergency' did suprisingly little) a friend solved it after hours of searching. From what I understand he renamed the vps's config file and made a new symbolic link to /etc/vz/conf. No idea how this is suddenly possible with a server...

Is this somehow related? root@3 /etc/pve/nodes/Debian-70-wheezy-64-minimal/openvz # ls -lah /etc/vz/conf lrwxrwxrwx 1 root root 15 Aug 26 2013 /etc/vz/conf -> /etc/pve/openvz root@3 /etc/pve/nodes/Debian-70-wheezy-64-minimal/openvz # ls -lha /etc/pve/openvz lrwxr-x--- 1 root www-data 0 Jan 1...

########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...

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...

I saw when I login to the interface of node10 directly it does not show the deleted container. This is the error message I got when migrating, scary that it deleted everything although there was a error:

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...

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.

Thanks its running now (phieuw).

Dear Tom, I appreciate your advice and will follow it asap but in the meantime I have problems at hand that needs to be solved. I do: and get as a response: The contents of my sources.list: