Hi Guillaume, Indeed! This is the issue. An error in one of my script is passing -s 'memory=malloc, ' to Varnish, instead of a sane value.
Cheers, -Hugues On Thu, May 2, 2019 at 5:54 PM Guillaume Quintard < [email protected]> wrote: > could it be that you are using unbounded Transient? If so, while it's > indeed a bit weird, it's more or less explained by the fact that the space > value is irrelevant anyway. > > -- > Guillaume Quintard > > > On Thu, May 2, 2019 at 5:06 PM Hugues Alary <[email protected]> wrote: > >> Hi, >> >> I am using varnish-6.0.0 revision >> a068361dff0d25a0d85cf82a6e5fdaf315e06a7d and the malloc storage. >> >> My vcl_deliver looks like this: >> >> sub vcl_deliver { >> set resp.http.X-Varnish-Storage = {"Free: "} + >> storage.memory.free_space + " Used: " + storage.memory.used_space + " >> Happy? : " + storage.memory.happy; >> } >> >> I am confused because upon making a request to my varnish server, >> storage.memory.free_space >> is always equal to storage.memory.used_space * -1. >> >> E.g if storage.memory.used_space is 150000.000 then >> storage.memory.free_space is -150000.000. >> >> Moreover, storage.memory.happy is always false. >> >> This has been the case for the longest time. I'm pretty sure I had this >> issue with Varnish 4, and maybe even earlier versions. >> >> Am I doing something wrong? Or is this a bug? >> >> Sincerely, >> -Hugues >> >> _______________________________________________ >> varnish-misc mailing list >> [email protected] >> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc >> >
_______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
