#2358: logrotate config broken

Type: BugItem Feature: DebianPackage, Infrastructure Tags:  
ScheduledFor: 0.38.1 Assigned to: AntonioTerceiro Sites:  
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


-- AntonioTerceiro - 14 Aug 2012

Add comment
You need to login to be able to comment.

ActionItemForm edit

Title logrotate config broken
ActionItemType? BugItem
Priority 0
Feature DebianPackage, Infrastructure
ResponsibleDevelopers AntonioTerceiro
ScheduledFor? 0.38.1
Status Done
Ticket SAC:30779
Topic revision: r7 - 17 Aug 2012 - 15:37:40 - DanielaFeitosa

irc Talk with Devs Now!

Translations: English
Search on Docs:
ActionItem Search:

Copyright © 2007-2015 by the Noosfero contributors
Colivre - Cooperativa de Tecnologias Livres