If /tmp/varnishlog.log is actually growing in size and yet using the -r flag in varnishncsa doesn't work, then I wouldn't know what to say.
Nathan On Wed, Mar 13, 2013 at 5:39 PM, Juan Andrade <[email protected]> wrote: > Hello Nathan, > So I tried that and no output even reading from file > > varnishlog -w /tmp/varnishlog.log // This writes > > varnishncsa -r /tmp/varnishlog // No output > > On Wed, Mar 13, 2013 at 12:56 PM, Nathan Kinkade > <[email protected]> wrote: >> >> Have you tried using the -r option to make varnishncsa read from a >> file instead of shared memory? It could be one way to help narrow >> down the problem. In our setup varnishlog logs to >> /var/log/varnish/varnish.log, so I can always use: >> >> # varnishncsa -r /var/log/varnish/varnish.log >> >> ... this effectively gives me the same output as varnishncsa without >> any options. >> >> Nathan >> >> On Tue, Mar 12, 2013 at 8:04 PM, Juan Andrade <[email protected]> >> wrote: >> > Varnishlog works fine but varnishncsa does not output anything. Also >> > tried >> > std.syslog but messages are empty >> > >> > Here is my config: >> > >> > sub vcl_recv { >> > if (req.http.host) { >> > std.syslog(191, "vcl_recv(" + req.xid + ") Req: " + >> > req.request + " http://"; + req.http.host + >> > req.url + " " + req.proto); >> > set req.backend = stage; >> > } >> > } >> > >> > Log messages: No message as set above >> > 2013-03-12T16:55:23.725466-07:00 stage-cache1 varnishd[10191]: >> > 2013-03-12T16:56:43.413369-07:00 stage-cache1 varnishd[10530]: >> > >> > Running varnish version >> > varnishd (varnish-trunk revision 5582b35) >> > >> > Anybody run into this problem? Thanks for any help. >> > >> > Juan >> > >> > _______________________________________________ >> > 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
