From: dea <dea@corep.it>
To: pbs-devel@lists.proxmox.com
Subject: Re: [pbs-devel] Scheduler causing connectivity issues?
Date: Wed, 13 Jul 2022 09:55:01 +0200 [thread overview]
Message-ID: <44003613-8b69-f6b1-9ac8-4f7d16235a36@corep.it> (raw)
In-Reply-To: <emd3a2db7f-02fe-4abf-8754-a57c0c1dfbb3@e231eb23.com>
Hi,
I can confirm, serious problems with the 2.2-3 release. Continuous
disconnections, backups never started due to non-availability of the PBS.
Downgraded to release 2.2-1, all fixed, works perfectly.
Luca
Il 11/07/22 10:44, Mark Schouten ha scritto:
> Hi,
>
>>> Hope you guys can find something.. If I need to debug anything, let
>>> me know!
>>
>> Thanks for the info, this already helps quite a bit. We'll look into
>> it and re-check
>> with you if we need more info.
>>
>
> Any chance you can think of a workaround for the time being, other
> than downgrading?
>
> —
> Mark Schouten, CTO
> Tuxis B.V.
> mark@tuxis.nl
>
>
>
> _______________________________________________
> pbs-devel mailing list
> pbs-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2022-07-13 7:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 15:49 Mark Schouten
2022-07-08 7:09 ` Thomas Lamprecht
2022-07-08 9:36 ` Jorge Boncompte
2022-07-08 9:40 ` dea
2022-07-11 8:44 ` Mark Schouten
2022-07-13 7:55 ` dea [this message]
2022-07-13 8:14 ` Thomas Lamprecht
2022-07-13 10:41 ` Mark Schouten
2022-07-15 11:49 ` Thomas Lamprecht
2022-07-15 12:01 ` dea
2022-07-15 12:57 ` Thomas Lamprecht
2022-07-15 13:02 ` dea
2022-07-15 13:24 ` dea
2022-07-15 14:43 ` dea
2022-07-17 15:04 ` dea
2022-07-18 13:30 ` Thomas Lamprecht
2022-07-19 11:01 ` David Lawley
2022-07-19 13:04 ` Thomas Lamprecht
2022-07-19 15:08 ` dea
2022-07-18 7:31 ` Mark Schouten
2022-07-18 11:03 ` Thomas Lamprecht
2022-07-20 7:30 ` Mark Schouten
2022-07-21 13:10 ` Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44003613-8b69-f6b1-9ac8-4f7d16235a36@corep.it \
--to=dea@corep.it \
--cc=pbs-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox