public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: dea <dea@corep.it>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
	Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>, Mark Schouten <mark@tuxis.nl>
Subject: Re: [pbs-devel] Scheduler causing connectivity issues?
Date: Fri, 15 Jul 2022 16:43:24 +0200	[thread overview]
Message-ID: <e4d60e8c-1a62-3b8e-a9cc-b3ab29d75f33@corep.it> (raw)
In-Reply-To: <8da163af-207a-af23-4f2b-c68c226b4d5c@corep.it>


... no... better than before, much better, but I still have network 
holes. Traffic in sync at 250 mbps ... I see that it collapses to zero, 
I try to log into the console .. nothing, then I see that the traffic 
resumes and then yes, it authenticates me immediately. There are still 
some holes in the network.


Il 15/07/22 15:24, dea ha scritto:
>
> After reboot with version 2.2-4 everything seems OK. I keep you 
> updated in case there are any problems.
>
> THANK YOU
>
>
> Il 15/07/22 15:02, dea ha scritto:
>> retry to upgrade 2.2-1->2.2-4 and reboot...
>>
>>
>> Il 15/07/22 14:57, Thomas Lamprecht ha scritto:
>>> Am 15/07/2022 um 14:01 schrieb dea:
>>>> Mmmmm no, for me the same problem.
>>>>
>>>> Rollback 2.2.4 -> 2.2.1 and works great.
>>>>
>>>>
>>> how do you test?
>>>
>>> did you reboot in between or dropped the page cache?
>>>
>>> also what is your output for the requested info:
>>>
>>> Am 13/07/2022 um 10:14 schrieb Thomas Lamprecht:
>>>> FWIW, it would be still interesting to see a few metrics/CLI 
>>>> outputs from an affected
>>>> system to hopefully ensure that there's nothing additional to that 
>>>> problem.
>>>>
>>>> - `head /proc/pressure/*` for some general info if the system is 
>>>> overloaded
>>>> - `ls /var/lib/proxmox-backup/jobstates` just out of interest
>>>> - `ss -tlpn` to see if another (old) proxy process is still accepting
>>>> - `uptime`
>>> `lscpu` and `free` would be good to know too.
>>>
>>
>> _______________________________________________
>> pbs-devel mailing list
>> pbs-devel@lists.proxmox.com
>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
>
> _______________________________________________
> pbs-devel mailing list
> pbs-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel



  reply	other threads:[~2022-07-15 14:43 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 [this message]
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=e4d60e8c-1a62-3b8e-a9cc-b3ab29d75f33@corep.it \
    --to=dea@corep.it \
    --cc=mark@tuxis.nl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal