Dzień dobry,
czy myśleli Państwo o wnioskowaniu w sprawie pozyskania dodatkowych środków na
bieżącą działalność i inwestycje?
Jeżeli są Państwo zainteresowani wsparciem z tego zakresu, chętnie przedstawię
szereg propozycji, zgodnych z Państwa potrzebami i oczekiwaniami.
Bardzo proszę o informa
On Tue, Apr 12, 2022 at 08:14:25AM +0200, Willy Tarreau wrote:
> Hi Shawn,
> [...]
> On Mon, Apr 11, 2022 at 01:05:21PM -0600, Shawn Heisey wrote:
> > An astute observer will notice that the backend says 81 while the packet
> > capture shows port 82. This is because I changed the port number on th
On 4/12/22 02:22, Amaury Denoyelle wrote:
then you can display the traces with the following command :
$ show events buf0
For the h3 layer, the trace mechanism is not currently implemented. You
should instead recompile your haproxy binary with the DEBUG options :
-DDEBUG_H3 -DDEBUG_QPACK
and w
On Tue, Apr 12, 2022 at 08:01:59AM -0600, Shawn Heisey wrote:
> On 4/12/22 02:22, Amaury Denoyelle wrote:
> > then you can display the traces with the following command :
> > $ show events buf0
> > > For the h3 layer, the trace mechanism is not currently implemented. You
> > should instead recompil
On 4/12/22 08:01, Shawn Heisey wrote:
I didn't do the H3 debug yet, if you still need it after looking at > the traces, let me know. You'll also need to tell me how to make >
those debugs active when I build haproxy.
I figured this out. I put those debug definitions in a DEBUG="stuff"
parame
On Tue, Apr 12, 2022 at 05:26:41PM +0200, Amaury Denoyelle wrote:
> On Tue, Apr 12, 2022 at 08:01:59AM -0600, Shawn Heisey wrote:
> > On 4/12/22 02:22, Amaury Denoyelle wrote:
> > > then you can display the traces with the following command :
> > > $ show events buf0
> > > > For the h3 layer, the t
On 4/12/22 09:45, Amaury Denoyelle wrote:
After much analysis of the code, it may be useful to have a run with the
stream traces as well :
$ trace stream sink buf0; trace stream level developer; trace stream verbosity
clean; trace stream start now
All 3 traces enabled, this time it should only
Hello Shawn,
On 4/12/22 18:30, Shawn Heisey wrote:
> On 4/12/22 09:45, Amaury Denoyelle wrote:
>> After much analysis of the code, it may be useful to have a run with the
>> stream traces as well :
>> $ trace stream sink buf0; trace stream level developer; trace stream
>> verbosity clean; trace st
On 4/12/22 14:07, Frederic Lecaille wrote:
Please, you could you double check on your side the "stream" traces are
correctly enabled? Also ensure you provide use with traces dumped by
haproxy when you validate the PHP form.
These are the trace commands that I am sending to the stats socket:
t
On 4/12/22 22:42, Shawn Heisey wrote:
>> Please, you could you double check on your side the "stream" traces are
>> correctly enabled? Also ensure you provide use with traces dumped by
>> haproxy when you validate the PHP form.
>
>
> These are the trace commands that I am sending to the stats soc
Hi
My configuration do not do what I thought it should do, so I would like to
debug it.
Old school with "print" commands of acl's, but I cannot find a method to do
that.
Is it possible and if so what is the command.
Regards
Henning
On 4/12/22 16:06, Frederic Lecaille wrote:
so this command:
$ echo "trace quic sink buf0; trace quic level developer; trace quic
verbosity clean; trace quic start now; trace qmux sink buf0; trace qmux
level developer; trace qmux verbosity minimal; trace qmux start now;
trace stream sink buf0;
On 4/12/22 19:20, Shawn Heisey wrote:
https://paste.elyograg.org/view/bd5df44d
I repeated it, this time issuing the stream traces first, just in case
the order of the trace commands might matter. THat's the sort of thing
that shouldn't matter,
https://paste.elyograg.org/view/22ddec0a
And
13 matches
Mail list logo
