Mantis - Resin
|
|||||
Viewing Issue Advanced Details | |||||
|
|||||
ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
5789 | minor | always | 08-21-14 12:53 | 08-27-14 10:49 | |
|
|||||
Reporter: | ferg | Platform: | |||
Assigned To: | ferg | OS: | |||
Priority: | normal | OS Version: | |||
Status: | closed | Product Version: | |||
Product Build: | Resolution: | fixed | |||
Projection: | none | ||||
ETA: | none | Fixed in Version: | 4.0.41 | ||
|
|||||
Summary: | 0005789: access-log rollover-count | ||||
Description: |
(rep by Uv Wildner) we are operating a number of resin 4 nodes for some weeks for our website. Our operations team observed now that the access.log rotation works fine, however, the access-log directive in the cluster-default.xml is not observing the rollover-count directive limiting the number of compressed access.log files. We use the standard approach to overwrite the resin.properties and resin.xml with resin-ipc.properties and resin-ipc.xml. But there is no other access-log configuration in our config files. cluster-default.xml: <resin xmlns="http://caucho.com/ns/resin" [^] xmlns:resin="urn:java:com.caucho.resin"> <!-- - default configuration applied to all clusters --> <cluster-default> ....... <host-default> <access-log path="log/access.log" format='%h %l %u %t "%r" %s %b "%{Referer}i" "%{User-Agent}i"' archive-format="access-%Y%m%d.log.gz" rollover-period="1D" rollover-count="10"/> ...... </host-default> </cluster-default> </resin> Please advise if 1.) this directive to limit the number of access log files is placed in the wrong xml configuration context, or 2.) if this is simply not implemented using date based logfile rotation. In this case would have to create a cronjob to do this externally... |
||||
Steps To Reproduce: | |||||
Additional Information: | |||||
Relationships | |||||
Attached Files: |
Notes | |||||
|
|||||
|
|