The error gives a filename which is similar to one of our custom log files but not exact case which makes me think it is some kind of setting. I've tried everything I could think to this point but none worked. The application which was writing to this log is no longer active. I don't see any code or configuration settings which would be referencing this log file. Below is what is written to the error log. The main error is on line 4 and then it spawns some other errors which are either directly or indirectly related to the first error. The service ends in a running state but just returns 500 errors for requests. If you have any suggestions they would be appreciated.
INFO: ColdFusionStartUpServlet: ColdFusion: Starting application services
Nov 17, 2019 6:09:39 PM org.apache.catalina.core.ApplicationContext log
INFO: ColdFusionStartUpServlet: ColdFusion: VM version = 25.202-b08
coldfusion.log.LogService$InvalidLogFileException: The specified log File is invalid: transferequiv_uploads.log.
Copy link to clipboard
That's an odd one indeed, because:
So if I were in your shoes, I'd consider a couple of things:
Let us know what you may find.
Thanks for the response Charlie. I had tried some of your suggestions. I worked with Support and we figured out there were some extra entries in neo-logging.xml that once removed resolved the issue. I'm looking back at the troubleshooting process because I didn't find that XML file when searching for references to the erroneous filename.