#2358: logrotate config broken
| Type: | BugItem | Feature: | DebianPackage, Infrastructure | Tags: | |
|---|---|---|---|---|---|
| ScheduledFor: | 0.38.1 | Assigned to: | AntonioTerceiro | Task Points: | |
| Priority: | 0 | Status: | Done | ||
Description of the bug
after logs are rotated, noosfero keeps writing to the old logfile that was renamed to (production.log.1) the provided logrotate configuration file has to be checked, maybe it needs to restart the application server after rotating the logs. -- AntonioTerceiro -- 15 May 2012 The same happens to the thin, ferret and delayed_job logs! -- AntonioTerceiro - 09 Aug 2012 well, ferret does not matter anymore. -- AntonioTerceiro - 13 Aug 2012 tried to reproduce this on a fresh VM install, but couldn't. even with very frequent access (10req/s), at leasr production.log is rotated ok with the provided configuration. -- AntonioTerceiro - 13 Aug 2012 Gitorious:207 -- AntonioTerceiro - 14 Aug 2012ActionItemForm edit
| Title | logrotate config broken |
| ActionItemType? | BugItem |
| Priority | 0 |
| Tags | |
| Feature | DebianPackage, Infrastructure |
| Plugin | |
| TaskPoints? | |
| ResponsibleDevelopers | AntonioTerceiro |
| ScheduledFor? | 0.38.1 |
| AffectsVersion? | |
| Status | Done |
| Ticket | SAC:30779 |
Topic revision: r7 - 17 Aug 2012 - 15:37:40 - DanielaFeitosa
Development
Development
Roadmap
Documentation
ArchiveDevelopers
-
Start
-
Current developers
-
Next: 0.43.0
- Next: 0.42.2
-
Be a developer
-
Milestones
-
My Action Items
-
Unscheduled items
- Easy to solve items
-
Bugs
-
Features
- quick item creation
-
New Bug
- New Feature
Copyright © 2007-2013 by the Noosfero contributors
