September 23, 2013, 4:11 pm
Hi!
It seems that some CTs cannot be suspended when backup or migration takes place.
Code:
root@app1:~# vzctl chkpnt 111
Setting up checkpoint...
suspend...
Can not suspend container: Interrupted system call
Error: timed out (10 seconds).
Error: Unfrozen tasks (no more than 10): see dmesg output.
Checkpointing failed
Here comes dmesg output:
Code:
CPT ERR: ffff88033b65c000,111 :timed out (10 seconds).
CPT ERR: ffff88033b65c000,111 :Unfrozen tasks (no more than 10): see dmesg output.
saslauthd D ffff88061609e2c0 0 9553 9551 111 0x00800004
ffff880616797dd8 0000000000000082 0000000000000000 ffffffff8104dc65
0000000116797e48 0000000000000000 0000000000000000 ffffffffa0441720
0000000000000286 000000010006a01c ffff880616797fd8 ffff880616797fd8
Call Trace:
[<ffffffff8104dc65>] ? __wake_up_common+0x55/0x90
[<ffffffff8109b31e>] ? prepare_to_wait+0x4e/0x80
[<ffffffffa0434ea3>] dlm_posix_lock+0x193/0x360 [dlm]
[<ffffffff8109b350>] ? autoremove_wake_function+0x0/0x40
[<ffffffffa04f6599>] gfs2_lock+0x79/0xf0 [gfs2]
[<ffffffff811f2123>] vfs_lock_file+0x23/0x40
[<ffffffff811f27c3>] fcntl_setlk+0x143/0x2f0
[<ffffffff8153ff4c>] ? thread_return+0xbc/0x870
[<ffffffff811b2e07>] sys_fcntl+0xc7/0x550
[<ffffffff81543115>] ? page_fault+0x25/0x30
[<ffffffff8100b182>] system_call_fastpath+0x16/0x1b
I have tried to reproduce the issue, and discovered that any CT with running saslauthd process inside cannot be suspended.
The FS for CTs is GFS2, the version of Proxmox is:
Code:
root@app1:~# pveversion -v
proxmox-ve-2.6.32: 3.1-111 (running kernel: 2.6.32-24-pve)
pve-manager: 3.1-13 (running version: 3.1-13/262cf0b8)
pve-kernel-2.6.32-24-pve: 2.6.32-111
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-7
qemu-server: 3.1-4
pve-firmware: 1.0-23
libpve-common-perl: 3.0-6
libpve-access-control: 3.0-6
libpve-storage-perl: 3.0-13
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.0-2
root@app1:~# dpkg -l | grep gfs2
ii gfs2-utils 3.1.3-1 amd64 Global file system 2 tools
↧
September 23, 2013, 8:47 pm
[SOLVED] Error: Proxy loop detected (500) in Cluster test on Proxmox 3.1
Anyone here in the group had this problem when trying to migrate a container in a cluster without storage: Proxy loop detected (500)
In my test environment I tried to configure a cluster and it worked normally, however in time to test the migration of containet this error occurred and secondary node stopped responding and never came back, even with the reset of both the master and the slave.
I wonder if this error is normal or I did set up something wrong?
Following the data to help detect what may be the problem:
NODE MASTER
root@proxmox1:~# pvecm status
Version: 6.2.0
Config Version: 2
Cluster Name: tacioandrade
Cluster Id: 48385
Cluster Member: Yes
Cluster Generation: 8
Membership state: Cluster-Member
Nodes: 2
Expected votes: 2
Total votes: 2
Node votes: 1
Quorum: 2
Active subsystems: 5
Flags:
Ports Bound: 0
Node name: proxmox1
Node ID: 1
Multicast addresses: 239.192.189.190
Node addresses: 192.168.0.15
root@proxmox1:~# pvecm nodes
Node Sts Inc Joined Name
1 M 4 2013-09-23 23:40:58 proxmox1
2 M 8 2013-09-23 23:43:52 proxmox2
root@proxmox1:~# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.0.15 proxmox1.tacioandrade.com proxmox1 pvelocalhost
192.168.0.16 proxmox2.tacioandrade.com proxmox2
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
NODE SLAVE
root@proxmox2:~# pvecm status
Version: 6.2.0
Config Version: 2
Cluster Name: tacioandrade
Cluster Id: 48385
Cluster Member: Yes
Cluster Generation: 8
Membership state: Cluster-Member
Nodes: 2
Expected votes: 2
Total votes: 2
Node votes: 1
Quorum: 2
Active subsystems: 5
Flags:
Ports Bound: 0
Node name: proxmox2
Node ID: 2
Multicast addresses: 239.192.189.190
Node addresses: 192.168.0.16
root@proxmox2:~# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.0.15 proxmox1.tacioancrade.com proxmox1
192.168.0.16 proxmox2.tacioandrade.com proxmox2 pvelocalhost
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
Thanks in advance for any help. =)
↧
↧
September 24, 2013, 12:29 am
Hello !
I've a problem on PX 3.0 (I know, it is not the latest version) on migration (node to node) on nodes with different hardware (processors).
The cluster has three nodes, node 1 and node 2 are identical and migration works fine. When I try to migrate to node 3, migration works but the VM (after migration) freeze with the CPU on 100%
Proxmox 2.3 works fine on the same hardware and migrates correctly on nodes 3.
Is a known issue?
Very thanks
Luca
*******************************
pve-manager: 3.0-23 (pve-manager/3.0/957f0862)
running kernel: 2.6.32-22-pve
proxmox-ve-2.6.32: 3.0-107
pve-kernel-2.6.32-22-pve: 2.6.32-107
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-18-pve: 2.6.32-88
lvm2: 2.02.95-pve3
clvm: 2.02.95-pve3
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 3.0-4
qemu-server: 3.0-20
pve-firmware: 1.0-23
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-8
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-13
ksm-control-daemon: 1.1-1
*******************************
↧
September 24, 2013, 2:33 am
I have a question
I currently have a pfSense VM setup with 4 NICs (vmbr0 - vmbr1).
The host has
VMBR0 - 87.210.232.xxx
VMBR1 - 10.10.1.xx
VMBR2 - 10.10.2.xx
VMBR3 - 10.10.3.xx
I can bind whatever IP I want with whatever gateway to the private NIC in pfSense but for the public IP, I cannot bind other ranges such as 87.210.233.xxx to the VM
I can do this on any other VM as the IP ranges are all part of the same VLAN ... pfsense can only be on the same subnet as the IP range on VMBR0, any ideas?
↧
September 24, 2013, 3:23 am
Hi,
I can't find a way to understand which virtio version is installed in my windows 2003 guest...
in "devices management" I see two "hard disk" devices labeled "red hat virtio scsi disk device", but in the "driver details" it seems to come from... "microsoft"?
virtio.png
is this expected? and how can I easily tell which version I have installed? :confused:
Thanks, Marco
↧
↧
September 24, 2013, 5:47 am
Hello
On a single host (no cluster) the Webinterface stopped working.
I can't connect to the webinterface (timeout)
In syslog, there is a log entry:
Code:
Sep 24 14:41:50 root2 pveproxy[678391]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/HTTPServer.pm line 1307
And I can't restart pve-cluster:
Code:
Restarting pve cluster filesystem: pve-clusterstart-stop-daemon: warning: failed to kill 639414: No such process
fuse: failed to access mountpoint /etc/pve: Transport endpoint is not connected
[main] crit: fuse_mount error: Transport endpoint is not connected
[main] notice: exit proxmox configuration filesystem (-1)
(warning).
What does this mean?
↧
September 24, 2013, 6:34 am
Hi, I have proxmox 2.3 installed. I configure like this:
vmbr0 -> LAN --> eth0
vmbr1 -> WAN ISP --> eth1
I configured the file in /etc/sysconfig/network-scripts/ifcfg-ethX:
ETH0:
DEVICE=eth0
HWADDR=2E:21:C3:BC:09:A3
TYPE=Ethernet
UUID=daf17b64-4246-4423-b4dc-734120590b04
ONBOOT=yes
NM_CONTROLLED=no
BOOTPROTO=static
IPADDR=10.10.10.206
NETMASK=255.255.0.0
GATEWAY=10.10.10.3
ETH1:
DEVICE=eth1
HWADDR=3A:B5:28:9E:36:58
TYPE=Ethernet
ONBOOT=yes
NM_CONTROLLED=no
BOOTPROTO=static
IPADDR=91.126.136.188
NETMASK=255.255.255.0
GATEWAY=91.126.136.161
The ip WAN static 91.126.136.188 is free and not used for any host, but I received this error:
[root@localhost ~]# /etc/init.d/network restart
Interrupción de la interfaz eth0: [ OK ]
Interrupción de la interfaz eth1: [ OK ]
Interrupción de la interfaz de loopback: [ OK ]
Activación de la interfaz de loopback: [ OK ]
Activando interfaz eth0: [ OK ]
Activando interfaz eth1: Error, some other host already uses address 91.126.136.188
And eth1 not up with address:
[root@localhost ~]# ifconfig eth1
eth1 Link encap:Ethernet HWaddr 3A:B5:28:9E:36:58
inet6 addr: fe80::38b5:28ff:fe9e:3658/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:74 errors:0 dropped:0 overruns:0 frame:0
TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4532 (4.4 KiB) TX bytes:950 (950.0 b)
I probed this in debian, and no problems anything...Sorry for my english...Do you think the problem is proxmox or centos...?
I assure you, that this IP is not being used because debian catches it perfectly. Now debian, is off.
Thanks in advanced.
↧
September 24, 2013, 7:10 am
hi, sorry if it is a dumb question...
I am still using lvm/iscsi storage for my vms,
on a 1TB shared iscsi/lvm storage I have many raw vm disks, but apparently many of them related to old or test machines now _deleted_
now I am thinking to remove those, to free up space there, but I wish to be shure no node is using them!!
I guess they are from old vm because of the LV name, like:
vm-112-disk-2 pve_vm_disks -wi----- 200.00g
so I guess this was created for a vm with VMID 112, and now is not "active/open" (I learned that it would show an "a" at bit 5, and "o" at bit 6 if "open")
to check this things I can log into each node and issue a lvs command, but i get a list of all disk on any node, even if that vm is not on the node.
simply, only the "owning" node will show it as "active/open" if it is so (if the VM using the LV is running there), the others will always show the LV with the two bits above as: as "--", and I don't know
I can check a couple of nodes manually, one by one, but is there any "unified" way of check this kind of things?
perhaps with distributed storage (ceph, sheepdog) is kinda easier to get this kind of cluster-wide vm-storage usage info.. ?
Marco
↧
September 24, 2013, 8:53 am
i create a CT MACHIN with Debian 6.0 ,but when a use the command " ping google.com"
i receive " Network is unreachable "
↧
↧
September 24, 2013, 9:50 am
We just upgraded from 2.3 to 3.1 on a cluster of nodes.
We have a couple of storage arrays connecting via iSCSI as LVM and NFS managed from the Proxmox web manager. All existing VMs are running fine and the interface show the iSCSI, LVM abnd NFS stores. When clicked the contents show up in the listing and all looks fine.
However when we try to create a new VM there is no option available (greyed) to set the storage target and when the pressing go, the creation attempt fails with:
TASK ERROR: create failed - storage 'undefined' does not exists.
The area we are concerned with is that we ran the upgrade script that seemed to complete without issue.
We also manually removed old pve kernels that seems to remain from way back.
Then ran the /purge option to clear down unnecessary packages and it seemed to removed pve-manager etc.
To fix that we then ran:
apt-get install pve-qemu-kvm proxmox-ve-2.6.32 vzctl pve-manager qemu-server ceph-common libpve-storage-perland
most things came back fine, but we are not sure if we have missed any packages.pveversion -v shows:
proxmox-ve-2.6.32: 3.1-109 (running kernel: 2.6.32-23-pve)
pve-manager: 3.1-3 (running version: 3.1-3/dc0e9b0e)
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 3.0-7
qemu-server: 3.1-1
pve-firmware: 1.0-23
libpve-common-perl: 3.0-6
libpve-access-control: 3.0-6
libpve-storage-perl: 3.0-10
pve-libspice-server1: 0.12.4-1
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.0-2
Which looks right.
Anyone have any ideas why storage is not showing where expected?
Other than that the upgrade looks good, thanks!
↧
September 24, 2013, 1:39 pm
Hi all,
On one node HA has simply stopped working. Removing the node and I can start it again but as soon as the vm is added to HA again I see the following in rgmanager.log:
Sep 24 22:37:06 rgmanager Initializing pvevm:115
Sep 24 22:37:06 rgmanager pvevm:115 was added to the config, but I am not initializing it.
A manual restart logs this:
Executing HA start for VM 115
Member esx2 trying to enable pvevm:115...Aborted; service failed
TASK ERROR: command 'clusvcadm -e pvevm:115 -m esx2' failed: exit code 254
And rgmanager.log:
Sep 24 22:48:40 rgmanager #43: Service pvevm:115 has failed; can not start.
Sep 24 22:48:40 rgmanager #13: Service pvevm:115 failed to stop cleanly
What could be wrong here?
↧
September 24, 2013, 4:32 pm
Hello everyone. I was trying to make VNC work through php calls but no success so far.
I use VNCViewer.jar which is used itself by the proxmox UI.
To implement console i copied "applet" tag completely from proxmox's console window and added auto replacement of all needed variales with php.
But when i open a page i get java IO exception saying that it can't load certificate "Incomplete data".
What could be wrong? I thought that maybe some extra steps should be taken besides "\n" with "|" replacement, but proxmox produces the same output as i do. But mine does not work.
Came up with this:
Code:
<html class="x-border-box x-quirks x-viewport"><head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body>
<applet width="100%" height="100%" border="false" archive="VncViewer.jar" code="com.tigervnc.vncviewer.VncViewer" id="pveOpenVZConsole-1018-vncapp" style="width: 745px; height: 426">
<param value="pveOpenVZConsole-1018-vncapp" name="id">
<param value="xxxx" name="PORT">
<param value="xxxx" name="PASSWORD">
<param value="root@pam" name="USERNAME">
<param value="No" name="Show Controls">
<param value="No" name="Offer Relogin">
<param value="-----BEGIN CERTIFICATE-----......." name="PVECert">
</applet>
</body>
</html>
↧
September 25, 2013, 7:41 am
I have updates populating my GUI, but I recall that the repositories must be adjusted after initial installation. How do I adjust the repositories properly, to match my subscription or non subscription? How do I purge the existing updates available, such as bing9-host, dnsutils, gnupg, gpgv, krb5-local, libbind9-80, etc...?
↧
↧
September 25, 2013, 9:03 am
Hi all,
I have been wondering. Is a high fsync value really needed if all your vm's and ct's run on a remote shared storage array?
If so, what specific gains do you get from a high fsync value in this specific situation?
↧
September 25, 2013, 10:34 am
I have a client on my proxmox, but he have can view the resources of my datacenter. I only have interest that he can see their vm but no the resources of the datacenter.
The user can see all this 'Node Disk usage/Memory usage/ CPU usage etc.'
Why letting VMUser see the server resources?
How to Block this??
Thanks
↧
September 25, 2013, 11:04 am
Hi all,
on last PHP API on function "public function get_next_vmid() {" on the end is failing }
without } the function does not work and give a error 500.
regards
↧
September 25, 2013, 11:06 am
↧
↧
September 25, 2013, 11:33 am
I have a pfSense VM that will not authenticate against my Comcast Static IP.
eth0 = vmbr0
eth1 = vmbr1
eth2 = vmbr2
eth3 = vmbr3
eth4,eth5 = bond0
bond0 = vmbr4
pfSense is exclusively Bridged to vmbr0 and vmbr2 (vmbr0 = LAN :: vmbr2 = WAN)
When I set the public IP on the WAN side and soft-reboot the Comcast modem, it does not obtain internet connection. (The "checking update status" says Unable)
pfSense version is Release-2.1
There is a possibility I have a faulty quad-port NIC from eBay due to the fact that eth0 and eth2 are directly next to each other. Also, when I plug an ethernet cable in the other ports, no lights flash, even for on-board. Assuming the card is good, is there anything special I need to do in order for the Comcast modem to see the pfSense vmbr2? I've read somewhere about routing, but there was nothing in-depth in regards as to what scenario this is for and why. I just want the vmbr2 to serve my pfSense WAN exclusively so that a connection is established with Comcast Modem.
Also, when I unplug the ethernet from eth2 (vmbr2) the dashboard never shows that WAN is down, but I do see nic is down in shell dmessages
Let me know if I need to clarify some of my details, and thanks for the help.
↧
September 25, 2013, 11:45 am
I seem to be having issue with the proxmox web gui on all 7 of my clusters. If I am on the GUI of node #1 and try to click on anything involving node #2 I get prompted for the username and password over and over. I am thinking this is some type of certificate issue but I am unsure. This happened within the past few weeks on everyone of my clusters. Has anyone seen this issue before? I appreciate the assistance.
↧
September 25, 2013, 11:20 pm
We released a new kernel for Proxmox VE 3.1 and a lot of fixes. All this can be updated via GUI with just a few clicks, or as always via "apt-get update && apt-get dist-upgrade".
A big Thank-you to our active community for all feedback, testing, bug reporting and patch submissions.
Release notes
- pve-kernel-2.6.32 (2.6.32-111)
- KVM: x86: Fix invalid secondary exec controls in vmx_cpuid_update()
- update to vzkernel-2.6.32-042stab079.6.src.rpm
- update aacraid to aacraid-1.2.1-30300.src.rpm
- update e1000e to 2.5.4
- update igb to 5.0.5
- update ixgbe to 3.17.3
- pve-manager (3.1-14)
- avoid warning in daily cron script
- dissable SSL compression (avoid TLS CRIME vulnerability)
- fix bug #456: allow glusterfs as backup storage
- vzdump: fix hook script environment for job-* phase
- vzdump: pass storage ID to hook scripts
- depend on libcrypt-ssleay-perl and liblwp-protocol-https-perl (for correct LWP https support)
- fix https proxy calls (always use CONNECT)
- use correct changelog URLs for pve repositories
- vzdump: correctly handle maxfiles parameter (0 is unlimited)
- improve API2Client.pm code
- update German translation
- update Chinese translation
- apt: proxy changelog API call to correct node
- qemu-server (3.1-4)
- qemu migrate : only wait for spice server online + eval
- speedup restore on glusterfs (do not write zero bytes)
- Allow VMAdmin/DatastoreUser to delete disk
- apt (0.9.7.10)
- fix Bug#669620: apt-transport-https: proxy authentication credentials are ignored
- ceph-common (0.67.3-1~bpo70+1), librados2 (0.67.3-1~bpo70+1), librbd1 (0.67.3-1~bpo70+1), python-ceph (0.67.3-1~bpo70+1)
- libpve-storage-perl (3.0-13)
- bug fix: use filesysetm_path for LVM/iSCSI storage
- glusterfs: really delete volumes when requested
- API fix: auto-detect format for files with vmdk extension
- API fix: return error if volume does not exists
- pve-libspice-server (0.12.4-2)
- conflict with debian package 'libspice-server1'
- pve-sheepdog (0.6.2-1)
Package Repositories
http://pve.proxmox.com/wiki/Package_repositories
Source Code
http://git.proxmox.com
__________________
Best regards,
Martin Maurer
Proxmox VE project leader
↧