Hello again everybody,
in order to get this issue finally resolved, I've contacted the
maintainer (Paul Martin) yesterday. Given the time of the year a reply
might take a few days. So for the moment: I've prepared a non-maintainer
upload for the new upstream version, please give it a try and repor
Mathieu Parent wrote...
> The actual upstream fix for it is:
> https://github.com/logrotate/logrotate/commit/fc1c3eff61edf8e9f0a4bfa980f3a6030a6b271f
>
> And it is included in version 3.11.0.
>
> The way forward is to update Debian package to 3.11.0.
ACK. This version handles my test cases in a
Control: tag -1 + upstream fixed-upstream
Hello,
2016-12-26 1:29 GMT+01:00 Christoph Biedl :
> Hello everybody,
>
> looking at this old but nasty bug that must be fixed for stretch:
>
> * Trying to understand what goes wrong I wrote a small script that
> creates a few scenarios and executes log
Hello everybody,
looking at this old but nasty bug that must be fixed for stretch:
* Trying to understand what goes wrong I wrote a small script that
creates a few scenarios and executes logrotate then. Run it in
an arbitrary directory like /tmp/ as regular user, with a single
parameter in
Hello,
I recently had /var/log fill up and am another conformation this bug
is in jessie. I was able to recover the issue and now have plenty of
space in /var/log but after cron.daily run I found this in my mailbox:
/etc/cron.daily/logrotate:
error: error creating output file /var/log/cups/access
On Wed, 16 Dec 2015, Michael Gebetsroither wrote:
> Package: logrotate
> Version: 3.8.7-1+b1
> Followup-For: Bug #734688
>
> Dear Maintainer,
>
> Seconded, the problem still persists in jessie.
> Logrotate was practically broken after /var/log got full a month ago.
>
> There where various .log.1.g
Package: logrotate
Version: 3.8.7-1+b1
Followup-For: Bug #734688
Dear Maintainer,
Seconded, the problem still persists in jessie.
Logrotate was practically broken after /var/log got full a month ago.
There where various .log.1.gz files, most of which where 0 bytes which
stopped logrotate to act
Package: logrotate
Version: 3.8.7-1+b1
Followup-For: Bug #734688
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear Maintainer,
the problem still persists in jessie. I suppose it started after running
out of space on /var/ which caused do stop log file compression to fail.
Logrotate does not
Regarding the patch proposed by Bolesław Tokarski
(logrotate-dest-file-exists(2).patch) , I would not want logrotate to
delete a zero-size log file that it happens to find on the system. An
empty log file could be telling you something very important!
However, if logrotate runs into an error which
I'm having the same problem in Wheezy (logrotate version 3.8.1-4).
also sprach Peter Pöschl [2014-06-02 09:45 +0200]:
> If this hunch is correct, putting
> PATH = /usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
> into /etc/fcrontab should help.
This has nothing to do with the original problem. I found that the
only way to solve it was to use --
I am using cron + latest fcron 3.1.3-1 from http://debs.slavino.sk and get
error mails from fcron:
/etc/cron.daily/logrotate:
logrotate_script: 2: logrotate_script: invoke-rc.d: not found
error: error running shared postrotate script for '/var/log/cups/*log '
logrotate_script: 2: logrotate_script
I did some basic testing and investigations and I am attaching a
corrected patch.
I have found that the problem only started appearing in version 3.8.0.
In versions prior to that, the security-388608.patch used an
unlink(fileName) in the beginning of createOutputFile function call.
However,
I have just bumped myself to the same issue. Your error message:
error: error creating output file /var/log/syslog.1.gz: File exists
indicates that the file syslog.1.gz exists. @madduck can you check that the
file doesn't really exist?
In my case a previous logrotate command must have been i
also sprach Paul Martin [2014-01-11 23:58 +1300]:
> What's in /etc/logrotate.d/rsyslog and /etc/logrotate.conf?
They are unmodified from the package.
> Running with -d (--debug) doesn't change anything. If you want to
> watch a forced rotation, use -v (--verbose).
Weird, but okay. This reveals:
On Thu, Jan 09, 2014 at 02:31:16PM +0800, martin f krafft wrote:
> I just happened to notice that /var/log/syslog had not been rotated
> in almost 1 month:
>
> % ls -l /var/log/syslog*
> -rw-r- 1 root adm 16588618 Jan 9 14:21 /var/log/syslog
> -rw-r- 1 root adm 336215 Dec 11 15:37
Package: logrotate
Version: 3.8.6-1
Severity: important
I just happened to notice that /var/log/syslog had not been rotated
in almost 1 month:
% ls -l /var/log/syslog*
-rw-r- 1 root adm 16588618 Jan 9 14:21 /var/log/syslog
-rw-r- 1 root adm 336215 Dec 11 15:37 /var/log/syslog.1
17 matches
Mail list logo
