From: Andrei Perapiolkin <andrei.perepiolkin@open-e.com>
To: pbs-devel@lists.proxmox.com
Subject: Re: [pbs-devel] [pve-devel][storage][ui] Debugging UI for storage
Date: Tue, 21 Dec 2021 14:22:44 -0500 [thread overview]
Message-ID: <cda1349f-7f2b-165b-a0f3-ea1c6931bd7e@open-e.com> (raw)
In-Reply-To: <1639640828.chveaf6ryc.astroid@nora.none>
Thanks for recommendations Fabian!
After checking logs and small tweaking I found that my issue can be
solved by:
Adding `timeout` property to the `run_command` from PVE::Tools call.
I hope this info will help other plugin developers.
Thanks for your time and attention,
Andrei Perepiolkin
On 12/16/21 02:56, Fabian Grünbichler wrote:
> On December 15, 2021 4:51 pm, Andrei Perapiolkin wrote:
>> Hi,
>>
>>
>> Im working plugin for a proxmox so it can use third party data storage
>> system.
>>
>> And Im having a hard time with implementing `list_images` method for my
>> plugin(/usr/share/perl5/PVE/Storage/Plugin.pm)
>>
>> Periodically proxmox web UI fails to show list of specific
>> volumes/images/backups using my plugin.
>>
>> One out of 3 or 4 calls are failing with "Too many redirections (599)"
>> error.
> that's strange - how's the load situation on the node? anything else
> that looks interesting in the logs?
>
>> This happens while `pvesh` and `pvesm` works perfectly fine and deliver
>> correct list on every call.
> those don't go through HTTP(S), so it's no surprise you don't see
> HTTP-related issues there ;) if you want to test the HTTP part you could
> use the perl API client (libpve-apiclient-perl) or plain curl (e.g., by
> copying from your browser's dev console).
>
>> What am I missing? Is there any test sets that I can run to verify
>> correctness of `list_images` output?
>>
>> Or is there any efficient way to debug UI issues like this?
> one potentially relevant information would be how long a pvesm list
> takes on average. the GUI has a 30s timeout for sync requests, listing
> storage contents is done in a sync fashion..
>
> are you doing the requests to the node where you are logged in, or is
> this a proxied situation?
>
> login on node A, query storage on node A
> (directly handled by node A)
>
> vs
>
> login on node A, query storage on node B
> (transparently proxied to node B by node A)
>
> ?
>
>
> _______________________________________________
> pbs-devel mailing list
> pbs-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
>
prev parent reply other threads:[~2021-12-21 19:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 15:51 Andrei Perapiolkin
2021-12-16 7:56 ` Fabian Grünbichler
2021-12-21 19:22 ` Andrei Perapiolkin [this message]
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=cda1349f-7f2b-165b-a0f3-ea1c6931bd7e@open-e.com \
--to=andrei.perepiolkin@open-e.com \
--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