Mailing List Archive

varnishstat and 2 instances of varnishd
Since yesterday I have been running 2 instances of varnishd on the same
server.

So far so good. My question is, I'm not sure how to direct varnishstat
to grab/display stats from a specific varnishd instance. --help only
reveal -cV args.

Xing
varnishstat and 2 instances of varnishd [ In reply to ]
Since yesterday I have been running 2 instances of varnishd on the same
server.

So far so good. My question is, I'm not sure how to direct varnishstat
to grab/display stats from a specific varnishd instance. --help only
reveal -cV args.

Xing
varnishstat and 2 instances of varnishd [ In reply to ]
In message <450AEE8D.4020906 at litespeedtech.com>, "xing at litespeedtech.com" write
s:
>Since yesterday I have been running 2 instances of varnishd on the same
>server.
>
>So far so good. My question is, I'm not sure how to direct varnishstat
>to grab/display stats from a specific varnishd instance. --help only
>reveal -cV args.

Ohh, uhm...

The shared memory file is currently (rather haphazardly) called
"tmp/_.vsl". At some point I planned on revisiting that but I
have not thought much about it.

Just including the listen port is not enough as you could have
two varnishes listening on specific IP# but same port.

Including the entire listen address seems needlessly cumbersome.

I guess assigning some kind of instance numbers is the way to
go...

The instance number would have to be specified to all the tools
then.

Ideas welcome.

--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
varnishstat and 2 instances of varnishd [ In reply to ]
In message <450AEE8D.4020906 at litespeedtech.com>, "xing at litespeedtech.com" write
s:
>Since yesterday I have been running 2 instances of varnishd on the same
>server.
>
>So far so good. My question is, I'm not sure how to direct varnishstat
>to grab/display stats from a specific varnishd instance. --help only
>reveal -cV args.

Ohh, uhm...

The shared memory file is currently (rather haphazardly) called
"tmp/_.vsl". At some point I planned on revisiting that but I
have not thought much about it.

Just including the listen port is not enough as you could have
two varnishes listening on specific IP# but same port.

Including the entire listen address seems needlessly cumbersome.

I guess assigning some kind of instance numbers is the way to
go...

The instance number would have to be specified to all the tools
then.

Ideas welcome.

--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.