Recent content by evharten

No one got an idea ?

Dear Everyone, I've upgraded my 2 ProxMox VE nodes, but now they are both hanging on kernel hung messages Anyone has an idea what to do ? the servers DO boot with an netboot and an 3.x kernel, but the Proxmox VE 2.6.32-107 it hangs. root@vps1:~# pveversion -v pve-manager: 3.0-23...

That solved it! GREAT :D

Aye its fixed!, just changed my hostname ;) appearantly i've updated it already, but didnt changed it back still ;)

One shortcoming there is that you cannot use any Domainname in the servername which starts with an number, i for instance got an domain which start with 16 its a .nl, but you cannot fill in : srv.16blabla.nl It says its NOT a valid domain, even tho its already registered for like 2 years or so...

You go to the VM options, and then you double click (or click once and then Edit) on Name

Finally got it working, it appeared that you REALLY have to parse the certificate and replace the \n's with |'s, if you do not do this, it just doesnt work ;) Now only need to find a way to include the darn applet into my webpage, as currently its only working with Open in new window, which i...

Ok, tested it myself with the 2>/dev/null which is just a redirect in a wrong sentence basicly :), got an proxy with that command aka VNC return, so now going to call it thru the API, and see if i can telnet to it. Update: That works also, guess something with the VNC applet is just wrong then...

root 93864 0.0 0.0 5972 692 ? S 07:53 0:00 /bin/nc -l -p 5900 -w 10 -c /usr/sbin/qm vncproxy 100 2>/dev/null Thats what is in the processlist.

so basicly the PVE interface uses the API also ? then ill have to debug some more in the vncproxy call, quite odd that it gives an extra 2 in the commandline. thats what i see in the output of an ps -auxww on the server itself within the 10second window nc runs

Yes it works in the Pve Gui, only doesnt work for the API which passes the wrong command (hence the extra 2 at the end of the command before the last ' after nc which isnt correct statement according to qm vncproxy, as this requires the syntax: qm vncproxy <vmid> , eg. qm vncproxy 100, but not...

Output: root@vps1:~# pveversion -v pve-manager: 2.0-57 (pve-manager/2.0/ff6cd700) running kernel: 2.6.32-10-pve proxmox-ve-2.6.32: 2.0-63 pve-kernel-2.6.32-10-pve: 2.6.32-63 lvm2: 2.02.88-2pve2 clvm: 2.02.88-2pve2 corosync-pve: 1.4.1-1 openais-pve: 1.1.4-2 libqb: 0.10.1-2 redhat-cluster-pve...

Dear Tom, Full-upgrade is only needed when packages are hold back in debian, which is basicly major changes, like kernel upgrades. Which was not the case for me, as there was no major change. Regards, Evert

Before i posted, i did an apt-get update && apt-get upgrade to ensure i've got the latest version. Sadly it still didnt fixed it. And i'm using the stock install.

POST /api2/json/nodes/{node}/qemu/{vmid}/vncproxy This gives back the cert, etc. And also starts the VNC Proxy, only the command it executes doesnt work, because of the added 2 at the end.