Log shifting error

rubyonrails-talk
1

Once again, here in the UK, we have had our switch back from summer time saving and once again various applications failed for things like

/usr/local/lib/ruby/1.8/logger.rb:501:in `write': Shifting failed. '/.../log/poll_sportsdb_for_updates.log.20101031' already exists. (Logger::ShiftingError)

These applications run 24/7 and obviously wrote to the log files before the clocks went back. Once they did though the applications died.

When this happened last year we changed mosts of the logs over from daily to weekly which got round the problem. But some logs do need to be rotated daily. Is there any way to fix this so that I don't have to go round checking out the world and it's dog next year?

2

can you add the timezone information to the logfilename?

'/.../log/poll_sportsdb_for_updates.log.20101031gmt '/.../log/poll_sportsdb_for_updates.log.20101031bst

3

Hi Peter,

4

I'm pretty sure that our server are running local time and not UTC (which would be a sure fix - I think). Not really sure that I would feel confident changing to UTC for nearly a dozen servers located on two continents.

5

I'm pretty sure that our server are running local time and not UTC (which would be a sure fix - I think).

Ok. Thanks.

Not really sure that I would feel confident changing to UTC for nearly a dozen servers located on two continents.

You have a knack for understatement :wink: At a minimum it would wreak havoc with your reporting apps which invariably use the system date/time to grab the 'right' records.

Best regards, Bill