Agh, my bad. I missed that in your first note you were using Apache rather than IIS (you made it clear: it's just that on my phone's small interface, I couldn't see that indication in the title and first paragraph as I was reading the rest of your initial note.)
Then again, you have now shared with us your properties file...and that's one that the CF wsconfig tool would create for in fact an IIS web server connection, rather than an Apache one (even Apache on Windows). Let's take things step by step.
1) What is the name of that file whose properties you're showing? Is it indeed iapi_redirect.properties? If so, that would again be the file that the wsconfig tool would setup for use with IIS. Are you saying that is in the same folder as the mod_jk.log you were initially referring to? that would seem odd.
(To be clear, for the sake of others who may have read my first reply, the name of the log file would indeed be mod_jk.log for an Apache connector rather than isapi_redirect.log for an IIS connector.)
2) The file that the wsconfig tool would create for such properties for an Apache connector would instead be mod_jk_vhost.conf. Do you have that file in this folder? It sure seems you should, if this is the folder that has the large mod_jk.log file.
3) If you do not have both in one folder, that will be odd. Note how the folder you're looking in (within CF's config/wsconfig folder) has a number for its name. Do you have more than one such numbered folder in config/wsconfig? If so, look at the others. Maybe one of them has the mod_jk_vhost.conf...and though it should NOT, maybe that file points to THIS folder where you are finding the large mod_jk.log.
4) Putting all this aside for a moment, as far as the huge log is concerned, if you stop Apache, you will be able to rename the large mod_jk.log. That way, you buy yourself time both to make it easier to work with and to work on keeping it from growing huge again.
5) As for the debug lines, that is indeed controlled by a setting similar to the log_level line I referred to originally. Instead, it's called JkLogLevel, and again its value would be "debug" for the config file that's causing creation of this large log you found. You'd want to change it to "info" (without the quotes)...once you figure out which mod_jk_vhost.conf file is controlling its creation.
6) As for finding what folder that should be, besides poking around in the config/wsconfig folder, it may well be in your apache conf folder, as in "C:/Apache24/conf/mod_jk.conf".
7) Perhaps better, you should let Apache itself tell you how it's configured for your sites and their respective config files. In the apache bin folder, you can use the -S -M args on the httpd.exe, to see that. If you have Apache installed in C:\Apache24\bin, this would do that:
C:\Apache24\bin\httpd.exe -t -D DUMP_VHOSTS
Better still, while that will list what httpd conf files are used for what sites you have, you can also ask it to tell you what files those conf files point to, as in:
C:\Apache24\bin\httpd.exe -t -D DUMP_INCLUDES
Let us know how you sort things out. Or if you may want consulting help, I can help (via remote screenshare). More at carehart.org/consulting. But if you ask follow up questions here, I (and others) are happy to help, of course.
/Charlie (troubleshooter, carehart.org)
9
Replies
AdChoices
