> I ask the question, because the 2 times I have problem, it was when shutting
> down a server.
> So maybe some strange behaviour occur with both corosync && pmxcfs are
> stopped at same time ?
pmxcfs cannot send anything in that case, so it is impossible that this has
effects on other nodes.
On 9/15/20 8:27 AM, Alexandre DERUMIER wrote:
>>> This is by intention - we do not want to stop pmxcfs only because coorosync
>>> service stops.
>
> Yes, but at shutdown, it could be great to stop pmxcfs before corosync ?
> I ask the question, because the 2 times I have problem, it was when shut
>>pmxcfs cannot send anything in that case, so it is impossible that this has
>>effects on other nodes.
yes, I understand that, but I was thinking of the case if corosync is in
stopping phase (not totally stopped).
Something racy (I really don't known).
I just send 2 patch to start pve-cluster
Signed-off-by: Alexandre Derumier
---
debian/pve-cluster.service | 1 +
1 file changed, 1 insertion(+)
diff --git a/debian/pve-cluster.service b/debian/pve-cluster.service
index cc909f0..d7d0712 100644
--- a/debian/pve-cluster.service
+++ b/debian/pve-cluster.service
@@ -13,6 +13,7 @@ After=rrdc
Currently we don't have any log at shutdown
Signed-off-by: Alexandre Derumier
---
...-start-corosync.service-after-syslog.patch | 25 +++
debian/patches/series | 1 +
2 files changed, 26 insertions(+)
create mode 100644
debian/patches/0003-start-corosyn
On 9/14/20 12:32 PM, Oguz Bektas wrote:
> Signed-off-by: Oguz Bektas
> ---
> src/PVE/LXC/Config.pm | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/src/PVE/LXC/Config.pm b/src/PVE/LXC/Config.pm
> index 4cd669c..223b10e 100644
> --- a/src/PVE/LXC/Config.pm
> +++ b/src/
On Tue, Sep 15, 2020 at 11:03:52AM +0200, Thomas Lamprecht wrote:
> On 9/14/20 12:32 PM, Oguz Bektas wrote:
> > Signed-off-by: Oguz Bektas
> > ---
> > src/PVE/LXC/Config.pm | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/src/PVE/LXC/Config.pm b/src/PVE/LXC/Conf
increase the limit of total cpu cores to 8192 to match it with the
kernel limit.
pve-container:
Oguz Bektas (1):
fix #2938: increase limit of max cores from 128 to 8192
src/PVE/LXC/Config.pm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
pve-manager:
Oguz Bektas (1):
lxc: incre
to match limit from kernel
https://git.proxmox.com/?p=mirror_ubuntu-focal-kernel.git;a=blob;f=arch/x86/Kconfig;h=8ef85139553f5a4ad5187375af898266355c4177;hb=b311b46c7d1ab21bf0a11a6fa5bad76f98fb77af#l1014
Signed-off-by: Oguz Bektas
---
src/PVE/LXC/Config.pm | 4 ++--
1 file changed, 2 insertions
Signed-off-by: Oguz Bektas
---
www/manager6/lxc/ResourceEdit.js | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/www/manager6/lxc/ResourceEdit.js b/www/manager6/lxc/ResourceEdit.js
index 476a9a28..dbc75f99 100644
--- a/www/manager6/lxc/ResourceEdit.js
+++ b/www/manager6/lxc/Res
On 9/15/20 11:14 AM, Oguz Bektas wrote:
> to match limit from kernel
>
> https://git.proxmox.com/?p=mirror_ubuntu-focal-kernel.git;a=blob;f=arch/x86/Kconfig;h=8ef85139553f5a4ad5187375af898266355c4177;hb=b311b46c7d1ab21bf0a11a6fa5bad76f98fb77af#l1014
>
> Signed-off-by: Oguz Bektas
> ---
> src/PV
On 9/15/20 11:16 AM, Oguz Bektas wrote:
> Signed-off-by: Oguz Bektas
> ---
> www/manager6/lxc/ResourceEdit.js | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
applied, thanks!
Note that you need to use the `--in-reply-to=message-id` CLI switch,
not "--reply-to", they are two differe
Hi,
I have finally reproduce it !
But this is with a corosync restart in cron each 1 minute, on node1
Then: lrm was stuck for too long for around 60s and softdog have been triggered
on multiple other nodes.
here the logs with full corosync debug at the time of last corosync restart.
node1 (
On 9/15/20 11:35 AM, Alexandre DERUMIER wrote:
> Hi,
>
> I have finally reproduce it !
>
> But this is with a corosync restart in cron each 1 minute, on node1
>
> Then: lrm was stuck for too long for around 60s and softdog have been
> triggered on multiple other nodes.
>
> here the logs with fu
Signed-off-by: Hannes Laimer
---
src/window/SafeDestroy.js | 24 +++-
1 file changed, 7 insertions(+), 17 deletions(-)
diff --git a/src/window/SafeDestroy.js b/src/window/SafeDestroy.js
index dfb0185..fb27659 100644
--- a/src/window/SafeDestroy.js
+++ b/src/window/SafeDestroy
Signed-off-by: Hannes Laimer
---
www/manager6/ceph/Pool.js | 5 +++--
www/manager6/lxc/Config.js | 5 +++--
www/manager6/qemu/Config.js | 5 +++--
www/manager6/storage/ContentView.js | 5 +++--
4 files changed, 12 insertions(+), 8 deletions(-)
diff --git a/www/manager6
Signed-off-by: Hannes Laimer
---
src/window/SafeDestroy.js | 30 +++---
1 file changed, 15 insertions(+), 15 deletions(-)
diff --git a/src/window/SafeDestroy.js b/src/window/SafeDestroy.js
index fb27659..39706b9 100644
--- a/src/window/SafeDestroy.js
+++ b/src/window/Safe
Signed-off-by: Hannes Laimer
---
src/window/SafeDestroy.js | 58 +++
1 file changed, 29 insertions(+), 29 deletions(-)
diff --git a/src/window/SafeDestroy.js b/src/window/SafeDestroy.js
index 4cc1d89..dfb0185 100644
--- a/src/window/SafeDestroy.js
+++ b/src/wi
Signed-off-by: Hannes Laimer
---
www/DirectoryList.js | 25 +
1 file changed, 25 insertions(+)
diff --git a/www/DirectoryList.js b/www/DirectoryList.js
index 00531fd0..e605a685 100644
--- a/www/DirectoryList.js
+++ b/www/DirectoryList.js
@@ -21,6 +21,24 @@ Ext.define('PBS
Signed-off-by: Hannes Laimer
---
src/api2/node/disks/directory.rs | 4
1 file changed, 4 insertions(+)
diff --git a/src/api2/node/disks/directory.rs b/src/api2/node/disks/directory.rs
index 0d9ddeef..38a0ba74 100644
--- a/src/api2/node/disks/directory.rs
+++ b/src/api2/node/disks/directory.
Signed-off-by: Hannes Laimer
---
src/Utils.js | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/Utils.js b/src/Utils.js
index 8595cce..9017277 100644
--- a/src/Utils.js
+++ b/src/Utils.js
@@ -645,6 +645,7 @@ utilities: {
stopall: ['', gettext('Stop all VMs and Containers')],
Signed-off-by: Hannes Laimer
---
www/manager6/Makefile | 1 -
www/manager6/window/SafeDestroy.js | 194 -
2 files changed, 195 deletions(-)
delete mode 100644 www/manager6/window/SafeDestroy.js
diff --git a/www/manager6/Makefile b/www/manager6/Makefile
Add functionality to remove directories in the PBS WebUI. In order to do that
SafeDestroy had to be moved from
pve-manager into proxmox-widget-toolkit and the possibility to show a small
note in the dialog had to be added.
Furthermore specifics to pve-manager in SafeRemove were replaces with a mo
Signed-off-by: Hannes Laimer
---
src/window/SafeDestroy.js | 28
1 file changed, 28 insertions(+)
diff --git a/src/window/SafeDestroy.js b/src/window/SafeDestroy.js
index 39706b9..87f81b7 100644
--- a/src/window/SafeDestroy.js
+++ b/src/window/SafeDestroy.js
@@ -21,6
Signed-off-by: Hannes Laimer
---
src/Makefile | 1 +
src/window/SafeDestroy.js | 194 ++
2 files changed, 195 insertions(+)
create mode 100644 src/window/SafeDestroy.js
diff --git a/src/Makefile b/src/Makefile
index 12dda30..ea71647 100644
---
here the previous restart log
node1 -> corosync restart at 10:46:15
-
https://gist.github.com/aderumier/0992051d20f51270ceceb5b3431d18d7
node2
-
https://gist.github.com/aderumier/eea0c50fefc1d8561868576f417191ba
node5
--
https://gist.github.com/aderumier/f2ce1bc5a93827045a5691583
also logs of node14, where the lrm was not too long
https://gist.github.com/aderumier/a2e2d6afc7e04646c923ae6f37cb6c2d
- Mail original -
De: "aderumier"
À: "Thomas Lamprecht"
Cc: "Proxmox VE development discussion"
Envoyé: Mardi 15 Septembre 2020 12:15:47
Objet: Re: [pve-devel] corosy
This series makes importing disks possible via GUI which is one step to make
migrating from other hypervisors easier.
qemu-server: Dominic Jäger (1):
Move importdisk from qm to API
pve-manager: Dominic Jäger (1):
Hardware View: Add GUI for importdisk
--
2.20.1
Make importing single disks easier.
Required to import a whole VM via GUI.
Signed-off-by: Dominic Jäger
---
v3->v4:
* Reuse propertyStringSet instead of building it myself
* More detailed permissions
* Reorder GUI elements such that source is first
* Assemble importdisk URL here instead of widget
Required to create a GUI for importdisk.
Add parameters that enable directly attaching the disk to a bus/device with all
known disk options. This avoids intermediate steps as unused disk.
We allow different places as source
* Regular VM images on PVE storages (Normal users + root)
* Other disk im
I'm looking forward to test this new feature.
Sometimes is really annoying make importdisk from cli.
I also would like to recommend add some feature to import OVA/OVF images
using WEB interface, if this is possible, of course.
Thanks for such wonderful work!
---
Gilberto Nunes Ferreira
Em ter.
Hi,
I have produce it again,
now I can't write to /etc/pve/ from any node
I have also added some debug logs to pve-ha-lrm, and it was stuck in:
(but if /etc/pve is locked, this is normal)
if ($fence_request) {
$haenv->log('err', "node need to be fenced - releasing
agent_l
On 9/15/20 2:49 PM, Alexandre DERUMIER wrote:
> Hi,
>
> I have produce it again,
>
> now I can't write to /etc/pve/ from any node
>
OK, so seems to really be an issue in pmxcfs or between corosync and pmxcfs,
not the HA LRM or watchdog mux itself.
Can you try to give pmxcfs real time scheduli
>>
>>Can you try to give pmxcfs real time scheduling, e.g., by doing:
>>
>># systemctl edit pve-cluster
>>
>>And then add snippet:
>>
>>
>>[Service]
>>CPUSchedulingPolicy=rr
>>CPUSchedulingPriority=99
yes, sure, I'll do it now
> I'm currently digging the logs
>>Is your most simplest/stabl
about node1: /etc/pve directory seem to be in bad state, that's why it can't
be mount
ls -lah /etc/pve:
?? ? ?? ?? pve
I have forced an lazy umount
umount -l /etc/pve
and now it's working fine.
(so maybe when pmxcfs was killed, it don't have cleanly umount
On 9/15/20 4:09 PM, Alexandre DERUMIER wrote:
>>> Can you try to give pmxcfs real time scheduling, e.g., by doing:
>>>
>>> # systemctl edit pve-cluster
>>>
>>> And then add snippet:
>>>
>>>
>>> [Service]
>>> CPUSchedulingPolicy=rr
>>> CPUSchedulingPriority=99
> yes, sure, I'll do it now
>
>
>>I mean this is bad, but also great!
>>Cam you do a coredump of the whole thing and upload it somewhere with the
>>version info
>>used (for dbgsym package)? That could help a lot.
I'll try to reproduce it again (with the full lock everywhere), and do the
coredump.
I have tried the real ti
Another small lock at 17:41:09
To be sure, I have done a small loop of write each second in /etc/pve, node
node2.
it's hanging at first corosync restart, then, on second corosync restart it's
working again.
I'll try to improve this tomorrow to be able to debug corosync process
- restarting
Hello good day !
First of all, I would like to congratulate Proxmox for the excellent
evolution of the solution, the possibility of being able to have via GUI
the option of being able to importdisk from other platforms such as ovf,
ova .. will also be possible. browser button to perform di
Hello good day !
First of all, I would like to congratulate Proxmox for the excellent
evolution of the solution, the possibility of being able to have via GUI
the option of being able to importdisk from other platforms such as ovf,
ova .. will also be possible. browser button to perform di
40 matches
Mail list logo
