Just got this kernel message here on dmesg: process rclone caught waking the CPU 45001 times over ~253 seconds, averaging 177 wakes / second and violating a limit of 45000 wakes over 300 seconds.
When I check on the process with ps auwx , it has not been killed by the OS and indeed seems to be happily running along: root 91967 0.0 0.1 4557216 86048 ?? S 9:17PM 2:11.65 rclone serve restic --stdio --b2-hard-delete --drive-use-trash=false --rc --rc-addr localhost:5582 --rc-no-auth REDACTED1:REDACTED2/REDACTED3
In fact, except for some slowness (which I attribute to restic and not to rclone ), the underlying restic backup operation seem to be progressing normally -- I just detected that message and wondered what the heck it's about, and then searched and found this topic.
Does anyone know what the heck it means? I'm far from being an expert on OSX... :-/
I agree with your analysis: despite the message's ominous tone, the Darwin kernel source you dug up seems to indicate it's just a 'warning' and not an 'error' and so I'm proceeding by suitably ignoring it
BTW: I just re-checked and all the "power-saving" configs on the machine are turned off, so I don't think it has anything to do with PM or similar.
Not a problem, and thank you for coming back and replying.
rclone serve restic is a special mode where it acts as a "backend server" for restic, answering to commands from the latter up and down a pair of pipes to manipulate the backend storage accordingly to restic needs. This resulted from a great idea by @ncw, if you are curious you can read more about it here: https://restic.net/blog/2018-04-01/rclone-backend.
BTW, if you have lots of small files and is hitting your head against GDrive transactions/second limit, or is in any way getting slow backup speeds from rclone alone, I can't speak highly enough of the restic+rclone combo -- it literally made possible my backing up to GDrive of a 70M files / 33TB server which would have been unfeasible otherwise. And fd0, the restic developer, is a great guy and very willing to help -- restic is not as perfect as rclone is (there are a few issues regarding memory use, performance, detection of changed files etc) but it's getting there!