If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[varnish] Upgrade production varnishes to 2.0

RESOLVED FIXED

Status

Mozilla Messaging
Server Operations
--
major
RESOLVED FIXED
9 years ago
9 years ago

People

(Reporter: gozer, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

9 years ago
Main reason this is needed/wanted is for the support of:

varnishncsa -f (Use X-Forwarded-For) in generating logs, otherwise, we are losing
remote IPs in the logs.

This is only an issue for SSL connections going thru Pound, but now that AUS is live, we need not loose this precious information.

varnish 2.0.2-2.el5 is already waiting for us in EPEL
(Reporter)

Comment 1

9 years ago
Completed without a problem. Asjusted log conversion cronjobs to invoke varnishncsa -f as well.

Only negative is that the varnish.log file format looks like it changed in an incompatible way, so varnish.log on momo-blade-01 ended up munged, so I backed it up for possible reconstruction and cleared a path for a brand new one.

Access logs for that box+day might be eaten, grr.

For later, the file that should be recovereable by tuncating it bit by bit is 'varnish.log-20090218-varnish1x'
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.