Opened 12 years ago
Closed 12 years ago
#10720 closed defect (duplicate)
Existing but unreadable trac.ini should be an error condition
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | general | Version: | 0.12.2 |
| Severity: | normal | Keywords: | config permissions |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
I spent about 6 weeks working out this one.
If trac.ini exists but trac cannot read it, what seems to happen is trac ignores the file and uses the default configuration. What should happen instead is an error.
Apparently trac now uses 0600 for trac.ini, which caused this situation for me as the user owning the trac instance files is different from the user running trac.
In my case, this error manifested itself by trac complaining about missing sqlite bindings and refusing to do anything, when I had postgres configured as the database in trac.ini. Even copying trac.ini from a known working instance did nothing (as the broken trac instance could not read the file regardless since permissions were kept).
Attachments (0)
Change History (1)
comment:1 by , 12 years ago
| Keywords: | config added; trac.ini removed |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
Yes, it's a duplicate of #10044. Thanks for your reporting.