What is the suggested method to deal with the vortex.log and monitor.log files growing endlessly. Is there a process that I can turn on in order to rename the files when they get to another size, or do I have to write my own?
Lately, I have been experiencing some wierdness with my search web servers. IIS will stop unexpectedly. I noticed that my vortex log file is huge (1.5 GB), and I wonder if maybe an error is happening, vortex is trying to write to the log file, but takes a long time doing so because the file is so big, and crashes IIS. Do you think this is possible / have you ever heard of anything like this?
Log rotation is currently up to the site administrator. There's no automatic rotation.
A large log file shouldn't take any longer to write to since it's just appending on the end. Nothing texis can do should be able to crash the webserver software.
In general though I would suggest looking at the vortex log to see what it's complaining about.
I have similar issue with vortex.log. Overtime it has grown to over 4GB and is causing the server to run low of space. We plan to delete and create an empty log file on a scheduled basis. Is this possible to setup withour affecting anything? Are there any process that need to be stopped prior to executing this delete/create procedure?
Yes, you can rotate it harmlessly. Make sure the file you create has the right ownership and perms. I'd just rename the file and let vortex recreate it itself.
If you're using vhttpd you should stop and restart that after rotating the log.
