November 11, 2014, 1:00 am
Hi.
Yesterday upon an automated backup and today I've stumbled upon an error:
Code:
INFO: starting new backup job: vzdump 163 --remove 0 --mode snapshot --compress lzo --storage ClusterFS_nas_backupftp --node node1
INFO: Starting Backup of VM 163 (qemu)
INFO: status = running
INFO: Unrecognized character \xBA; marked by <-- HERE after Net::LDAP<-- HERE near column 18 at /usr/share/perl5/Net/LDAP/Message.pm line 5.
INFO: Compilation failed in require at /usr/share/perl5/Net/LDAP.pm line 13.
INFO: BEGIN failed--compilation aborted at /usr/share/perl5/Net/LDAP.pm line 13.
INFO: Compilation failed in require at /usr/share/perl5/PVE/Auth/AD.pm line 6.
INFO: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Auth/AD.pm line 6.
INFO: Compilation failed in require at /usr/share/perl5/PVE/AccessControl.pm line 16.
INFO: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/AccessControl.pm line 16.
INFO: Compilation failed in require at /usr/share/perl5/PVE/RPCEnvironment.pm line 16.
INFO: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/RPCEnvironment.pm line 16.
INFO: Compilation failed in require at /usr/sbin/qm line 15.
INFO: BEGIN failed--compilation aborted at /usr/sbin/qm line 15.
ERROR: Backup of VM 163 failed - command 'qm set 163 --lock backup' failed: exit code 255
INFO: Backup job finished with errors
TASK ERROR: job errors
Upon trying to provide the version installed on the node, the same error appears:
Code:
pveversion -vUnrecognized character \xBA; marked by <-- HERE after Net::LDAP<-- HERE near column 18 at /usr/share/perl5/Net/LDAP/Message.pm line 5.
Compilation failed in require at /usr/share/perl5/Net/LDAP.pm line 13.
BEGIN failed--compilation aborted at /usr/share/perl5/Net/LDAP.pm line 13.
Compilation failed in require at /usr/share/perl5/PVE/Auth/AD.pm line 6.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Auth/AD.pm line 6.
Compilation failed in require at /usr/share/perl5/PVE/AccessControl.pm line 16.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/AccessControl.pm line 16.
Compilation failed in require at /usr/share/perl5/PVE/RPCEnvironment.pm line 16.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/RPCEnvironment.pm line 16.
Compilation failed in require at /usr/share/perl5/PVE/API2/APT.pm line 20.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/APT.pm line 20.
Compilation failed in require at /usr/bin/pveversion line 7.
BEGIN failed--compilation aborted at /usr/bin/pveversion line 7.
Looks like PVE became broken for some reason.
What are the correct steps in restoring correct behaviour?
Since I think upon node reboot it wont come up because of this error.
Thanks in advance.
↧
November 11, 2014, 1:07 am
Hi.
I have Debian squeeze. I use following instruction for upgrade
https://pve.proxmox.com/wiki/Upgrade_from_2.3_to_3.0. When I run
./pve-upgrade-2.3-to-3.0 I get following errors:
Code:
Unpacking libcoroipcc4 (from .../libcoroipcc4_1.4.2-3_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/libcoroipcc4_1.4.2-3_amd64.deb (--unpack):
trying to overwrite '/usr/lib/libcoroipcc.so.4.0.0', which is also in package libcorosync4-pve 1.4.4-4
Unpacking libconfdb4 (from .../libconfdb4_1.4.2-3_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/libconfdb4_1.4.2-3_amd64.deb (--unpack):
trying to overwrite '/usr/lib/libconfdb.so.4.1.0', which is also in package libcorosync4-pve 1.4.4-4
Unpacking libcpg4 (from .../libcpg4_1.4.2-3_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/libcpg4_1.4.2-3_amd64.deb (--unpack):
trying to overwrite '/usr/lib/libcpg.so.4.1.0', which is also in package libcorosync4-pve 1.4.4-4
Unpacking libdlm3 (from .../libdlm3_3.0.12-3.2+deb7u2_amd64.deb) ...
Unpacking libquorum4 (from .../libquorum4_1.4.2-3_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/libquorum4_1.4.2-3_amd64.deb (--unpack):
trying to overwrite '/usr/lib/libquorum.so.4.0.0', which is also in package libcorosync4-pve 1.4.4-4
Unpacking libsalck3 (from .../libsalck3_1.1.4-4.1_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/libsalck3_1.1.4-4.1_amd64.deb (--unpack):
trying to overwrite '/usr/lib/libSaLck.so.3.0.0', which is also in package libopenais3-pve 1.1.4-2
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for man-db ...
Errors were encountered while processing:
/var/cache/apt/archives/libcoroipcc4_1.4.2-3_amd64.deb
/var/cache/apt/archives/libconfdb4_1.4.2-3_amd64.deb
/var/cache/apt/archives/libcpg4_1.4.2-3_amd64.deb
/var/cache/apt/archives/libquorum4_1.4.2-3_amd64.deb
/var/cache/apt/archives/libsalck3_1.1.4-4.1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
I have same problem when I run
apt-get -f install
Code:
# apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
attr bridge-utils ceph-common clvm corosync-pve cstream dtach fancontrol fontconfig fontconfig-config fuse-utils ifenslave-2.6 iputils-arping libaio1 libapache2-mod-apreq2
libapache2-request-perl libapreq2 libasound2 libauthen-pam-perl libcairo2 libcgroup1 libconfdb4 libcoroipcc4 libcorosync4-pve libcpg4 libcrypt-openssl-bignum-perl
libcrypt-openssl-random-perl libcrypt-openssl-rsa-perl libdatrie1 libdbi0 libdevel-cycle-perl libdirectfb-1.2-9 libfile-readbackwards-perl libfile-sync-perl libfilesys-df-perl
libfont-freetype-perl libfontconfig1 libfontenc1 libgmp3c2 libintl-perl libio-multiplex-perl libiscsi1 libjpeg62 liblinux-inotify2-perl liblockfile-simple-perl liblog-agent-perl
liblzo2-2 libnet-dns-perl libnet-ip-perl libnet-snmp-perl libnet-telnet-perl libnspr4-0d libnss3-1d libopenais3-pve libopenipmi0 libpango1.0-0 libpixman-1-0 libpve-common-perl
libpve-storage-perl libqb libquorum4 librados2 librbd1 librrd4 librrds-perl libsalck3 libsdl1.2debian libsdl1.2debian-alsa libsensors4 libsgutils2-2 libsnmp-base libsnmp15
libstring-shellquote-perl libsvga1 libsysfs2 libthai-data libthai0 libts-0.0-0 libvncserver0 libx86-1 libxcb-render-util0 libxcb-render0 libxfont1 libxft2 libxml2-utils
libxrender1 libxslt1.1 lm-sensors lzop openais-pve openipmi pve-qemu-kvm python-openssl python-pexpect python-pycurl rrdcached sg3-utils snmp sqlite3 tsconf ttf-dejavu
ttf-dejavu-core ttf-dejavu-extra vlan vncterm vzquota x11-common xfonts-encodings xfonts-utils xsltproc
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
libconfdb4 libcoroipcc4 libcpg4 libquorum4 libsalck3
The following NEW packages will be installed:
libconfdb4 libcoroipcc4 libcpg4 libquorum4 libsalck3
0 upgraded, 5 newly installed, 0 to remove and 245 not upgraded.
209 not fully installed or removed.
Need to get 0 B/734 kB of archives.
After this operation, 970 kB of additional disk space will be used.
Do you want to continue [Y/n]?
(Reading database ... 57463 files and directories currently installed.)
Unpacking libcoroipcc4 (from .../libcoroipcc4_1.4.2-3_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/libcoroipcc4_1.4.2-3_amd64.deb (--unpack):
trying to overwrite '/usr/lib/libcoroipcc.so.4.0.0', which is also in package libcorosync4-pve 1.4.4-4
Unpacking libconfdb4 (from .../libconfdb4_1.4.2-3_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/libconfdb4_1.4.2-3_amd64.deb (--unpack):
trying to overwrite '/usr/lib/libconfdb.so.4.1.0', which is also in package libcorosync4-pve 1.4.4-4
Unpacking libcpg4 (from .../libcpg4_1.4.2-3_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/libcpg4_1.4.2-3_amd64.deb (--unpack):
trying to overwrite '/usr/lib/libcpg.so.4.1.0', which is also in package libcorosync4-pve 1.4.4-4
Unpacking libquorum4 (from .../libquorum4_1.4.2-3_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/libquorum4_1.4.2-3_amd64.deb (--unpack):
trying to overwrite '/usr/lib/libquorum.so.4.0.0', which is also in package libcorosync4-pve 1.4.4-4
Unpacking libsalck3 (from .../libsalck3_1.1.4-4.1_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/libsalck3_1.1.4-4.1_amd64.deb (--unpack):
trying to overwrite '/usr/lib/libSaLck.so.3.0.0', which is also in package libopenais3-pve 1.1.4-2
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/libcoroipcc4_1.4.2-3_amd64.deb
/var/cache/apt/archives/libconfdb4_1.4.2-3_amd64.deb
/var/cache/apt/archives/libcpg4_1.4.2-3_amd64.deb
/var/cache/apt/archives/libquorum4_1.4.2-3_amd64.deb
/var/cache/apt/archives/libsalck3_1.1.4-4.1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
↧
↧
November 11, 2014, 3:15 am
↧
November 11, 2014, 5:21 am
Hi,
We've been having some serious connection issues with our two node proxmox cluster while they were connected using 10Gb SFP link, so we decided to get a separated (direct) 1gbit RJ45 connection for the nodes to communicate and leave that 10gbit link exclusively for the shared storage NFS server.
My question is, was it enough to simply change the entries in /etc/hosts and /etc/network/interfaces for each node, or should we've done something more?
Here's our current pvecm output for one of the two nodes:
pvecm status
Version: 6.2.0
Config Version: 26
Cluster Name: proxmox-cluster
Cluster Id: 39604
Cluster Member: Yes
Cluster Generation: 288
Membership state: Cluster-Member
Nodes: 2
Expected votes: 3
Quorum device votes: 1
Total votes: 3
Node votes: 1
Quorum: 2
Active subsystems: 8
Flags:
Ports Bound: 0 177 178
Node name: prox-node0002
Node ID: 2
Multicast addresses: 239.192.154.79
Node addresses: 10.10.11.222
Previously the node's address was 10.10.10.222 so as you can see we've changed the subnet. There's another subnet 10.10.10/24 where our NFS server "lives" (which also hosts our quorum disk). Was that enough to separate nodes traffic from storage traffic? Or is there something else we should tweak to make sure that inter-nodes traffic stays separated from the storage?
↧
November 11, 2014, 6:14 am
I was under the impression, through several forum posts, that assigning Virtual Cores to KVM guests have zero (0) impact on KVM performance.
However, after a quick test, I show that there is a big difference when assigning the proper cores.
What is the general rule of thumb when assigning cores?
Below is the test:
Host is (16 x Intel Xeon CPU E5620 @ 2.40GHz (2 Sockets))
Centos 6.6_x64 KVM using the KVM64 chip
Zoneminder server with 8GB of memory and 45 cameras configured
Test one is using a single socket and single core (Machine was very laggy):
single_core.PNG
Test two is using a single socket and 8 cores (Machine load and host load was considerably lower):
octa_core.PNG
Host load:
Test 1 = 1.6
Test 2 = .92
↧
↧
November 11, 2014, 9:18 am
Hi Everybody
I have little problem:
After opening and closing (x) several novnc consoles I loose acces to my Proxmox GUI.
As far as I can see this this is caused due to the fact that the novnc consoles are still open. (no End Time shown in Tasks window at the bottom)
The only way to regain access to the gui is by ssh-ing "/etc/init.d/pveproxy restart" which closes the still open vnc connections and immediatelly gives me back control of the gui
But as I need to just quickly check on several vms to see if everything working fine several times a day, this gets pretty frustrating.
Am I the only one with this proplem?
Is there maybe a "correct" way to close the novnc consoles so the connection really gets closed?
Or do you have another possible solution?
Thanks in advance
Dan
↧
November 11, 2014, 9:50 am
Hello everybody,
Today I started getting the following error when trying to use the KVM on one of my proxmox nodes.
40b932b4ce.png
I have also tried to "pvecm updatecerts".
Any ideeas about what I can do ?
↧
November 11, 2014, 3:40 pm
Hi All,
I just purchased a subscription as I want to upgrade from 3.0-17 to 3.3; but I don't see any 'Updates' tab in the web console?
Can someone tell me how I can get the updates done? I'd like to try and minimize rebooting if I can!
Thanks
Anubis.
↧
November 11, 2014, 3:40 pm
After running a three node cluster for years the fuse system /etc/pve dramatically slowed down yesterday (starting vi on a file on /etc/pve can literally take minutes now). The first thing I did was upgrade all three nodes to the latest/greatest software. That didn't help. Can anyone offer suggestions about where to look/what to change to get our old performance back?
Thanks!
↧
↧
November 11, 2014, 4:05 pm
Hello,
I try to use the new feature avaible in disk Throttle but i don't find a good way to setup it and get decent result.
Maybe because i don't put good value.
How do you benchmark server iops read/write ?
What value would you put in burst based on iops ? Let's said i allow 15 minutes burst on iops
Same for MB, in burst i try many test for benchmark result, but maybe you can advise me a tools for generate data (and iop) so i can check result ?
How to monitor vps that's reach burst limit ?
Thanks for advice.
↧
November 11, 2014, 6:02 pm
Hi all.
Just went to install Proxmox 3.3 on a home box previously running ESXi for about a year. I got this error during install twice and I cannot proceed any further:
http://imgur.com/KjbOYhc
I checked the ISO I downloaded and the MD5 matches. I am using the SUSE Image Writer to "burn" the .raw (once renamed) image to a USB drive. The drive is fine that I am aware of, I get all through the install questions and shortly after it starts the actual install the above error message pops up and it stops.
I googled and looked around the forum but I didn't see anything of note? Any ideas are welcome. :)
↧
November 11, 2014, 8:01 pm
Dear all
i have promox and this have problem.
i'm installed ubuntu and debian guest os in proxmox.
and i found some file interest in guest os which after update online from fresh install.
in debian
1.i found file in /etc/rc3.d/S01afmievedhz
2.here the file
#root@bandrex:~# cat /etc/rc3.d/S01afmievedhz
#!/bin/sh
# chkconfig: 12345 90 90
# description: afmievedhz
### BEGIN INIT INFO
# Provides: afmievedhz
# Required-Start:
# Required-Stop:
# Default-Start : 1 2 3 4 5
# Default-Stop :
# Short-Decription: afmievedhz
### END INIT INFO
case $1 in
start)
/boot/afmievedhz
;;
stop)
;;
*)
/boot/afmievedhz
;;
esac
root@bandrex:~#
before that i try install ubuntu and found file in /boot
#/boot/pubyjjuoif
#/boot/tnsbyrnqjr
#/etc/rc3.d/S90awrmmrnnao -->/etc/init.d/awwrmmrnnao
#/etc/rc3.d/S90pubyjjuoif-->/etc/init.d/pubyjjuoif
#cat /etc/init.d/awwrmmrnnao
#!/bin/sh
# chkconfig: 12345 90 90
# description: awwrmmrnnao
### BEGIN INIT INFO
# Provides: awwrmmrnnao
# Required-Start:
# Required-Stop:
# Default-Start : 1 2 3 4 5
# Default-Stop :
# Short-Decription: awwrmmrnnao
### END INIT INFO
case $1 in
start)
/boot/awwrmmrnnao
;;
stop)
;;
*)
/boot/awwrmmrnnao
;;
esac
the size file all same as 648K
now every i ls -la found some file random /boot
it's is possible my proxmox have been hijack .
thanks for advice
↧
November 12, 2014, 12:18 am
Hey,
Last night's backup posted this error:
Code:
INFO: starting new backup job: vzdump 101 100 --quiet 1 --mode snapshot --compress gzip --storage pmx1-web1 --node mh-pmx1
INFO: filesystem type on dumpdir is 'fuse.sshfs' -using /var/tmp/vzdumptmp2445 for temporary files
INFO: Starting Backup of VM 100 (openvz)
INFO: CTID 100 exist mounted running
INFO: status = running
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating lvm snapshot of /dev/mapper/pve-data ('/dev/pve/vzsnap-mh-pmx1-0')
INFO: Logical volume "vzsnap-mh-pmx1-0" created
INFO: creating archive '/nfs/web1/dump/vzdump-openvz-100-2014_11_12-02_00_02.tar.gz'
INFO: Total bytes written: 35348459520 (33GiB, 20MiB/s)
INFO: archive file size: 19.47GB
INFO: Finished Backup of VM 100 (00:29:38)
INFO: filesystem type on dumpdir is 'fuse.sshfs' -using /var/tmp/vzdumptmp2445 for temporary files
INFO: Starting Backup of VM 101 (openvz)
INFO: CTID 101 exist mounted running
INFO: status = running
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating lvm snapshot of /dev/mapper/pve-data ('/dev/pve/vzsnap-mh-pmx1-0')
INFO: Logical volume "vzsnap-mh-pmx1-0" created
INFO: creating archive '/nfs/web1/dump/vzdump-openvz-101-2014_11_12-02_29_40.tar.gz'
INFO: tar: ./home/mysite/descarca/revista_2.pdf: File shrank by 5920717 bytes; padding with zeros
INFO: tar: ./home/mysite/descarca/revista_3.pdf: Read error at byte 0, while reading 10240 bytes: Input/output error
INFO: tar: ./home/mysite/site/: Cannot savedir: Input/output error
INFO: tar: ./home/mysite/site/phpinfo.php: Read error at byte 0, while reading 19 bytes: Input/output error
INFO: tar: ./home/mysite/css/: Cannot savedir: Input/output error
INFO: tar: ./home/mysite/css/sequencejs-theme.modern-slide-in.css: Read error at byte 0, while reading 3584 bytes: Input/output error
INFO: tar: ./home/mysite/css/jquery.fancybox.css: Read error at byte 0, while reading 8192 bytes: Input/output error
INFO: tar: ./home/mysite/css/fancybox-y.png: Read error at byte 0, while reading 176 bytes: Input/output error
INFO: tar: ./home/mysite/css/sequencejs-theme.modern-slide-in.ie.css: Read error at byte 0, while reading 29 bytes: Input/output error
INFO: tar: ./home/mysite/css/style.css: Read error at byte 0, while reading 7168 bytes: Input/output error
INFO: tar: ./home/mysite/css/fancybox.png: Read error at byte 0, while reading 5120 bytes: Input/output error
INFO: tar: ./home/mysite/css/normalize.css: Read error at byte 0, while reading 9004 bytes: Input/output error
INFO: tar: ./home/mysite/css/fancybox-x.png: Read error at byte 0, while reading 203 bytes: Input/output error
INFO: tar: ./home/mysite/downloads.php: Read error at byte 0, while reading 392 bytes: Input/output error
INFO: tar: ./home/mysite/search.php: Read error at byte 0, while reading 1586 bytes: Input/output error
INFO: tar: ./home/mysite/resetare-parola.php: Read error at byte 0, while reading 1823 bytes: Input/output error
INFO: tar: ./home/mysite/googlebbb5b9e4e5511985.html: Read error at byte 0, while reading 53 bytes: Input/output error
INFO: tar: ./home/mysite/blogroll.php: Read error at byte 0, while reading 2048 bytes: Input/output error
INFO: tar: ./home/mysite/mysql.php: Read error at byte 0, while reading 1327 bytes: Input/output error
INFO: tar: ./home/mysite/emails/: Cannot savedir: Input/output error
INFO: tar: ./home/mysite/emails/trimitere-factura.php: Read error at byte 0, while reading 206 bytes: Input/output error
INFO: tar: ./home/mysite/emails/factura.php: Read error at byte 0, while reading 5632 bytes: Input/output error
INFO: tar: ./home/mysite/emails/lost-password.php: Read error at byte 0, while reading 141 bytes: Input/output error
INFO: tar: ./home/mysite/emails/contact.php: Read error at byte 0, while reading 370 bytes: Input/output error
INFO: tar: ./home/mysite/emails/comanda-online-aprobata.php: Read error at byte 0, while reading 353 bytes: Input/output error
INFO: tar: ./home/mysite/epayment/: Cannot savedir: Input/output error
INFO: tar: ./home/mysite/epayment/function.php: Read error at byte 0, while reading 512 bytes: Input/output error
INFO: tar: ./home/mysite/epayment/pay.php: Read error at byte 0, while reading 4840 bytes: Input/output error
INFO: tar: ./home/mysite/epayment/ep_reply.php: Read error at byte 0, while reading 2357 bytes: Input/output error
INFO: tar: ./home/mysite/nws.php: Read error at byte 0, while reading 284 bytes: Input/output error
INFO: tar: ./home/mysite/plata.php: Read error at byte 0, while reading 370 bytes: Input/output error
INFO: tar: ./home/mysite/comanda.php: Read error at byte 0, while reading 5258 bytes: Input/output error
INFO: tar: ./home/mysite/articol.php: Read error at byte 0, while reading 2048 bytes: Input/output error
...with "Read error at byte 0..." repeating for every other file on *all* CTs.
Please note that:
- before using GZIP we've used LZO for backups and had no issues
- the NFS share is mounted and fully functional
- node and attached NFS have enough space
- node and attached NFS use new SSDs and have 0 corrupted sectors
Can you please give me a hint?
Thanks,
Razvan
↧
↧
November 12, 2014, 12:52 am
Hey,
Is there any way to set Proxmox to send an e-mail notification when a job has errors? As a quick example, we had
some backup errors last night and we didn't received any kind of notification, which is not OK.
Thanks,
Razvan
↧
November 12, 2014, 1:59 am
Hi, i have a VMware image with two partition (2 .vmdk files), i started this machine with a .vmx file. It's possibile import this VM to proxmox?
I have read thid guide
http://pve.proxmox.com/wiki/Migratio..._to_Proxmox_VE, but i don't know which method to follow (clonezilla or import vmdk directly)
↧
November 12, 2014, 2:15 am
Hi all,
Some time ago, I've used the defaults parameters for installing a 3.0 Proxmox server on a HP server with 4*600Go DD configured with RAID 1+0. This server is for now hosting only one VM (ubuntu 12.04 + postgresql 9.1) and I need to upgrade it to ubuntu 14.04 + PG 9.3, but the upgrade process requires more disk space than availabled as pg_upgradecluster will clone a big database.
For this purpose, I want to resize the swap and the root partitions as they are too large one the proxmox server :
Code:
root@dedale:~# lvs
LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert
data pve -wi-ao-- 865.64g
root pve -wi-ao-- 96.00g
swap pve -wi-ao-- 139.62g
Code:
root@dedale:~# df -h
Sys. fich. Taille Util. Dispo Uti% Monté sur
udev 10M 0 10M 0% /dev
tmpfs 19G 336K 19G 1% /run
/dev/mapper/pve-root 95G 971M 89G 2% /
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 38G 13M 38G 1% /run/shm
/dev/mapper/pve-data 853G 493G 361G 58% /var/lib/vz
/dev/sda1 495M 34M 436M 8% /boot
/dev/fuse 30M 12K 30M 1% /etc/pve
The same problem occurs in the Ubuntu VM as the defaults install parameters set a near 200Go swap partition:
Code:
minos@icare:/$ sudo lvs
[sudo] password for minos:
LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert
root icare -wi-ao--- 513,76g
swap_1 icare -wi-ao--- 186,00g
So, is it possible (and how) to shrink pve-root and pve-swap, says to 5Go each (if it's ok for Proxmox), and to extend pve-data accordingly and set the available space in the VM?
Thanks
↧
November 12, 2014, 4:39 am
Hi,
I have tried upgrading to pve-kernel-3.10.0-5-pve .
Code:
Starting DRBD resources: DRBD module version: 8.4.3
userland version: 8.3.13
you should upgrade your drbd tools
This error turns whole proxmox thing in to halt.
Included userlad is 8.3.13 (drbd8-utils), while kernel module is 8.4.3.
pve-no-subscription repository does not contain drbd-utils or drbd8-utils packages.
Does that mean i need to compile drbd utils appropriate version or your enterprise repositories contain ready package for this kernel.
Regards,
adg
↧
↧
November 12, 2014, 5:09 am
Hi everyone!
About 6 months ago we purchased brand new servers, installed Proxmox and started migrating our existing KVM virtual servers to the Proxmox platform.
We have 3 frontends running Proxmox in a cluster, all attached to a SAN running Nexenta.
Everything has been working smoothly, but a few days ago when I started to migrate an old server to the new system something weird happened.
In the Proxmox GUI, 2 vm's (running on the same server) show status as stopped, even though they are running just fine.
They show as stopped even if I log in to either of the two other Proxmox frontends.
I am afraid to do something right now in case of data corruption if I attempt to stop, start or migrate over to one of the other frontends.
Would a simple reboot from inside the vm's give them status running again?
I wanted to try the forums before I open a ticket, in case anyone else runs in to the same issue later on.
Note that the vm's running on the two other servers still show as running in the Proxmox GUI.
Hope anyone can shed some light on this as it is quite confusing.
Thank you in advance boys and girls!
-Tore
↧
November 12, 2014, 9:14 am
Good day, I want to say that I have a problem with a disk 1 tb you add to storage via lvm, on Sunday there was a cut of electricity lit the physical machine, by either Proxmox but the virtual machine I do not get up, check the log yy indicates that I can not find the disk with uuid, I had two groups DiscoGrande pve and I have no backup in / etc / lvm / backup, I made a --removemissing vgreduce can now add the physical disk and create the group but access DiscoGrande I had the virtual disk within the lvm partition someone can help me please?
↧
November 12, 2014, 11:09 am
I'm experimenting with the VM Disk Throttle settings. So far here is my understanding:
- Read limit (MB/s): total read bandwidth per second allowed (I'm using 115 to simulate a HDD)
- Write limit (MB/s): total write bandwidth per second allowed (I'm using 115 to simulate a HDD)
- Read limit (ops/s): number of read io operations per second (iops) (I'm using 300 to simulate a HDD doing sequential reads)
- Read limit (ops/s): number of write io operations per second (iops) (I'm using 100 to simulate a HDD doing sequential writes)
In terms of the Read max burst (MB) (similar theory for Write max burst (MB), Read max burst (ops), Write max burst (ops)):
- This value refers to a leaky bucket algorithm which I'm assuming works like so:
- You set it for something equal to or larger than the "Read limit (MB/s)" say 500.
- This will allow you to burst up to 500MB at the max speed or the storage system.
- Once you hit that limit you have to wait for the bucket to refill from the value you set for "Read Limit (MB/s)". So for a value of 115 this would take 4.34s. This is assuming you have no IO happening after the burst otherwise that will delay the refill.
Now the questions
- Is this correct so far?
- What are the default values if you don't fill in a value for Read max burst etc..?
- What values are others using for Disk Throttle?
Thanks, James.
↧