On 2019-09-20 19:36:02 +0200, Christian Göttsche wrote:
> > It is only access.log that it doesn't rotate. After last night:
> >
> > -rw-r- 1 root adm 308 2019-09-17 16:39:00 access.log
> > -rw-r- 1 root adm 156 2019-09-16 16:31:06 access.log.3.gz
> > -rw-r- 1 root adm 157 2019-09-13
> It is only access.log that it doesn't rotate. After last night:
>
> -rw-r- 1 root adm 308 2019-09-17 16:39:00 access.log
> -rw-r- 1 root adm 156 2019-09-16 16:31:06 access.log.3.gz
> -rw-r- 1 root adm 157 2019-09-13 12:36:03 access.log.4.gz
> -rw-r- 1 root adm 155 2019-09-12
On 2019-09-19 11:27:37 +0200, Vincent Lefevre wrote:
> So, the rotation occurs at midnight, according to the systemd timer.
> This conflicts with the crontab configuration.
Hmm... I see that /etc/cron.daily/logrotate disables the rotation
by cron in case of systemd. So, the issue with the missing
On 2019-09-19 11:03:36 +0200, Vincent Lefevre wrote:
> On 2019-09-18 12:52:32 +0200, Christian Göttsche wrote:
> > If yes, please share 'systemctl status logrotate.timer' and
> > 'journalctl -u logrotate' (the most recent part of it).
>
> ● logrotate.timer - Daily rotation of log files
>
On 2019-09-18 12:52:32 +0200, Christian Göttsche wrote:
> Please share your current setup:
> Debian version: (old-stable | stable | testing | unstable)
unstable
> Logrotate version: (logrotate --version)
logrotate 3.15.1
Default mail command: /usr/bin/mail
Default compress
Please share your current setup:
Debian version: (old-stable | stable | testing | unstable)
Logrotate version: (logrotate --version)
Please share your cronjob config '/etc/cron.daily/logrotate'
Are you using systemd?
If yes, please share 'systemctl status logrotate.timer' and
'journalctl -u
On 2019-09-17 15:32:10 +0200, Vincent Lefevre wrote:
> OK, I understand the reason with the upstream discussion. I think
> that the best thing is to try to reproduce the issue under the
> usual conditions (i.e. via cron and without trying to change the
> status file). So, on some machine, I've set
On 2019-09-08 17:22:15 +0200, Christian Göttsche wrote:
> Control: tags -1 moreinfo unreproducible
>
> The timestamp in the state file stands for the last attempt to rotate
> the file (see https://github.com/logrotate/logrotate/issues/223), so
> an update of it is fine.
>
> In message #27
Control: tags -1 - fixed-upstream
> Control: tags -1 moreinfo unreproducible
>
> The timestamp in the state file stands for the last attempt to rotate
> the file (see https://github.com/logrotate/logrotate/issues/223), so
> an update of it is fine.
>
> In message #27 logrotate probably did not
Control: tags -1 moreinfo unreproducible
The timestamp in the state file stands for the last attempt to rotate
the file (see https://github.com/logrotate/logrotate/issues/223), so
an update of it is fine.
In message #27 logrotate probably did not show any error cause the
option 'daily' was used;
On 2018-08-22 23:44:05 +0200, Christian Göttsche wrote:
> I tested logrotate version 3.14.0-2 with an ancient logfile from 1904
> and it got rotated. Also no such date should show up in the state file
> (only rotation times, not file mtimes).
> Can you reproduce this issue with logrotate 3.14.0-2
Control: tags -1 moreinfo unreproducible
Hi,
I tested logrotate version 3.14.0-2 with an ancient logfile from 1904
and it got rotated. Also no such date should show up in the state file
(only rotation times, not file mtimes).
Can you reproduce this issue with logrotate 3.14.0-2 or newer?
Please
On 2008-11-03 04:04:50 +, Paul Martin wrote:
That shouldn't be possible without getting an error:
if ((year != 1900) (year 1970 || year 2100)) {
message(MESS_ERROR, bad year %d for file %s in state file %s\n,
year, argv[0], stateFilename);
Package: logrotate
Version: 3.7.1-5
Severity: normal
When /var/lib/logrotate/status has files with date 1904-1-1 (e.g.
/var/log/wtmp), these files are no longer rotated. I don't even
get any error message.
Note: the 1904-1-1 is due to the fact that on the PowerBook G4,
when the battery is empty,
On Sun, Nov 02, 2008 at 11:04:23PM +0100, Vincent Lefevre wrote:
When /var/lib/logrotate/status has files with date 1904-1-1 (e.g.
/var/log/wtmp), these files are no longer rotated. I don't even
get any error message.
That shouldn't be possible without getting an error:
if ((year !=
15 matches
Mail list logo
