On Tue, 23 Feb 2016 13:55:08 +0000 Richard Harris <richardjhar...@gmail.com> wrote: > There is no need to guess, you can run logrotate with the --verbose setting > and find out which log it was processing before the error occured. A good > way to do this is to modify the logrotate cron to add --verbose and sit and > wait for the logs to reach your inbox.
Running a rotation manually may have bad side effects. Some daemons need a complete service restart (including complete interruption during a few seconds) via postrotate. Manually run daily rotationsmore than once a day can lead to conflictuous names. Finaly, a manual run may not trigger then "file size change" for various random reasons. I had that strange message for the first time, on machines working fine since over 3 months. So, happens once in 150 days. I would thus need to run it manually at least 150 times before getting it ? Cron reported me an issue, with an irrelevant message that can't contribute to any solution. => On Sun, 7 Dec 2014 16:59:07 +0000 Paul Martin <p...@debian.org> wrote: > To associate an error message with a particular script, logrotate > would have to capture stdout and stderr from its running of the > compressor and then prefix it with the name of the script or other > external program. YES. It will take what it will take, but that's the only way to provide usefull error reports. -- >o_/ DEMAINE Benoît-Pierre (aka DoubleHP) http://benoit.demaine.info/ If computing were an exact science, IT engineers would'nt have work \_o< "So all that's left, Is the proof that love's not only blind but deaf." (FAKE TALES OF SAN FRANCISCO, Arctic Monkeys)
