This looks like an older hub with a lot of things on it that has been running without a reboot for over a month. Busy systems produce memory leaks, and while we've worked (and are working) to minimize them, such leaks add up over time. The cure is having a scheduled reboot; once a week should work.
I have a reboot scheduled every Sunday middle of the night on my 2 production hubs, one of which has 480 devices (real and virtual) and many, many apps and rules. It does the trick!
Hmm, I found the trigger "days of week", but my attempt at action "http://192.168.0.60:8080/hub/reboot" didn't work, I'll see if I can get the rebooter app..
Thanks, I tried a rebooter, I think it was that one. Copied the code into the script screen. But it didn't seem to work. I'd set it to reboot, but it didn't reboot.
Now I'm chasing a problem that no actions for which I select a "delay" actually do anything now. I deleted rebooter in case that was the problem but it doesn't seem to be....