During debugging of file rolling (self-rotating logs) we’ve stumbled upon a bug in the logging gem. In multithreaded environment, it does not work correctly. I fixed but it might take some time to get it.
For this reason I will go ahead and turn off this in smart proxy and dynflow, the capability will be still present and if user wants she can configure this via settings but our deployments will continue to rely on logrotate with SIGUSR1 for reopening files.