Logging problem

in the lucee-stout log file, I get a strange error. (See below) Not sure how to fix this but as I was reading the pages it links to it might solve another problem I have…
I get massive log files - to the point of it being a denial of service - when robots hit my website trying random nonexistent pages. I am on a VPS with limited hard drive space and the log files were over 100 gigs.
So do i need to fix this error? How? And how do I turn off the verbose error reporting - I do not need the entire dump each time. My administrator limits the size of the log files but apparently not the lucee-stout file. Today’s log file alone is 4.5 gigs.
Lucee 5.2.9.31
Windows Server 2012 R2 (6.3) 64bit
Java: 1.8.0_112 (Oracle Corporation) 64bit

===========================================================
.MissingIncludeException: Page /rulog4j:WARN No stdout.log file, appenders could be found for logger (org.apache.http.client.protocol.RequestAddCookies).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See Apache log4j 1.2 - Frequently Asked Technical Questions for more info.
log4j:WARN No appenders could be found for logger (org.apache.http.client.protocol.RequestAddCookies).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See Apache log4j 1.2 - Frequently Asked Technical Questions for more info.

please vote for this issue

404 lucee-stderr log entries don’t need a verbose stacktrace
https://luceeserver.atlassian.net/browse/LDEV-1436

(and can somebody with jira admin rights change the status from rejected?)

Maybe I have the 404 page and redirect from http to https settings wrong. What is the correct way to force someone to use https?
Currently, in the application.cfm, I redirect to the https version using cflocate and use status code 301 - permanent move.
For a page not found error, I use custom page not found page and return code 404 - Not Found via a cfheader

Just to let everyone know - the instructions floating around for the log4J fix link to the wrong versions of files. Destroyed my setup and had to reinstall from backups.