reg: not getting ReqAcct tag in varnishlog

[Hardik]

Hi Dridi,

We should able to recreate with load and mobile requests. I have not tried
with 6.0.3.

@Nils,
We are seeing issue with both varnishlog and varnishlog with -g option. But
here problem is, shared memory it self does not have ReqAcct tag I think (
please correct me if I am wrong). Because all the clients which are reading
shm all are getting same thing..means no ReqAcct. But yes I am agree that
impact with "varnishlog -g session" is more.

So If shared memory it self has no ReqAcct tag then all clients will also
not get right ? How to fix this problem ? Please help with some details
which I can understand because we are loosing bills for which we are
serving traffic...!

*Normal varnish command we use to grep running logs*
varnishlog -g request -q "ReqURL ~ '/abc/xyz'"

*command uses to read shared memory directly for billing*
varnishlog -g session
--> we are already planing to use "varnishlog -g xvid" for billing api.
Because I understood is, -g session option is taking more time to arrange
in particular order and delivery final output. Please help with some more
detail.. It will really helpful.

Thank you
Hardik


On Tue, 12 Mar 2019 at 17:32, Nils Goroll <slink at schokola.de> wrote:

> Hi,
>
> On 12/03/2019 11:07, Hardik wrote:
> > *Error cases when ReqAcct is not present in varnishlog*
> >
> > 1.
> > -   VSL            timeout
> > -   End            synt
> >
> > 2.
> > -   VSL            store overflow
> > -   End            synth
>
> The VSL clients (varnishlog and friends) store transactions in the client
> program's memory when varnishd comes close to overwriting the respective
> region
> of the VSL shared memory ring.
>
> The -L and -T options allow you to specify these limits, see for example
> the
> varnishlog man page.
>
> I _suspect_ you are seeing this with the -g request or -g session
> transaction
> grouping (please specify how you invoke the respective command). If yes, an
> alternative would be to reduce the time the VCL client needs to store open
> transactions by switching to the vxid or raw grouping (-g argument).
>
> hth, Nils
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20190313/39c0e5f7/attachment.html>