Re: [pve-devel] clustered /var/log/pve

Never mind.I found the culprit the file is just read to early by other nodes. Stefan Excuse my typo sent from my mobile phone. > Am 22.03.2017 um 15:19 schrieb Stefan Priebe - Profihost AG > : > > Hi, > > this works fine with /var/log/pve/tasks which is the folder i wanted to > share. > > It

[pve-devel] [PATCH pve-zsync] fix check for cdrom.

It is false positive if cache mode is set to none. --- pve-zsync | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pve-zsync b/pve-zsync index bf71894..68a03d4 100644 --- a/pve-zsync +++ b/pve-zsync @@ -770,7 +770,7 @@ sub parse_disks { while ($text && $text =~ s/^(.*?)(\n|$

Re: [pve-devel] clustered /var/log/pve

Hi, this works fine with /var/log/pve/tasks which is the folder i wanted to share. It seems to work for all logs which are now also available after migrations. The only thing which is not working is the migration log itself. Which always get's a status of "unexpected status". Is there anything s

Re: [pve-devel] Proxmox VE 5.0 beta1 released!

Hi Martin Can't wait to try it! Is this release already include Cloud-Init?? Thanks a lot 2017-03-22 10:51 GMT-03:00 Martin Maurer : > Hi all! > > We are proud to announce the release of the first beta of our Proxmox VE > 5.x family - based on the great Debian Stretch. > > Get more details from

[pve-devel] Proxmox VE 5.0 beta1 released!

Hi all! We are proud to announce the release of the first beta of our Proxmox VE 5.x family - based on the great Debian Stretch. Get more details from the forum announcement: https://forum.proxmox.com/threads/proxmox-ve-5-0-beta1-released.33731/ -- Best Regards, Martin Maurer Proxmox VE proje

[pve-devel] [PATCH firewall 2/2] log errors encountered by the daemon to syslog

--- This has been bugging me for way too long. That whole $verbose/$noerr mess needs to be cleaned up at some point. src/PVE/Firewall.pm | 11 --- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/src/PVE/Firewall.pm b/src/PVE/Firewall.pm index 0535d78..cc81325 100644 --- a/sr

[pve-devel] [PATCH firewall 1/2] forbid trailing commas in lists

iptables-restore doesn't allow them --- Another one of these annoying cases... We really need to start testing with `iptables-restore -t` and flag broken rules somehow... src/PVE/Firewall.pm | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/src/PVE/Firewall.pm b/src/PVE/

[pve-devel] Pve and Amazon S3

Hi all In order to make hybrid environment, it's reasonable suggest that Proxmox could access Amazon S3 as Storage backend?? Could this been a nice feature??? -- Obrigado Cordialmente Gilberto Ferreira Consultoria em Servidores e Serviços Linux | Virtualização Proxmox | Zentyal Server | Zimbr

[pve-devel] [PATCH cluster] Use a real FQDN when defining the CommonName entry of SSL certs

The proper way to set the fqdn is via /etc/hosts or via DNS -see hostname(1)- --- data/PVE/Cluster.pm | 14 -- 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/data/PVE/Cluster.pm b/data/PVE/Cluster.pm index ab57da9..e694d93 100644 --- a/data/PVE/Cluster.pm +++ b/data/PVE/

[pve-devel] [PATCH common] Use "real" Fully Qualified Domain Name for setting the common name of a ssl cert

In the future we want to have multiple search domains set or read from the API, so a single search domain is not a good fit for building a full qualified domain name. For backwards compatibility, the previously generated way of getting the fqdn is prepended to the list of Alternative Subject Names

[pve-devel] [PATCH common] Add utility subroutine to get the fully qualified domain name of a host

--- src/PVE/Tools.pm | 20 +++- 1 file changed, 19 insertions(+), 1 deletion(-) diff --git a/src/PVE/Tools.pm b/src/PVE/Tools.pm index 69c8730..4815d61 100644 --- a/src/PVE/Tools.pm +++ b/src/PVE/Tools.pm @@ -4,7 +4,7 @@ use strict; use warnings; use POSIX qw(EINTR EEXIST EOPNOT

[pve-devel] [PATCH manager 2/2] ceph/pool: allow bigger size and min_size values

Some setups may want to use more replicas as three, while my proposed maximal 7 replicas is also arbitrary it should cover all normal usecases (i.e. 5 replicas) and a bit more, just to be sure. --- www/manager6/ceph/Pool.js | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ww

[pve-devel] [PATCH manager 1/2] ceph/pool: change default replica to 3/2

size/min_size 2/1 is unsafe as it can result in split brains, so we should not recommend it as default. If the user really wants it he can still set it explicit. --- www/manager6/ceph/Pool.js | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/www/manager6/ceph/Pool.js b/www/m

[pve-devel] [PATCH container] pct: improve error message output of die

--- src/PVE/CLI/pct.pm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/PVE/CLI/pct.pm b/src/PVE/CLI/pct.pm index 53d110c..4b92280 100755 --- a/src/PVE/CLI/pct.pm +++ b/src/PVE/CLI/pct.pm @@ -605,7 +605,7 @@ __PACKAGE__->register_method({ my $code = sub {