(Solved) Were there changes affecting the S3 sleep plugin

Edit: Yours truly had a setting deleted when updating the plugin at some point. The setting "Debug mode" has to be set in the plugin's prefs in order to actually get status updates from the plugin.

I have the most recent version of Unraid on three servers and I use the S3 sleep plugin on all three. I've noticed some changes, and I'm not sure when they first happened.

The plugin used to output its status to the syslog. When started, and after that about once per minute, what was the status of the drives monitored. So either a "disk activity detected" or a "all drives spun down" and a counter showing how many minutes to sleep execution.

Now the initial start message is outputted with the parameters the sleep plugin was executed. And then silence.

I have one server with a mix of mechanical drives for the array and ssd's for cache pools. Here sleep actually works - even though the plugin is silent in the log.

On my other 2 servers consisting of ssd's exclusively s3 sleep has stopped working completely.

Have anybody else noticed this? Is there a way to check the status of this plugin? In the log startup message it always said "type s3_sleep -q to quit" but that command is not recognized in a cli. It does say "Running" on the plugin page, so that's something but it still does not work and the silence is annoying.

Edited April 6Apr 6 by helgrimm