|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 2405 | minor | always | 02-06-08 09:04 | 02-11-08 19:09 | |
|
|
|||||
| Reporter: | ckchris | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 3.1.4 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.1.5 | ||
|
|
|||||
| Summary: | 0002405: <access-log> path not properly read by DeployController in <host-default> config | ||||
| Description: |
I have multiple hosts with logs in their respective directories: /var/vhosts/abc.com/logs /var/vhosts/def.com/logs I have configured my <access-log> config in host-default. <access-log path="logs/access.log" format='%h %l %u %t "%r" %s %b "%{Referer}i" "%{User-Agent}i"' rollover-period="1M" rollover-count="12"/> <stdout-log path="logs/stdout.log" rollover-size="5mb" rollover-count="4"/> <stderr-log path="logs/stderr.log" rollover-size="5mb" rollover-count="4"/> This setting previously worked without any problems on 3.1.3. In subsequent <host> configurations, I set the <root-directory> to its proper location (ie. abc.com). After upgrading to 3.1.4, I can gett the following exception: [2008/02/06 08:59:51.987] SEVERE [com.caucho.server.deploy.DeployController] /apps/etc/resin.conf:80: java.io.IOException: Cannot create directory: /var/vhosts/bogus-root/logs Even though I get this exception, I can still see logs being used in the proper location. However, this exception shouldn't be thrown given that the configuration is correct. <access-log> relative paths should go according to the root-directory set in <host> |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||