public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: dea <dea@corep.it>
To: pbs-devel@lists.proxmox.com
Subject: Re: [pbs-devel] Scheduler causing connectivity issues?
Date: Fri, 8 Jul 2022 11:40:40 +0200	[thread overview]
Message-ID: <cd20589d-2981-b939-2443-906e3aaa46d5@corep.it> (raw)
In-Reply-To: <94e2e388-2d57-dd62-1063-585e7af2ab38@gmail.com>

Yes, same behavior for me too.

release 2.2-3 is problematic (NFS storage connected to PBS)

Previous releases work fine


Thanks

Luca


Il 08/07/22 11:36, Jorge Boncompte ha scritto:
> El 8/7/22 a las 9:09, Thomas Lamprecht escribió:
>> Hi,
>>
>> On 07/07/2022 17:49, Mark Schouten wrote:
>>> We’re getting complaints that one of our PBS’es is periodically unreachable. After investigation if the network might be at fault (even though it’s handling about 5.5Gbit at night), we found that PBS is piling up waiting connections every minute, on the minute, as you can see below. You see the output of `date`, combined with `ss -np | grep -c 8007`, the number of active connections.
>>>
>>> At first I thought that pvestatd was ddossing PBS, but pvestatd seems to run more often than once in a minute.
>>>
>>> So stracing the API process, I found that that process is also just waiting for something; must be the proxy-process.
>>>
>>> grepping for ‘minute’ in the code, I stumbled upon the function `next_minute` in ./src/bin/proxmox-backup-proxy.rs. I’m not quite sure if I understand it correctly, but it seems that every minute, the scheduler is going to try and find out if it should be doing something.
>>>
>>> Drilling down on that in my strace-foo, I think I see quite some read/write/rename actions on jobstate-files. Which leads me to conclude that the proxy process is waiting for the scheduler..
>>>
>>> This is just guess-work, but you guys can surely find out better what’s going on than me.
>>>
>>> This PBS is running with 45 users and 67 datastores.
>>>
>>> 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.
> 	Hi, We've been having a problem that resembles this one with several
> proxmox-backup-server 2.2.x versions. Our PBS stopped accepting backups
> jobs sometimes, but if we retried manully they started fine. The only
> message I could find was:
>
>    backup failed: could not activate storage 'XXXXXXX': XXXXXX: error
> fetching datastores - 500 Can't connect to XXXXXXXX:8007
>
> 	Restarting the proxy seemed to help to get it working one or two days
> more. We have reverted proxmox-backup-server to 2.1.8-1 and every is
> fine again.
>
> 	Regards.
>
>> cheers,
>> Thomas
>>
>>
>> _______________________________________________
>> 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-08  9:50 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 [this message]
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
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=cd20589d-2981-b939-2443-906e3aaa46d5@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal