From: dea <dea@corep.it>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Thomas Lamprecht <t.lamprecht@proxmox.com>,
David Lawley <davel@upilab.com>
Subject: Re: [pbs-devel] Scheduler causing connectivity issues?
Date: Tue, 19 Jul 2022 17:08:17 +0200 [thread overview]
Message-ID: <ea5f044b-9cf0-56ad-1baf-d4393606a4a4@corep.it> (raw)
In-Reply-To: <4b8215df-059b-d7e8-c253-1e4c52ebf192@proxmox.com>
Sorry but i can't upgrade for testing from 2.2-1 to 2.2-5 right now.
It is a production server and I am completing a garbage collector, which
takes several days to finish. I have to free up space and if I update
the process is interrupted and I have to start it again losing days.
Sorry
Il 19/07/22 15:04, Thomas Lamprecht ha scritto:
> Am 19/07/2022 um 13:01 schrieb David Lawley:
>> Just a note, most if not all of my timeout issues seem to have "disappeared"
>>
>> proxmox-backup: 2.2-1 (running kernel: 5.15.39-1-pve) proxmox-backup-server:
>> 2.2.5-1 (running version: 2.2.5) pve-kernel-5.15: 7.2-6 pve-kernel-helper: 7.2-6
>> pve-kernel-5.13: 7.1-9 pve-kernel-5.11: 7.0-10 pve-kernel-5.4: 6.4-4
>> pve-kernel-5.15.39-1-pve: 5.15.39-1 pve-kernel-5.15.35-3-pve: 5.15.35-6
>> pve-kernel-5.13.19-6-pve: 5.13.19-15 pve-kernel-5.13.19-2-pve: 5.13.19-4
>> pve-kernel-5.11.22-7-pve: 5.11.22-12 pve-kernel-5.4.124-1-pve: 5.4.124-1
>> pve-kernel-5.4.65-1-pve: 5.4.65-1 ifupdown2: 3.1.0-1+pmx3 libjs-extjs: 7.0.0-1
>> proxmox-backup-docs: 2.2.5-1 proxmox-backup-client: 2.2.5-1
>> proxmox-mini-journalreader: 1.2-1 proxmox-widget-toolkit: 3.5.1 pve-xtermjs:
>> 4.16.0-1 smartmontools: 7.2-pve3 zfsutils-linux: 2.1.4-pve1
>>
> thank you very much, such notes are already helping a lot - silence is hard
> to parse after all :-)
>
>
> _______________________________________________
> 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-19 15:08 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
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 [this message]
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=ea5f044b-9cf0-56ad-1baf-d4393606a4a4@corep.it \
--to=dea@corep.it \
--cc=davel@upilab.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=t.lamprecht@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.