Running multiple nighly jobs will slow down even more and i'm already
using 1/128 as period.
But that's not the issue, the issue is that BPC is flooding the log
writing the same message tens time per second, every time.
Il giorno ven 27 dic 2019 alle ore 10:19 Alfred Weintoegl
ha scritto:
>
> May
Maybe you should change the following options?:
$Conf{MaxBackupPCNightlyJobs}
and
$Conf{BackupPCNightlyPeriod}
The BackupPC Documentaion says:
If BackupPC_nightly takes too long to run, the settings
$Conf{MaxBackupPCNightlyJobs} and $Conf{BackupPCNightlyPeriod} can be
used to run several Backu
2019-12-26 22:44:23 Running BackupPC_rrdUpdate (pid=20275)
2019-12-26 22:44:24 admin-1 : ERROR: /var/log/BackupPC/poolUsage.rrd:
illegal attempt to update using time 1577404800 when last update time
is 1577404800 (minimum one second step)
2019-12-26 22:44:24 Finished admin-1 (BackupPC_rrdUpdate)
Got this error:
2019-12-26 22:44:19 Running BackupPC_nightly -m -P 10 864 867 (pid=20264)
2019-12-26 22:44:19 admin : /usr/local/backuppc/bin/BackupPC_nightly:
bad poolRangeStart '864'
2019-12-26 22:44:19 Finished admin (BackupPC_nightly -m -P 10 864 867)
_
When nighly job spawn multiple days (in my case, even 1 week), log are
flooded with:
Botch on admin job for admin : already in use!!
would be possible to relax this log or add a sort of ratelimit like
syslog does ?
There is no need to log the same error line 50 times per second, like
the follow
