> But, Debian Stretchs Version of Systemd makes TimeoutStopSec defaults
> to 'DefaultTimeoutStopSec' if it was not set, which is by default 90
> seconds – much less than infinity.
Thank for finding this bug !!!
___
pve-devel mailing list
pve-devel@pve.p
This services is responsible for bringing up 'onboot' marked guests
on host power-on and stop _all_ guests gracefully on host shutdown
(be it reboot, shutdow, halt, ..)
It's type is set to 'oneshot', which implies a TimeoutStartSec of
'infinity', by default. With Jessies Version of Systemd the
Tim
the name 'pve-manager' collides with our pve-manager package name,
which - from the user point of view - provides mainly the API and
WebUI.
An user could thus think that restarting 'pve-manager' would restart
the WebUIs server, which is relatable.
But, the pve-manager.service does not controls the
Since Stretch with its newer systemd this service had a regression
when stopping. The timeout for stop changed from infinity to 90
seconds, meaning that if it is not finished until then it receives a
sigkill shortly therafter.
As it shutdowns (first gracefully, then after 180 seconds
ungracefully)
Signed-off-by: Thomas Lamprecht
---
bin/init.d/pve-manager.service | 1 -
bin/init.d/pve-storage.target | 1 +
2 files changed, 1 insertion(+), 1 deletion(-)
diff --git a/bin/init.d/pve-manager.service b/bin/init.d/pve-manager.service
index 5e6bcdf9..daba7d4e 100644
--- a/bin/init.d/pve-manager
The API calls are not to chatty but may give helpfull hints about
what gets tried to be done.
This may help an Admin to figure out which guest delays his host
shutdown.
Signed-off-by: Thomas Lamprecht
---
bin/init.d/pve-manager.service | 2 --
1 file changed, 2 deletions(-)
diff --git a/bin/in
Signed-off-by: Thomas Lamprecht
---
bin/init.d/pve-manager.service | 2 ++
1 file changed, 2 insertions(+)
diff --git a/bin/init.d/pve-manager.service b/bin/init.d/pve-manager.service
index 9f4e6277..69ebd2e9 100644
--- a/bin/init.d/pve-manager.service
+++ b/bin/init.d/pve-manager.service
@@ -1,
Using the nodename is not correct and can lead to mails not forwarding
in restrictive mail server configurations.
---
src/PVE/HA/Env/PVE2.pm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/PVE/HA/Env/PVE2.pm b/src/PVE/HA/Env/PVE2.pm
index fdfadd7..722d1b7 100644
--- a/s
Hi,
Seem than mellanox connectx-5 card are buggy on kernel 4.10.
works fine with kernel 4.4 and 4.12.
I'll try to backport last patches from 4.12 or 4.9.
Too bad that 4.10 is not lts :(
[ 38.920764] mlx5_core :04:00.1 eth5: TX timeout detected
[ 38.920786] mlx5_core :04:00.1 eth5: TX
applied
On Fri, Sep 08, 2017 at 11:31:33AM +0200, Dominik Csapak wrote:
> it is '/etc/pve/nodes/' not '/etc/pve/node/'
>
> Signed-off-by: Dominik Csapak
> ---
> pvesr.adoc | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/pvesr.adoc b/pvesr.adoc
> index 8dc9c87..eafc
as cherry-picks to stable-4. please mark such series with stable-4 in
the future and indicate that they are cherry-picks ('cherry-pick -x'
automates this ;))
___
pve-devel mailing list
pve-devel@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/lis
it is '/etc/pve/nodes/' not '/etc/pve/node/'
Signed-off-by: Dominik Csapak
---
pvesr.adoc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/pvesr.adoc b/pvesr.adoc
index 8dc9c87..eafc9e6 100644
--- a/pvesr.adoc
+++ b/pvesr.adoc
@@ -220,8 +220,8 @@ issue itself.
- move both
applied
On Mon, Aug 14, 2017 at 02:16:36PM +0200, Dominik Csapak wrote:
> qm importdisk has only three positional arguments:
> vmid source-disk target-storage
>
> Signed-off-by: Dominik Csapak
> ---
> qm.adoc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/qm.adoc b/qm
13 matches
Mail list logo
