All you see there is the rsync output redirected to the logfile by L2R unmodified. You should be able to find info about rsync output fairly easily I guess.
Right at the beginning I highlighted L2R is not a finished solution. It’s taken over a year since I first floated the idea of using L2R to get to the point were it gets any consideration at all. I do not maintain the original L2R, but I am willing to develop it for our needs, first we need to establish what they are, then I will look to improve L2R.
I agree timestamped logs are essential. I have already suggested more verbose logs throughout L2R with a user set loglevel. (Look at emonhub for an idea of how I like to do logging.)
We have also discussed L2R providing data to emonhub/emoncms for capture/monitoring eg write stats, logfile sizes, disk usage etc.
Are the permissions and ownership correct on the folder you created? Had you not created the folder, I would have confidently said “in that case no rotations were needed/performed” but cannot now be 100% sure. The folder only gets created automatically IF it doesn’t exist, so I suspect if one does exist, but is not the right permissions, it will fail.
Another thing regarding the logs, logrotate doesn’t actually maintain a log of it’s own. I think it’s output might go to syslog? I have been using redirection in my commandline whilst debugging
sudo logrotate -v /etc/logrotate.conf | sudo tee >> /var/log/logrotate.log
but I would also like to see this output in the L2R logs aswell.
I wasn’t aware of that because there is no log output from L2R in cp mode and since changing to rsync, I had no time to work on this, spent some time looking into rsync rules because Trystan was having issues, moved onto tackling logrotation because you found it wasn’t working and then the discussion got heavily into the logrotation side.
Now there is some interest in using L2R etc, I will start developing further as and when time allows me to, this is something I could have been doing over the last year had there been any interest, but in true OEM fashion we have gone from zero interest to I want it now with no middle ground. My main aim has to be to get it operational for inclusion before we lose interest again, the rest can happen over time.
I will look into the duplicate logs, but at the moment L2R logs hardly anything once an hour so this is a fairly trivial thing until we get more log output, I think if the L2R logging is overhauled to include timestamps and loglevels etc, this would get addressed then anyway. In the meantime, the duplicated logs mean there IS probably a timestamp available via daemon.log if you need one