[SOLVED] error: log /var/log/yum.log last rotated in the future -- rotation forced

General support questions
Post Reply
richard_chapman
Posts: 252
Joined: 2006/09/08 02:54:11

[SOLVED] error: log /var/log/yum.log last rotated in the future -- rotation forced

Post by richard_chapman » 2012/04/21 02:32:52

I have a Centos 5 server with (presumably) a flat battery in the motherboard clock. It recently recovered from a power fail with the date set to 2017. The date and time is now OK - and we can change the battery - but every day I get this error from cron. It has persisted for a couple of weeks now.

error: log /var/log/yum.log last rotated in the future -- rotation forced

Can anyone suggest how I get rid of this error? Googling hasn't helped much so far.

Thanks.

Richard.

User avatar
TrevorH
Forum Moderator
Posts: 25576
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: error: log /var/log/yum.log last rotated in the future -- rotation forced

Post by TrevorH » 2012/04/21 02:36:21

What is the date on the file? Using `touch --reference=someotherfile-withthecorrectdate /var/log/yum.log` would fix it.

richard_chapman
Posts: 252
Joined: 2006/09/08 02:54:11

Re: error: log /var/log/yum.log last rotated in the future -- rotation forced

Post by richard_chapman » 2012/04/21 03:02:56

Thanks Trevor. The /var/log/yum.log did have the stupid date (2017). I have just touched it to give it today's date - and we'll see what happens overnight. I'll let you know in a day or so.
Richard.

richard_chapman
Posts: 252
Joined: 2006/09/08 02:54:11

[SOLVED] error: log /var/log/yum.log last rotated in the fut

Post by richard_chapman » 2012/05/04 07:12:19

It has taken me a while to get back - but I that does seem to have fixed it.
Thanks.

User avatar
AlanBartlett
Forum Moderator
Posts: 9320
Joined: 2007/10/22 11:30:09
Location: ~/Earth/UK/England/Suffolk
Contact:

Re: [SOLVED] error: log /var/log/yum.log last rotated in the future -- rotation forced

Post by AlanBartlett » 2012/05/04 22:30:26

Excellent! Thanks for reporting back.

For posterity (and on your behalf) this thread is now marked [SOLVED].

Post Reply