Search results

  1. H

    Upgrade from 3.4-6 to 4.0 failed

    Introducing a new server running with 4.1-1 we have to upgrade our 3 servers running 3.4-6. Following exactly the wiki "Upgrade from 3.x to 4.0" (cut and paste) the upgrade failed and the server hangs in shell. All VMs on that server have been moved to the new server. So we decided to install a...
  2. H

    No webinterface after Updates

    So would it be appropriate to log-in via ssh and then apt-get update apt-get upgrade apt-get dist-upgrade I understand that the enterprise repository is password protected.
  3. H

    No webinterface after Updates

    "grub-install /dev/sdb" worked. pvs output is: root@vwsrv2:~# pvs PV VG Fmt Attr PSize PFree /dev/sda pve lvm2 a-- 1.06t 285.43g /dev/sdb2 pve lvm2 a-- 135.47g 0 root@vwsrv2:~# So far everything seems ok. I will restart the server this evening and see if the...
  4. H

    No webinterface after Updates

    I initiated updates from the Proxmox webinterface. After working for some time the console window disappeared. I was able to access the server via ssh and realised (netstat -ltn) that no process was listening on port 8006. I issued apt-get update from the CLI. It told me that there was nothing...
  5. H

    /etc/pve/nodes/vwsrv3/qemu-server read-only

    Your suggestion did not work. I edited vwsrv3's /etc/cluster.conf and changed the version number. Then suddenly I had the quorum needed. But still I could not change the the xxx.conf I wanted to change on vwsrv3. I repeated the commands service cman restart service pvestatd restart service...
  6. H

    /etc/pve/nodes/vwsrv3/qemu-server read-only

    34 1 -r--r----- 1 root www-data 339 Mar 21 2014 /etc/pve/cluster.conf 1794903 4 -rw-r--r-- 1 root root 340 Mar 21 2014 /etc/cluster/cluster.conf root@vwsrv3:/etc/pve/nodes# root@vwsrv3:/etc/pve/nodes# diff /etc/cluster/cluster.conf /etc/pve/cluster.conf 2c2 <...
  7. H

    /etc/pve/nodes/vwsrv3/qemu-server read-only

    See output of the commands: root@vwsrv3:~# service cman restart Stopping cluster: Stopping dlm_controld... [ OK ] Stopping fenced... [ OK ] Stopping cman... [ OK ] Unloading kernel modules... [ OK ] Unmounting configfs... [ OK ] Starting cluster: Checking if cluster...
  8. H

    NoVNC Console size adaption

    If You regard the following scenario: I set screen resolution to 800x600 which works for me. Another admin working with remote desktop sets it to 1024x768. Then I have no chance to set it back, because I cannot reach the bottom part of the screen. As far as I know Windows does not have a "per...
  9. H

    /etc/pve/nodes/vwsrv3/qemu-server read-only

    Sorry, I have to post this issue again. This was addressed also by frantek two weeks ago and answered by Udo. "reach quorum again and your /etc/pve should be writable! .... The answer of frantek was "Thanks. Worked" But he did not share with us how he managed to reach quorum. I am sure that it...
  10. H

    NoVNC Console size adaption

    Guest OS is Windows Meanwhile I found that if I set the Windows Display to 800x600 the noVNC window fits completely into my Laptop Screen. But this makes no sense. If You work with Remote Desktop Full Screen You want to have a better resolution.
  11. H

    NoVNC Console size adaption

    When I start a guest console using noVNC on my laptop its size is bigger in hight that my laptop screen. So it is useless. It starts with a smaller window but then extends to a size that does not fit into my display. I can not resize it with the mouse. Normally I work with remote desktop. But if...
  12. H

    Bonding with LACP and VLANS

    This was exactly the solution! Thank You. Trying to set up a tagged VLAN bridge was not possible until I found that the network admins set a tagged Vlan 404 and an untagged Vlan 404 to the same switch port. Very weird! After removing the untagged Vlan 404 it worked as expected. It took one week...
  13. H

    Bonding with LACP and VLANS

    My Version Proxmox VE 3.4-1/3f2d890e I changed my running /etc/config/interfaces accordingly to enable bonding with LACP, but had problems. So tried this interfaces file: auto lo iface lo inet loopback iface eth1 inet manual bond-master bond0 iface eth2 inet manual bond-master bond0 auto...
  14. H

    No write acces to /etc/pve/

    We have 3 nodes vwsrv1 proxmox version 3.0 vwsrv2 proxmox version 3.3.5 vwsrv3 proxmox version 3.3.5 All nodes are in separate physical locations. conf files are named xyy.conf x=1..3 y=100-999 So 101.conf and 301.conf 201.conf are the same VMs on different nodes. Only one is running, the...
  15. H

    Upgrade 3.0 to current fails

    Thank You for Your quick reply. Using Opera instead of Firefox I was able to trigger the update & upgrade from the webbrowser. So everything worked. No idea what happened using Firefox. I have another node to be upgraded. I have 3 licences. I will make detailed notes what I do and what happens...
  16. H

    Upgrade 3.0 to current fails

    The fact, that the nodes are not displayed in the webinterface are browser related. I use FirefoxESR 31.4.0. Deperately I tried an old Opera Version 12.15 and it works in this environment. So what is the reason? It works on Proxmox version 3.3-5 and 3.0-23 with the same Firefox browser but not...
  17. H

    Upgrade 3.0 to current fails

    I did what You suggested. The result is: I now see Version 3.1 -21/93bf03d4 But all nodes have disappeared in the browser view. If I login to another server running Proxmox I can see them. All conf's and vdisks are there. root@vwsrv2:/etc/pve/qemu-server# ls 201.conf 203.conf 204.conf...
  18. H

    Upgrade 3.0 to current fails

    root@vwsrv2:/etc/apt/sources.list.d# cat pve-enterprise.list deb https://enterprise.proxmox.com/debian wheezy pve-enterprise root@vwsrv2:/etc/apt/sources.list.d# apt-get update Hit http://security.debian.org wheezy/updates Release.gpg Hit http://security.debian.org wheezy/updates Release Hit...
  19. H

    /dev/pve_backup

    Solved. There was a disk attached via USB long time ago, which has been removed. So after cleaning up the configuration everything was OK
  20. H

    /dev/pve_backup

    I installed the CT FileServer and was looking how to mount a host directory to it. This server is running PVE 3.1-21, while the other two (production servers) are running PVE 3.0. I bought the community subsciption, but have not installed it yet. I want to upgrade 3.0 to 3.2 without a new...